If I think about this with my Maven hat on, a discrepancy arises.
groupId: commons-logging
artifactId: commons-logging artifactId: commons-logging-api
As such these would/should be two separate projects within the commons-logging group. Each having a separate project.xml with the same groupId and different artifactId's. The source would be in separate directories and "commons-logging" would be dependent on "commons-logging-api"
-Mark
Stefan Bodewig wrote:
On Fri, 14 May 2004, Brett Porter <[EMAIL PROTECTED]> wrote:
Sorry... I didn't realise that gump had a notion of a project that
produces multiple artifacts.
Hmm, commons-logging is built by Maven. Its Ant build file produces two jars, commons-logging.jar and commons-logging-api.jar - how does Maven deal with this? Are these two separate projects? Or a group of two artifacts? This is the case we need to get mapped when running Gump.
Stefan
--------------------------------------------------------------------- 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]
