I don't know about the jbossas project, but for e.g. Hibernate or JBossIDE
I simply have it chekked out from the root (without using eclipse) e.g.
for HibernateExt I checkout
https://hibernate.labs.jboss.com/repos/hibernate/trunk/HibernateExt
and then import them into eclipse as individual projects.
/max
So for that, I think we need to change the current means of checking
out
jbossas because I also tried that and it did not work. When I tried to
do a commit of two project folders from the explorer, tortoiseSVN
complained that there was no working copy. The container folder was the
eclipse workspace, and was not something checked out from svn. However,
from within the same explorer I could commit each project folder, so I
did not understand why both could not be committed.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Max
Rydahl Andersen
Sent: Saturday, August 05, 2006 10:03 AM
To:
JBoss.org development list
Subject: Re: [JBoss-dev] eclipse workspace/svn issue
It's a known limitation of eclipse not being able (in some cases)
to perform multi-project operations.
What I do for these things is that i ensure that I have it chekked
out on disk in a way so I can use command line or prefereably
tortoiseSVN
for these things.
/max
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss Inc
max.andersen(a)jboss.com