activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bish, Tim" <Tim.B...@Sensis.com>
Subject RE: SVN Repository Reorganization
Date Wed, 06 Sep 2006 14:47:17 GMT
> 
> 
> +1 for reorganizing
> +1 for putting all the C++ clients together in their own trunk
> I would also suggest getting rid of the CMS project altogether - this
has
> been replaced by activemq-cpp

Yeah, I've got a Jira issue to do this, just waiting to get SVN access.

> 
> 
> tabish121 wrote:
> >
> >
> > +1 for reorg, getting a bit cluttered now.
> >
> > I don't know that I'd really like to shove all the c/c++ clients
into
> one
> > branch, some of them don't have much if any activity, so I don't
know if
> > I'd like to drag all the extra baggage along for each release.  Then
> > again, having them all in one place would make it easy for someone
to
> see
> > all the available options and try them out to see which one works
best
> for
> > them.
> >
> >
> > Hiram Chirino wrote:
> >>
> >> Perhaps we should put all the c/c++ stuff together???  I think that
> >> would make it simpler to merge implementations and share ideas.
> >>
> >> On 9/5/06, Hiram Chirino <hiram@hiramchirino.com> wrote:
> >>> Hi Everybody,
> >>>
> >>> The ActiveMQ project has been growing tremendously and our source
tree
> >>> now has many modules that are at different stages of development.
> >>> Furthermore, we require multiple build systems and platforms to
build
> >>> all our supported native clients.  I think we are getting to the
point
> >>> where we need reorganize the svn repository a little so that when
we
> >>> do a main ActiveMQ release, our src distro just includes the
things
> >>> that are being built / tested in the main ActiveMQ build.
> >>>
> >>> So.. the reorg would look something like:
> >>>
> >>> /incubator/activemq/trunk/sandbox - > /incubator/activemq/sandbox
> >>> /incubator/activemq/trunk/activemq-dotnet - >
> >>> /incubator/activemq/activemq-dotnet/trunk
> >>> /incubator/activemq/trunk/activemq-cpp - >
> >>> /incubator/activemq/activemq-cpp/trunk
> >>> /incubator/activemq/trunk/cms - > /incubator/activemq/cms/trunk
> >>> /incubator/activemq/trunk/openwire-c - >
> >>> /incubator/activemq/openwire-c/trunk
> >>> /incubator/activemq/trunk/openwire-cpp - >
> >>> /incubator/activemq/openwire-cpp/trunk
> >>> /incubator/activemq/trunk/amazon - >
/incubator/activemq/amazon/trunk
> >>> /incubator/activemq/trunk/activeio - >
> >>> /incubator/activemq/activeio/trunk
> >>> /incubator/activemq/trunk/activecluster - >
> >>> /incubator/activemq/activecluster/trunk
> >>> /incubator/activemq/trunk/activemq-jmeter - >
> >>> /incubator/activemq/activemq-jmeter/trunk
> >>> /incubator/activemq/trunk/activemq-tooling/maven-gram-plugin - >
> >>> /incubator/activemq/maven-plugins/trunk/maven-gram-plugin
> >>> /incubator/activemq/trunk/activemq-tooling/maven-bundle-plugin - >
> >>> /incubator/activemq/maven-plugins/trunk/maven-bundle-plugin
> >>> /incubator/activemq/trunk/activemq-tooling/maven-bundle-plugin - >
> >>> /incubator/activemq/maven-plugins/trunk/maven-bundle-plugin
> >>>
> >>> And finally.. to keep a consistent
> >>> /incubator/activemq/${project}/trunk structure...
> >>> /incubator/activemq/trunk -> /incubator/activemq/activemq/trunk
> >>> /incubator/activemq/tags -> /incubator/activemq/activemq/tags
> >>> /incubator/activemq/branches ->
/incubator/activemq/activemq/branches
> >>>
> >>> What do you guys think?  Am i missing anything that should also
get
> >>> moved?  When do you think would be a good time for the re-org?
> >>>
> >>> --
> >>> Regards,
> >>> Hiram
> >>>
> >>> Blog: http://hiramchirino.com
> >>>
> >>
> >>
> >> --
> >> Regards,
> >> Hiram
> >>
> >> Blog: http://hiramchirino.com
> >>
> >>
> >
> >
> 
> --
> View this message in context: http://www.nabble.com/SVN-Repository-
> Reorganization-tf2221183.html#a6172870
> Sent from the ActiveMQ - Dev forum at Nabble.com.


Mime
View raw message