How to live with m2eclipse's WTP support projects?

[Trinition <tr...@trinition.org>]

I have a typical project structure that works perfectly fine for me:

myproject
|__myproject-app
|__myproject-shared
|__myproject-ejb
|__myproject-web

Within the EJB project's pom (packaging=ejb), I have two build plugin:

* org.codehaus.mojo:was6-maven-plugin:ejbdeploy
* org.apache.maven.plugins:maven-ejb-plugin:2.0 (ejbVersion=2.0,
generateClient=true)

When we build with plain-old Maven, we get one extra artifact:
myproject-ejb-client.jar.  However, when I import the projects with
m2eclispe, I'm gaining an extra eclipse project: myproject-ebjClient.  Its
also modifying the myproject-ejb's ejb-jar.xml to include this new project's
name.

This explicit ceration of the project and mismatch of the name is vexing me
greatly.  Where's my disconnect?
-- 
View this message in context: http://www.nabble.com/How-to-live-with-m2eclipse%27s-WTP-support-projects--tp22740678p22740678.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: How to live with m2eclipse's WTP support projects?

[Eugene Kuleshov <eu...@md.pp.ru>]

Trinition,

  Usually, a client ejb artifact is a secondary artifact produced from an
ejb project, and it normally would be named as myproject-ejb-1.0-ejb-client,
where "ejb-client" is a classifier you'd specify in <dependency> element.
When such dependency is resolved from Eclipse workspace, the m2eclipse
should normally resolve it as a reference to the myproject-ejb.

  Anyways, it is better to follow up on this in m2eclipse's own mailing
list. Also, I am not quite sure what you meant by gaining an extra eclipse
project and how exactly you imported your projects in Eclipse.

  regards,
  Eugene

[1]
http://maven.apache.org/plugins/maven-ejb-plugin/examples/generating-ejb-client.html
[2]
http://maven.apache.org/plugins/maven-ejb-plugin/examples/ejb-client-dependency.html



Trinition wrote:
> 
> I have a typical project structure that works perfectly fine for me:
> 
> myproject
> |__myproject-app
> |__myproject-shared
> |__myproject-ejb
> |__myproject-web
> 
> Within the EJB project's pom (packaging=ejb), I have two build plugin:
> 
> * org.codehaus.mojo:was6-maven-plugin:ejbdeploy
> * org.apache.maven.plugins:maven-ejb-plugin:2.0 (ejbVersion=2.0,
> generateClient=true)
> 
> When we build with plain-old Maven, we get one extra artifact:
> myproject-ejb-client.jar.  However, when I import the projects with
> m2eclispe, I'm gaining an extra eclipse project: myproject-ebjClient.  Its
> also modifying the myproject-ejb's ejb-jar.xml to include this new
> project's name.
> 
> This explicit ceration of the project and mismatch of the name is vexing
> me greatly.  Where's my disconnect?
> 

-- 
View this message in context: http://www.nabble.com/How-to-live-with-m2eclipse%27s-WTP-support-projects--tp22740678p22745564.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org