ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47002] New: junitreport: expose classpath of internal XSLTProcess task
Date Wed, 08 Apr 2009 21:25:07 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47002

           Summary: junitreport: expose classpath of internal XSLTProcess
                    task
           Product: Ant
           Version: 1.7.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Optional Tasks
        AssignedTo: notifications@ant.apache.org
        ReportedBy: Martin.vGagern@gmx.net


junitreport does create an internal xslt task to format its report. It doesn't
expose most of the configuration options of that task, though. In particular,
it does not allow the classpath to be specified.

I've been writing a build.xml relying only on ant core, and fetching optional
tasks along with their dependency libs through ivy. I <taskdef>ed junitreport
to its implementing class with a suitable classpath, but still got a
ClassNotFoundException because XSLTProcess couldn't find its TraXLiaison.

As XSLTProcess itself is core, it was loaded using the main ant classloader,
not the one used to load the junit classes like XMLResultAggregator. That class
loader didn't know about my additional libs, so adding ant-trax to the
classpath used when redefining the jnitreport task didn't help at all.

While some cleaner solution to load tasks on the fly would be desirable, and
I'll write a separate bug report about this, the quick solition would be to
provide some nested classpath element, maybe as a child of the report element.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message