Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Grzegorz Grzybek 
+1 (non-binding)

regards
Grzegorz Grzybek

śr., 3 kwi 2019 o 21:03 Francois Papon 
napisał(a):

> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 03/04/2019 à 18:14, Guillaume Nodet a écrit :
> > I've staged another RC for a 4.2.0 release of the maven-bundle-plugin
> which
> > includes the following changes:
> >
> > e1236412f2 Fix typo in scope
> >
> > 54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
> > calculate osgi.ee for embedded dependencies
> >
> > fbfdb2985d [FELIX-6078] Add an option to silently ignore some project
> types
> > instead of displaying a warning
> >
> > 2d559f601b [FELIX-6074] Do not write all stale files at info level
> >
> > 9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
> > check
> >
> > e12e94cb84 [FELIX-6073] Upgrade to Maven 3
> >
> > 4857cb9616 [FELIX-6075] Upgrade to JDK 8
> >
> > e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
> > build,  upgrade to jdk 8
> >
> > The staging repository is available at:
> >   https://repository.apache.org/content/repositories/orgapachefelix-1296
> >
> > Please review and vote !
> >
>

Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Francois Papon 
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 03/04/2019 à 18:14, Guillaume Nodet a écrit :
> I've staged another RC for a 4.2.0 release of the maven-bundle-plugin which
> includes the following changes:
>
> e1236412f2 Fix typo in scope
>
> 54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
> calculate osgi.ee for embedded dependencies
>
> fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
> instead of displaying a warning
>
> 2d559f601b [FELIX-6074] Do not write all stale files at info level
>
> 9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
> check
>
> e12e94cb84 [FELIX-6073] Upgrade to Maven 3
>
> 4857cb9616 [FELIX-6075] Upgrade to JDK 8
>
> e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
> build,  upgrade to jdk 8
>
> The staging repository is available at:
>   https://repository.apache.org/content/repositories/orgapachefelix-1296
>
> Please review and vote !
>

Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Karl Pauls 
+1

regards,

Karl

On Wednesday, April 3, 2019, Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> Regards
> JB
>
> Le 3 avr. 2019 à 20:52, à 20:52, Georg Henzler  a
> écrit:
> >+1 (non-binding)
> >
> >-Georg
> >
> >On 2019-04-03 18:51, Raymond Auge wrote:
> >> +1
> >>
> >> - Ray
> >>
> >> On Wed, Apr 3, 2019 at 12:07 PM Stefan Seifert
> >
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> checked signatures & tested it in a couple of projects
> >>>
> >>> stefan
> >>>
>


-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Health Check Core 2.0.2

2019-04-03 Thread Karl Pauls 
+1

regards,

Karl

On Wednesday, April 3, 2019, Georg Henzler  wrote:

> +1 (non-binding)
>
> -Georg
>
> On 2019-04-01 16:22, Jean-Baptiste Onofré wrote:
>
>> +1 (binding)
>>
>> Regards
>> JB
>>
>> On 01/04/2019 14:04, Georg Henzler wrote:
>>
>>> Hi,
>>>
>>> We solved 1 issues in this release:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>>> 20FELIX%20AND%20fixVersion%20%3D%20%22healthcheck.core%202.0.2%22
>>>
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachefelix-1294/
>>>
>>> You can use this UNIX script to download the release and verify the
>>> signatures:
>>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>
>>> Usage:
>>> sh check_staged_release.sh 1294 /tmp/felix-staging
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>> This vote will be open for 72 hours.
>>>
>>> -Georg
>>>
>>

-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Jean-Baptiste Onofré 
+1 (binding)

Regards
JB

Le 3 avr. 2019 à 20:52, à 20:52, Georg Henzler  a écrit:
>+1 (non-binding)
>
>-Georg
>
>On 2019-04-03 18:51, Raymond Auge wrote:
>> +1
>>
>> - Ray
>>
>> On Wed, Apr 3, 2019 at 12:07 PM Stefan Seifert
>
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> checked signatures & tested it in a couple of projects
>>>
>>> stefan
>>>

Re: [VOTE] Release Health Check Core 2.0.2

2019-04-03 Thread Georg Henzler 

+1 (non-binding)

-Georg

On 2019-04-01 16:22, Jean-Baptiste Onofré wrote:

+1 (binding)

Regards
JB

On 01/04/2019 14:04, Georg Henzler wrote:

Hi,

We solved 1 issues in this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20%22healthcheck.core%202.0.2%22


Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-1294/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1294 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for 72 hours.

-Georg

Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Georg Henzler 

+1 (non-binding)

-Georg

On 2019-04-03 18:51, Raymond Auge wrote:

+1

- Ray

On Wed, Apr 3, 2019 at 12:07 PM Stefan Seifert 
wrote:


+1 (non-binding)

checked signatures & tested it in a couple of projects

stefan

Re: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Raymond Auge 
+1

- Ray

On Wed, Apr 3, 2019 at 12:07 PM Stefan Seifert 
wrote:

> +1 (non-binding)
>
> checked signatures & tested it in a couple of projects
>
> stefan
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

RE: [VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Stefan Seifert 
+1 (non-binding)

checked signatures & tested it in a couple of projects

stefan

[VOTE] Release maven-bundle-plugin 4.2.0 (2nd try)

2019-04-03 Thread Guillaume Nodet 
I've staged another RC for a 4.2.0 release of the maven-bundle-plugin which
includes the following changes:

e1236412f2 Fix typo in scope

54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
calculate osgi.ee for embedded dependencies

fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
instead of displaying a warning

2d559f601b [FELIX-6074] Do not write all stale files at info level

9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
check

e12e94cb84 [FELIX-6073] Upgrade to Maven 3

4857cb9616 [FELIX-6075] Upgrade to JDK 8

e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
build,  upgrade to jdk 8

The staging repository is available at:
  https://repository.apache.org/content/repositories/orgapachefelix-1296

Please review and vote !

-- 

Guillaume Nodet

[CANCEL][VOTE] Release maven-bundle-plugin 4.2.0

2019-04-03 Thread Guillaume Nodet 
Cancelling this vote, I'll fix the pom and recut the release.

Le mer. 3 avr. 2019 à 13:04, Guillaume Nodet  a écrit :

> I've staged a 4.2.0 release of the maven-bundle-plugin which includes the
> following changes:
>
> 54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
> calculate osgi.ee for embedded dependencies
>
> fbfdb2985d [FELIX-6078] Add an option to silently ignore some project
> types instead of displaying a warning
>
> 2d559f601b [FELIX-6074] Do not write all stale files at info level
>
> 9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
> check
>
> e12e94cb84 [FELIX-6073] Upgrade to Maven 3
>
> 4857cb9616 [FELIX-6075] Upgrade to JDK 8
>
> e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
> build,  upgrade to jdk 8
>
> The staging repository is available at:
>   https://repository.apache.org/content/repositories/orgapachefelix-1295
>
> Please review and vote !
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release maven-bundle-plugin 4.2.0

2019-04-03 Thread Jean-Baptiste Onofré 
-1 (binding)

There's a typo in the pom.xml (tet instead of test), causing build
failure (validation).

Regards
JB

On 03/04/2019 13:04, Guillaume Nodet wrote:
> I've staged a 4.2.0 release of the maven-bundle-plugin which includes the
> following changes:
> 
> 54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
> calculate osgi.ee for embedded dependencies
> 
> fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
> instead of displaying a warning
> 
> 2d559f601b [FELIX-6074] Do not write all stale files at info level
> 
> 9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
> check
> 
> e12e94cb84 [FELIX-6073] Upgrade to Maven 3
> 
> 4857cb9616 [FELIX-6075] Upgrade to JDK 8
> 
> e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
> build,  upgrade to jdk 8
> 
> The staging repository is available at:
>   https://repository.apache.org/content/repositories/orgapachefelix-1295
> 
> Please review and vote !
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

RE: [VOTE] Release maven-bundle-plugin 4.2.0

2019-04-03 Thread Stefan Seifert 
-1 (non-binding)

there is a syntax error in the pom, leading to invalid maven dependencies
https://github.com/apache/felix/blob/trunk/tools/maven-bundle-plugin/pom.xml#L253

stefan


>-Original Message-
>From: Guillaume Nodet [mailto:gno...@apache.org]
>Sent: Wednesday, April 3, 2019 1:05 PM
>To: dev@felix.apache.org
>Subject: [VOTE] Release maven-bundle-plugin 4.2.0
>
>I've staged a 4.2.0 release of the maven-bundle-plugin which includes the
>following changes:
>
>54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
>calculate osgi.ee for embedded dependencies
>
>fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
>instead of displaying a warning
>
>2d559f601b [FELIX-6074] Do not write all stale files at info level
>
>9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
>check
>
>e12e94cb84 [FELIX-6073] Upgrade to Maven 3
>
>4857cb9616 [FELIX-6075] Upgrade to JDK 8
>
>e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
>build,  upgrade to jdk 8
>
>The staging repository is available at:
>  https://repository.apache.org/content/repositories/orgapachefelix-1295
>
>Please review and vote !
>
>--
>
>Guillaume Nodet

[jira] [Issue Comment Deleted] (FELIX-6088) NPE in LoggerImpl when formatted logger called with null or empty arguments

2019-04-03 Thread Jan Hendriks (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hendriks updated FELIX-6088:

Comment: was deleted

(was: Pull-Request: [https://github.com/apache/felix/pull/195])

> NPE in LoggerImpl when formatted logger called with null or empty arguments 
> 
>
> Key: FELIX-6088
> URL: https://issues.apache.org/jira/browse/FELIX-6088
> Project: Felix
>  Issue Type: Bug
>  Components: Log Service
>Affects Versions: log-1.2.0
>Reporter: Jan Hendriks
>Priority: Major
>  Labels: NPE, logger, logging
>
> When calling the "formatter" logger with null or empty arguments like the 
> following sample code (using bnd launchpad):
> {code:java}
> import org.junit.Test;
> import org.osgi.service.log.Logger;
> import org.osgi.service.log.LoggerFactory;
> import aQute.launchpad.Launchpad;
> import aQute.launchpad.LaunchpadBuilder;
> public class FelixLoggerTest {
> @Test
> public void letApacheFelixLogThrowNPE() throws Exception {
> try (final Launchpad launchpad = new 
> LaunchpadBuilder().runfw("org.apache.felix.framework").bundles("org.apache.felix.log;version='[1.2.0,1.2.1)'").create())
>  {
> LoggerFactory osgiLoggerFactory = 
> launchpad.getService(LoggerFactory.class).get();
> Logger osgiLogger = 
> osgiLoggerFactory.getLogger(getClass().getName());
> osgiLogger.info("Test formatted logging...", new Object[0]); // 
> throws NPE
> osgiLogger.debug("Test formatted logging...", null); // throws NPE
> }
> }
> }
> {code}
> following NPE is thrown:
> {noformat}
> java.lang.NullPointerException
> at org.apache.felix.log.LoggerImpl.format(LoggerImpl.java:335)
> at org.apache.felix.log.LoggerImpl.info(LoggerImpl.java:164)
> at 
> com.[REDACTED].run.FelixLoggerTest.letApacheFelixLogThrowNPE(FelixLoggerTest.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at 
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release maven-bundle-plugin 4.2.0

2019-04-03 Thread Raymond Auge 
+1

- Ray

On Wed, Apr 3, 2019, 07:05 Guillaume Nodet,  wrote:

> I've staged a 4.2.0 release of the maven-bundle-plugin which includes the
> following changes:
>
> 54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
> calculate osgi.ee for embedded dependencies
>
> fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
> instead of displaying a warning
>
> 2d559f601b [FELIX-6074] Do not write all stale files at info level
>
> 9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
> check
>
> e12e94cb84 [FELIX-6073] Upgrade to Maven 3
>
> 4857cb9616 [FELIX-6075] Upgrade to JDK 8
>
> e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
> build,  upgrade to jdk 8
>
> The staging repository is available at:
>   https://repository.apache.org/content/repositories/orgapachefelix-1295
>
> Please review and vote !
>
> --
> 
> Guillaume Nodet
>

[VOTE] Release maven-bundle-plugin 4.2.0

2019-04-03 Thread Guillaume Nodet 
I've staged a 4.2.0 release of the maven-bundle-plugin which includes the
following changes:

54d0740058 [FELIX-6081] Upgrade bndlib to 4.2.0 in order to properly
calculate osgi.ee for embedded dependencies

fbfdb2985d [FELIX-6078] Add an option to silently ignore some project types
instead of displaying a warning

2d559f601b [FELIX-6074] Do not write all stale files at info level

9487647dc2 [FELIX-6074] Do not analyze dependencies before the upToDate
check

e12e94cb84 [FELIX-6073] Upgrade to Maven 3

4857cb9616 [FELIX-6075] Upgrade to JDK 8

e971b02f67 [FELIX-6074][FELIX-6075] Support plain incremental manifest
build,  upgrade to jdk 8

The staging repository is available at:
  https://repository.apache.org/content/repositories/orgapachefelix-1295

Please review and vote !

-- 

Guillaume Nodet

[jira] [Commented] (FELIX-6088) NPE in LoggerImpl when formatted logger called with null or empty arguments

2019-04-03 Thread Jan Hendriks (JIRA) 


[ 
https://issues.apache.org/jira/browse/FELIX-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808576#comment-16808576
 ] 

Jan Hendriks commented on FELIX-6088:
-

Pull-Request: [https://github.com/apache/felix/pull/195]

> NPE in LoggerImpl when formatted logger called with null or empty arguments 
> 
>
> Key: FELIX-6088
> URL: https://issues.apache.org/jira/browse/FELIX-6088
> Project: Felix
>  Issue Type: Bug
>  Components: Log Service
>Affects Versions: log-1.2.0
>Reporter: Jan Hendriks
>Priority: Major
>  Labels: NPE, logger, logging
>
> When calling the "formatter" logger with null or empty arguments like the 
> following sample code (using bnd launchpad):
> {code:java}
> import org.junit.Test;
> import org.osgi.service.log.Logger;
> import org.osgi.service.log.LoggerFactory;
> import aQute.launchpad.Launchpad;
> import aQute.launchpad.LaunchpadBuilder;
> public class FelixLoggerTest {
> @Test
> public void letApacheFelixLogThrowNPE() throws Exception {
> try (final Launchpad launchpad = new 
> LaunchpadBuilder().runfw("org.apache.felix.framework").bundles("org.apache.felix.log;version='[1.2.0,1.2.1)'").create())
>  {
> LoggerFactory osgiLoggerFactory = 
> launchpad.getService(LoggerFactory.class).get();
> Logger osgiLogger = 
> osgiLoggerFactory.getLogger(getClass().getName());
> osgiLogger.info("Test formatted logging...", new Object[0]); // 
> throws NPE
> osgiLogger.debug("Test formatted logging...", null); // throws NPE
> }
> }
> }
> {code}
> following NPE is thrown:
> {noformat}
> java.lang.NullPointerException
> at org.apache.felix.log.LoggerImpl.format(LoggerImpl.java:335)
> at org.apache.felix.log.LoggerImpl.info(LoggerImpl.java:164)
> at 
> com.[REDACTED].run.FelixLoggerTest.letApacheFelixLogThrowNPE(FelixLoggerTest.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at 
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)