That's great - but I'm wondering how this works from an IP-flow point of view.
I guess that by attaching a patch to a JIRA issue one formally donates
the code to Apache.
But by merging a github pull request you take a few commits from
someone's own fork and add this to the main repo. I guess you
Proxy iTests are failing with the exception below when building on a clean
system (cleared out .m2 repository), it seems to work ok on systems that
have the required files already in the local repo.
It looks as though PAX runner is trying to download from
http://osgi.sonatype.org (which
Hi,
I think it is a pax-runner issue as the old Pax Exame (1.x) tests do fail
with the same reason.
regards, Achim
2014-03-27 19:00 GMT+01:00 Simon Gormley sgorm...@uk.ibm.com:
Proxy iTests are failing with the exception below when building on a clean
system (cleared out .m2 repository), it
David Bosschaert created ARIES-1168:
---
Summary: Proxy / Blueprint itests fail with missing Pax-Exam
dependency
Key: ARIES-1168
URL: https://issues.apache.org/jira/browse/ARIES-1168
Project: Aries
[
https://issues.apache.org/jira/browse/ARIES-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated ARIES-1168:
Attachment: springsource.repo.diff
The attached patch (springsource.repo.diff) fixed the
I ran into the same issue recently with the Blueprint itests. I was
able to work around it by adding the Springsource EBR to the
repositories and explicitly depending on
org.junit/com.springsource.org.junit/4.4.0 but I'm not sure whether
that's really the right way to fix it.
I've created
Would moving to the latest pax-exam help (v3.4) Wondering whether the two
bumps in major version number mean a lot of API breaking changes.
Cheers,
Jeremy
On 28 March 2014 10:44, David Bosschaert david.bosscha...@gmail.com wrote:
I ran into the same issue recently with the Blueprint itests. I
It definitely would help ;)
Though yes there are some API breaking changes and you'll need to rework
your POM a bit.
Still I think this switch is really worth it.
Regards, Achim
2014-03-28 11:49 GMT+01:00 Jeremy Hughes jpjhug...@gmail.com:
Would moving to the latest pax-exam help (v3.4)
There's a long discussion on the members@ list.
https://mail-search.apache.org/members/private-arch/members/201311.mbox/%3c9cc82400-9a4b-4de3-a502-c18a7c6a3...@gmail.com%3E
(sorry that's a private list).
This summarises it:
https://issues.apache.org/jira/browse/LEGAL-156
Cheers,
Jeremy
On 28
On Mar 28, 2014, at 4:35 AM, dav...@apache.org wrote:
That's great - but I'm wondering how this works from an IP-flow point of view.
I guess that by attaching a patch to a JIRA issue one formally donates
the code to Apache.
But by merging a github pull request you take a few commits from
[
https://issues.apache.org/jira/browse/ARIES-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert reassigned ARIES-1164:
---
Assignee: David Bosschaert
itests.BlueprintContainerBTCustomizerTest fails
[
https://issues.apache.org/jira/browse/ARIES-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951055#comment-13951055
]
David Bosschaert commented on ARIES-1164:
-
Thanks for the patch Grzegorz. It's
Cool - thanks for the explanation.
In terms of Aries, since we're still using SVN, can I actually push
commits to git directly?
FWIW I tried pushing to git://git.apache.org/aries.git and
https://git-wip-us.apache.org/repos/asf/aries.git but they don't seem
to work...
Or, should I, since Aries
Right - ok. So it has to go through SVN, at least for Aries right now.
Thanks for the help!
David
On 28 March 2014 16:27, Daniel Kulp dk...@apache.org wrote:
On Mar 28, 2014, at 12:09 PM, dav...@apache.org wrote:
Cool - thanks for the explanation.
In terms of Aries, since we're still using
[
https://issues.apache.org/jira/browse/ARIES-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert resolved ARIES-1164.
-
Resolution: Fixed
itests.BlueprintContainerBTCustomizerTest fails
On Mar 28, 2014, at 12:09 PM, dav...@apache.org wrote:
Cool - thanks for the explanation.
In terms of Aries, since we're still using SVN, can I actually push
commits to git directly?
FWIW I tried pushing to git://git.apache.org/aries.git and
See
https://builds.apache.org/job/Aries/org.apache.aries.jpa$org.apache.aries.jpa.container.itest/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.subsystem$org.apache.aries.subsystem.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.proxy$org.apache.aries.proxy.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.samples.blueprint.helloworld$org.apache.aries.samples.blueprint.helloworld.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.jmx$org.apache.aries.jmx.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.blueprint$org.apache.aries.blueprint.itests/changes
See
https://builds.apache.org/job/Aries/org.apache.aries.jndi$org.apache.aries.jndi.url.itest/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.ejb$org.apache.aries.ejb.modeller.itest/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.web$org.apache.aries.web.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.application$org.apache.aries.application.runtime.isolated.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.blueprint$org.apache.aries.blueprint.annotation.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.quiesce$org.apache.aries.quiesce.manager.itest/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.jmx$org.apache.aries.jmx.whiteboard/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.samples.twitter$org.apache.aries.samples.twitter.itests/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.ejb$org.apache.aries.ejb.openejb.extender.itest/1917/
See
https://builds.apache.org/job/Aries/org.apache.aries.transaction$org.apache.aries.transaction.itests/1917/
See https://builds.apache.org/job/Aries/changes
I noticed that Jenkins is now failing all the itests as well because
of this issue...
On 28 March 2014 11:16, Achim Nierbeck bcanh...@googlemail.com wrote:
It definitely would help ;)
Though yes there are some API breaking changes and you'll need to rework
your POM a bit.
Still I think this
Hah. Yeah wondered why my inbox was suddenly full of similar looking emails!
On 28 Mar 2014 20:53, David Bosschaert david.bosscha...@gmail.com wrote:
I noticed that Jenkins is now failing all the itests as well because
of this issue...
On 28 March 2014 11:16, Achim Nierbeck
35 matches
Mail list logo