[jbosstools-dev] Changes to JBoss Tools' parent pom affecting all JBT/JBDS Core & SOA Tooling builds -- please read!

[Mickael Istria]

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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120423/8f0f09c0/attachment.html