Hi,
The problem here is the phase in the life cycle.. The best thing would
be to use the generated application.xml from the ear plugin but thats
generated very late in the packaging phase. The eclipse plugin runs in a
very early phase to be able to generate eclipse config files also for
broken
We could also think to extract some part of ear/war/... plugins to
reuse some services throught a shared library
Arnaud
On Thu, Mar 20, 2008 at 9:03 AM, Richard van Nieuwenhoven
[EMAIL PROTECTED] wrote:
Hi,
The problem here is the phase in the life cycle.. The best thing would
be to use
Richard,
I've noticed the plugin does invoke
ear:generate-application-xmlhttp://maven.apache.org/plugins/maven-ear-plugin/generate-application-xml-mojo.htmlgoal
- may be the lifecycle isn't a problem here?
I agree with Arnaud, that way we could keep up with plugins and be more
consistent.
Hi,
i also agree with Arnaud that this would be great but i think it is
almost not do-able. I tried for example to use the plexus manifest
generator (= service reuse) but failed because the dependencies are not
yet resolved (or something simulator) when the eclipse plugin starts.
Now to the
Hi All,
When I was trying to do a workaround with
http://jira.jboss.org/jira/browse/JBIDE-1862 (actually seems to be WTP
2.0.2bug) it appears that maven-eclipse-plugin ignores
application.xml that is generated by maven ear plugin. While this might be
ok with WTP 2.0.2 you will have a problem if
