On Thu, Sep 8, 2011 at 1:53 PM, ant elder wrote:
> As an FYI I've brought up the JMS compliance test suite runner in
> trunk and included it in the build. Thats in preparation for
> submitting the evidence to OASIS that Tuscany has a complaint impl.
> Unfortunately three tests aren't running corre
As an FYI I've brought up the JMS compliance test suite runner in
trunk and included it in the build. Thats in preparation for
submitting the evidence to OASIS that Tuscany has a complaint impl.
Unfortunately three tests aren't running correctly now, they did used
to work, so i need to fix those be
Aug 18 08:12:00 2011
>>>> New Revision: 1159076
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=1159076&view=rev
>>>> Log:
>>>> Add exclude for 4020 test thats been failing for ages
>>>>
>>>> Modified:
>>&g
t;> URL: http://svn.apache.org/viewvc?rev=1159076&view=rev
>>> Log:
>>> Add exclude for 4020 test thats been failing for ages
>>>
>>> Modified:
>>> tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>>>
>>> Modifie
Add exclude for 4020 test thats been failing for ages
>>
>> Modified:
>> tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>>
>> Modified: tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>> URL:
>> http://svn.apache.o
Add exclude for 4020 test thats been failing for ages
>>
>> Modified:
>> tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>>
>> Modified: tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>> URL:
>> http://svn.apache.o
tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
>
> Modified: tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.xml
> URL:
> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/testing/compliance-tests/policy/pom.x
> Policy appliesTo not correctly specified in policy compliance tests
> ---
>
> Key: TUSCANY-3893
> URL: https://issues.apache.org/jira/browse/TUSCANY-3893
>
[
https://issues.apache.org/jira/browse/TUSCANY-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-3893:
---
Assignee: Simon Laws
> Policy appliesTo not correctly specified in policy compliance te
been fixed to ensure that all @appliesTo
XPath values use sca: prefix for any and all SCA elements, as of 20 July 2011
> Policy appliesTo not correctly specified in policy compliance tests
> ---
>
> K
[
https://issues.apache.org/jira/browse/TUSCANY-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-3893:
Summary: Policy appliesTo not correctly specified in policy compliance
tests (was: Policy
Policy applies to no correctly specified in policy compliance tests
---
Key: TUSCANY-3893
URL: https://issues.apache.org/jira/browse/TUSCANY-3893
Project: Tuscany
Issue Type
It turns out that there was already a surefire plugin config on the
test module which was setting some memory settings, but if i removed
them it all started working fine. I've committed that change and
kicked off a Hudson build to see if that still works, but if these
settings break it for anyone e
Thats a good point, i shall go play around with surefire config in the
tuscany-compliance-test-java-caa to see if that helps.
...ant
On Mon, May 9, 2011 at 4:45 PM, Raymond Feng wrote:
> The maven option won't help as surefire plugin forks the jvm. Try to
> configure the surefire plugin.
>
>
The maven option won't help as surefire plugin forks the jvm. Try to configure
the surefire plugin.
Raymond Feng
Sent from my iPhone
On May 9, 2011, at 4:41 AM, ant elder wrote:
> On Mon, May 9, 2011 at 11:51 AM, Simon Laws wrote:
>> On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
>>> Anot
On Mon, May 9, 2011 at 11:51 AM, Simon Laws wrote:
> On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
>> Another issue i have getting the build running on a new machine is
>> that the Java CAA compliance test suite always fails with an
>> OutOfMemoryError. It doesn't matter how I run that, in a
On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
> Another issue i have getting the build running on a new machine is
> that the Java CAA compliance test suite always fails with an
> OutOfMemoryError. It doesn't matter how I run that, in a full build
> the suite on its own, or what memory setting
Another issue i have getting the build running on a new machine is
that the Java CAA compliance test suite always fails with an
OutOfMemoryError. It doesn't matter how I run that, in a full build
the suite on its own, or what memory setting i use it always ends up
getting the following exception in
[
https://issues.apache.org/jira/browse/TUSCANY-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-3781.
--
Resolution: Fixed
Fixed now
> The Java CAA compliance tests keep failing on the Hudson bu
058897&view=rev
> Log:
> JCAA still seems to be loading a logging configuration from somewhere that
> requires Log4J. I can't find it so to get the build going I'll add the
> dependency.
>
> Modified:
> tuscany/sca-java-2.x/trunk/testing/compliance-tests/j
Mmm, i've not debugged it at all but the fails I see are due to loop in
xmlschema code so r1043206 seems suspicious.
...ant
On Wed, Dec 8, 2010 at 10:38 AM, Simon Laws wrote:
> On Wed, Dec 8, 2010 at 9:06 AM, ant elder wrote:
> > The versions of the xsd's that are planned to be final ones ha
On Wed, Dec 8, 2010 at 9:06 AM, ant elder wrote:
> The versions of the xsd's that are planned to be final ones have just been
> published by OASIS so we should move up to them which would also help test
> them for OASIS, see:
> http://lists.oasis-open.org/archives/sca-assembly/201012/msg0.html
The versions of the xsd's that are planned to be final ones have just been
published by OASIS so we should move up to them which would also help test
them for OASIS, see:
http://lists.oasis-open.org/archives/sca-assembly/201012/msg0.html
...ant
On Wed, Dec 8, 2010 at 6:42 AM, Raymond Feng
I'm trying to fix it ...
Raymond Feng
rf...@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
After debugging into the problem, I found out the OASIS OpenCSA XSDs for SCA
specs (pulled into Tuscany under assmbly-xsd project) are inconsistent. For
example,
sca-core-1.1-cd05-rev1.xsd includes sca-policy-1.1-cd03-rev1.xsd
sca-policy-1.1-cd03-rev1.xsd includes sca-core-1.1-cd06.xsd (doesn't
been commented out. It's more important to me
to be running the tests and have hudson fail now and again. I'd be happy to
create a profile that hudson understands if that's what people want and in lieu
of getting Husdon fixed (or setting it to only run Tuscany build on Solaris).
> T
The Java CAA compliance tests keep failing on the Hudson build
--
Key: TUSCANY-3781
URL: https://issues.apache.org/jira/browse/TUSCANY-3781
Project: Tuscany
Issue Type: Bug
--
> [INFO]
>
> [INFO] Building Apache Tuscany SCA Specification Compliance Tests Java CAA
> [INFO] task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean {execu
On Fri, Oct 29, 2010 at 2:04 PM, Brent Daniel wrote:
> I'm a little confused. It looks like the runtime is behaving
> correctly, but for some reason it's still looking for the old error
> message. The error messages were updated in both
> compliance-tests/assembly/src
I'm a little confused. It looks like the runtime is behaving
correctly, but for some reason it's still looking for the old error
message. The error messages were updated in both
compliance-tests/assembly/src/test/resources and in
tuscany-test-runner/src/test/resources, so I'm not
On Thu, Oct 28, 2010 at 5:16 PM, wrote:
> Author: bdaniel
> Date: Thu Oct 28 16:16:05 2010
> New Revision: 1028369
>
> URL: http://svn.apache.org/viewvc?rev=1028369&view=rev
> Log:
> TUSCANY-3709 re-enable excluded compliance tests
>
> Modified:
> tuscany/sca
On Wed, Oct 13, 2010 at 12:44 PM, Simon Laws wrote:
> On Wed, Oct 13, 2010 at 12:39 PM, Simon Laws
> wrote:
>> On Wed, Oct 13, 2010 at 12:31 PM, ant elder wrote:
>>> Whats the status of the compliance tests in trunk? I've managed to get
>>> a build throu
On Wed, Oct 13, 2010 at 12:39 PM, Simon Laws wrote:
> On Wed, Oct 13, 2010 at 12:31 PM, ant elder wrote:
>> Whats the status of the compliance tests in trunk? I've managed to get
>> a build through all the way to the java-ci tests without failing which
>> is further t
On Wed, Oct 13, 2010 at 12:31 PM, ant elder wrote:
> Whats the status of the compliance tests in trunk? I've managed to get
> a build through all the way to the java-ci tests without failing which
> is further than its got for ages, that fails with missing dependencies
> and c
Whats the status of the compliance tests in trunk? I've managed to get
a build through all the way to the java-ci tests without failing which
is further than its got for ages, that fails with missing dependencies
and compile errors and looking at the pom.xml its still using the old
feature (
On Wed, Oct 6, 2010 at 7:12 AM, Mike Edwards
wrote:
> On 04/10/2010 07:56, Luciano Resende wrote:
>>
>> Yes, that's what I'm doing for M5.1. For next releases, I was
>> wondering if we should have a better strategy either by working with
>> OASIS or by remo
On 04/10/2010 07:56, Luciano Resende wrote:
Yes, that's what I'm doing for M5.1. For next releases, I was
wondering if we should have a better strategy either by working with
OASIS or by removing all of the compliance tests from the final
release. It also makes me wonder if Oasis wi
That does seem a bit of a bug in the M5 release.
It feels a bit odd to me for us in Tuscany to be making releases of the
compliance tests when we didn't write them and they're not AL licensed, I
think we should push on OASIS to make proper releases of them. In the short
term if you&#x
ticed we already move into the direction of using tuscany internal
> maven repo instead of the one in ant's people account, which is good,
> but are we planning to "release these artifacts" as part of our
> official releases ? Or are we going to disable the compliance tests in
&
On Sun, Oct 3, 2010 at 11:36 PM, ant elder wrote:
> That does seem a bit of a bug in the M5 release.
>
> It feels a bit odd to me for us in Tuscany to be making releases of the
> compliance tests when we didn't write them and they're not AL licensed, I
> think we sho
tead of the one in ant's people account, which is good,
but are we planning to "release these artifacts" as part of our
official releases ? Or are we going to disable the compliance tests in
our official releases ? AFAIK, users probably care if we are compliant
or not, but they don
>
> Is there a reason we can't use the base jar any more? I'd quite like
> to if possible as this is a good way to verify it works ok. (and same
> for the node2.Node)
>
> ...ant
>
Not particularly, it just didn't work so first things first I want to
get the otests up and running in the build. Wi
On Thu, Sep 16, 2010 at 5:46 PM, wrote:
> Author: slaws
> Date: Thu Sep 16 16:46:41 2010
> New Revision: 997837
>
> URL: http://svn.apache.org/viewvc?rev=997837&view=rev
> Log:
> Switch to using the latest jcaa otests (r197).
>
> Modified:
> tuscany/sca-ja
gt; URL: http://svn.apache.org/viewvc?rev=980365&view=rev
>>> Log:
>>> Add an exclude for another test thats started to fail
>>>
>>> Modified:
>>> tuscany/sca-java-2.x/trunk/compliance-tests/java-caa/pom.xml
>>>
>>> Modified:
Add an exclude for another test thats started to fail
>>
>> Modified:
>> tuscany/sca-java-2.x/trunk/compliance-tests/java-caa/pom.xml
>>
>> Modified: tuscany/sca-java-2.x/trunk/compliance-tests/java-caa/pom.xml
>> URL:
>> http://svn.apache.org/viewvc/tusca
cany/sca-java-2.x/trunk/compliance-tests/java-caa/pom.xml
>
> Modified: tuscany/sca-java-2.x/trunk/compliance-tests/java-caa/pom.xml
> URL:
> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/compliance-tests/java-caa/po
On Wed, Jul 28, 2010 at 9:37 AM, kelvin goodson
wrote:
> ASM_10003 is fixed when running from the otests/newlayout directory
> (An expected message update only). I'm not sure what the process is
> get this update transferred to the compliance-tests directory.
>
> Kelvin.
H
ASM_10003 is fixed when running from the otests/newlayout directory
(An expected message update only). I'm not sure what the process is
get this update transferred to the compliance-tests directory.
Kelvin.
On Mon, Jul 26, 2010 at 10:11 AM, wrote:
> Author: antelder
> Date: Mon J
On Fri, May 14, 2010 at 10:40 AM, ant elder wrote:
> On Fri, May 14, 2010 at 10:05 AM, kelvin goodson
> wrote:
>> When I build with just "mvn" in the compliance-tests folder I
>> sometimes get a successful completion of the build, but with each of
>> the 4 s
On Fri, May 14, 2010 at 10:05 AM, kelvin goodson
wrote:
> When I build with just "mvn" in the compliance-tests folder I
> sometimes get a successful completion of the build, but with each of
> the 4 subprojects reporting zero tests to run. I just had an IRC chat
> with
On Fri, May 14, 2010 at 10:05 AM, kelvin goodson
wrote:
> When I build with just "mvn" in the compliance-tests folder I
> sometimes get a successful completion of the build, but with each of
> the 4 subprojects reporting zero tests to run. I just had an IRC chat
> with
When I build with just "mvn" in the compliance-tests folder I
sometimes get a successful completion of the build, but with each of
the 4 subprojects reporting zero tests to run. I just had an IRC chat
with ant, who suggested mvn clean install (guess I should have tried
that anyway, bu
turns out that the runtime
> was still going out to w3.org to get the XMLSchema DTD. I fixed that
> in r920155 and the 16 minutes for running all the compliance tests has
> dropped down to less than 4 minutes.
>
> ...ant
>
Hey, nice one!
Simon
155 and the 16 minutes for running all the compliance tests has
dropped down to less than 4 minutes.
...ant
On Wed, Mar 3, 2010 at 8:36 AM, ant elder wrote:
> Now that we have some of the compliance test suites running cleanly
> again what would people think about having them run as part of the
> full build? That seems like the best way to prevent or spot
> regressions but it would add some time to the
> extra 16 mins on the build. Then we'll have the otests starting to
>> come in from the extensions.
>>
>> I think we need to get back to this idea about having profiles. I'e a
>> core profile that does include these compliance tests. Never got round
>> to do
be a problem with Assembly/CAA/CII/Policy hooked up. An
> extra 16 mins on the build. Then we'll have the otests starting to
> come in from the extensions.
>
> I think we need to get back to this idea about having profiles. I'e a
> core profile that does include these compliance
Right, the tests are pretty much back to where they were. Failures I see are
Assembly:
6015 - TUSCANY-3481 - OASIS fix required
6033 - TUSCANY-3486 - Tuscany fix required
JCAA:
8005 & 8007 - TUSCANY-3482 - OASIS fix required
JCI:
8003 & 8012 - TUSCANY-3483 - TUSCANY fix (I think) required
Po
The failures are nearly all to do with the changes that have been made
in OASIS. Am looking at them.
Simon
se)
> testDummy(client.ASM_4002_TestCase)
>
> Tests run: 122, Failures: 10, Errors: 0, Skipped: 0
>
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
> --------
t;
> [ERROR] BUILD FAILURE
> [INFO]
> --------
> [INFO] There are test failures.
>
> Please refer to
> D:\
[INFO] There are test failures.
Please refer to D:\sca-java-2.x\compliance-tests\assembly-tests\target\surefire-
reports for the individual test results.
[INFO]
[INFO] For more information, run Maven with the -e sw
ons of going and running
> them separately... then it's a matter of getting in peoples mind that
> we should run the oTests frequently with our commits.
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.
On Tue, Mar 2, 2010 at 11:36 AM, ant elder wrote:
> Now that we have some of the compliance test suites running cleanly
> again what would people think about having them run as part of the
> full build? That seems like the best way to prevent or spot
> regressions but it would add some time to the
Now that we have some of the compliance test suites running cleanly
again what would people think about having them run as part of the
full build? That seems like the best way to prevent or spot
regressions but it would add some time to the build.
When we did this before it used svn externals whic
Pass the OASIS SCA Java EE Integration Specification V1.1 specification
compliance tests
Key: TUSCANY-2896
URL: https://issues.apache.org/jira/browse/TUSCANY-2896
Pass the OASIS SCA Spring Component Implementation V1.1 specification
compliance tests
--
Key: TUSCANY-2895
URL: https://issues.apache.org/jira/browse/TUSCANY-2895
Pass the OASIS SCA EJB Session Bean Binding V1.1 specification compliance tests
---
Key: TUSCANY-2894
URL: https://issues.apache.org/jira/browse/TUSCANY-2894
Project: Tuscany
Pass the OASIS SCA Web Services Binding V1.1 specification compliance tests
---
Key: TUSCANY-2893
URL: https://issues.apache.org/jira/browse/TUSCANY-2893
Project: Tuscany
Pass the OASIS SCA Java Component Implementation V1.1 specification compliance
tests
Key: TUSCANY-2890
URL: https://issues.apache.org/jira/browse/TUSCANY-2890
Pass the OASIS SCA JMS Binding Specification V1.1 specification compliance tests
Key: TUSCANY-2892
URL: https://issues.apache.org/jira/browse/TUSCANY-2892
Project
Pass the OASIS SCA BPEL Client and Implementation V1.1 specification compliance
tests
-
Key: TUSCANY-2891
URL: https://issues.apache.org/jira/browse/TUSCANY-2891
Pass the OASIS SCA Policy Framework V1.1 specification compliance tests
---
Key: TUSCANY-2888
URL: https://issues.apache.org/jira/browse/TUSCANY-2888
Project: Tuscany
Issue
Pass the OASIS SCA Assembly Model V1.1 specification compliance tests
-
Key: TUSCANY-2887
URL: https://issues.apache.org/jira/browse/TUSCANY-2887
Project: Tuscany
Issue
Pass the OASIS SCA Java Common Annotations and APIs V1.1 specification
compliance tests
---
Key: TUSCANY-2889
URL: https://issues.apache.org/jira/browse/TUSCANY-2889
75 matches
Mail list logo
