|maven 2 parent pom and eclipse project structure [message #184681]
||Thu, 14 December 2006 07:32
| Leif Hanack
Registered: July 2009
I'm struggling using maven2 project structure with eclipse (3.2.1) project
Here is my wish:
|- pom.xml (parent pom)
| |- pom.xml
| |- ..
Where as *projectManagement* contains stuff that is not necessary to build
I want *project* to be an eclipse project under version control.
Using mvn eclipse:eclipse inside *project* creates two eclipse projects:
one for module1 and one for module2.
Importing the two projects, the eclipse navigator or package explorer
looks like this:
What should I do next?
As mentioned above, I want to have the parent pom and some general stuff
under version control as well.
When I now create a simple project for directory *project*, I got the
problem, that module1 and module2 are included.
I don't want a flat project/pom structure. Is there a way to have a kind
I've heard about the flexible project structure but didn't get it.
How do you using a parent pom structure in conjunction with eclipse?!
Please give me your experience / best practices.
Thanks in advance, Leif
|Re: maven 2 parent pom and eclipse project structure [message #184824 is a reply to message #184741]
||Thu, 14 December 2006 11:49
Originally posted by: kosta.bea.com|
I don't believe "flexible project" structure will help in this case. You
may want to consider posting a request on the Eclipse Platform news
group and/or opening an enhancement request against the platform as this
goes beyond WTP and needs to be implemented at the platform level.
We have been requesting support for this from the platform for quite a
while now. Hasn't happened yet. But the more people that ask for it, the
more likely that it will eventually be supported.
|Re: maven 2 parent pom and eclipse project structure [message #185113 is a reply to message #185042]
||Fri, 15 December 2006 16:23
| Eugene Kuleshov
Registered: July 2009
Konstantin Komissarchik wrote:|
> Multiple modules per Eclipse project is a proven bad approach that WTP
> community has struggled with for a long time and finally abandoned.
> There are no plans to go back to it.
Konstantin, I was referring not to multiple modules, but to API or
some other way to dynamically create and register WTP-specific stuff.
Currently we can't tell WTP how dependencies should be packaged
without duplicating the same information in several places and in my
opinion it is a huge extensibility limitation of the WTP as a platform.
Powered by FUDForum
. Page generated in 0.02499 seconds