activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: ActiveMQ svn directory organization question
Date Thu, 27 Jul 2006 15:01:53 GMT
Good question. Given how interdependent many of the modules are, its
failrly unlikely we'd want to branch only one of the modules I guess.
Its certainly much simpler to branch the entire maven build in one go,
then you can for example change the super-pom in the branch.


On 7/27/06, Sanjiv Jivan <sanjiv.jivan@gmail.com> wrote:
> Off topic, but in looking at the Active MQ SVN directory structure with the
> multiple modules and all, I was wondering what the pro's on con's are in
> 1) using one top level "trunk" and "branch" directory with all the modules
> going under "trunk" versus
> 2) having each module have its own  "trunk" and "branck" sub directory as
> described here :
> http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.branchmerge.using
>
> What criteria did Active MQ use to go with approach 1). Was it because the
> maven directory layout is an issue with approach 2?
>
> Thanks,
> Sanjiv
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message