I've done a bit of tidying, defragging etc on my machine and have got
it down to approx 30 mins. Sometimes a little less sometimes a little
more. Better but still too long and no where near the kind of time
Luciano is getting.
One of the outstanding issues is...
[INFO] Apache Tuscany SCA All-in-o
On Fri, Nov 20, 2009 at 9:20 AM, Simon Laws wrote:
> I've done a bit of tidying, defragging etc on my machine and have got
> it down to approx 30 mins. Sometimes a little less sometimes a little
> more. Better but still too long and no where near the kind of time
> Luciano is getting.
>
> One of t
>
> I agree that needs to happen, but its not great that it would further
> add to the already excessive build time and we've only just moved the
> otest out of trunk as it was a bit of a pain with the way they use
> externals. I can think of some things we could try to alleviate those
> issues:
>
>
> A comment on that is that if there are different configurations for
> releases and regular builds then theres a good chance they will get
> out of sync and we dont notice the difference until a release is being
> reviewed so we lose a lot of the point of testing the distribution.
> Thats exactl
On Fri, Nov 20, 2009 at 10:10 AM, Simon Laws wrote:
>>
>> A comment on that is that if there are different configurations for
>> releases and regular builds then theres a good chance they will get
>> out of sync and we dont notice the difference until a release is being
>> reviewed so we lose a lo
> I think it would be good to wait till there are some official final
> published specs if thats not going to be too far away, i heard that
> may happen around February which sounds ok.
+1, I wasn't suggesting otherwise.
>Doing a 2.0 release before
> any specs are final seems premature, and there
> And I agree with all that too. The itest\distribution\bin-distro-unzip
> unzips the zip anyway so it would be simpler to just replace that
> itest with dir. Where it starts to go wrong though
> is if there is separate assembly plugin bin.xml files, one for just
> the dir and another for dir, zip
The assembly tests now run completely cleanly for me. Thanks for the
update mike.
Rather strangely though, after svn up for the tests and a clean build
of everything I got several failures in the assembly tests. On the
second run they all ran through?
Simon
Did anyone ever find any more on this problem? I get it too, it seems
a bit random and happens on different modules. It only seems to happen
for me when running a build from the top, building modules, itests,
samples etc separately is fine.
...ant
On Tue, Nov 17, 2009 at 6:46 PM, Raymond Feng
I got a completely clean 2.x build this morning for the first time in
a while. I'll set off another one over lunch to see if I can
replicate.
Simon
Spoke too soon! On the repeat run it came back :-(
Simon
I wanted to see if I could run the 1.x and 2.x runtimes in the same
JVM at the same time. Given that we have reused class and package
names in 2.x the only way I could think of doing it was by using OSGi.
So I built a single bundle out of (a subset of) the 1.x source and
installed it in OSGi alongs
Ok by me. I don't have any big changes outstanding at the moment.
Simon
NPE in XSDModelResolver when many schemas
-
Key: TUSCANY-3378
URL: https://issues.apache.org/jira/browse/TUSCANY-3378
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Af
[
https://issues.apache.org/jira/browse/TUSCANY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780615#action_12780615
]
Martin Clough commented on TUSCANY-3378:
The problem is caused because the facade
[
https://issues.apache.org/jira/browse/TUSCANY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Clough updated TUSCANY-3378:
---
Attachment: TUSCANY-3378.patch
A patch to XSDModelResolver with test case.
> NPE in XSDMod
[
https://issues.apache.org/jira/browse/TUSCANY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Clough updated TUSCANY-3378:
---
Patch Info: [Patch Available]
> NPE in XSDModelResolver when many schemas
> ---
[
https://issues.apache.org/jira/browse/TUSCANY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Clough updated TUSCANY-3379:
---
Attachment: TUSCANY-3379.patch
Patch JDKLoggingPolicyProcessor.java
> useParentHandlers in
useParentHandlers in JDKLoggingPolicy cannot be set
---
Key: TUSCANY-3379
URL: https://issues.apache.org/jira/browse/TUSCANY-3379
Project: Tuscany
Issue Type: Bug
Components: Java SCA
Can I assume that we only want to support the co-existence of 1.x and 2.x in
the same JVM under OSGi?
I agree that we need to filter out META-INF/services/... from 1.x bundles.
There are a few options:
1) Based on a special header in the OSGi MF, such as:
SCA-Spec-Version: 1.0 (for osoa)
SCA-
> Can I assume that we only want to support the co-existence of 1.x and 2.x in
> the same JVM under OSGi?
Safe assumption for now.
> 1) Based on a special header in the OSGi MF, such as:
> SCA-Spec-Version: 1.0 (for osoa)
> SCA-Spec-Version: 1.1 (for oasis)
>
> 2) Based on an attribute of each en
After much messing about the solution to this seems to be to replace
the maven-antrun-plugin with the exec-maven-plugin. Not sure what's
actually behind the problem or, indeed, why it just started to happen
all of a sudden.
Simon
Could it be introduced by something this is recently added to the build,
such as the shades? I'm trying to isolate now.
--
From: "Simon Laws"
Sent: Friday, November 20, 2009 9:22 AM
To: ;
Subject: Re: [2.x] Strange build errors
After much messi
Quite possibly. I just committed my fix. Feel free to revert if you
find what causes the original problem.
This may be of some help. I found that I could comment everything out
in the build before itest/distribution and still get the error when
compiling from the top level. Made life a little easi
Your fix assumes there is an "ant" executable installed on the path. I don't
think it is safe.
Thanks,
Raymond
--
From: "Simon Laws"
Sent: Friday, November 20, 2009 10:04 AM
To:
Subject: Re: [2.x] Strange build errors
Quite possibly. I just com
The problem is now fixed under [1]. I'll revert your changes.
Apparently, web-javascript-dojo module is missing a workaround for [2].
[1] http://svn.apache.org/viewvc?rev=882681&view=rev
[2] http://jira.codehaus.org/browse/MNG-1323
Thanks,
Raymond
---
The SCA project source has moved to a new location in SVN.
For SCA 1.x, which is based on the OSOA SCA Specifications 1.0, you
can find all the code (trunk, branches, tags, contrib) at [1], the SCA
1.x
trunk is available at [2].
[1] https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/
[2] https
On Fri, Nov 20, 2009 at 6:32 AM, Simon Laws wrote:
> Ok by me. I don't have any big changes outstanding at the moment.
>
> Simon
>
Done. I have also updated Website, 2.x development guide and posted in
Tuscany blog a summary of the recent changes.
Please let me know if you find any issues, I'll
[
https://issues.apache.org/jira/browse/TUSCANY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-3378:
-
Assignee: Raymond Feng
> NPE in XSDModelResolver when many schemas
> --
[
https://issues.apache.org/jira/browse/TUSCANY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-3379:
-
Assignee: Raymond Feng
> useParentHandlers in JDKLoggingPolicy cannot be set
>
30 matches
Mail list logo
