I don't know why it's set up that way either, and I don't think other projects are set up that way, but if you remove those settings and it doesn't work when it comes time for a release, you can always put them back.
Christian,
you asked for a Spec POM Cleanup, in particular for removing the assembly. I did so today, but there is a question open:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.2</version>
<configuration>
<mavenExecutorId>forked-path</mavenExecutorId>
<useReleaseProfile>false</useReleaseProfile>
<arguments>${release.arguments}</arguments>
</configuration>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9.4</version>
</dependency>
</dependencies>
</plugin>
I don't know why the original author thought he has to use these particular settings. Typically when I am using the Maven Release Plugin, I do not use such settings. As we cannot simply try it out without actually releasing the spec, what shall we do? Just throw it away, in the hope it still works? Just keeping it, possibly without any need?
-Markus
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
