Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PLANNER-1299: Add a root (aggregate) POM #88

Merged
merged 2 commits into from
Apr 10, 2019

Conversation

yurloc
Copy link
Member

@yurloc yurloc commented Apr 6, 2019

No description provided.

@yurloc yurloc requested a review from rsynek April 8, 2019 07:25
<goal>install-node-and-npm</goal>
</goals>
<configuration>
<nodeVersion>v8.12.0</nodeVersion>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These versions could be defined in properties to simplify maintenance. It's also likely that in the future the build will be connected to kie-parent, which might define the versions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree. Using version properties makes maintenance simpler when multiple artifacts share the same version. Or when a value is repeated in multiple plugin configurations. This is not the case.

Ad kie-parent connection. Maybe yes, maybe not. When we start using it we will reuse versions from there. Defining our own properties now won't make the transition easier.

<plugins>
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed some interesting output messages from this plugin:
warnings https://gist.github.com/rsynek/ff9ffc3c2b4a06a89c1bd017c742099a
warnings about deprecations shown as errors https://gist.github.com/rsynek/a529c7d2616e45d27dd4cd5c0f574a4d
information about successfully running all tests presented as an error: https://gist.github.com/rsynek/b1e5baae33b131d20b4d4baa7ba9ebe1

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, warnings are true npm warnings that can be observed even when running npm install from command line. Unrelated to this PR.

Errors are related to this PR because it's a combination of Jest using stderr for output and Maven, displaying stderr output as [ERROR]. Maven's behavior is more or less correct, at least unsurprising. Jest's behavior is debatable. I'd classify it as a bug as multiple people are running into it. Until they fix it, there's nothing we can do about it.

Deprecation warnings displayed as errors - similar to Jest test report. They're valid warnings unrelated to this PR, but displayed as errors thanks to Maven's translation of stderr.

@yurloc yurloc force-pushed the root-maven-build branch from 51cfcc1 to e552bb3 Compare April 8, 2019 12:36
@yurloc
Copy link
Member Author

yurloc commented Apr 10, 2019

Ready for evaluation. Merging.

@yurloc yurloc merged commit 29caf92 into kiegroup:master Apr 10, 2019
@yurloc yurloc deleted the root-maven-build branch April 10, 2019 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants