- This topic has 3 replies, 3 voices, and was last updated 15 years, 7 months ago by Jason Taylor.
-
AuthorPosts
-
ryanrlamotheMemberI did not see a place on the poll for adding your own suggestions, so I want to add mine in this thread.
I have been using MyEclipse for going on 2 years now, developing a large-scale enterprise application for the state of VA. Using amongst other things JBoss AS, JBoss jBPM, JBoss Portal, Spring Web MVC and more.
What is the single largest problem our 20+ member development team has had to deal with for the past 2 years? The lack of a standalone build system or build system integration with MyEclipse.
Let me explain. It is very nice that MyEclipse does a lot of the work building EAR’s and WAR’s automatically for you, with a nice GUI deployer, resolving dependencies and exporting projects and libs with proper configuration. But, this is also its greatest weakness. The underlying build system is completely hidden and inaccessible from the individual developer as well as the development team. Project and workspace variables get completely tied to MyEclipse. Therefore, limiting the usefulness of project building using MyEclipse to single-user mode.
My suggestion for a new feature in MyEclipse is to have the ability for ALL of MyEclipse project configuration, project dependency, project build and project deployment functionality be exported to Ant. This is so that projects can be checked out headless and dependency-free, as much as possible, by an external process (ie. CruiseControl), built and deployed solely using automated scripts. Currently, we are using MyEclipse for individual development and then additionally managing external build scripts, which is really awful.
Ton HuismanMemberAbout 80% ditto, and then read for Maven instead of Ant, and Continuum instead of CruiseControl.
TIA
Ton
ryanrlamotheMemberAnyone else have any suggestions? Thoughts?
Jason TaylorMemberIn general MyEclipse has really come a long way and provides most of the functionality I’m really interested in right now. Besides keeping up with the standards and frameworks (JSF 1.2, Struts 2.0, Spring 2.5.6, etc), I really would like to see 64-bit support. I think with the latest chipsets/configurations for systems, 64-bit OSes are going to be the default if not only choice available moving forward.
Support for Apache CXF as the XFire replacement would be nice too.
-
AuthorPosts