On Wed, Apr 04, 2001 at 04:30:54PM -0700, Scott M Stark wrote:
> I added a JBoss_2_2_0_Final to the jbosssx module codebase that went into
> the JBossSX jars(jbosss-client.jar, jboss-jaas.jar, jbosssx.jar) included with
> the JBoss_2_2_0_Final release. This allows the source for these to be obtained
> and patched if necessary.
>
> I think we need to do the same for the other modules for subsequent releases.
The approach I favour is to version each module independently. For example,
JBoss currently includes jbosscx-0.2. You can go to the JBossCX module and
check out version 0.2 (because I tagged it) if you need that source code.
The advantage of doing it this way is that the core is kept decoupled from
the modules. There are some disadvantages, e.g.
- Updating the module means removing and readding the jar in the core, which
means you need to remember to remove the old jar from your dist directory.
This could perhaps be solved using a more sophisticated install procedure
that copied jbossfoo-x.y.jar to jboss-foo in dist.
- It is not as easy to go the other way, i.e. figure out which version of
JBoss a particular version of the module depends on. This could be
addressed by versioning jboss-client.jar and jboss-util.jar and whatever
else is shared.
- It probably makes it more difficult to issue a single command to grab all
of the source (core and modules) for a specified version. This is the
worst one, I think.
Toby.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
