I'm trying to run proxy-itest and attach the eclipse debugger. I launch from
the command line:
mvn -Dmaven.surefire.debug
-Dtest=org.apache.aries.proxy.itests.BasicProxyBundlesTest test
and as expected the command line execution halts with a message:
Listening for transport dt_socket at
splay/PAXEXAM3/FAQ#FAQ-WhydoestheJavadebuggernotstopatabreakpointIsetinmyPaxExamJUnittest?
regards
Grzegorz Grzybek
2016-01-14 22:18 GMT+01:00 Samuel E Bratton <sbrat...@us.ibm.com>:
> I'm trying to run proxy-itest and attach the eclipse debugger. I launch from
> the command line:
>
&g
at the itests pom and it points at 2.0.7-SNAPSHOT as
> expected. Are you sure you're looking at the latest version?
>
> David
>
> On 6 November 2015 at 18:54, Samuel E Bratton <sbrat...@us.ibm.com> wrote:
>> It looks like after the last subsystem 2.0.6
It looks like after the last subsystem 2.0.6 release the
subsystem/subsystem-itests/pom.xml was not updated to point to new maven
dependencies,
org.apache.aries.subsystem.core:2.0.7-SNAPSHOT,
org.apache.aries.subsystem.api:2.0.7-SNAPSHOT (still pointing to
2.0.5-SNAPSHOT).
I think this also
The Namespaces class is a new class for this release but the
org.apache.aries.blueprint.core-1.4.5.jar MANIFEST shows the package exported
as org.apache.aries.blueprint;version="1.3.0". Doesn't that need to be raised
to 1.4? Or is that happening elsewhere as part of the release process?
Hi.
Sometime back the org.apache.aries.jpa project was changed to require a
1.7 compiler. We have a requirement to support 1.6 for a while still.
Is there any objection to our changing jpa so it will compile with 1.6? It
seems the only 1.7 construct used is the diamond operator in a number of
Is trunk now stable after the jmx release?
When I build it, it seems to be broken due to jmx-itests/pom.xml
referencing a org.apache.aries.jmx.parent:1.1.5-SNAPSHOT (as opposed to
1.1.6-SNAPSHOT).
--
Samuel Bratton
IBM WebSphere System Management
Bldg 903 5E005, 11501 Burnet Road, Austin,
Hi,
Tom was referring to ARIES-1228 , which has been resolved in aries and in
the CT.
Sam
From: David Bosschaert david.bosscha...@gmail.com
To: dev@aries.apache.org dev@aries.apache.org
Date: 09/23/2014 03:55 AM
Subject:Re: Subsystem Core release sometime soon?
Just
Hi
I noticed that a full aries build leaves ~70MB in /tmp (about 85% of that
appears to be from blueprint-itest related logs and from OSGI workspaces).
I know some systems automatically clean out tmp periodically, but for
those that do not, shouldn't component builds be cleaning up those
use.
Cheers,
David
On 26 August 2014 17:25, Samuel E Bratton sbrat...@us.ibm.com wrote:
Hi
I noticed that a full aries build leaves ~70MB in /tmp (about 85% of
that
appears to be from blueprint-itest related logs and from OSGI
workspaces).
I know some systems automatically
Hi,
The Aries builds have been red for about the last 5 days. It looks like a
couple of different people have been working on fixing it. Is this a
coordinated effort? Are there a particular set of JIRAs where this is
going on and can be followed?
Thanks
Sam Bratton
I'm also having issues building aries on the subssystem itests. It's been
failing the last few days including with the latest updates from this
morning. I see multiple compile errors. It looks like non-Genericized
classes being used with generics, for example
I think I fixed that yesterday, it seems to work for me on latest trunk.
2014-06-04 22:41 GMT+02:00 Samuel E Bratton sbrat...@us.ibm.com:
I'm also having issues building aries on the subssystem itests. It's
been
failing the last few days including with the latest updates from
GMT+02:00 Samuel E Bratton sbrat...@us.ibm.com:
I'm still seeing it after updating just now. How did you fix it?
Thanks
Sam Bratton
Guillaume Nodet gno...@apache.org wrote on 06/04/2014 03:44:05 PM:
From: Guillaume Nodet gno...@apache.org
To: dev@aries.apache.org
Date: 06/04
14 matches
Mail list logo