You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Barrie Treloar <ba...@gmail.com> on 2006/08/16 05:20:49 UTC
[m2] eclipse:eclipse and eclipse 3.2 projects within a project support.
With Eclipse 3.2 I was lead to believe you could create projects
within projects, so that I could checkout a maven project that
contains modules and wire that up in Eclipse correctly. Instead of
manually checking out the modules as I did under Eclipse 3.1.
I am able to manually add the project in Eclipse via File -> Import ->
General -> Existing Projects into Workspace and use the module
directoy as the value for "Select root directory".
The project then appears in the "Projects" list for importing.
If I select the project root then there are no projects to choose from.
I thought that the snapshot version of the eclipse:eclipse plugin had
the functionality to do this for me, but it is not working how I
expect. I assume I am doing something wrong. Should mvn
eclipse:eclipse at the project root do what I expect?
Any help appreciated.
Bae
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
m2eclipse & eclipse:eclipse
Posted by Douglas Ferguson <do...@epsiia.com>.
I have a few questsion about m2eclipse:
1) When configuring the external tool how do you specify a profile?
2) What settings.xml will get read? I am not sure that either my maven_install_dir/settings.xml or ~/.m2/settings.xml are getting read.
3) Can someone explain what update source directies does?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
suppo
Posted by Max Cooper <ma...@maxcooper.com>.
Valerio Schiavoni wrote:
> Hello Max,
>
>
> Max Cooper wrote:
>> If you have a structure like this:
>>
>> root
>> |--module1
>> |--module2
>> |--submodule2-1
>>
>
> my structure is a bit simpler, without nested submodules.
Okay, like this:
root
|--module1
|--module2
>
>
> Max Cooper wrote:
>> ... you would have to make sure that you hide/delete/rename the .project
>> file in both the root and module2 directories for the submodule2-1
>> project to show up on the import.
>>
>
> so fortunately this is not my case.
Generally, this still is the case. You MUST hide/delete the .project
file in root so that Eclipse will allow you to add module1 and module2.
It is the same issue, but you only have to worry about one level.
I have verified that the procedure outlined in this email thread works
in Eclipse 3.2, as have others. If it isn't working for you, something
is wrong.
>
>
> Max Cooper wrote:
>> Eclipse does not support hierarchical project structures.
>>
> i thought eclipse 3.2 just introduced this new feature ...
Eclipse 3.2 does not support hierarchical project hierarchies. It was
rumored that 3.2 would have such support before the release, but it does
not.
The procedure in this email thread is just a trick to get Eclipse to
accept having "overlapping" projects. This trick allows a hierarchical
structure of Maven modules to be mapped into a flat structure of Eclipse
projects.
>
>
> Max Cooper wrote:
>> IMO, moving your parent pom to a subdir is a better compromise than
>> having all of your files show up two or more times in Eclipse.
>>
> of course, but this would break a well established maven convention, which
> i'd like to avoid..
Moving the parent to a subdir is documented on the Maven site, and many
people are using this technique successfully.
The Eclipse trick in this thread is not as clean, IMO.
-Max
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
Posted by Douglas Ferguson <do...@epsiia.com>.
I also am using hierarchial projects. I got 3 levels deep and it works fine. It only creates project files for the leaf nodes. The parent poms (packaging=pom) will not get project files.
I am having 1 problem with eclipse:eclipse. I have a parent pom that isn't intended to be portable. It uses variables that prevent it from validating, however, I need it so my 100s of sub poms don't have to define the same stuff over and over. Anyway, eclipse:eclipse is barfing on some paths, just curious if there is a way to get it to be "less strict" or something.
-----Original Message-----
From: Barrie Treloar [mailto:baerrach@gmail.com]
Sent: Friday, August 25, 2006 3:16 AM
To: Maven Users List
Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
On 8/25/06, Valerio Schiavoni <va...@gmail.com> wrote:
> > Eclipse does not support hierarchical project structures.
> >
> i thought eclipse 3.2 just introduced this new feature ...
Yes it does.
Hence my original post wondering how to get it to work.
The notes I posted worked for me.
Try to get it working manually to prove to yourself that it can be done.
Just checkout a multi-module project and then try to import the
modules as existing projects.
If you can't get that to work you may have other problems.
Then its just a matter of running mvn eclipse:eclipse from the root,
delete the root/.project file and doing the same steps again.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
Posted by Barrie Treloar <ba...@gmail.com>.
On 8/25/06, Valerio Schiavoni <va...@gmail.com> wrote:
> > Eclipse does not support hierarchical project structures.
> >
> i thought eclipse 3.2 just introduced this new feature ...
Yes it does.
Hence my original post wondering how to get it to work.
The notes I posted worked for me.
Try to get it working manually to prove to yourself that it can be done.
Just checkout a multi-module project and then try to import the
modules as existing projects.
If you can't get that to work you may have other problems.
Then its just a matter of running mvn eclipse:eclipse from the root,
delete the root/.project file and doing the same steps again.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
suppo
Posted by Valerio Schiavoni <va...@gmail.com>.
Hello Max,
Max Cooper wrote:
>
> If you have a structure like this:
>
> root
> |--module1
> |--module2
> |--submodule2-1
>
my structure is a bit simpler, without nested submodules.
Max Cooper wrote:
>
> ... you would have to make sure that you hide/delete/rename the .project
> file in both the root and module2 directories for the submodule2-1
> project to show up on the import.
>
so fortunately this is not my case.
Max Cooper wrote:
>
> Eclipse does not support hierarchical project structures.
>
i thought eclipse 3.2 just introduced this new feature ...
Max Cooper wrote:
>
> IMO, moving your parent pom to a subdir is a better compromise than
> having all of your files show up two or more times in Eclipse.
>
of course, but this would break a well established maven convention, which
i'd like to avoid..
-Max
Valerio Schiavoni wrote:
>
> baerrach wrote:
>> Because there is no .project file eclipse will show all the
>> subprojects as being available.
>>
>
> i don't get this step working...it doesn't show submodule projects as
> being
> availble, even if each of them have their respective .project and
> .classpath
>
> any one with my same issue ?
>
> thanks,
> valerio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
--
View this message in context: http://www.nabble.com/-m2--eclipse%3Aeclipse-and-eclipse-3.2-projects-within-a-project-support.-tf2112924.html#a5979145
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
suppo
Posted by Max Cooper <ma...@maxcooper.com>.
If you have a structure like this:
root
|--module1
|--module2
|--submodule2-1
... you would have to make sure that you hide/delete/rename the .project
file in both the root and module2 directories for the submodule2-1
project to show up on the import. When Eclipse finds a .project file at
a node in the file tree, all projects from the subtree rooted at that
node are hidden, because Eclipse does not support hierarchical project
structures.
IMO, moving your parent pom to a subdir is a better compromise than
having all of your files show up two or more times in Eclipse. I would
use the technique outlined in this thread ONLY in cases where you could
not move the parent pom to a subdirectory.
-Max
Valerio Schiavoni wrote:
>
> baerrach wrote:
>> Because there is no .project file eclipse will show all the
>> subprojects as being available.
>>
>
> i don't get this step working...it doesn't show submodule projects as being
> availble, even if each of them have their respective .project and .classpath
>
> any one with my same issue ?
>
> thanks,
> valerio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
suppo
Posted by Valerio Schiavoni <va...@gmail.com>.
baerrach wrote:
>
> Because there is no .project file eclipse will show all the
> subprojects as being available.
>
i don't get this step working...it doesn't show submodule projects as being
availble, even if each of them have their respective .project and .classpath
any one with my same issue ?
thanks,
valerio
--
View this message in context: http://www.nabble.com/-m2--eclipse%3Aeclipse-and-eclipse-3.2-projects-within-a-project-support.-tf2112924.html#a5964416
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project support.
Posted by Barrie Treloar <ba...@gmail.com>.
> I setup a workspace using the procedure outlined in this thread. The end
> result that I get has the root and modules in a flat layout (not
> hierarchical) like this:
>
> root
> module1
> module2
> module3
>
> At first I thought that it didn't work for me, but I suspect that this
> was the same result that others got. I was expecting a hierarchical
> layout in Eclipse, but I see now that this is really just a trick that
> allows you to create overlapping Eclipse projects. Normally, Eclipse
> would not allow you to add both "root" and "module1" projects to the
> same workspace, since they overlap.
Eclipse creates the projects as you describe above, but the actual
contents of moduleX is contained within root. As you noted.
> 3. You can commit changes in multiple modules/projects in one
> transaction, by committing the changes from root project. (However, I
> see now that the Subversive subversion plugin supports "cross project
> atomic commits", which sounds like it will work even if you don't have
> your project root setup as an Eclipse project.)
At the moment I am using CVS, so I haven't noticed this issue.
> But it is still lacking in several respects:
>
> 1. If one team member adds a module, every person on the team has to do
> some fiddling to setup their workspace.
Only if that person wants to work on that module.
It's a small price to pay.
You really only want to create projects in your eclipse workspace on
stuff you are actually working on anyway.
> 2. The display in Eclipse is still flat, rather than hierarchical,
> making it impractical to have more than one multi-module project in the
> same workspace (since there is no indication which "root" project owns
> "moduleX").
In the Package Explorer there is a down arrow in the view toolbar,
choose "Select Working Set..." from it and you can then group your
projects together into whatever logical organisation you want.
Alternatively create more than one workspace if the projects are not related.
> 3. You are limited to one level of inheritance in your project
> hierarchy. Or maybe not, if you do the same .project-hide and import
> trick more than once. Whatever the case, it still flattens the view.
The project can be setup at any level of subdirectory below the root.
I think what you might be talking about is
root
- groupingA
- moduleX
- moduleY
- groupingB
- module G
I don't have such a structure but I see no reason why you could not
create a project for groupingA, moduleX and moduleY.
> 4. All of your files show up twice (or worse, if your project hierarchy
> has more than one level) -- once as root/moduleX/file and again as
> moduleX/file. This can be confusing. The double-display of file
> modification label decorations is annoying. I suspect that it also has a
> significant negative impact on Eclipse performance.
I doubt the impact is significant enough to worry about.
And you would soon get over the confusing part.
If for some reason there is a performance penalty, you can always go
back to having a single project. For me the benefits far outway any
drawbacks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
support.
Posted by Max Cooper <ma...@maxcooper.com>.
Sorry that this discussion is somewhat off-topic, but I hope that it is
okay since there are so many people trying to get
hierarchically-organized Maven projects to work well in Eclipse...
I setup a workspace using the procedure outlined in this thread. The end
result that I get has the root and modules in a flat layout (not
hierarchical) like this:
root
module1
module2
module3
At first I thought that it didn't work for me, but I suspect that this
was the same result that others got. I was expecting a hierarchical
layout in Eclipse, but I see now that this is really just a trick that
allows you to create overlapping Eclipse projects. Normally, Eclipse
would not allow you to add both "root" and "module1" projects to the
same workspace, since they overlap.
This does have a few advantages over the method I was using before:
1. The import process is a convenient way to create an Eclipse project
for each Maven module in one step. Previously, I was adding each one
individually. (This also works if you have checked out your project from
the root outside of the workspace.)
2. You can have your parent pom.xml in the root directory of your
project, AND still be able to edit it in Eclipse. Previously, I was
forced to put the parent pom in subdir under root.
3. You can commit changes in multiple modules/projects in one
transaction, by committing the changes from root project. (However, I
see now that the Subversive subversion plugin supports "cross project
atomic commits", which sounds like it will work even if you don't have
your project root setup as an Eclipse project.)
But it is still lacking in several respects:
1. If one team member adds a module, every person on the team has to do
some fiddling to setup their workspace.
2. The display in Eclipse is still flat, rather than hierarchical,
making it impractical to have more than one multi-module project in the
same workspace (since there is no indication which "root" project owns
"moduleX").
3. You are limited to one level of inheritance in your project
hierarchy. Or maybe not, if you do the same .project-hide and import
trick more than once. Whatever the case, it still flattens the view.
4. All of your files show up twice (or worse, if your project hierarchy
has more than one level) -- once as root/moduleX/file and again as
moduleX/file. This can be confusing. The double-display of file
modification label decorations is annoying. I suspect that it also has a
significant negative impact on Eclipse performance.
-Max
Barrie Treloar wrote:
> On 8/16/06, Barrie Treloar <ba...@gmail.com> wrote:
>> I thought that the snapshot version of the eclipse:eclipse plugin had
>> the functionality to do this for me, but it is not working how I
>> expect. I assume I am doing something wrong. Should mvn
>> eclipse:eclipse at the project root do what I expect?
>
> With the help of Nicolas' mail, these are the steps.
>
> Checkout your project root.
> Run mvn -DuseProjectReferences=false eclipse:eclipse at the project
> root. (I recommend not using project references so that you get
> repository copies and only when you need to work on related projects
> that you are changing sources files for at the same time to switch to
> project references)
> Rename the ROOT/.project file to something else
> File -> Import -> General -> Existing Projects and browse to your
> workspace and the project root.
> Because there is no .project file eclipse will show all the
> subprojects as being available. Select them and click ok.
> Now rename the ROOT/.project file back.
> Press F5 to refresh your Navigator view.
>
> You should have all your projects links up hierarchically!
> Weeeeee
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project support.
Posted by Barrie Treloar <ba...@gmail.com>.
On 8/16/06, Barrie Treloar <ba...@gmail.com> wrote:
> I thought that the snapshot version of the eclipse:eclipse plugin had
> the functionality to do this for me, but it is not working how I
> expect. I assume I am doing something wrong. Should mvn
> eclipse:eclipse at the project root do what I expect?
With the help of Nicolas' mail, these are the steps.
Checkout your project root.
Run mvn -DuseProjectReferences=false eclipse:eclipse at the project
root. (I recommend not using project references so that you get
repository copies and only when you need to work on related projects
that you are changing sources files for at the same time to switch to
project references)
Rename the ROOT/.project file to something else
File -> Import -> General -> Existing Projects and browse to your
workspace and the project root.
Because there is no .project file eclipse will show all the
subprojects as being available. Select them and click ok.
Now rename the ROOT/.project file back.
Press F5 to refresh your Navigator view.
You should have all your projects links up hierarchically!
Weeeeee
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
support.
Posted by Max Cooper <ma...@maxcooper.com>.
Douglas Ferguson wrote:
> Does anybody have any experience switching between project dependencies and
> jar dependencies?
>
> I assume that if you are working on multiple modules at the same time the
> project dependencies would be necessary, but then when you are working on 1
> specific module that may use an older version (non trunk) or another module,
> then jar dependencies would be needed.
>
> Do you have to keep using mvn eclipse:eclipse all the time?
I think you do. But you have to do that anyway, so that you get any new
dependencies that someone else adds to the project.
-Max
>
>
> -----Original Message-----
> From: Barrie Treloar [mailto:baerrach@gmail.com]
> Sent: Wednesday, August 16, 2006 5:50 PM
> To: Maven Users List
> Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
> support.
>
> On 8/17/06, Max Cooper <ma...@maxcooper.com> wrote:
>> I, too, have been anxiously awaiting hierarchical project support in
>> Eclipse. And I thought that it was going to be available in Eclipse 3.2.
>>
>> But this feature was omitted from the Eclipse 3.2 release. The feature
>> is not available yet.
>
> You can do it, I was able to manually create another project pointing
> to one that was already in the workspace and a subdirectory of that
> project.
>
> i.e
>
> project_root/
> - module1
> - module2
>
> I was able to have in Eclipse a project for "project_root" as well as
> create one manually for module1 and module2 so that they appear in the
> project list.
>
> But I can't figure out what Eclipse does under the covers for that,
> there are no docs that I could find in the help or googling, and I
> can't see in the source code of the eclipse:eclipse plugin whether it
> is attempting to do this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m2] eclipse:eclipse and eclipse 3.2 projects within a project support.
Posted by Douglas Ferguson <do...@epsiia.com>.
Does anybody have any experience switching between project dependencies and
jar dependencies?
I assume that if you are working on multiple modules at the same time the
project dependencies would be necessary, but then when you are working on 1
specific module that may use an older version (non trunk) or another module,
then jar dependencies would be needed.
Do you have to keep using mvn eclipse:eclipse all the time?
-----Original Message-----
From: Barrie Treloar [mailto:baerrach@gmail.com]
Sent: Wednesday, August 16, 2006 5:50 PM
To: Maven Users List
Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
support.
On 8/17/06, Max Cooper <ma...@maxcooper.com> wrote:
> I, too, have been anxiously awaiting hierarchical project support in
> Eclipse. And I thought that it was going to be available in Eclipse 3.2.
>
> But this feature was omitted from the Eclipse 3.2 release. The feature
> is not available yet.
You can do it, I was able to manually create another project pointing
to one that was already in the workspace and a subdirectory of that
project.
i.e
project_root/
- module1
- module2
I was able to have in Eclipse a project for "project_root" as well as
create one manually for module1 and module2 so that they appear in the
project list.
But I can't figure out what Eclipse does under the covers for that,
there are no docs that I could find in the help or googling, and I
can't see in the source code of the eclipse:eclipse plugin whether it
is attempting to do this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project support.
Posted by Barrie Treloar <ba...@gmail.com>.
On 8/17/06, Max Cooper <ma...@maxcooper.com> wrote:
> I, too, have been anxiously awaiting hierarchical project support in
> Eclipse. And I thought that it was going to be available in Eclipse 3.2.
>
> But this feature was omitted from the Eclipse 3.2 release. The feature
> is not available yet.
You can do it, I was able to manually create another project pointing
to one that was already in the workspace and a subdirectory of that
project.
i.e
project_root/
- module1
- module2
I was able to have in Eclipse a project for "project_root" as well as
create one manually for module1 and module2 so that they appear in the
project list.
But I can't figure out what Eclipse does under the covers for that,
there are no docs that I could find in the help or googling, and I
can't see in the source code of the eclipse:eclipse plugin whether it
is attempting to do this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a projectsupport.
Posted by Nicolas De Loof <ni...@capgemini.com>.
I've just tested it and it works fine with sub-projects. It also looks
better than sublcipse IMHO, and has a better handling of renamed/moved
files (specific icon) that subclipse handles as removed+added.
>> In the meantime, it might be worth giving Subversive a try (
>> http://www.polarion.org/index.php?page=overview&project=subversive ).
>> It's an open source subversion plugin for eclipse, just like subclipse.
>>
>> Cheers,
>> -Ralph.
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a projectsupport.
Posted by Nicolas De Loof <ni...@capgemini.com>.
> Are you talking about subclipse issue 511(
> http://subclipse.tigris.org/issues/show_bug.cgi?id=511 ) ? If so,
> people interested in having this fixed should probably create an
> account on tigris.org and vote for this issue.
You're right. Please vote !
>
> In the meantime, it might be worth giving Subversive a try (
> http://www.polarion.org/index.php?page=overview&project=subversive ).
> It's an open source subversion plugin for eclipse, just like subclipse.
>
> Cheers,
> -Ralph.
>
>
>> Max Cooper a écrit :
>>> I, too, have been anxiously awaiting hierarchical project support in
>>> Eclipse. And I thought that it was going to be available in Eclipse
>>> 3.2.
>>>
>>> But this feature was omitted from the Eclipse 3.2 release. The
>>> feature is not available yet.
>>>
>>> -Max
>>>
>>> Barrie Treloar wrote:
>>>> With Eclipse 3.2 I was lead to believe you could create projects
>>>> within projects, so that I could checkout a maven project that
>>>> contains modules and wire that up in Eclipse correctly. Instead of
>>>> manually checking out the modules as I did under Eclipse 3.1.
>>>>
>>>> I am able to manually add the project in Eclipse via File -> Import ->
>>>> General -> Existing Projects into Workspace and use the module
>>>> directoy as the value for "Select root directory".
>>>> The project then appears in the "Projects" list for importing.
>>>>
>>>> If I select the project root then there are no projects to choose
>>>> from.
>>>>
>>>> I thought that the snapshot version of the eclipse:eclipse plugin had
>>>> the functionality to do this for me, but it is not working how I
>>>> expect. I assume I am doing something wrong. Should mvn
>>>> eclipse:eclipse at the project root do what I expect?
>>>>
>>>> Any help appreciated.
>>>> Bae
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a projectsupport.
Posted by Ralph Pöllath <li...@poellath.org>.
On 17.08.2006, at 10:24, Nicolas De Loof wrote:
> I use hierarchical projects in eclipse myself. Import wizard
> doesn't search sub-directories if the top-directory has a .project
> file.
> I had to delete the .project generated during checkout before
> importing all sub-projects in one click. Then I can restore
> the .project and import the top level project. Please notice this
> creates a freeze when using SVN and subclipse. This bug has been
> reported to subclipse devs but doesn't seem to get more interest.
Are you talking about subclipse issue 511( http://
subclipse.tigris.org/issues/show_bug.cgi?id=511 ) ? If so, people
interested in having this fixed should probably create an account on
tigris.org and vote for this issue.
In the meantime, it might be worth giving Subversive a try ( http://
www.polarion.org/index.php?page=overview&project=subversive ). It's
an open source subversion plugin for eclipse, just like subclipse.
Cheers,
-Ralph.
> Max Cooper a écrit :
>> I, too, have been anxiously awaiting hierarchical project support
>> in Eclipse. And I thought that it was going to be available in
>> Eclipse 3.2.
>>
>> But this feature was omitted from the Eclipse 3.2 release. The
>> feature is not available yet.
>>
>> -Max
>>
>> Barrie Treloar wrote:
>>> With Eclipse 3.2 I was lead to believe you could create projects
>>> within projects, so that I could checkout a maven project that
>>> contains modules and wire that up in Eclipse correctly. Instead of
>>> manually checking out the modules as I did under Eclipse 3.1.
>>>
>>> I am able to manually add the project in Eclipse via File ->
>>> Import ->
>>> General -> Existing Projects into Workspace and use the module
>>> directoy as the value for "Select root directory".
>>> The project then appears in the "Projects" list for importing.
>>>
>>> If I select the project root then there are no projects to choose
>>> from.
>>>
>>> I thought that the snapshot version of the eclipse:eclipse plugin
>>> had
>>> the functionality to do this for me, but it is not working how I
>>> expect. I assume I am doing something wrong. Should mvn
>>> eclipse:eclipse at the project root do what I expect?
>>>
>>> Any help appreciated.
>>> Bae
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a projectsupport.
Posted by Nicolas De Loof <ni...@capgemini.com>.
I use hierarchical projects in eclipse myself. Import wizard doesn't
search sub-directories if the top-directory has a .project file.
I had to delete the .project generated during checkout before importing
all sub-projects in one click. Then I can restore the .project and
import the top level project. Please notice this creates a freeze when
using SVN and subclipse. This bug has been reported to subclipse devs
but doesn't seem to get more interest.
Max Cooper a écrit :
> I, too, have been anxiously awaiting hierarchical project support in
> Eclipse. And I thought that it was going to be available in Eclipse 3.2.
>
> But this feature was omitted from the Eclipse 3.2 release. The feature
> is not available yet.
>
> -Max
>
> Barrie Treloar wrote:
>> With Eclipse 3.2 I was lead to believe you could create projects
>> within projects, so that I could checkout a maven project that
>> contains modules and wire that up in Eclipse correctly. Instead of
>> manually checking out the modules as I did under Eclipse 3.1.
>>
>> I am able to manually add the project in Eclipse via File -> Import ->
>> General -> Existing Projects into Workspace and use the module
>> directoy as the value for "Select root directory".
>> The project then appears in the "Projects" list for importing.
>>
>> If I select the project root then there are no projects to choose from.
>>
>> I thought that the snapshot version of the eclipse:eclipse plugin had
>> the functionality to do this for me, but it is not working how I
>> expect. I assume I am doing something wrong. Should mvn
>> eclipse:eclipse at the project root do what I expect?
>>
>> Any help appreciated.
>> Bae
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project
support.
Posted by Max Cooper <ma...@maxcooper.com>.
I, too, have been anxiously awaiting hierarchical project support in
Eclipse. And I thought that it was going to be available in Eclipse 3.2.
But this feature was omitted from the Eclipse 3.2 release. The feature
is not available yet.
-Max
Barrie Treloar wrote:
> With Eclipse 3.2 I was lead to believe you could create projects
> within projects, so that I could checkout a maven project that
> contains modules and wire that up in Eclipse correctly. Instead of
> manually checking out the modules as I did under Eclipse 3.1.
>
> I am able to manually add the project in Eclipse via File -> Import ->
> General -> Existing Projects into Workspace and use the module
> directoy as the value for "Select root directory".
> The project then appears in the "Projects" list for importing.
>
> If I select the project root then there are no projects to choose from.
>
> I thought that the snapshot version of the eclipse:eclipse plugin had
> the functionality to do this for me, but it is not working how I
> expect. I assume I am doing something wrong. Should mvn
> eclipse:eclipse at the project root do what I expect?
>
> Any help appreciated.
> Bae
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org