RE: [JBoss-dev] eclipse workspace/svn issue
by Scott M Stark
What is really needed is an ability to perform an svn op on a working
set(I think that is the correct eclipse notion) as I do often checkout
common, microcontainer, tomcat, etc source if I need to work with the
source for a binary.
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Adrian Brock
> Sent: Saturday, August 05, 2006 7:07 AM
> To: JBoss.org development list
> Subject: Re: [JBoss-dev] eclipse workspace/svn issue
>
> I think I'm going temporarily fork subclipse so I can fix
> some of its scalability issues and understand how it works.
>
> Once I have something I can use, I'll contribute the patches back.
>
> It is slow, resource hungry and buggy for me. :-(
>
19 years, 8 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
Are we ready to move container to its own svn root and update
microcontainer, aop and jbossas to refer to a separate container binary?
Also, container is a rather vague name. What is this project really
about?
19 years, 8 months
eclipse workspace/svn issue
by Scott M Stark
One issue with the requirement to checkout each project making up
jbossas is that you cannot apply workspace wide ops like switching
between branches. Maybe this is a limitation of the svn client, but I
cannot select all projects in a workspace and then switch them to a new
branch. Is there a way to structure/configure a workspace such that this
can be done?
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
VP Architecture & Technology
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 8 months