In local builds I'm seeing a number of failures. The first is in
itest/import-export
java.lang.IllegalStateException:
org.apache.tuscany.sca.contribution.processor.ContributionResolveException:
org.apache.tuscany.sca.contribution.processor.ContributionResolveException:
Processing composite {ht
Did an update this morning and am getting a stack of failures. E.g.
binding-rmi, implementation-node-runtime node-launcher-equinox etc.
Before I go into detail, is it just me?
Simon
On Fri, May 15, 2009 at 8:54 AM, Simon Laws wrote:
> Did an update this morning and am getting a stack of failures. E.g.
> binding-rmi, implementation-node-runtime node-launcher-equinox etc.
> Before I go into detail, is it just me?
>
Yes ;)
Well all of those are working ok for me after updating
On Fri, May 15, 2009 at 9:23 AM, ant elder wrote:
> On Fri, May 15, 2009 at 8:54 AM, Simon Laws wrote:
>> Did an update this morning and am getting a stack of failures. E.g.
>> binding-rmi, implementation-node-runtime node-launcher-equinox etc.
>> Before I go into detail, is it just me?
>>
>
> Ye
On Fri, May 15, 2009 at 9:47 AM, Simon Laws wrote:
> On Fri, May 15, 2009 at 9:23 AM, ant elder wrote:
>> On Fri, May 15, 2009 at 8:54 AM, Simon Laws
>> wrote:
>>> Did an update this morning and am getting a stack of failures. E.g.
>>> binding-rmi, implementation-node-runtime node-launcher-equi
I updated and set a build off and am seeing the following. It's the
usual suspects usually caused by stuff being moved about. Is someone
about to commit fixes or should I look into it?
[INFO]
[INFO] Error for project: Apache
The 1.x night build on Hudson is almost there, only the fails below
remaining which look like the same dojo install issue fixed for
another sample in r802314 I'll plod through them but if any one wants
to help please go right ahead.
...ant
INFO]
I'm getting a clean build presently, the Hudson build also looks ok
other than some issue with the store sample.
...ant
On Tue, Nov 16, 2010 at 12:36 PM, Simon Laws wrote:
> I updated and set a build off and am seeing the following. It's the
> usual suspects usually caused by stuff being move
On Tue, Nov 16, 2010 at 1:47 PM, ant elder wrote:
> I'm getting a clean build presently, the Hudson build also looks ok
> other than some issue with the store sample.
>
> ...ant
>
> On Tue, Nov 16, 2010 at 12:36 PM, Simon Laws
> wrote:
>> I updated and set a build off and am seeing the followi
This is what I'm seeing this morning following a 2.x update and
"clean install". Haven't looked at the details yet.
INFO]
INFO] Error for project: Apache Tuscany Async Integration Tests SCA Binding Map
er (during install)
IN
I can look into this in the morning PST time.
On Mon, Aug 10, 2009 at 11:19 PM, ant elder wrote:
> The 1.x night build on Hudson is almost there, only the fails below
> remaining which look like the same dojo install issue fixed for
> another sample in r802314 I'll plod through them but if any one
On Thu, Dec 9, 2010 at 9:16 AM, Simon Laws wrote:
> This is what I'm seeing this morning following a 2.x update and
> "clean install". Haven't looked at the details yet.
>
> INFO]
> INFO] Error for project: Apache Tuscany As
On Thu, Dec 9, 2010 at 10:35 AM, Simon Laws wrote:
> On Thu, Dec 9, 2010 at 9:16 AM, Simon Laws wrote:
>> This is what I'm seeing this morning following a 2.x update and
>> "clean install". Haven't looked at the details yet.
>>
>> INFO]
>> ---
On Thu, Dec 9, 2010 at 10:38 AM, ant elder wrote:
> On Thu, Dec 9, 2010 at 10:35 AM, Simon Laws wrote:
>> On Thu, Dec 9, 2010 at 9:16 AM, Simon Laws wrote:
>>> This is what I'm seeing this morning following a 2.x update and
>>> "clean install". Haven't looked at the details yet.
>>>
>>> INFO]
It all seems fine now and the Hudson build is passing:
https://hudson.apache.org/hudson/job/Tuscany-2x/13/
...ant
On Thu, Dec 9, 2010 at 11:47 AM, Simon Laws wrote:
> On Thu, Dec 9, 2010 at 10:38 AM, ant elder wrote:
>> On Thu, Dec 9, 2010 at 10:35 AM, Simon Laws
>> wrote:
>>> On Thu, Dec
I have been trying to build 1.x from an empty local repo. On
dowloading some artefacts, the pom files were invalid, they contained
html indicating the artefacts should be found on the java.net maven 1
repo. The artefacts in question are
jaxws-rt-2.1.3
jaxb-xjc-2.1.6
jaxwstools-2.1.3
I managed to g
On Thu, Dec 10, 2009 at 3:05 AM, kelvin goodson wrote:
> I have been trying to build 1.x from an empty local repo. On
> dowloading some artefacts, the pom files were invalid, they contained
> html indicating the artefacts should be found on the java.net maven 1
> repo. The artefacts in question ar
On Mon, Dec 14, 2009 at 10:11 PM, Luciano Resende wrote:
> On Thu, Dec 10, 2009 at 3:05 AM, kelvin goodson
> wrote:
>> I have been trying to build 1.x from an empty local repo. On
>> dowloading some artefacts, the pom files were invalid, they contained
>> html indicating the artefacts should be
On Tue, Dec 15, 2009 at 7:02 AM, ant elder wrote:
> On Mon, Dec 14, 2009 at 10:11 PM, Luciano Resende
> wrote:
>> On Thu, Dec 10, 2009 at 3:05 AM, kelvin goodson
>> wrote:
>>> I have been trying to build 1.x from an empty local repo. On
>>> dowloading some artefacts, the pom files were invalid
On Tue, Dec 15, 2009 at 3:20 PM, Luciano Resende wrote:
> On Tue, Dec 15, 2009 at 7:02 AM, ant elder wrote:
>> On Mon, Dec 14, 2009 at 10:11 PM, Luciano Resende
>> wrote:
>>> On Thu, Dec 10, 2009 at 3:05 AM, kelvin goodson
>>> wrote:
I have been trying to build 1.x from an empty local re
On Wed, Dec 16, 2009 at 3:38 AM, ant elder wrote:
> Various errors about tuscany dependencies not being available as they
> hadn't been built yet, or some errors when snapshot tuscany
> dependencies got found in the snapshot repo but they're back level,
> I've now done a deploy of the latest snaps
In answer to the inter-module dependency point I just built 1.6 (which
I guess is still very much like 1.x) with mvn -fae clean install and I
got a full build but for the following (this is not with a clean
repo)...
[INFO]
[
Can you try to specify a version such as 1.1.1 for exec-maven-plugin in the
pom?
Thanks,
Raymond
--
From: "Simon Laws"
Sent: Monday, January 04, 2010 5:37 AM
To:
Subject: Re: 1.x build failures from refesh repo - maven poms problem
Ok, have made the fix and got a clean build so will check in. Ant has
mentioned that there is some maven magic that will tell us when we
have unversioned dependencies (which is what caused this issue). So am
hoping he'll post on the details.
Simon
On Tue, Jan 5, 2010 at 11:21 AM, Simon Laws wrote:
> Ok, have made the fix and got a clean build so will check in. Ant has
> mentioned that there is some maven magic that will tell us when we
> have unversioned dependencies (which is what caused this issue). So am
> hoping he'll post on the detail
Ah, OK thanks Ant.
Simon
On Tue, Jan 5, 2010 at 2:02 PM, ant elder wrote:
> On Tue, Jan 5, 2010 at 11:21 AM, Simon Laws wrote:
>> Ok, have made the fix and got a clean build so will check in. Ant has
>> mentioned that there is some maven magic that will tell us when we
>> have unversioned dependencies (which is what caus
On Tue, Jan 5, 2010 at 6:40 PM, ant elder wrote:
> On Tue, Jan 5, 2010 at 2:02 PM, ant elder wrote:
>> On Tue, Jan 5, 2010 at 11:21 AM, Simon Laws
>> wrote:
>>> Ok, have made the fix and got a clean build so will check in. Ant has
>>> mentioned that there is some maven magic that will tell us w
Build failures in itests when using JDK 5
-
Key: TUSCANY-3706
URL: https://issues.apache.org/jira/browse/TUSCANY-3706
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.6
, r1006270 and r1022053 in the 1.6.1
branch and revisions r1027534, r1027538, r1027540 and r1027541 in the 1.x trunk.
> Build failures in itests when using JDK 5
> -
>
> Key: TUSCANY-3706
> URL: https://issues.apache.
Andrew Potter created TUSCANY-4053:
--
Summary: Build failures for trunk/testing/itest/* with IBM JDK 7
Key: TUSCANY-4053
URL: https://issues.apache.org/jira/browse/TUSCANY-4053
Project: Tuscany
[
https://issues.apache.org/jira/browse/TUSCANY-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Potter closed TUSCANY-4053.
--
Resolution: Fixed
Committed, thanks Ant
> Build failures for trunk/test
32 matches
Mail list logo
