Hi David,
That last build failure http://build.eclipse.org:7777/dashboard/tab/build/detail/jaxws-R0.5-I
Is it a build environment problem? Looking through the logs i found a stacktrace here: http://build.eclipse.org:7777/dashboard/tab/build/download/artifacts/jaxws-R0.5-I/log20100121001022.xml/I-I20100121001022-20100121001022/testResults/consolelogs/testLogs/org.eclipse.jst.ws.cxf.tests.AllTestsSuite.output.txt
All units tests are running fine locally in 3.6M4.
Shane
To: wtp-incubator-dev@xxxxxxxxxxx Subject: RE: [wtp-incubator-dev] JAX-WS Build failure From: david_williams@xxxxxxxxxx Date: Tue, 19 Jan 2010 00:46:04 -0500
Is it noon yet? :)
Guess you've noticed they are fixed
now. One problem was a simple typo. The other was the (usual) complication
of trying to build a subset of WTP, while using WTP as a prereq, which
already contains what you are trying to build.
I've documented that issue and fix in
bug 300015.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=300015
From:
| shane clarke <shane_clarke@xxxxxxxxxxx>
|
To:
| <wtp-incubator-dev@xxxxxxxxxxx>
|
Date:
| 01/18/2010 09:06 AM
|
Subject:
| RE: [wtp-incubator-dev] JAX-WS Build
failure
|
Sent by:
| wtp-incubator-dev-bounces@xxxxxxxxxxx |
Hi David,
Those pre-reqs have been there for a good while.
Now I did change the 'javax.xml.soap' and 'org.apache.xerces' dependencies
from import-package to require-bundle after the first build failure yesterday
just to test if it made any difference.
All 3 dependencies are in WTP itself.
The error was not flagged in the last WTP 3.2.0 I-Build and the changes
i made are all present and correct there.
Thanks for your help,
Shane
To: wtp-incubator-dev@xxxxxxxxxxx
Subject: Re: [wtp-incubator-dev] JAX-WS Build failure
From: david_williams@xxxxxxxxxx
Date: Mon, 18 Jan 2010 08:36:00 -0500
Thanks for letting me know (I saw it breaking, but figured it was something
you were doing, so I didn't look at it, so, seriously, thanks for asking).
I don't be able to "dive deep" into this until this afternoon
(Eastern time) but here's some thoughts.
Were these recently added as pre-reqs? Or, did they "break suddenly"?
If the former, where are they expected to come from? Another pre-req package,
like WTP itself? If not, you probably have to add them to a feature, similar
to others in org.eclipse.jst.ws.jaxws.feature:
<plugin
id="javax.xml.bind"
download-size="0"
install-size="0"
version="2.1.9.qualifier"
unpack="false"/>
<plugin
id="javax.xml.stream"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
If they were working and suddenly broke, then I might have changed some
pre-req version of WST or something such that its currently incorrect.
(incorrect version, or content ... I don't recall your prereqs right off,
and will look at that around noon.
Thanks,
From:
| shane clarke <shane_clarke@xxxxxxxxxxx>
|
To:
| <wtp-incubator-dev@xxxxxxxxxxx>
|
Date:
| 01/18/2010 02:11 AM
|
Subject:
| [wtp-incubator-dev] JAX-WS Build failure
|
Sent by:
| wtp-incubator-dev-bounces@xxxxxxxxxxx |
Hi David,
The build output states that the org.eclipse.jst.ws.jaxws.core bundle failed
to resolve due to missing required plug-ins:
org.eclipse.jst.ws [1.0.304, 1.1.0)
javax.xml.soap [1.2.0, 1.3.0)
org.apache.xerces [2.9.0, 3.0.0)
But those version ranges should be fine.
Any ideas what might be causing this?
Thanks,
Shane
Windows 7: Find the right PC for you. Learn
more._______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
Windows 7: Simplify what you do everyday.
Find
the right PC for you._______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
New Windows 7: Find the right PC for you. Learn more.
|