pom.xml housekeeping

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-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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-developmentlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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-developmentlists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
>> _______________________________________________
>> jboss-development mailing list
>> jboss-developmentlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

but shouldn't we reconsider this now that we have cleaned
the build? 
Furthermore, we could "externalize" this
information in an external 
project (as describe in the post), but I guess projects that
are really 
allergic to this approach could still rely on their
"custom" dependency 
set (and take the risk of being publicly bashed in case they
don't 
maintain their version up-to-date).

Is it possible to write a scripts that tests these things
(i.e. gather 
all dependency information for the complete build, flatten
that 
information and look for multiple
"PROJECT-NAME_X_Y_Z" tag that have the 
same PROJECT_NAME part but not the same X_Y_Z part? could
this be part 
of the build process as a testsuite or anyhting like that?

On 04/23/2008 11:13 AM, Dimitris Andreadis wrote:
> 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-developmentlists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
>>>
_______________________________________________
>>> jboss-development mailing list
>>> jboss-developmentlists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
>> _______________________________________________
>> jboss-development mailing list
>> jboss-developmentlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Which is wrong, because they should point to the latest
parent with 
which they're compatible. Now you'll probably get some nice
incompatible 
snapshots all over the place.

Likewise for any dependency on any other ejb3 component. It
should not 
point to a snapshot, but the latest stable.

Carlo
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Carlo de Wolf wrote:
> 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
> 
> Which is wrong, because they should point to the latest
parent with 
> which they're compatible. Now you'll probably get some
nice incompatible 
> snapshots all over the place.

The parent is supposed to point to a set of component
versions that must be shared by the 
subcomponents.

What's the point of using multiple versions of the same
parent among peer subcomponents? The 
subcomponents will receive different version dependencies,
which is a recipe for disaster.

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

On Wed, 2008-04-23 at 10:57 +0200, 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?

No because that breaks version control/reproducability.
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

On Wed, 23 Apr 2008 12:08:51 +0200, Carlo de Wolf
<cdewolfredhat.com> wrote:

> Sacha Labourey wrote:
>> but shouldn't we reconsider this now that we have
cleaned the build?
>> Furthermore, we could "externalize" this
information in an external
>> project (as describe in the post), but I guess
projects that are really
>> allergic to this approach could still rely on their
"custom" dependency
>> set (and take the risk of being publicly bashed in
case they don't
>> maintain their version up-to-date).
>>
>> Is it possible to write a scripts that tests these
things (i.e. gather
>> all dependency information for the complete build,
flatten that
>> information and look for multiple
"PROJECT-NAME_X_Y_Z" tag that have the
>> same PROJECT_NAME part but not the same X_Y_Z part?
could this be part
>> of the build process as a testsuite or anyhting
like that?
>
> That's the job Maven should really do for us, but
doesn't. See the 'Why
> Maven sucks (part 1)' thread.

did you look at the enforcer plugin which I referenced in
that thread ?

/max
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

> 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?
What was the problem?

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment