[Jboss-dev-forums] [Design of JBoss Build System] - Requirements - Top level build - versioning

[<ad...@jb...>]

This gets a bit complicated because there are lots of different versions,
I'll try to enumerate them:

1) The top level build version e.g. 4.0.2
2) The top level build branch e.g. JBoss4
3) The cvs version e.g. JBoss_4_0_2
4) The cvs branch e.g. Branch_4_0
5) The component version (if it is standalone or thirdparty)
6) The component specification version e.g. JMS1.1
7) Patch versions e.g. 4.0.2-JBAS1234
8) Different builds for different JVMs 1.3/1.4/5

When defining versions, the "head" description wants to be unspecific as possible
where the top level is a federation of direct components like JBossAS and naming/transaction/jbossmq

In other cases, the versions need to be specific. i.e. the JBossAS head branch uses log4j-1.2.8 until we say otherwise.

Then there are the issues of compatiblity. e.g.
JBossAS needs log4j-1.2.8 or does it need log4j-1.2.8+ or
log4j-1.2.8-log4j-1.2.11
or maybe JBossAS 4.0.2 needs log4j-1.2.8+ but not log4j-1.2.10
etc.

These issues fall into a number of different categories:
1) Who is reponsible for the versions used
a) the top level buld
b) the component
c) something else
2) How are conflicts resolved
a) by changing the top level build
b) by changing the offending component
c) other
3) How does this version information propogate
a) in the build scripts
b) in the artifacts
4) Who is responsible for verifying the information and how are problems signalled
to the user
a) the top level build
b) cruise control
c) testing

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878084#3878084

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878084