Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Subject: DO NOT REPLY [Bug 34867]  New:  -
    Deploying an ear to weblogic seems to break junitreport only in ant 1.6.3
Message-Id: <20050511145551.A92832E2@ajax.apache.org>
Date: Wed, 11 May 2005 16:55:51 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34867>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34867

           Summary: Deploying an ear to weblogic seems to break junitreport
                    only in ant 1.6.3
           Product: Ant
           Version: 1.6.3
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P3
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: apache@nimmaj.com


We're deploying an ear to weblogic 8.1 (have tried both SP3 and SP4).  We run
some functional tests against that deployment which are driven by junit.  The
results of these tests are generated using junit report.

We can do this using ant 1.6.2 but upgrading to ant 1.6.3 gives us the following
error:

/home/jammin/src/aol/ordermanagement/build2/functional.build.xml:58: Could not
find a valid processor version implementation from
weblogic.xml.jaxp.RegistrySAXTransformerFactory
        at
org.apache.tools.ant.taskdefs.optional.junit.Xalan2Executor.getProcVersion(Xalan2Executor.java:67)
        at
org.apache.tools.ant.taskdefs.optional.junit.XalanExecutor.newInstance(XalanExecutor.java:88)
        at
org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.transform(AggregateTransformer.java:144)
        at
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.execute(XMLResultAggregator.java:139)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at org.apache.tools.ant.Main.runBuild(Main.java:668)
        at org.apache.tools.ant.Main.startAnt(Main.java:187)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

We commented out the WLDeploy part of the deployment task and then this problem
goes away with 1.6.3.

You'll notice that it's suddenly trying to use a weblogic SAX factory. So we
think that something's hanging over from the wldeply task.

That it works in ant 1.6.2 makes us feel this is an ant problem.

No idea whether it will help but we've pasted a few targets after this so that
you can see what we're doing...

Thanks

------

    <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
        <classpath
path="/home/jammin/apps/bea814/weblogic81/server/lib/weblogic.jar"/>
    </taskdef>

    <target name="deploy-ear" depends="assemble-ear">
        <wldeploy action="deploy"
            source="${ear_file_path}"
            name="bbms"
            user="${wl_admin_username}"
            password="${wl_admin_password}"
            verbose="true"
            adminurl="t3://${wl_admin_listen_address}:${wl_admin_listen_port}"
            debug="true"
            targets="${wl_deploy_target}" upload="true"/>
    </target>

    <target name="test-functional" depends="run-functional-tests,
format-functional-reports">
        <fail if="functional.fail" message="Functional test failure"/>
    </target>

    <target name="format-functional-reports" if="functional.fail">
        <junitreport todir="${functional_test_reports_dir}">
            <fileset dir="${functional_test_results_dir}" includes="*.xml"/>
            <report format="noframes" todir="${functional_test_reports_dir}"/>
        </junitreport>
    </target>

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org