In future versions, they will declare a relationship via the POM.
For now, there is nothing that needs to be done, except that the dependency lists will probably be shorter. See commons-logging/commons-logging-api for an example of this in practice. Cheers, Brett On 29/06/06, David Jencks <[EMAIL PROTECTED]> wrote:
I'm working on writing working poms for xmlbeans (for the benefit of projects that use xmlbeans, not to try to write an m2 build for xmlbeans). They publish a "full" jar xbean.jar and an "interface" jar xmlpublic.jar that contains a subset of xbean.jar I believe the idea is that you can compile your program using xmlpublic.jar to make sure you aren't poking your nose in where you shouldn't, and then run it with xbean.jar. What is the best way to express this using m2? Do the xmlbeans poms need to include any information regarding this? many thanks david jencks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Apache Maven - http://maven.apache.org "Better Builds with Maven" book - http://library.mergere.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
