Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-158 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-158 Summary: Busted taskdefs in maven.xml Type: Bug Status: Assigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Component: core Versions: 1.0-beta-8 Assignee: Jason van Zyl Reporter: James CE Johnsom Created: Fri, 22 Nov 2002 10:17 AM Updated: Fri, 22 Nov 2002 10:17 AM Environment: Linux, jsdk 1.4.0-01 Description: The specific problem is with trying to define a junit taskdef in maven.xml. The classloader doesn't get the junit jar into the classpath because we haven't invoked anything in the test plugin which "owns" that jarfile (even though project.xml requsts junit*jar to be in the root classloader). To quote from a conversation between myself and Bob: (10:29:51) bob: so, to boil it down... (10:30:08) bob: a taskdef in maven.xml can't get its own jar loaded into [root] like the plugins do. (10:30:32) jcej: Even though project.xml specifies the jar *and* does the <properties> thing to stuff it into [root] (10:30:34) bob: a project's project.xml should be inspected, just like plugins' project.xml, to find extra jars to put in the forehead loader. (10:30:41) jcej: Exactly. (10:30:47) bob: so, the bug is we ignore the project's <properties> stuff. (10:30:53) jcej: Apparently. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.werken.com/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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
