| RE: [iam-dev] WTP project structure |
|
Abel, Thanks for the reply. My biggest goal right now is to stop
developers from checking jars into source control—i.e., get everyone
using dependency management even if they are not “Maven savvy”. So
the idea is to migrate older “WTP layout” style projects to using
Maven (at least for dependency management) with as little pain as possible. If
IAM does not show the issue MNGECLIPSE-1191, that would at least be a good
start. When do you anticipate a stable build of the current trunk? Brennan Spies Sr. Programmer Analyst E. & J. Gallo Winery From:
iam-dev-bounces@xxxxxxxxxxx [mailto:iam-dev-bounces@xxxxxxxxxxx] On Behalf
Of Abel Muiño Hello Brennan, 2009/4/9 Spies, Brennan <Brennan.Spies@xxxxxxxxxxx> Hi, I am currently using m2eclipse to handle Maven integration with Eclipse, but
am running into a big sticking point: using non-Maven project structures,
specifically the default structure generated by the Dynamic Web project wizard
in Eclipse. https://issues.sonatype.org/browse/MNGECLIPSE-781 https://issues.sonatype.org/browse/MNGECLIPSE-1191 When trying to add dependency management to projects generated with the
Dynamic Web project wizard using m2eclipse (specifically Maven-->Enable
Dependency Management) is still a bit buggy, even using a manually created
pom.xml file. It used to work fine in older versions of m2eclipse. Is IAM/q4e any better in this regard? Brennan
|