Thomas created 1.0.2 and 1.0.1.
Unfortunately he’s on vacation this
week and I don’t know how these version have been produced.
He will be back on Monday. Maybe you could
wait until then to discuss it with him.
There have been reasons for this that are
unknown to me and I want to avoid breaking jbossws/branch_4_0,
because we are in the middle of the 1.0.3
release.
I think it doesn’t matter if it goes
back into the application server module,
but at least it should be separated from
xb.
/Heiko
From: jboss-development-bounces@lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of
Sent: Thursday, August 24, 2006
12:26 PM
To:
Subject: RE: [JBoss-dev] common
project structure changes
I think we need to clean-up the
status of the common project, a bit.
We have in repository a common project
with versions, none of which is tracked in JIRA (http://jira.jboss.com/jira/browse/JBCOMMON)
snapshot-Branch_4_0
snapshot
1.0.2
1.0.1
- Out of which trunck/branch were the
versions 1.0.1, 1.0.2 produced?
- I've renamed the common Branch_4_0 to
Branch_1_0 as we originally discussed. From this we'll produce jboss-common
1.0.0.CR1 (for jboss 4.0.5.CR1), so the repository versions 1.0.1, 1.0.2 should
not really be there. I need to update the jboss project and repository
accordingly.
(I would even argue we could keep the
common stuff of Branch_4_0 inside the application server module, if nobody else
is using it?)
- The refactored common version that will
go to jboss head should be 2.0.0.x, right?
- I guess we don't need in the common
module all those branches & tags carried over from jboss? The history is
stored in the jboss module anyway.
- With the latest break-up, jboss xb could
really be on its own.
From:
jboss-development-bounces@lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Ruel Loehr
Sent: Tuesday, August 15, 2006
9:13 PM
To:
Subject: [JBoss-dev] common
project structure changes