Note that I did get a Jenkins Maven project job running to produce a cdi-api staging release using a multi-module setup by including a configuration of the maven-deploy-plugin like the following in both the root and spec submodule pom:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <version>3.0.0-M1</version> <configuration> <skip>true</skip> </configuration> </plugin>
Hi, In terms of the “just ‘cd’ into the api dir”, that creates the problem I pointed out where the maven release plugin then does not update the version number of the parent and spec pom.xml files.
You're right. Dmitry's scripts already did take this partially into consideration. They don't just cd into the API dir and be done with it, but they cd in and out if that dir all the time, but not yet in a way to account for the new /api and /spec folders. That would need to be fixed. Good catch!
Kind regards, Arjan
--
Sent from Gmail Mobile _______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ee4j-pmc mailing listee4j-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/ee4j-pmc
|