[JBoss-dev] common project structure changes

[Heiko Braun]

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 at lists.jboss.org
[mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Dimitris
Andreadis
Sent: Thursday, August 24, 2006 12:26 PM
To: JBoss.org development list
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 at lists.jboss.org
[mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Ruel
Loehr
Sent: Tuesday, August 15, 2006 9:13 PM
To: JBoss.org development list
Subject: [JBoss-dev] common project structure changes

	We've been working on the file structure of the jboss common
project and are now ready to merge the changes back into the trunk.
The changes are substantial, so I want to make sure everyone is clear
before I commit them in.

	 

	Currently the common project consists of 1 source tree which
creates 4 artifacts:

	 

	Jboss-archive-browsing.jar

	Jboss-common.jar

	Jboss-common-client.jar

	Namespace.jar

	 

	The project has been refactored in a branch
(https://svn.jboss.org/repos/common/branches/logging_refactoring/ )

	 

	It has been broken into 5 projects

	 

	Common-core

	Common-logging-jdk

	Common-logging-log4j

	Common-logging-spi

	Jbossxb

	 

	Each of these projects builds a single jar.   A maven build has
been setup for each of these projects.  The idea behind these changes is
to cleanly separate each project into its own entity.   

	 

	After these changes are committed, binaries will be published to
the repository for all projects and then they will be integrated to
jbossAS/trunk.

	 

	These changes apply only to the trunk version, not the 4.0
branch.  

	 

	Thoughts or concerns?

	 

	 

	 

	 

	 

	 

	 

	 

	Ruel Loehr

	JBoss QA

	 

	 

	 

	--

	 

	 

	--
	No virus found in this outgoing message.
	Checked by AVG Free Edition.
	Version: 7.1.405 / Virus Database: 268.10.10/419 - Release Date:
8/15/2006

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20060824/ac566ba7/attachment.html