par and ejb3 files must expose its classes to the classpath, so other modules can use them when compiling ---------------------------------------------------------------------------------------------------------
Key: MNG-1620 URL: http://jira.codehaus.org/browse/MNG-1620 Project: Maven 2 Type: Bug Components: maven-artifact Versions: 2.1 Reporter: Bruno Aranda Priority: Minor Attachments: components.diff *.par (persistence archives) and *.ejb3 packages must add its classes to the classpath, so other poms can use them when compiling. In the compatible servers, pars are exposed as jars, so no client should be used, only the par file is necessary. The solution I am attaching was proposed in the mailing list [1], so I've just created the patch in order to be included in the sources. I've seen no issue opened for this, although it was proposed in the mailing list in answer to that mail. All credit should go for Thomas Marek, Regards, Bruno [1] http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]