Shash Chatterjee wrote:
Berin,
Yep. The project.xml for those files are set up using
<id>excalibur-pool-api</id> as opposed to the groupId/artifactId
pairing. All I did was make everything build for me.
It was a mess just trying to get everything to work just so I could
build the docs for the SourceResolver package because those JavaDocs
are missing from the website.
Yes, I see what you mean about the "<id>" element. Even, with that
though, it built/deployed fine for me on both Windows and Linux (using
Maven-1.0.2). The shared ../project-common.xml does define the
<groupId> correctly. Looks like this pattern is used for all the
directories/modules, not just for excalibur-pool/lifecycle.
Wonder why it worked one way for me and another for you! Anybody else
have any idea on how it should work?
Maven 1.1 should have something to do with it. It might be stricter
about the <id> vs. the groupId/artifactId split.
Instead of defining <id> in those project.xmls, use <artifactId> so that
it will respect it properly in all versions.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
