The spec documents and the API classes are often revised at
different times for different reasons. There's no reason to require
updating the version number of one when the other one is updated.
Plus, the version numbers of the spec documents should not use micro
version numbers. If a spec document is updated outside of a
specification release, e.g., to fix errata, it should be given a new
"rev level". For example, it might have versions "2.0", "2.0 rev
a", "2.0 rev b", "2.1", etc.
You can use the Maven release plugin starting at the parent pom as
long as the spec document Maven project is not a sub-module of the
parent Maven project.
David Blevins wrote on 7/24/19 3:32 PM:
Correct that we don’t want to publish the EFSL
spec to Maven Central. Using CDI as an example, they would
creat two versions of their spec:one with the ASL license that
they can push to Maven Central; another version with the JCP
license they distribute only via the JCP website. Spec
projects can definitely do that.
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.
There should a few ways around it and still use
the maven release plugin. Theoretically one could specificity
the ‘distributionManagement’ differently in the spec pom.xml. I
tried that but couldn’t quite get it to work. I tried the ‘cd’
approach and that worked, but didn’t notice the “snapshot”
version in the tag till after.
On cell now so don’t have diffs, build output or
links handy.
Hi,
Ok, so all we need to do is make sure we only
mvn deploy the api jar then I suppose - thanks
for the info!
Yes, that's what all the projects I'm working on
do. CD into the API folder, then deploy that one.
Kind regards,
Arjan
_______________________________________________
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
--
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
|
