[cherngje]

Will MyEclipse 7.2M have ear plugin support? For example, can I define everything (dependencies, modules, properties, etc) in the pom.xml of an ear project instead use MyEclipse’s tradition ear project setup, and still use the MyEclipse deploy mechanism to deploy the ear to the application server?

Thanks~

[Loyal Water]

We have m2eclipse plugin support targeted for the next release but the EAR plugin is not on the cards yet. I’ll make a note of this feature request and take it to the management.

[jordan.parker]

I concur, this would be a great feature to have! Thanks

[Loyal Water]

I concur, this would be a great feature to have! Thanks

Your welcome.

[denis.zjukow]

I am interested in this subject too. Is there any plans to add Maven support for EAR projects? Thanks.

[Loyal Water]

Does you mean adding this in the EAR itself, or on the new module wizard pages when creating an EAR ?

[denis.zjukow]

I mean are you going to add a possibility to manage dependences through maven in EAR projects. It would be nice if it were possible to define dependences in pom.xml. So we could package EAR modules using maven package. MyEclipse already allows maven support for WAR and EJB projects for example.

[support-eugene]

We plan to add Maven support to EAR projects but we don’t yet have a set release date for this functionality.

[mst98sub]

Could you please outline a possible workaround for the missing EAR maven support!

We are using MyEclipseBlue 7 and the WebSphere 6.1 Server Adapater to deploy our EARs.
To reduce the size of our workspaces, we plan to use mostly pre-built binary EJB modules as artifacts from our maven repository instead of checking out all EJB modules’ source projects.

Is there a possibilty to include binary EJB modules into a non-maven MyEclipse EAR project?

A possible workaround might be to create empty wrapper EJB projects with maven support enabled for every binary EJB module to be included. The empty wrapper project could resolve the maven dependency to the original binary EJB module artifact and unpack it as a depdent EJB jar.
Has someone already tried this approach?

Is there perhaps a better solution?

thx,
Mathias

[Riyad Kalla]

Mathias,

That’s definitely an interesting use-case, but no, we have no plans to support something like that right now. Also the bigger question (you guys are asking for) of marrying the Maven tooling and MyEclipse tooling for building, packaging and deploying is a *serious* request and not something the exec team will evaluate lightly. It’s on their plate for assessment, but given the extent of the changes required for something like that I wouldn’t expect that to popup in the 7.x release series.

I know that’s a bummer, I just want to manage expectations appropriately for you guys.

[gongtow]

Maven EAR support will be great. I don’t need to manually control the packaged ejb and library files.
Does 7.x include this feature? My 6.6 did not yet.

Lance

[Loyal Water]

Lance,
Im afraid this has not made it to 7.X yet. We will keep you posted via this thread.

[HbFan]

Has this been added to MyEclipse yet? If not, is there a documented workaround?

[baeurlem]

*push*

What about a release date in the 8.x line?

Regards

[denis.zjukow]

Hi, any news about the subject? Are there any plans about implementing Maven support for EAR projects? It looks like JBoss Tools already has this feature.

[Author]

Posts