Message: The following issue has been closed.
Resolver: dion gillard Date: Sun, 29 Jun 2003 12:50 PM jar and ejb types are added to the dependency classpath now --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-512 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-512 Summary: EJB Dependencies are not added to classpath Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: 5 minutes Estimate: 0 minutes Project: maven Components: core Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 22 Jun 2003 10:38 PM Updated: Sun, 29 Jun 2003 12:50 PM Description: Hi Folks, I'm using beta-9 sucessfully. A minor problem leads me to a new question: How does maven assebles maven.depedency.classpath? For instance the following dependencies _won't_ work with java:compile: <dependency> <id>jPortal-ejb</id> <version/> <type>ejb</type> <jar>jPortal-ejb-0.6.1.jar</jar> </dependency> <dependency> <id>jPortal-security</id> <version/> <type>ejb</type> <jar>jPortal-security-0.1.5.jar</jar> </dependency> It seems that java:compile will take care only on assemblies under jar/ and not under the type you mave configure. This coulde be very usefull if you try to assemble a modular enterprise application. Or is this against a strategy the maven.dependecy.classpath follows? Thx Toby --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]