-
Notifications
You must be signed in to change notification settings - Fork 60
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
Use plugin parent POM #98
Conversation
|
||
<name>Groovy Sandbox</name> | ||
<description>Executes untrusted Groovy script safely</description> | ||
|
||
<properties> | ||
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Part of the parent POM as of jenkinsci/pom#257.
<plugin> | ||
<artifactId>maven-release-plugin</artifactId> | ||
<configuration> | ||
<releaseProfiles>release</releaseProfiles> | ||
</configuration> | ||
</plugin> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parent POM uses a profile named jenkins-release
as of jenkinsci/pom#296.
@@ -94,18 +89,12 @@ | |||
|
|||
<profiles> | |||
<profile> | |||
<id>release</id> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parent POM uses a profile named jenkins-release
as of jenkinsci/pom#296.
<execution> | ||
<id>attach-sources</id> | ||
<goals> | ||
<goal>jar-no-fork</goal> | ||
</goals> | ||
</execution> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parent POM's jenkins-release
profile includes this logic as of jenkinsci/pom#296. However, the logic to attach the test sources is still necessary. I tested this by running mvn clean verify -Pjenkins-release
and verified that the sources and test sources still got generated.
<plugin> | ||
<artifactId>maven-javadoc-plugin</artifactId> | ||
<executions> | ||
<execution> | ||
<id>attach-javadocs</id> | ||
<goals> | ||
<goal>jar</goal> | ||
</goals> | ||
</execution> | ||
</executions> | ||
</plugin> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parent POM's jenkins-release
profile includes this logic as of jenkinsci/pom#296. I tested this by running mvn clean verify -Pjenkins-release
and verified that the Javadoc still got generated.
Per dwnusbaum/groovy-cps#1 (comment) we actually want to use the plugin parent POM here. |
Updates the parent POM to the latest version as well as adding a
CODEOWNERS
file and updating the.gitignore
file to match the latest archetype. See self-review for details.CC @dwnusbaum