Hi Brian,
I'm writing in relation to the j2ee artifact that was released and the
maven-eclipse-plugin patch that you wrote. If I didn't understand
wrongly it might be possible to put all projects on one level and then
reference the modules in the main pom in a relative way like:
<modules>
<module>
../child-project1
</module>
<module>
../child-project2
</module>
</modules>
So perhaps the eclipse plugin should also have the role of flattening
hierarchical projects?
That way it would be unnecessary to fork the j2ee archetype and
maven-eclipse-plugin would know what would it need to be done.
Brian Bonner wrote:
Hi guys,
I was able to get the project to install with the required
dependencies of servlet on primary-sources and logging.
I'm not sure about the EAR because I haven't created an EAR project in
the WTP. I've mostly done dynamic web projects. I use
spring/hibernate and have stayed clear of the packaging. I haven't
used j2ee clients per se.
To get the web side working, I needed to add a build section to the
j2ee web's POM and the patch to EclipsePlugin *was* required.
It also needed a base web.xml included in the tree to get the project
to load in tomcat. I think this should be added anyway as part of
the archetype.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
