1:01 p.m.
Recently, we moved the parent pom from version 0.0.4-SNAPSHOT to
3.3.0.Beta3-SNAPSHOT in trunk.
When we branch next week for the Beta3 code freeze, this version will
become the parent pom in the branch, and trunk will move to version
3.3.0.CR1-SNAPSHOT (then later to 3.3.0.GA-SNAPHOT, etc.)
Anyone who depends on the parent pom 0.0.4 can continue to do so (as
it's now in Nexus) but should sooner or later move up to use the correct
3.3.0.x version of the parent pom before the 0.0.4 snapshot disappears
from Nexus.
Details on this change: https://issues.jboss.org/browse/JBIDE-11157
If I've forgotten to cc: a SOA Tools project lead, please fwd this on.
If there's a soa-tooling mailing list you'd like me to cc: in future for
these sorts of changes, let me know.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4:19 a.m.
Thanks Nick for notifying.
Anyone who depends on the parent pom 0.0.4 can continue to do so (as
it's now in Nexus) but should sooner or later move up to use the
correct 3.3.0.x version of the parent pom before the 0.0.4 snapshot
disappears from Nexus.
By that way, you should move from 0.0.4-SNAPSHOT to 3.3.0.Beta3-SNAPSHOT
*now* because:
* It requires a few seconds, not more. It will take more time to write a
TODO on a post-it than to actually do it
* If you don't do it, you don't leverage new "transversal features of
build", such as the come-back of Jacoco reports.
The goal is to ensure a better isolation of build streams, and then make
builds even more reliable.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4:53 a.m.
For more concrete stuff, here is what you should read in your root pom.xml
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>3.3.0.Beta3-SNAPSHOT</version>
<relativePath>../build/parent/pom.xml</relativePath>
</parent>
This will poll the parent from JBoss Nexus. We publish the parent to
Nexus in a CI job. You should also include this to ensure your build can
find it:
<repositories>
<!-- To resolve parent artifact -->
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</repository>
<repository>
<id>jboss-snapshots-repository</id>
<name>JBoss Snapshots Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/snapshots/...
</repository>
</repositories>
As discussed on other threads, this repositories thing may be subject to
change later, but it's the easier way for your build to work fine and
leverage the new stuff we set up for you. So please enjoy it ;)
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
6:42 a.m.
Good change - makes it much easier to see which modules are actually kept uptodate.
What actually happens if you build everything from root and multiple parents are used ?
how does maven resolve that some is using 3.3.0* and others 0.0.4-?
For more concrete stuff, here is what you should read in your root
pom.xml
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>3.3.0.Beta3-SNAPSHOT</version>
<relativePath>../build/parent/pom.xml</relativePath>
</parent>
This will poll the parent from JBoss Nexus. We publish the parent to Nexus in a CI job.
You should also include this to ensure your build can find it:
Which areas was this changed for ? Just the build setup or did you change the modules ?
for the repositories setup: Just put this in settings.xml like needed for many other
jboss.org projects: https://community.jboss.org/wiki/MavenGettingStarted-Developers
/max
7:55 a.m.
On 04/23/2012 01:42 PM, Max Rydahl Andersen wrote:
What actually happens if you build everything from root and multiple
parents are used ? how does maven resolve that some is using 3.3.0* and others 0.0.4-?
I need to give it a try, but I think there is no "smart" dependency
resolution for the parent. Those specifying 3.3.0* will receive 3.3.0*
as parent; those specifying 0.0.4-SNAPSHOT will get 0.0.4-SNAPSHOT.
> For more concrete stuff, here is what you should read in your
root pom.xml
>
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>3.3.0.Beta3-SNAPSHOT</version>
> <relativePath>../build/parent/pom.xml</relativePath>
> </parent>
>
> This will poll the parent from JBoss Nexus. We publish the parent to Nexus in a CI
job. You should also include this to ensure your build can find it:
Which areas was this changed for ? Just the build setup or did you change the modules ?
The root pom.xml of each module has /parent/version changed.
for the repositories setup: Just put this in settings.xml like needed
for many other jboss.org projects:
https://community.jboss.org/wiki/MavenGettingStarted-Developers
Ok, I just put
https://issues.jboss.org/browse/JBIDE-11615 in my TODO-list.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4649
days inactive
4653
days old
jbosstools-dev@lists.jboss.org
4 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt