[JBoss-dev] Microcontainer/Breakout Strategy

Scott M Stark scott.stark at jboss.com
Thu Aug 3 00:59:45 EDT 2006


All I have done so far is copy the aop-mc-int into the
microcontainer/trunk. Further work can wait for you and Kabir to get in
synch.

-----Original Message-----
From: jboss-development-bounces at lists.jboss.org
[mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Adrian
Brock
Sent: Wednesday, August 02, 2006 9:39 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy

Can we hold on changes for a couple of days.

It is nearly 24 hours since I last had an environment that I could
use to do any work. ;-)

Everytime I resynch and build, I find something different is broken.

On Wed, 2006-08-02 at 23:18 -0500, Scott M Stark wrote:
> > It should be in the microcontainer build.
> Ok
> 
> > > I can move the container project into a separate root under
> > > https://svn.jboss.org/repos/jbossas/projects/
> >
> > Ok, but I think this should really be a seperate build.
> > When AOP has a standalone build, it will need a binary of this
> project.
> > MC will also use the binary.
> 
> Everything under jbossas/projects should be a separate build that
> produces a binary.
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-development at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development




More information about the jboss-development mailing list