[jboss-dev] pom.xml housekeeping

[Dimitris Andreadis]

Typically you can, by having an external 'parent' project defining the versions. We tried 
that initially but reverted to the more standard 'each project controls its own versions':

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139754#4139754

Sacha Labourey wrote:
> could we use instead "generic" tags - or aliases - (like ejb-parent => 
> LATEST-OFFICIAL-EJB) and "move" that tag so that all modules that depend 
> on that tag automagically refer to the good tag once we move it?
> 
> On 04/23/2008 10:50 AM, Dimitris Andreadis wrote:
>> While there, ejb-parent points to
>>
>> AOP 2.0.0.CR7
>> MC 2.0.0.Beta9
>>
>> AS component-matrix points to
>>
>> AOP 2.0.0.CR8
>> MC 2.0.0.Beta13
>>
>> When are those going to move? Are the missing updates for EJB3 tracked 
>> somewhere?
>>
>> I know AOP was rolledback because of a problem, what about MC?
>>
>> Dimitris Andreadis wrote:
>>> My obligatory pastime those days is to reduce the entropy of the 
>>> jboss universe by messing up with people's poms.
>>>
>>> I just spotted that the various ejb3 subprojects used different 
>>> snapshots of their own ejb3-parent pom! Some used 0.13-1-SNAPSHOT, 
>>> others 0.13-3-SNAPSHOT, so I moved them to the latest.
>>>
>>> Sure maven sucks, but can you also do your own housekeeping, please?
>>>
>>> /D
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development