| Author |
Message |
|
|
Post subject: Standard way to setup Enterprise project w Maven/MyEclipse?
Posted: Sep 03, 2009 - 01:56 PM
|
|
Registered Member

Joined: Apr 21, 2008
Posts: 21
|
|
I need some advice on how to set up a new large multiple-module project in myeclipse 7, using Maven. I'm seeking a tutorial for a "from scratch with a brand new MyEclipse workspace, here's how to get your enterprise project structured, building, testing and (hot) deploying".
I don't think we're requiring anything non-standard here - ultimately our deployed artifact will be an EAR with a WAR inside representing our UI layer and several other jars representing service layer, persistence layer, integration layer etc.
We really need to keep the ability to hot-deploy as we've been able to do in the past with non-maven myeclipse projects. The project is large and greenfields, and we have the opportunity at this point to set up our development environment in new workspaces with no code at all having been written yet. Weblogic 10 is the container but we're very open to developing using Tomcat or something else to speed up the day-to-day development.
Having spent a few days now creating projects with MyEclipse 7 (sorry I'm not at work at the moment so I don't know the exact version), we're frustrated at our inability to get a project of this description up and running with Maven. We've tried adding simple Maven projects - I guess this is the Maven4MyEclipse plugin - and then adding web capabilities etc, but these projects don't seem to integrate with MyEclipse very well...we get weird behaviour where we have to do a Project/Clean 3 times in a row before the web project's build path is synced with our Maven POM...we get lots of different "black magic" scenarios and we're thoroughly confused. We've tried generating a Maven EAR project but have no idea how to integrate this into MyEclipse so that it can be deployed inside the IDE.
Shouldn't there be a standard way to set all this up? Having looked at the tutorials on this site and googled till our fingers bled we still can't seem to find out how everyone else is setting up a standard enterprise project with MyEclipse and Maven (with hot deploy).
Any advice appreciated.
cheers,
Ian |
|
|
| |
|
|
|
 |
|
|
Post subject: more
Posted: Sep 04, 2009 - 02:04 AM
|
|
Registered Member

Joined: Apr 21, 2008
Posts: 21
|
|
FYI, while I'm waiting on advice, I can confirm we're using 7.1.1. |
|
|
| |
|
|
|
 |
|
|
Post subject: update
Posted: Sep 08, 2009 - 09:01 AM
|
|
Registered Member

Joined: Apr 21, 2008
Posts: 21
|
|
We're still banging our heads against the wall on this one. We can get a Mavenized Web project deploying and deploying (and hot-deploying) to Tomcat in MyEclipse, but we still can't get a Mavenized Enterprise project deploying to Weblogic in MyEclipse.
This doesn't seem like we're after anything unusual. At this stage I think we're heading for a situation where we might need to either ditch Maven or ditch MyEclipse.
Any suggestions as to how you've accomplished anything similar? |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: update
Posted: Sep 08, 2009 - 02:08 PM
|
|
Registered Member

Joined: May 12, 2005
Posts: 473
|
|
Unfortunately, there is no support for Mavenized enterprise application at the moment. |
_________________ Eugene
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: update
Posted: Jan 21, 2010 - 04:58 PM
|
|
Joined: Dec 28, 2009
Posts: 19
|
|
Isn't that the entire point of Maven integration?
We have a similar issue here: We have a multi-module project using the Maven4MyEclipse features. We have the module projects open in MyEclipse 8.0, but no matter what I do and what instructions I follow, I cannot seem to get the parent project created. We have the following STANDARD BEST-PRACTICE multi-module folder structure:
| Code: | /eclipse-workspaces
+ /project-workspace
+ /proj-parent
+ /build-tools
+ /modules
+ /module1
+ /module2
|
At the moment, we are able to utilize the module projects in MyEclipse 8.0, but we've been completely unable to open the "proj-parent" and "build-tools" as projects. Considering that this is THE standard way going forward to do multi-module projects with Maven and Eclipse, what exactly is the correct path to working with projects like this in MyEclipse 8.0? I've been searching and searching the net for instructions, but everything I've found is for standard Eclipse with the m2eclipse plugin. I could not find even one page that describes how to use MyEclipse with Maven4Eclipse with multi-module projects. The "help" page for the Maven integration in MyEclipse 8.0 skips ALL relevant details. Can someone please direct me to some relevant instructions for using this IDE properly with Maven? If we can't use MyEclipse for this STANDARD project layout, we will need to switch back to the standard Eclipse, so please let me know right away what I should do.
Thanks,
Tom Harris |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: update
Posted: Feb 24, 2010 - 01:41 PM
|
|
Joined: Feb 24, 2010
Posts: 2
|
|
Hi all,
I am currently viewing into myEclipse as an alternative to our RAD installations.
I'm wondering about the same point than Tom: How can we use multi-module projets with myEclipse? This is crucial in our decision whether to switch to MyEclipse or not...
Thank you for any hint on this!
Andreas |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Feb 24, 2010 - 03:03 PM
|
|
Joined: Dec 28, 2009
Posts: 19
|
|
anweibel:
We are continuing to use MyEclipse, but with the Maven4MyEclipse feature removed and the specially packaged M2Eclipse plugin for MyEclipse. You can use http://m2eclipse.sonatype.org/update-maven4youreclipse as the update site. I found that this is the only way to get multi-module maven projects to work properly in MyEclipse.
There is a caveat, in that you will have to use the project context menu Maven > Disable Dependency Management, then Maven > Enable Dependency Management to get things working properly. This is to get around an outstanding bug in M2Eclipse which presents itself as a popup error on each project, something about a @BeginRule failure. The Sonatype folks know about it and are working to patch. This one defect with the workaround is better than having no multi-module support at all, IMHO.
For more information, read http://www.sonatype.com/people/2008/09/how-did-myeclipse-get-their-maven-integration-so-wrong/
Genuitec has known about this issue for three releases, and keep promising to fix, but they still have not fixed it, so we're on our own. Let's hope this ESSENTIAL information stays up on the forum so others can actually get some work done.
Tom |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Feb 24, 2010 - 04:42 PM
|
|
Joined: Feb 24, 2010
Posts: 2
|
|
Hi Tom,
Thanks for this - indeed - essential information.
Best,
andreas |
|
|
| |
|
|
|
 |
|
|