Message: The following issue has been closed.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVEN-1567 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-1567 Summary: No way to include App type dependency in classpath Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0.2 Assignee: Reporter: Havard Bjastad Created: Fri, 11 Feb 2005 8:43 AM Updated: Tue, 22 Feb 2005 12:55 AM Description: We have created a Java application, using maven-javaapp-plugin. This plugin creates an executable jar file, registered as type 'app' in Maven (and it's repository). There are two problems with this: 1. There is no way to add support for new types in Maven. When another module depends on a module of type 'app', Maven is unable to find it. Workaround: Specify the full jar file name in the dependency tag. 2. The 'app' type module is not included in the classpath of the dependent module. This is the biggest problem, as it is hardcoded in the isAddedToClasspath() method of org.apache.maven.project.Dependency that only modules of type 'jar' and 'ejb' gets added to the classpath. I have tried to modify the maven.dependency.classpath in maven.xml, but it doesn't seem to work. --------------------------------------------------------------------- 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/secure/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]
