maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Updated: (MAVEN-158) Busted taskdefs in maven.xml
Date Wed, 31 Dec 2003 04:16:39 GMT
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Tue, 30 Dec 2003 10:14 PM
    Comment:
worth evaluating for 1.0 if not already fixed. This would probably sort out those XSLT problems
    Changes:
             Fix Version changed to 1.0-final
             Fix Version changed from 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-158&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/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: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Fix Fors:
             1.0-final
   Versions:
             1.0-beta-8

   Assignee: 
   Reporter: James CE Johnsom

    Created: Fri, 22 Nov 2002 10:17 AM
    Updated: Tue, 30 Dec 2003 10:14 PM
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.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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message