I used
maven ant tasks to download the artifacts for the Seam test.
In older versions of maven-ant-tasks.jar the versionsId stuff isn't
implemented. QA lab machines have an older version of
maven-ant-tasks.jar (2.0.5 IIRC) in the ant userlib directory. For some
reason sometimes ant uses the one we tell it to (from thirdparty) and
sometimes from ant's userlib dir. I couldn't isolate why.
I got round this on the Seam Hudson builds by running ant with the
-nouserlib option (which means it always uses the up to date version).
Ales Justin wrote:
Guess they are ran on different machines with different ant env.
Since Pete can't really fully determine the cause of it.
Scott M Stark wrote:
> We have had successful test runs with the seam.xml previously, 254 for
> example:
>
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
>
>
> _jars-seam:
> [copy] Copying 5 files to
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
>
>
>
> Scott M Stark wrote:
>> The build has failed due to the seam.xml section. Must be due to an ant
>> version problem:
>>
>> BUILD FAILED
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
>>
>> The following error occurred while executing this line:
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
>>
>> The <urn:maven-artifact-ant:dependencies> type doesn't support the
>> "versionsid" attribute.
>>
>> testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
>> what ant would be used for the build?
>>
>> Dimitris Andreadis wrote:
>>> Trunk is now building again, and there is an in-progress run that needs
>>> another 5 hours:
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> Can we get a status of the last tasks?
>>>
>>>
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
>>> (Alexey/Scott)
>>>
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
>>>
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>>>
>>> ThomasD made also a last minute update to juddi/scout. This is being
>>> tested now in the current test run, but I don't know how/if it
>>> affects TCK.
>>>
>>> He also reported the following regression. Was AbstractAnnotationImpl
>>> somehow moved?
>>>
>>> NoClassDefFoundError:
>>> org/jboss/metadata/annotation/AbstractAnnotationImpl
>>>
http://jira.jboss.com/jira/browse/JBAS-5093
>>>
>>> We need to wrap-up, ASAP.
>>>
>>> /D
>>>
>>> Scott M Stark wrote:
>>>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>>>> testsuite run to branch.
>>>>
>>>> Scott M Stark wrote:
>>>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>>>> failures. Still working on whether the ManagedDeployment problem
with
>>>>> the deploy/messaging directory is an api problem that needs to be
>>>>> fixed.
>>>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>>>> minimum.
>>>>>
>>>>> Rajesh Rajasekaran wrote:
>>>>>> Yes. That's right. The build was still running.
>>>>>> The testsuite run completed but before publishing and email
>>>>>> notification
>>>>>> someone had aborted.
>>>>>> However the results are available on the internal instance.
>>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 191 failures.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development