Eclipse Community Forums: ServerTools (WTP) » maven 2 parent pom and eclipse project structure

Home » Language IDEs » ServerTools (WTP) » maven 2 parent pom and eclipse project structure

maven 2 parent pom and eclipse project structure [message #184681]

Thu, 14 December 2006 07:32

Eclipse User

Hello,

I'm struggling using maven2 project structure with eclipse (3.2.1) project
structure.

Here is my wish:

project
|
|- projectManagement/
|- pom.xml (parent pom)
|- module1/
| |
| |- pom.xml
| |- ..
|- module2/
|
|- pom.xml
|- ..

Where as *projectManagement* contains stuff that is not necessary to build
the system.

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:

|- module1/
|- module2/

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
of "eclipse-project-contains-eclipse-project"?

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 #184689 is a reply to message #184681]

Thu, 14 December 2006 07:40

Eclipse User

Got some problems with newlines:

2nd try:

- project
---pom.xml
---projectManagement
---module1
------pom.xml
------..
---module2
------pom.xml
------..

TIA, Leif

Re: maven 2 parent pom and eclipse project structure [message #184717 is a reply to message #184689]

Thu, 14 December 2006 09:35

Eclipse User

Originally posted by: kosta.bea.com

Leif,

Unfortunately, Eclipse does not support nested project structure. You
can certainly import the projectManagement directory as a separate
project, but the trick is what to do with the top-level pom.xml file.
The only solution that I am aware of is to move it into a sub-directory
that can then be imported as a project.

Hope this helps.

- Konstantin

Re: maven 2 parent pom and eclipse project structure [message #184741 is a reply to message #184717]

Thu, 14 December 2006 10:40

Eclipse User

Are there any plans to support maven project structure? Will the flexible
project structure help?

TIA, Leif

Re: maven 2 parent pom and eclipse project structure [message #184824 is a reply to message #184741]

Thu, 14 December 2006 11:49

Eclipse User

Originally posted by: kosta.bea.com

Leif,

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.

- Konstantin

Re: maven 2 parent pom and eclipse project structure [message #184912 is a reply to message #184824]

Thu, 14 December 2006 18:58

Eclipse User

Konstantin,

How about other way around? Everybody still waiting response from WTP
team on bug 154251
https://bugs.eclipse.org/bugs/show_bug.cgi?id=154251

regards,
Eugene

Konstantin Komissarchik wrote:
> Leif,
>
> 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.
>
> - Konstantin

Re: maven 2 parent pom and eclipse project structure [message #185042 is a reply to message #184912]

Fri, 15 December 2006 11:00

Eclipse User

Originally posted by: kosta.bea.com

Eugene,

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

Re: maven 2 parent pom and eclipse project structure [message #185113 is a reply to message #185042]

Fri, 15 December 2006 16:23

Eclipse User

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.

regards,
Eugene

Previous Topic:	Creating a web service from wsdl (Top Down Java Bean Web Service)
Next Topic:	WSDL explorer goes to blank page in browser

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 16 08:27:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter