I'm working on the Maven2 build for the shale-usecases example (on the
mvn_reorg branch). Currently, the application buids, but it fails on some
XML parsing errors when you deploy it. In turn, this happens because
xml-apis-1.0.b2.jar and xercesImpl-2.2.1.jar are getting picked up as
Commons Digester has this dependency.
Niall
On 6/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I'm working on the Maven2 build for the shale-usecases example (on the
mvn_reorg branch). Currently, the application buids, but it fails on some
XML parsing errors when you deploy it. In turn,
On 6/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I've tried Wendy's suggestion of using -X on the mvn execution, which gives
a pretty copious amount of output ... and still doesn't make it clear from
which POM the dependency is actually getting inherited. Is there some
mechanism in Maven2
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
You get rid of them by adding a dependency in the webapp pom marked
provided or optional. Maven constructs a dependency graph and uses
the closest definition.
Missed a word there. :) You _can_ get rid of them this way, though
excludes are
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
You get rid of them by adding a dependency in the webapp pom marked
provided or optional. Maven constructs a dependency graph and uses
the closest definition.
Missed a word there. :) You
