Skip to content

Conversation

@khmarbaise
Copy link
Contributor

  • Moved life cycle binding to plugins instead of pluginManagement.
  • Removed other plugins which are bound by default via life cycle.

 - Moved life cycle binding to plugins instead of pluginManagement.
 - Removed other plugins which are bound by default via life cycle.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
Copy link
Owner

Choose a reason for hiding this comment

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

I've always put this in the pluginManagement. Why should it be here out of curiosity?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Technically it is working in pluginManagement, but I recommend to separate the configuration/version definition of plugins... in dependencyManagement... and in build do the bindings to a life cycle....

Copy link
Owner

Choose a reason for hiding this comment

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

For me, having it in pluginManagement is more, well, manageable :D I prefer to leave it there.

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