8:15 p.m.
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
3:52 a.m.
New subject: [JBoss-dev] eclipse workspace/svn issue
So, explain me, how did you get there? :)
I am trying to make "any" solution work but I think I am doing it wrong.
What do you do first? you create an empty "jboss-head" project in
Eclipse or do you first start by installing subclipse and do a CO?
Then, if you do a CO, how do you co project "jboss-head" from trunk?
subclipse seems only able to get HEAD from Trunk or a specific branch.
Then, if I do that, it doesn't seem able to find the Eclipse project
definition files that are part of the checkout.
And don't tell me to RTFM, there is no detailed information on how to do
this from Eclipse ;)
Thanks. Cheers,
sacha
Scott M Stark wrote:
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
9:18 a.m.
New subject: [JBoss-dev] eclipse workspace/svn issue
I never checkout big multi projects from with in eclipse (or any IDE for
that matter ;)
for eclipse I simply checkout the complete project (or projects) into its
"natural"
structure as delivered by cvs or svn commandline/tortoise.
Then in my IDE I go and tell it to create a project or use the project
info found at those locations.
I eclipse if the .project etc. files are already there it is just a matter
of choosing
"File/Import/Existing projects into workspace" and then point it to the
root directory
of where all the projects are and eclipse will find them all for you and
then press ok.
/max
So, explain me, how did you get there? :)
I am trying to make "any" solution work but I think I am doing it wrong.
What do you do first? you create an empty "jboss-head" project in
Eclipse or do you first start by installing subclipse and do a CO?
Then, if you do a CO, how do you co project "jboss-head" from trunk?
subclipse seems only able to get HEAD from Trunk or a specific branch.
Then, if I do that, it doesn't seem able to find the Eclipse project
definition files that are part of the checkout.
And don't tell me to RTFM, there is no detailed information on how to do
this from Eclipse ;)
Thanks. Cheers,
sacha
Scott M Stark wrote:
> 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
>
>
_______________________________________________
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
6:07 a.m.
New subject: [JBoss-dev] eclipse workspace/svn issue
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
7188
days inactive
7188
days old
jboss-development@lists.jboss.org
3 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Sacha Labourey -
Scott M Stark