I'm also experiencing this problem. As discussed here (under Inheritance v.
Aggregation):
http://www.propellors.net/maven/site/pom.html#POM%20Relationships
it appears to make sense in what is called the aggregation use case, but
not in the inheritance use case. I'm wondering if there's some
/configuration
/plugin
I do not really understand what's wrong, is it the lake of phase tag
(the
plugin does not set a default phase)?
Explanations would be very appreciate.
Thanks all,
Alexis
On 8/31/06, Jared Bunting [EMAIL PROTECTED] wrote:
Another thought - the guide here talks
I might be missing what you're trying to do here, and it seems to me that
creating a multi-module project, as suggested, would be the best way to go
about this. However, what if you bound your source generation to the
generate-sources phase. I'm not sure of how it would be done in ant, but
I
The option I can see that seems to relate to my issue is the
generateApplicationXml ,
which one can set to true, to turn off generation of the
application.xml.Butthen how do
I tell the plugin where the pre-existing application.xml file is
located?I'm
looking for something
similar to Maven1's
From what I've been able to tell in the past, it seems that the rule is if
your project has the modules element, then it has to be of packaging type
pom. It looks like you have an ear project that you want to include an
ejbModule and a warModule - I have done this in the past by having a
Another thought - the guide here talks about using private fields for mojo
configuration - i noticed that yours is protected. It specifically mentions
that setters can be used in place of private fields, but makes no mention of
protected fields. Now, while it would make sense to me that the
I have attached a zip containing poms and checksums for 1.2.8 to the ticket
you mention. What else do I need to do to get these uploaded to ibiblio?
Thanks,
Jared
On 8/30/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
any questions about spring and their poms must be asked there, or you
provide
