[jira] [Updated] (ARIES-2058) Aries 1.16.0 RSA fails OSGi RemoteServiceAdmin TCK test

[A. J. David Bosschaert (Jira)]

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

A. J. David Bosschaert updated ARIES-2058:
--
Attachment: aries.log

> Aries 1.16.0 RSA fails OSGi RemoteServiceAdmin TCK test
> ---
>
> Key: ARIES-2058
> URL: https://issues.apache.org/jira/browse/ARIES-2058
> Project: Aries
>  Issue Type: Bug
>  Components: Remote Service Admin
>Affects Versions: rsa-1.16.0
>    Reporter: A. J. David Bosschaert
>Priority: Major
> Attachments: aries.log
>
>
> When running the OSGi RSA TCK 13 of the 39 tests fail:
> {code:java}
> Test run finished after 458266 ms
> [11 containers found  ]
> [ 0 containers skipped]
> [11 containers started]
> [ 0 containers aborted]
> [11 containers successful ]
> [ 0 containers failed ]
> [39 tests found   ]
> [ 0 tests skipped ]
> [39 tests started ]
> [ 0 tests aborted ]
> [26 tests successful  ]
> [13 tests failed  ]
> # test ran
> # queue []
>  
> > Task :org.osgi.test.cases.remoteserviceadmin:testOSGi FAILED {code}
> To reproduce make the following change in https://github.com/osgi/osgi:
> {code}
> $ git diff
> diff --git a/cnf/ext/central.mvn b/cnf/ext/central.mvn
> index 2a8e2f44b2..e43331adac 100644
> --- a/cnf/ext/central.mvn
> +++ b/cnf/ext/central.mvn
> @@ -89,12 +89,12 @@ 
> org.apache.aries.jpa:org.apache.aries.jpa.eclipselink.adapter:2.4.0
>  org.apache.aries.spec:org.apache.aries.javax.jax.rs-api:1.0.4
>  org.apache.aries.spifly:org.apache.aries.spifly.dynamic.bundle:1.0.8
>  
> org.apache.aries.spifly:org.apache.aries.spifly.dynamic.framework.extension:1.3.3
> -org.apache.aries.rsa:org.apache.aries.rsa.core:1.13.0
> -org.apache.aries.rsa:org.apache.aries.rsa.spi:1.13.0
> -org.apache.aries.rsa:org.apache.aries.rsa.topology-manager:1.13.0
> -org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.local:1.13.0
> -org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.zookeeper:1.13.0
> -org.apache.aries.rsa.provider:org.apache.aries.rsa.provider.tcp:1.13.0
> +org.apache.aries.rsa:org.apache.aries.rsa.core:1.16.0
> +org.apache.aries.rsa:org.apache.aries.rsa.spi:1.16.0
> +org.apache.aries.rsa:org.apache.aries.rsa.topology-manager:1.16.0
> +org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.local:1.16.0
> +org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.zookeeper:1.16.0
> +org.apache.aries.rsa.provider:org.apache.aries.rsa.provider.tcp:1.16.0
>  org.apache.felix:org.apache.felix.configadmin:1.9.22
>  org.apache.felix:org.apache.felix.configurator:1.0.8
> {code}
> Then run in the {{org.osgi.test.cases.remoteserviceadmin}} directory:
> {code}
> $ ../gradlew check
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ARIES-2058) Aries 1.16.0 RSA fails OSGi RemoteServiceAdmin TCK test

[A. J. David Bosschaert (Jira)]

A. J. David Bosschaert created ARIES-2058:
-

 Summary: Aries 1.16.0 RSA fails OSGi RemoteServiceAdmin TCK test
 Key: ARIES-2058
 URL: https://issues.apache.org/jira/browse/ARIES-2058
 Project: Aries
  Issue Type: Bug
  Components: Remote Service Admin
Affects Versions: rsa-1.16.0
Reporter: A. J. David Bosschaert


When running the OSGi RSA TCK 13 of the 39 tests fail:

{code:java}
Test run finished after 458266 ms
[11 containers found  ]
[ 0 containers skipped]
[11 containers started]
[ 0 containers aborted]
[11 containers successful ]
[ 0 containers failed ]
[39 tests found   ]
[ 0 tests skipped ]
[39 tests started ]
[ 0 tests aborted ]
[26 tests successful  ]
[13 tests failed  ]
# test ran
# queue []
 
> Task :org.osgi.test.cases.remoteserviceadmin:testOSGi FAILED {code}

To reproduce make the following change in https://github.com/osgi/osgi:

{code}
$ git diff
diff --git a/cnf/ext/central.mvn b/cnf/ext/central.mvn
index 2a8e2f44b2..e43331adac 100644
--- a/cnf/ext/central.mvn
+++ b/cnf/ext/central.mvn
@@ -89,12 +89,12 @@ 
org.apache.aries.jpa:org.apache.aries.jpa.eclipselink.adapter:2.4.0
 org.apache.aries.spec:org.apache.aries.javax.jax.rs-api:1.0.4
 org.apache.aries.spifly:org.apache.aries.spifly.dynamic.bundle:1.0.8
 
org.apache.aries.spifly:org.apache.aries.spifly.dynamic.framework.extension:1.3.3
-org.apache.aries.rsa:org.apache.aries.rsa.core:1.13.0
-org.apache.aries.rsa:org.apache.aries.rsa.spi:1.13.0
-org.apache.aries.rsa:org.apache.aries.rsa.topology-manager:1.13.0
-org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.local:1.13.0
-org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.zookeeper:1.13.0
-org.apache.aries.rsa.provider:org.apache.aries.rsa.provider.tcp:1.13.0
+org.apache.aries.rsa:org.apache.aries.rsa.core:1.16.0
+org.apache.aries.rsa:org.apache.aries.rsa.spi:1.16.0
+org.apache.aries.rsa:org.apache.aries.rsa.topology-manager:1.16.0
+org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.local:1.16.0
+org.apache.aries.rsa.discovery:org.apache.aries.rsa.discovery.zookeeper:1.16.0
+org.apache.aries.rsa.provider:org.apache.aries.rsa.provider.tcp:1.16.0

 org.apache.felix:org.apache.felix.configadmin:1.9.22
 org.apache.felix:org.apache.felix.configurator:1.0.8
{code}

Then run in the {{org.osgi.test.cases.remoteserviceadmin}} directory:

{code}
$ ../gradlew check
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Aries JAX-RS Whiteboard 2.0.1 release

[David Bosschaert]

+1

David

On Wed, 25 Aug 2021 at 09:31, Francois Papon 
wrote:

> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 24/08/2021 à 18:15, Tim Ward a écrit :
> > Hi all,
> >
> > I submit the Aries JAX-RS 2.0.1 release for your vote.
> >
> > This release includes numerous dependency updates, a performance fix for
> JAX-RS clients, and a fix for a startup ordering issue.
> >
> > Staging Maven Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1201/ <
> https://repository.apache.org/content/repositories/orgapachearies-1201/>
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Best Regards,
> >
> > Tim Ward
>

Re: [DISCUSS] New component - Type Safe Events

[David Bosschaert]

+1 from me too

Best regards,

David

On Mon, 7 Sep 2020 at 15:34, Christian Schneider 
wrote:

> +1
>
> Christian
>
> Am Mo., 7. Sept. 2020 um 13:14 Uhr schrieb Tim Ward <
> timothyjw...@apache.org
> >:
>
> > Hi all,
> >
> > The “Type Safe Events” RFC (
> > https://github.com/osgi/design/tree/main/rfcs/rfc0244 <
> > https://github.com/osgi/design/tree/main/rfcs/rfc0244>) from the OSGi
> > Alliance has been turned into a draft specification chapter, and will be
> in
> > need of a reference implementation.
> >
> > The work so far in this RFC has been part of a European Union Horizon
> 2020
> > program called BRAIN-IoT (http://www.brain-iot.eu <
> > http://www.brain-iot.eu/>). This project has received funding from the
> > European Union’s Horizon 2020 research and innovation programme under
> grant
> > agreement No 780089. This work includes some implementation prototyping,
> > but the end objective has always been to create an Open Source
> > implementation.
> >
> > Assuming that the Aries community are happy for me to go ahead I plan to
> > develop the reference implementation of the OSGi specification chapter in
> > the Aries project, based on this prototype code. If the Aries Community
> has
> > any thoughts or suggestions I would be keen to hear them.
> >
> > Best Regards,
> >
> > Tim Ward
>
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: would like to call vote on spi-fly

[David Bosschaert]

Thanks Ray! +1 from me.

David

On Sun, 29 Mar 2020 at 07:07, Jean-Baptiste Onofre  wrote:

> +1 it looks good to me.
>
> Regards
> JB
>
> > Le 28 mars 2020 à 17:56, Raymond Auge  a
> écrit :
> >
> > Hey All,
> >
> > SPI Fly recently got a fix to work on Java 14 (asm related).
> > I'd like to call a vote of a release in the next day or so.
> >
> > Any objections?
> >
> > --
> > *Raymond Augé* 
> > (@rotty3000)
> > Senior Software Architect *Liferay, Inc.* 
> > (@Liferay)
>
>

Re: [VOTE] Aries CDI 1.1.1 release

[David Bosschaert]

+1

David

On Tue, 11 Feb 2020 at 07:37, Jean-Baptiste Onofre  wrote:

> Hi everyone,
>
> As discussed on the mailing list, this is a call to vote Aries CDI 1.1.1
> release.
>
> This release include:
> - Support of @Reference(value = Any.class)
> - Couple of fixes on OWB support
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12346973
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12346973
> >
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1173
>
> 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.
>
> Thanks,
> Regards
> JB

Re: [VOTE] Release Aries CDI version 1.1.0

[David Bosschaert]

+1

David

On Thu, 2 Jan 2020 at 19:16, Raymond Auge  wrote:

> Hey all,
>
> I'd like to call a vote for Aries CDI 1.1.0 which is a significant
> restructuring in order to support a number of use cases.
>
> Of note are:
> - the ability to run with both Apache OpenWebBeans and JBoss Weld
> implementations
> - an SPI enabling different CDI implementations as above
> - a JAX-RS extension
> - an extension SPI for common scenarios [1]
>
> The release details are here
> https://issues.apache.org/jira/projects/ARIES/versions/12346547
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1171
>
> 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.
>
> [1] https://github.com/apache/aries-cdi#aries-cdi-extension-spi
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
>

Re: [VOTE] Release Aries CDI version 1.0.3

[David Bosschaert]

+1

David

On Mon, 25 Nov 2019 at 17:32, Raymond Auge  wrote:

> Hey all,
>
> Please vote for release 1.0.3 of Aries CDI which is just a wrapping up of
> build and documentation changes prior to large pending architectural
> changes.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1170
>
> 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.
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
>

Re: [Discuss] Upgrading aries-rsa to Java 8

[David Bosschaert]

Sounds good to me!

David

On Mon, 28 Oct 2019 at 16:52, Dominik Przybysz  wrote:

> +1
> I would also suggest to test aries projects with java 8 and java 11.
>
> pon., 28 paź 2019 o 17:34 Christian Schneider 
> napisał(a):
>
> > I would like to require Java 8 in aries-rsa to be able to use closures.
> > Does anyone have objections against this?
> >
> > Christian
> >
> > --
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Computer Scientist
> > http://www.adobe.com
> >
>
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.6

[David Bosschaert]

+1

David

On Fri, 20 Sep 2019 at 15:35, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.6 for Aries JAX-RS Whiteboard.
>
> The release notes can be found here:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12346248
>
> which are important fixes and there are also improvements in performance.
>
> The modules are tagged at
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs-1.0.6
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1169
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all.
>
> Carlos.
>
>
>
>
>
>
>

Re: [VOTE] Apache Aries Proxy Impl 1.1.6 release

[David Bosschaert]

+1

David

On Mon, 16 Sep 2019 at 16:30, Jean-Baptiste Onofré  wrote:

> Hi everyone,
>
> I submit Aries Proxy Impl 1.1.6 release to your vote.
>
> We fixed one issue in this release:
>
> * [ARIES-1923] - aries-proxy fails when presented with Java 11 classes
> with nested classes
>
> Here's the detailed Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12345678
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1167
>
> Git tag:
> org.apache.aries.proxy-1.1.6
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Aries Component-DSL 1.2.2

[David Bosschaert]

+1

David

On Tue, 17 Sep 2019 at 15:50, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.2.2 for Aries Component DSL. It brings mostly
> bug fixes.
>
> Release notes can be found at
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344178
> The module is tagged at
>
> https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;a=tag;h=refs/tags/org.apache.aries.component-dsl.parent-1.2.2
> Artifacts are in one staged repo:
> https://repository.apache.org/content/repositories/orgapachearies-1168
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1168 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all,
>
> Carlos.
>
>

Re: [VOTE] Apache Aries SPI Fly 1.2.3 release

[David Bosschaert]

+1

David

On Wed, 3 Jul 2019 at 20:26, Raymond Auge  wrote:

> Hi,
>
> I submit Apache Aries SPI Fly 1.2.3 release to your vote.
>
> We fixed a couple of minor issues with packaging.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12345719
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1166
>
> 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.
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [Discuss] Moving Aries website to github pages or other static generator?

[David Bosschaert]

+1 from me.

I recently worked with Jekyll on Github pages and it works very well.

I would be happy to take on a few pages that need to be migrated too.

Best regards,

David

On Wed, 29 May 2019 at 08:13, Jean-Baptiste Onofré  wrote:

> Hi Christian,
>
> It's definitely a good idea.
>
> I have a preference for the asciidoc approach we are using at Karaf,
> especially for the documentation.
>
> For winegrower (http://github.com/jbonofre/winegrower), I tested github
> pages, and it works fine as well.
>
> Regards
> JB
>
> On 29/05/2019 07:53, Christian Schneider wrote:
> > The Aries website currently looks quite broken. I guess the css is not
> > loading or something. Of course we should fix this but it will only
> > marginally improve :-)
> > I wonder if we should move to some static generator like github pages or
> > the way e.g. Apache Karaf builds their site.
> >
> > So first question is if we should move to such a model?
> > If we decide so .. does anyone have experience building such sites and is
> > willing to help?
> > I guess once we have the basic structure then editing content is easy but
> > for the first step some good experience is needed.
> >
> > Christian
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.5

[David Bosschaert]

+1

David

On Tue, 28 May 2019 at 11:59, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.5 for Aries JAX-RS Whiteboard.
>
> The release notes for Whiteboard 1.0.5 can be found here:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12345589
>
> which are important fixes and there are also improvements in
> registration and packaging.
>
> The modules are tagged at
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs-1.0.5
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1163
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all.
>
> Carlos.
>
>
>
>
>
>

Re: New committer Amichai Rothman

[David Bosschaert]

Welcome Amichai!

David

On Thu, 23 May 2019 at 09:53, Raymond Auge  wrote:

> Welcome Amichai!
>
> :)
>
> - Ray
>
> On Thu, May 23, 2019 at 8:15 AM Jean-Baptiste Onofré 
> wrote:
>
> > Welcome aboard !
> >
> > Regards
> > JB
> >
> > On 23/05/2019 12:27, Carlos Sierra Andrés wrote:
> > > Hey Amichai,
> > >
> > > welcome to Apache Aries!! Thx for your contribution.
> > >
> > > Carlos.
> > >
> > > El 23/5/19 a las 10:35, Christian Schneider escribió:
> > >> The Project Management Committee (PMC) for Apache Aries
> > >> has invited Amichai Rothman to become a committer and we are pleased
> > >> to announce that he has accepted.
> > >>
> > >> Please welcome our new committer.
> > >>
> > >> Christian
> > >> on behalf of the Apache Aries PMC
> > >>
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: Enable an ESA file as a maven artifact attachment

[David Bosschaert]

Hi Bob,

Sounds like a useful addition to me!

Best regards,

David

On Sun, 19 May 2019 at 20:43, Bob Paulin  wrote:

> Hi,
>
> I am using the esa-maven-plugin for a project that currently creates an
> OSGi bundle.  I found with some small modifications [1] to the plugin I
> could add the esa as an attachment with dependencies while allowing the
> existing bundle to be built and used by itself.  The ESA could then be
> downloaded instead by applying a classifier.  Adding a flag would allow
> this to be enabled for projects that want this behavior but disable
> would not modify existing behavior.
>
>  
> org.apache.aries
> esa-maven-plugin
> 1.0.3-SNAPSHOT
> 
>   true
>   ..
> 
>   
>
> Is this something the community would be interested in integrating to
> the main line?  I have a few different usecases that would benefit from
> this addition.  I'd be happy to submit a PR like the one below with some
> tests.  Thanks!
>
>
> - Bob
>
> [1]
>
> https://github.com/bobpaulin/aries/commit/8e26e6da7b1bacdd3b0d21261dc7d56acd467ca0
>
>

Re: [VOTE] Release Apache Aries Remote Service Admin 1.14.0

[David Bosschaert]

+1

David

On Thu, 16 May 2019 at 15:21, Christian Schneider 
wrote:

> This release mainly fixes some bugs and contains some improvements to the
> fastbin transport.
> Special thanks go to Amichai who provided a big part of the changes.
>
> I've staged the release at
> https://repository.apache.org/content/repositories/orgapachearies-1162
>
> For a list of issues resolved see:
> https://issues.apache.org/jira/projects/ARIES/versions/12344197
>
> Release Notes - Aries - Version rsa-1.14.0
>
> ** Bug
> * [ARIES-1846] - Topologymanager doesn't import
> org.osgi.service.clusterinfo.* remote services
> * [ARIES-1847] - IllegalArgumentException: Path cannot be null when
> handling zookeeper event
> * [ARIES-1850] - Local service modification is not reflected in changed
> export registration
> * [ARIES-1851] - NoClassDefFoundError ZooTrace on shutdown of zookeeper
> discovery
> * [ARIES-1906] - Regression - export of superclass interface fails
> * [ARIES-1907] - IllegalStateException when stopping bundle
> * [ARIES-1913] - Exception event properties are incorrect
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: Draft of Aries board report for April 2019

[David Bosschaert]

+1 from me too!

David

On Thu, 11 Apr 2019 at 06:04, Christian Schneider 
wrote:

> I prepared a draft of the board report for April.
> Please give feedback fast as I am a little late with submitting it :-)
>
> cheers,
>
> Christian
>
> 
>
> ## Description:
>  - Apache Aries delivers a set of pluggable Java components enabling an
> enterprise OSGi application programming model.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>  - Several feature and bugfix releases
>  - OSGi CDI specification is now released. With Aries CDI as reference
> implementation.
>  - Aries Journaled Events progressed well but is now a bit stalled as we
> try to join forces with Data in Motion to work together
>on an OSGi spec around messaging. It is not yet decided where the spec
> will be hosted.
>  - All subprojects of Aries are have now migrated to gitbox
>
> ## Health report:
>  - Good activity in the new projects like CDI and JAX-RS-Whiteboard. Most
> other projects are more in maintenance mode.
>  - We plan to retire the oldest parts of Aries the have not been touched
> for years to give more focus to the active subprojects.
>
> ## PMC changes:
>
>  - Currently 41 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Carlos Sierra Andrés on Tue Jul 03 2018
>
> ## Committer base changes:
>
>  - Currently 56 committers.
>  - Daniel Estermann was added as a committer on Fri Feb 22 2019
>
> ## Releases:
>
>  - cdi-1.0.0 was released on Sun Feb 10 2019
>  - cdi-1.0.1 was released on Thu Mar 07 2019
>  - cdi-1.0.2 was released on Sat Apr 06 2019
>  - jax-rs-whiteboard-1.0.4 was released on Mon Feb 25 2019
>  - jax-rs-whiteboard-integrations-1.0.2 was released on Mon Feb 25 2019
>  - spifly-1.2.1 was released on Tue Mar 12 2019
>  - tx-control-1.0.1 was released on Tue Feb 26 2019
>  - blueprint-core-1.10.2 was released on Fri Mar 22 2019
>  - cdi-extension-http-1.0.1 was released on Thu Mar 07 2019
>  - jpa-2.7.2 was released on Sat Feb 16 2019
>  - proxy-impl-1.1.4 was released on Thu Jan 17 2019
>
> ## Mailing list activity:
>
>  - dev@aries.apache.org:
> - 123 subscribers (down -2 in the last 3 months):
> - 312 emails sent to list (413 in previous quarter)
>
>  - u...@aries.apache.org:
> - 233 subscribers (up 0 in the last 3 months):
> - 12 emails sent to list (50 in previous quarter)
>
>
> ## JIRA activity:
>
>  - 29 JIRA tickets created in the last 3 months
>  - 20 JIRA tickets closed/resolved in the last 3 months
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Apache Aries Blueprint Core 1.10.2 release

[David Bosschaert]

+1

David

On Mon, 18 Mar 2019 at 17:32, Jean-Baptiste Onofré  wrote:

> Hi all,
>
> I submit Apache Aries Blueprint Core 1.10.2 release to your vote.
>
> We fixed one issue in this release:
>   * [ARIES-1886] - Globally configurable number of extender threads and
> grace period timeout
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12345020
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1160
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Aries sources now on git

[David Bosschaert]

Thanks a lot Christian!

David

On Fri, 15 Mar 2019 at 12:56, Guillaume Nodet  wrote:

> Awesome ! I've just pushed my first commit there in order to test it :-)
>
> Le jeu. 14 mars 2019 à 22:44, Christian Schneider  >
> a écrit :
>
> > The main Aries sources are now migrated from svn to git. (See
> > https://issues.apache.org/jira/browse/INFRA-17806).
> >
> > This means all committers can now directly work using the github repo
> > https://github.com/apache/aries.
> > You should be able to directly merge pull requests done on github.
> >
> > A small downside is that working with github requires to enable two
> factor
> > authentication.
> > See https://gitbox.apache.org/setup/
> >
> > I found that the conversion screwed the existing pull requests. So please
> > recreate or rebase existing pull requests.
> >
> > Cheers,
> >
> > Christian
> >
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Computer Scientist
> > http://www.adobe.com
> >
>
>
> --
> 
> Guillaume Nodet
>

Re: [VOTE] Release Spi-Fly Version 1.2.1

[David Bosschaert]

+1

Thanks Ray!

David

On Thu, 7 Mar 2019 at 20:16, Raymond Auge  wrote:

> Hello everyone,
>
> Here are the release notes for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344558
>
> The staging repo is here:
> https://repository.apache.org/content/repositories/orgapachearies-1158
>
> 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 1158 /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.
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.4 and integrations 1.0.2

[David Bosschaert]

+1

David

On Thu, 21 Feb 2019 at 14:37, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.4 for Aries JAX-RS Whiteboard and 1.0.2 for
> whiteboard integrations.
>
> The release notes for Whiteboard 1.0.4 can be found here:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344853
>
> The modules are tagged at
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs-1.0.4
>
> and
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs.integration-1.0.2
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1156
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all.
>
> Carlos.
>
>
>
>

Re: [VOTE] Release Aries Transaction Control Services and Providers 1.0.1

[David Bosschaert]

+1

David

On Thu, 21 Feb 2019 at 15:34, Timothy Ward  wrote:

> Hello all,
>
> I have staged a release 1.0.1 for the entirety of Aries Transaction
> Control.
>
> The release notes for this release can be found here<
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344984>,
> but are included below for your convenience:
>
> Artifacts are in one staged repo
> https://repository.apache.org/content/repositories/orgapachearies-1157
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all.
>
> Tim
>
> Release Notes
> 
> Improvement
>
>   *   [ARIES-1897] -
> Update to HikariCP 3.3.0
>   *   [ARIES-1898] -
> Update to bnd 4.1.0
>
> Test
>
>   *   [ARIES-1895] -
> Add tests for OpenJPA 3.0
>   *   [ARIES-1896] -
> Provide integration tests for the Transaction Control Service
> implementations
>
>

Re: [VOTE] Release Aries CDI version 1.0.0

[David Bosschaert]

+1

David

On Wed, 6 Feb 2019 at 20:07, Raymond Auge  wrote:

> Hi,
> This is release 1.0.0 of Aries CDI, the very first implementation of
> OSGi CDI Integration spec v1.0.
>
> Staging repository is
> here:
> https://repository.apache.org/content/repositories/orgapachearies-1154
>
> 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.
>
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [DISCUSS] Retire old modules?

[David Bosschaert]

+1 from me.

David

On Fri, 18 Jan 2019 at 14:03, Raymond Auge  wrote:

> +1
>
> Thanks for doing this Christian. It was on my TODO list :)
>
> (now to fix jenkins builds which have been broken for several months...)
>
> - Ray
>
> On Fri, Jan 18, 2019 at 4:36 AM Jean-Baptiste Onofré 
> wrote:
>
> > +1
> >
> > it makes sense regarding the activity ;)
> >
> > Regards
> > JB
> >
> > On 18/01/2019 09:40, Christian Schneider wrote:
> > > I have compiled a list of old modules in Aries that I think we should
> > > retire.
> > > The modules below were not touched for a long time. I propose we move
> > these
> > > to a branch "attic" and remove them from master.
> > > What do you think?
> > >
> > > Christian
> > >
> > > ---
> > > Modules proposed to remove:
> > >
> > > - application (5 years)
> > > - eba-maven-plugin (6 years)
> > > - ejb (5 years)
> > > - esa-ant-task (4 years)
> > > - esa-maven-plugin (2 years)
> > > - quiesce (5 years)
> > > - samples (3 years)
> > > - sandbox/samplee (3 years)
> > > - tutorials (3 years)
> > > - web (4 years)
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [VOTE] Apache Aries Proxy Impl 1.1.4 release

[David Bosschaert]

+1

David

On Mon, 14 Jan 2019 at 10:15, Jean-Baptiste Onofré  wrote:

> Hi all,
>
> I submit Apache Aries Proxy Impl 1.1.4 release to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344825
>
> It contains a fix (ARIES-1849) to deal with interface default methods.
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1153/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.3 and integrations 1.0.1

[David Bosschaert]

+1

David

On Fri, 21 Dec 2018 at 14:09, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.3 for Aries JAX-RS Whiteboard and 1.0.1 for
> whiteboard integrations.
>
> This release fixes a bug that was causing a bad interaction with Karaf,a
> missing license headers and a wrong artifact reference in the former
> release of the whiteboard integrations.
>
> The release notes for Whiteboard 1.0.3 can be found here:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344639
>
> The modules are tagged at
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs-1.0.3
>
> and
>
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs.whiteboard.integrations-1.0.1
>
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1152
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all.
>
> Carlos.
>
>
>

Re: [vote] Removing the reactor POM from root of main Aries repo

[David Bosschaert]

Hi Ray,

Sounds like a good plan to me.

Best regards,

David

On Mon, 17 Dec 2018 at 17:07, Raymond Auge  wrote:

> Hey all,
>
> I'd like to remove the reactor POM from the root of the main Aries repo.
> This is just a source of pain for attracting new contributors who don't
> realize that the Aries repo has evolved to an aggregate of disparate
> projects.
>
> Thoughts?
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.2 and integrations 1.0.0

[David Bosschaert]

+1

David

On Mon, 10 Dec 2018 at 18:15, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.2 for Aries JAX-RS Whiteboard and 1.0.0 for
> whiteboard integrations.
>
> The release notes for Whiteboard 1.0.2 can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343907=12310981
>
> The release notes for whiteboard integrations can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344174
>
> The module is tagged at
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs.whiteboard.integrations-1.0.0
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1151
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all,
>
> Carlos.
>
>

Re: [VOTE] Apache Aries Proxy Impl 1.1.3 release

[David Bosschaert]

+1

David

On Sat, 8 Dec 2018 at 14:49, Jean-Baptiste Onofré  wrote:

> Hi all,
>
> I submit Apache Aries Proxy Impl 1.1.3 release to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344611
>
> Basically, this release extends the ASM import version range to support
> ASM 7 (used in Apache Karaf to have a better support of Java 11).
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1150/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Aries Blueprint Core 1.10.1 & Blueprint CM 1.3.1 release

[David Bosschaert]

+1

David

On Tue, 4 Dec 2018 at 08:00, Jean-Baptiste Onofré  wrote:

> Hi all,
>
> I submit Apache Aries Blueprint Core 1.10.1 & Blueprint CM 1.3.1 release
> to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12343583
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=12344423
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1149/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Aries JPA 2.7.1

[David Bosschaert]

+1

David

On Mon, 3 Dec 2018 at 16:35, Christian Schneider 
wrote:

> I've staged a release for vote at:
> https://repository.apache.org/content/repositories/orgapachearies-1148
>
> It mainly contains an important bugfix when mixing transactional and non
> transactional behaviour. Thanks to Daniel for the fix.
>
> I was also notified that the Aries JPA example currently does not work in
> apache karaf 4.2.1.
> The error is in blueprint core. So it does not affect our release. JB is
> working on a fix for karaf 4.2.2. See
> https://github.com/apache/aries-jpa/tree/master/examples
>
> Release Notes - Aries - Version jpa-2.7.1
>
> https://issues.apache.org/jira/projects/ARIES/versions/12343100
>
> ** Bug
>
> * [ARIES-1783] - TransactionRequiredException when non-transactional
> method precedes a transactional one in the same service.
>
> * [ARIES-1869] - Example does not work with current karaf 4.2.1
>
> Please review and vote:
>
>   [ ] +1 Release the above artifacts
>   [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Release Aries SpiFly version 1.2

[David Bosschaert]

+1

Thanks Ray!

David

On Tue, 20 Nov 2018 at 04:57, Raymond Auge  wrote:

> Hello everyone,
>
> We solved the following issues in this release:
> *Bug*
> [ARIES-1739] - Specifiying a version in Require-Capability prevents
> registration
> [ARIES-1857] - Regression in framework.extension due to work on
> ARIES-1739
> [ARIES-1860] - Dynamic Spifly fails on java 11
> [ARIES-1863] - Ensure type compatibility when running in an environment
> that already has bnd uses elsewhere
> [ARIES-1864] - Fix failure in security compliance test
> *New Feature*
> [ARIES-1806] - Support to create prototype scoped services
> *Improvement*
> [ARIES-1859] - source of org.apache.aries.spifly.dynamic.bundle on
> maven isn't complete
> [ARIES-1862] - Remove superfluous transitive dependencies from spifly
> dynamic.bundle
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981=1235
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1147
>
> 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.
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [VOTE] Release Aries spi-fly version 1.1

[David Bosschaert]

+1

Thanks Ray!

David

On Wed, 31 Oct 2018 at 00:29, Raymond Auge  wrote:

> Hi,
>
> The following issues were addressed in this release:
>
> ** Improvement
> * [ARIES-1854] - Add support for ServiceLoader.load(Class, ClassLoader)
> * [ARIES-1855] - Finish removing legacy of LogService
>
> ** Dependency upgrade
> * [ARIES-1844] - Support for ASM 7 (Java 11)
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARIES%20AND%20fixVersion%20%3D%20spifly-1.1
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1146
>
> 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.
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [VOTE] Release Apache Aries Remote Service Admin 1.13.0 (OSGi R7)

[David Bosschaert]

+1 from me!

Thanks Christian!

David

On Mon, 1 Oct 2018 at 10:40, Christian Schneider 
wrote:

> This release fixes some bugs that were reported by users and found during
> stabilization of the OSGi R7 CT checks.
>
> See here for the specs we implement:
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteservices.html
>
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteserviceadmin.html
>
> Keep in mind though that at the moment only the TCP transport fully
> supports the new spec.
>
> I've staged the release at
>
> https://repository.apache.org/content/repositories/orgapachearies-1145
>
> For a list of issues resolved see:
>
> https://issues.apache.org/jira/projects/ARIES/versions/12342751
>
>
> Release Notes - Aries - Version rsa-1.13.0
>
> ** Bug
> * [ARIES-1751] - Typo in namespace url in
> OSGI-INF/metatype/zookeeper.xml
> * [ARIES-1788] - NPE on log line
> * [ARIES-1815] - ConcurrentModificationException in
> TopologyManagerImport.unImportForGoneEndpoints
> * [ARIES-1817] - Export remove do no always end up in REMOVE events
> (timing issue)
> * [ARIES-1837] - ConcurrentModificationException in
> InterestManager.endpointChanged
> * [ARIES-1838] - Zookeeper discovery does not send modified events
> * [ARIES-1839] - Invalid zookeeper path
> /osgi/service_registry#osgi#service_registry is created
> * [ARIES-1840] - ConcurrentModificationException in
>
> org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.importServices
>
> ** Test
> * [ARIES-1835] - TestFastbinRoundTrip fails in a high percentage of the
> builds
>
> ** Dependency upgrade
> * [ARIES-1779] - Upgrade ZooKeeper to 3.4.13
> * [ARIES-1822] - Upgrade plugins
>
>
> Please review and vote
>
> Here is my
> +1
>
> Christian
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.1

[David Bosschaert]

+1

David

On Tue, 25 Sep 2018 at 11:33, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.1 for Aries JAX-RS Whiteboard. It brings bug
> fixes and a new optional feature to prepend paths to all applications
> inside a whiteboard.
>
> The module is tagged at
>
> https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=refs/tags/org.apache.aries.jax.rs-1.0.1
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1144
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1144 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Here is my +1.
>
> Thanks to all,
>
> Carlos.
>
>

Re: [VOTE] SpiFly 1.0.14

[David Bosschaert]

+1

Thanks Ray!

David

On Mon, 20 Aug 2018 at 21:03, Raymond Auge  wrote:

> Hi All,
>
> I have staged a release of SpiFly for vote at:
>
> https://repository.apache.org/content/repositories/orgapachearies-1142
>
> Release Notes:
>
> Release Notes - Aries - Version spifly-1.0.14
> ** Improvement
> * [ARIES-1814] - Solve the start order limitations with SPI Fly
>
> How to verify release:
> http://aries.apache.org/development/verifyingrelease.html
>
> Please review and vote:
> [ ] +1 Release the above artifacts
> [ ] -1 Do not
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

Re: [HEADS UP] Move current git repos to gitbox

[David Bosschaert]

+1 from me too!

David

On Fri, 27 Jul 2018 at 14:19, Christian Schneider 
wrote:

> It seems that our git repos are still on git-wip. I would like to move them
> to gitbox.
> This allows us to directly work with the github UI like reviewing, merging
> and closing PRs.
>
> The current repos we have are:
> https://github.com/apache/aries-rsa
> https://github.com/apache/aries-jpa
> https://github.com/apache/aries-jax-rs-whiteboard
> https://github.com/apache/aries-containers
>
> This is already on gitbox:
> https://github.com/apache/aries-tx-control
>
> If no one objects during the next days I will ask infra to move the repos.
>
> Christian
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: spifly changes

[David Bosschaert]

Hi Ray,

I see what you mean now. I dug a little in the history and noticed that the
code that populated the logService had been removed some time ago (the
class used to have a LogServiceTracker).
Ah well, at least that is fixed now with your changes writing to JUL...

Thanks!

David

On Thu, 19 Jul 2018 at 23:41, Raymond Auge  wrote:

> David, that's the logging side... But it does nothing because there are
> never any log services.
>
> - Ray
>
> On Thu, Jul 19, 2018, 15:20 David Bosschaert, 
> wrote:
>
> > Thanks Ray!
> >
> > Just for completeness, one file that uses this a few times is this one:
> >
> >
> https://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-core/src/main/java/org/apache/aries/spifly/Util.java
> >
> > Just search for 'BaseActivator.activator.log(' in there...
> >
> > Best regards,
> >
> > David
> >
> > On Thu, 19 Jul 2018 at 18:41, Raymond Auge 
> > wrote:
> >
> > > I've made a change as you've suggested.
> > >
> > > - Ray
> > >
> > > On Thu, Jul 19, 2018 at 12:58 PM, Raymond Auge <
> raymond.a...@liferay.com
> > >
> > > wrote:
> > >
> > > > David, regarding the log change, I couldn't find any code that
> > populated
> > > > the log services anywhere, not through reflection, not through
> > > inheritance,
> > > > nothing.
> > > >
> > > > Maybe you could show me where that takes place.
> > > >
> > > > - Ray
> > > >
> > > > On Thu, Jul 19, 2018 at 9:35 AM, Raymond Auge <
> > raymond.a...@liferay.com>
> > > > wrote:
> > > >
> > > >>
> > > >>
> > > >> On Thu, Jul 19, 2018 at 9:28 AM, David Bosschaert <
> > > >> david.bosscha...@gmail.com> wrote:
> > > >>
> > > >>> Thanks Ray!
> > > >>>
> > > >>> It looks good to me except for one thing. This commit
> > > >>> https://svn.apache.org/r1836063 changes the log() method in the
> base
> > > >>> activator to do nothing. I understand that this is to ensure that
> the
> > > >>> framework extension has no external dependencies but that log()
> > method
> > > is
> > > >>> actually used quite a lot. (Just run find . -name "*.java" | xargs
> > grep
> > > >>> 'log(' and you'll find 24 or so references).
> > > >>> I think losing those log messages may not be ideal :)
> > > >>>
> > > >>
> > > >> I'll double check, but I think the logging code was not even used,
> > ever.
> > > >>
> > > >>
> > > >>
> > > >>>
> > > >>> Being a framework extension you don't want to have any dependencies
> > > going
> > > >>> to the outside, but would it be an idea to replace those logging
> > > message
> > > >>> with java.util.logging ones?
> > > >>>
> > > >>
> > > >> Perhaps. I'll check about this.
> > > >>
> > > >> Thanks for reviewing David. I'll keep you posted.
> > > >>
> > > >> - Ray
> > > >>
> > > >>
> > > >>>
> > > >>> Best regards,
> > > >>>
> > > >>> David
> > > >>>
> > > >>> On Mon, 16 Jul 2018 at 21:14, Raymond Auge <
> raymond.a...@liferay.com
> > >
> > > >>> wrote:
> > > >>>
> > > >>> > @David Bosschaert, et al,
> > > >>> >
> > > >>> > Could you take a look at the changes I made for
> > > >>> > https://issues.apache.org/jira/projects/ARIES/issues/ARIES-1814
> ?
> > > >>> >
> > > >>> > Basically, I changed the logic that correlated the woven imported
> > > >>> package
> > > >>> > back to the extender, which previously used package attributes. I
> > > >>> replaced
> > > >>> > it with "uses" constraints on the osgi.extender capability:
> > > >>> >
> > > >>> > e.g.
> > > >>> > >
> > > >>> >
> > > >>> > osgi.extender;osgi.extender=osgi.serviceloader.processor;ver
> > > >>> sion:Version=1.0;uses:="org.apa

Re: spifly changes

[David Bosschaert]

Thanks Ray!

It looks good to me except for one thing. This commit
https://svn.apache.org/r1836063 changes the log() method in the base
activator to do nothing. I understand that this is to ensure that the
framework extension has no external dependencies but that log() method is
actually used quite a lot. (Just run find . -name "*.java" | xargs grep
'log(' and you'll find 24 or so references).
I think losing those log messages may not be ideal :)

Being a framework extension you don't want to have any dependencies going
to the outside, but would it be an idea to replace those logging message
with java.util.logging ones?

Best regards,

David

On Mon, 16 Jul 2018 at 21:14, Raymond Auge  wrote:

> @David Bosschaert, et al,
>
> Could you take a look at the changes I made for
> https://issues.apache.org/jira/projects/ARIES/issues/ARIES-1814 ?
>
> Basically, I changed the logic that correlated the woven imported package
> back to the extender, which previously used package attributes. I replaced
> it with "uses" constraints on the osgi.extender capability:
>
> e.g.
> >
>
> osgi.extender;osgi.extender=osgi.serviceloader.processor;version:Version=1.0;uses:="org.apache.aries.spifly"
>
> which assures the imported package `org.apache.aries.spifly` must come from
> the extender. Make sense?
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
> (@OSGiAlliance)
>

Re: [VOTE] Aries parent 2.1.0

[David Bosschaert]

+1

David

On Sat, 14 Jul 2018 at 10:31, Dominik Przybysz  wrote:

> Hi,
> I have staged a release for vote at:
> https://repository.apache.org/content/repositories/orgapachearies-1141
>
> Release Notes:
> Improvement
>
>- [ARIES-1809 ] - Run
>rat plugin by default
>- [ARIES-1818 ] -
>Upgrade java version to 8 and aries parent to 20
>
>
> How to verify release:
> http://aries.apache.org/development/verifyingrelease.html
>
> Please review and vote:
> [ ] +1 Release the above artifacts
> [ ] -1 Do not
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529594#comment-16529594
 ] 

David Bosschaert commented on ARIES-1814:
-

Thanks for offering to help out with this issue [~rotty3000]!

> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in 
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as 
> Import-Package



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

[jira] [Assigned] (ARIES-1814) Solve the start order limitations with SPI Fly

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1814:
---

Assignee: Raymond Augé  (was: David Bosschaert)

> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in 
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as 
> Import-Package



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

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.0 (take two)

[David Bosschaert]

+1

David

On Tue, 26 Jun 2018 at 16:26, Carlos Sierra Andrés 
wrote:

> Hello again,
>
> I have staged a new release 1.0.0 for Aries JAX-RS Whiteboard.
>
> The module is tagged at
>
> https://github.com/apache/aries-jax-rs-whiteboard/releases/tag/org.apache.aries.jax.rs-1.0.0
>
> Artifacts are in one staged repo:
> https://repository.apache.org/content/repositories/orgapachearies-1140
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1140 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> There are a couple of RAT warnings in highlight.js and github.css that
> should be covered in LICENSE file.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Bests,
>
> Carlos Sierra.
>
>

[jira] [Assigned] (ARIES-1814) Solve the start order limitations with SPI Fly

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1814:
---

Assignee: David Bosschaert

> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: David Bosschaert
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in 
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as 
> Import-Package



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

Re: [VOTE] Release Aries JAX-RS Whiteboard 1.0.0

[David Bosschaert]

+1

David

On Tue, 26 Jun 2018 at 05:46, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I have staged a release 1.0.0 for Aries JAX-RS Whiteboard.
>
> The module is tagged at
> https://git-wip-us.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;a=tag;h=d33739d7eef06620c7155f0faab3f30f08a5d118
>
> Artifacts are in one staged repo:
> https://repository.apache.org/content/repositories/orgapachearies-1139
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1139 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> There are a couple of RAT warnings in highlight.js and github.css that
> should be covered in LICENSE file.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Bests,
>
> Carlos Sierra.
>
>

Re: [VOTE] Release Aries Component-DSL 1.2.0

[David Bosschaert]

+1

David

On Fri, 22 Jun 2018 at 11:55, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> As discussed in an earlier mail thread, I have staged a release 1.2.0 for
> Aries Component DSL.
>
> The module is tagged at
> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.component-dsl.parent-1.2.0
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1138
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1138 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Thanks to all,
>
> Carlos.
>
>

Re: New release of Aries Component DSL 1.2.0

[David Bosschaert]

+1

David

On Mon, 18 Jun 2018 at 17:06, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> I would like to make a new release 1.2.0 of Aries Component DSL.
>
> Four JIRA tickets have been closed:
>
> * ARIES-1810
>
> * ARIES-1811
>
> * ARIES-1812
>
> * ARIES-1813
>
> some of which can be considered severe bugs that could prevent usage in
> some scenarios.
>
> If no one opposes I will open a vote in the next days.
>
> Thanks.
>
> Carlos.
>
>
>

Re: [VOTE] Apache Aries Proxy Impl 1.1.2 release

[David Bosschaert]

+1

David

On 7 June 2018 at 09:56, Jean-Baptiste Onofré  wrote:

> Hi all,
>
> In order to have a better support of Java 9, 10, 11, and upgrading to
> ASM 6.2, I'm submitting Aries  Proxy Impl 1.1.2 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310981=12343402
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1137/
>
> Please, review and vote:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The vote will be open for at least 72 hours.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

[jira] [Resolved] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

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

David Bosschaert resolved ARIES-1801.
-
Resolution: Fixed

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: spifly-1.0.10
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

Re: [VOTE] Release Blueprint 1.10

[David Bosschaert]

+1

David

On 4 June 2018 at 17:21, Guillaume Nodet  wrote:

> I've staged a bunch of blueprint artifacts to the following repositories:
> https://repository.apache.org/content/repositories/orgapachearies-1134
> 
> https://repository.apache.org/content/repositories/orgapachearies-1135
>
> Below is a list of changes.  The most important one is ARIES-1298 which
> affects a bunch of bundles and warrant a minor (vs micro) update.
>
> 
>
> cb260e7d9 [ARIES-1793] Blueprint interceptors do not work anymore
>
> a3413a963 [ARIES-1805] Blueprint core does not honor Java beans
> specification
>
> 4fda9b5dc [ARIES-1761] Provide support for camel-spring from
> blueprint-spring
>
> 4e89276a0 [ARIES-1298] Support typed configurations in property
> placeholders
>
> df905723c [ARIES-1009] BlueprintContainerImpl - Add INFO logging when the
> blueprint container has been created
>
> e832f7917 Upgrade blueprint-noosgi to latest blueprint-core / parser
>
> 3188ff944 [ARIES-1781] ExtendedReferenceMetadata should extend
> ExtendedServiceReferenceMetadata
>
> Please review and vote !
>
> Cheers,
> Guillaume Nodet
>

Re: [VOTE] Release transaction-jdbc 2.1.3

[David Bosschaert]

+1

David

On 4 June 2018 at 17:28, Guillaume Nodet  wrote:

> I've staged another release at:
>   https://repository.apache.org/content/repositories/orgapachearies-1136
>
> This fixes the following problems:
>
> 7499ef6a3 [ARIES-1790] ValidatingDelegatingManagedConnectionFactory is not
> used with aries.xa.validateOnMatch
>
> 5eca2985c [ARIES-1550] getConnection with null user. Closes #47
>
> 01ef4c88c ARIES-1276: Add monitoring capability via MBean to Aries
> Transaction JDBC
>
> Please review and vote !
>
> Cheers,
> Guillaume
>

[jira] [Commented] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497985#comment-16497985
 ] 

David Bosschaert commented on ARIES-1801:
-

[~vampire] FYI the release thread has started. Feel free to vote :) 
http://mail-archives.apache.org/mod_mbox/aries-dev/201806.mbox/%3CCAMit8Soa_g5wQXL6zHx0DESyY%2BC4pJannmanLe79Nc_LxHZ7FA%40mail.gmail.com%3E

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: spifly-1.0.10
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

Re: [VOTE] Release Aries Component-DSL 1.1.0

[David Bosschaert]

+1

David

On 1 June 2018 at 11:39, Carlos Sierra Andrés  wrote:

> Hello all,
>
> As discussed in an earlier mail thread, I have staged a release 1.1.0
> for Aries Component DSL.
>
> The module is tagged at
> https://svn.apache.org/repos/asf/aries/tags/org.apache.
> aries.component-dsl.parent-1.1.0
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1132
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> MAVEN_OPTS='-Dbnd.baseline.skip=true' ./verify_staged_release.sh 1132
> mytempdirectory 2>&1 | tee verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> I add the bnd.baseline.skip because the plugin is incorrectly using
> 1.1.0-SNAPSHOT as the baseline instead of 1.0.0.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Bests,
>
> Carlos Sierra.
>
>

[jira] [Commented] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492420#comment-16492420
 ] 

David Bosschaert commented on ARIES-1801:
-

[~vampire] I'll prepare a release soon.

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: spifly-1.0.10
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Updated] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1801:

Affects Version/s: (was: 1.0)
   spifly-1.0.10

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: spifly-1.0.10
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Updated] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1801:

Fix Version/s: spifly-1.0.12

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Assigned] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1801:
---

Assignee: David Bosschaert

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Björn Kautler
>Assignee: David Bosschaert
>Priority: Major
> Fix For: spifly-1.0.12
>
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Commented] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490663#comment-16490663
 ] 

David Bosschaert commented on ARIES-1801:
-

I added a commit with an additional test:
https://svn.apache.org/viewvc?view=revision=1832236

I *think* that the test should be exactly what you're describing in this issue, 
but the test passes so it's probably missing something. 
[~vampire] would you be able to add/modify a test in the codebase which exposes 
the problem?

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Björn Kautler
>Priority: Major
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Commented] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489205#comment-16489205
 ] 

David Bosschaert commented on ARIES-1801:
-

Hmm, but when I run the test with the two lines you quoted commented out, the 
test still passes. Or am I missing something?

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Björn Kautler
>Priority: Major
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

[jira] [Commented] (ARIES-619) Fix SPI-FLY and SUBSYSTEM tio use release by bundle scheme

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489199#comment-16489199
 ] 

David Bosschaert commented on ARIES-619:


This is a very old issue and I'm not sure it's still relevant. [~zoe] 
[~hughesj] do you think we still need this, or can the issue be closed?

> Fix SPI-FLY and SUBSYSTEM tio use release by bundle scheme
> --
>
> Key: ARIES-619
> URL: https://issues.apache.org/jira/browse/ARIES-619
> Project: Aries
>  Issue Type: Bug
>Reporter: zoe slattery
>Assignee: Jeremy Hughes
>Priority: Major
>
> In summary:
> Split parent and reactor poms (Reactor just contains a list of modules, no 
> SCM element)
> Add packageinfo files for package export versions
> Make each bundle pom depend on the 0.4 released parent (if possible)
> Switch depenedencies to point at released versions (where possible)
> Add an SCM element to each modules pom.
> Fix build warnings caused by default settings for maven-bundle-plugin



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

[jira] [Commented] (ARIES-1470) java.util.ServiceConfigurationError

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489198#comment-16489198
 ] 

David Bosschaert commented on ARIES-1470:
-

[~setya] Is this issue still relevant, or can we close it?

> java.util.ServiceConfigurationError
> ---
>
> Key: ARIES-1470
> URL: https://issues.apache.org/jira/browse/ARIES-1470
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.6
> Environment: Eclipse Virgo Jetty Server 3.6.4, Spring Framework 3.2.5
>Reporter: Setya
>Priority: Major
>
> Deploying application that relies on 3rd party framework that's using 
> ServiceLoader into Eclipse Virgo intermittenly causes the following exception 
> to be thrown:
> Caused by: java.util.ServiceConfigurationError: 
> org.axonframework.serializer.ContentTypeConverter: Provider 
> org.axonframework.serializer.converters.ByteArrayToInputStreamConverter not a 
> subtype
>   at java.util.ServiceLoader.fail(ServiceLoader.java:231)
>   at java.util.ServiceLoader.access$300(ServiceLoader.java:181)
>   at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:369)
>   at java.util.ServiceLoader$1.next(ServiceLoader.java:445)
>   at 
> org.axonframework.serializer.ChainingConverterFactory.(ChainingConverterFactory.java:51)
>   at 
> org.axonframework.serializer.AbstractXStreamSerializer.(AbstractXStreamSerializer.java:106)
>   at 
> org.axonframework.serializer.AbstractXStreamSerializer.(AbstractXStreamSerializer.java:81)
>   at 
> org.axonframework.serializer.AbstractXStreamSerializer.(AbstractXStreamSerializer.java:70)
>   at 
> org.axonframework.serializer.xml.XStreamSerializer.(XStreamSerializer.java:53)
>   at 
> org.axonframework.contextsupport.spring.FileSystemEventStoreBeanDefinitionParser.doParse(FileSystemEventStoreBeanDefinitionParser.java:76)
>   at 
> org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:85)
>   at 
> org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:59)
>   at 
> org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73)
>   at 
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1438)
>   at 
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1428)
>   at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:195)
>   at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:139)
>   at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:108)
>   at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
>   at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
>   ... 21 common frames omitted
> Have tried to weave static bundle using SPI Fly, but the problem persists.



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

[jira] [Closed] (ARIES-938) Proposal: SPI Catch (plug-in discovery for both plain Java >=5 and OSGi)

[David Bosschaert (JIRA)]

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

David Bosschaert closed ARIES-938.
--
Resolution: Won't Do

> Proposal: SPI Catch (plug-in discovery for both plain Java >=5 and OSGi)
> 
>
> Key: ARIES-938
> URL: https://issues.apache.org/jira/browse/ARIES-938
> Project: Aries
>  Issue Type: New Feature
>Reporter: Jeremias Maerki
>Priority: Major
> Attachments: spi-catch.zip
>
>
> As discussed in http://aries.markmail.org/thread/i2vgjryf5caitqmy I propose a 
> new component for Apache Aries, code-named "SPI Catch", as a complement to 
> SPI Fly.
> SPI Catch provides an abstraction to plug-in discovery that for libraries 
> that make use of the JAR service provider mechanism (through 
> META-INF/services) to discover plug-ins. It shields the client from OSGi 
> specifics but all the same offering the dynamics provided through the OSGi 
> service registry. It is an deal counter-part to Apache Aries SPI Fly which is 
> used to publish SPI providers as OSGi services. And finally, another focus is 
> on preserving the runnability totally outside of OSGi.



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

[jira] [Commented] (ARIES-1801) SPI Fly does not work with a dynamic class object

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489175#comment-16489175
 ] 

David Bosschaert commented on ARIES-1801:
-

Interestingly enough, there seems to be a test for this use case:

The method testClientSpecifyingDifferentMethodsLimitedToDifferentProviders() in 
https://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-dynamic-bundle/src/test/java/org/apache/aries/spifly/dynamic/ClientWeavingHookTest.java
internally exercises the testService() method in 
https://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-dynamic-bundle/src/test/java/org/apache/aries/spifly/dynamic/TestClient.java
 which passes a Class object which is a parameter to the method to 
ServiceLoader.load()

So I guess the question is: how is the use-case filed in this issue different?

> SPI Fly does not work with a dynamic class object
> -
>
> Key: ARIES-1801
> URL: https://issues.apache.org/jira/browse/ARIES-1801
> Project: Aries
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Björn Kautler
>Priority: Major
>
> SLF4J changes in version 1.8 how implementations are looked up to 
> {{java.util.ServiceLoader}}.
> In our codebase we dynamically search for an SLF4J implementation and use a 
> default logger if none is found.
> To adapt to the new mechanism but remain compatible with SLF4J 1.7 I added to 
> our codebase
> {code:java}
> try {
> // post-1.8 mechanism
> Class slf4jServiceProviderClass = 
> Class.forName("org.slf4j.spi.SLF4JServiceProvider");
> if (ServiceLoader.load(slf4jServiceProviderClass).iterator().hasNext()) {
> noLogger.set(false);
> return true;
> }
> } catch (ClassNotFoundException e) {
> // ignore
> }
> {code}
> If I now use the {{org.apache.aries.spifly.dynamic.bundle}} 1.0.10, I get an 
> exception as SPI Fly seemingly only supports class constants. While 
> traversing the ASM tree it remembers the last class constant seen and uses 
> that to transform the {{load}} call.
> Here the exception I get:
> {code:java}
> java.lang.ClassFormatError: Weaving hook failed.
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2479)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>   at 
> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.javacord.core.util.logging.ExceptionLoggerDelegateImpl.(ExceptionLoggerDelegateImpl.java:20)
>   at 
> org.javacord.core.util.DelegateFactoryDelegateImpl.createExceptionLoggerDelegate(DelegateFactoryDelegateImpl.java:180)
>   at 
> org.javacord.api.util.internal.DelegateFactory.(DelegateFactory.java:74)
>   at org.javacord.api.DiscordApiBuilder.(DiscordApiBuilder.java:20)
>   at net.kautler.test.osgi.OsgiTest.start(OsgiTest.java:17)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: value null
>   at org.objectweb.asm.ClassWriter.newConstItem(ClassWriter.java:1057)
>   at org.objectweb.asm.MethodWriter.visitLdcInsn(MethodWriter.java:1126)
>   at 
> org.apache.aries.spifly.weaver.TCCLSetterVisitor$TCCLSetterMethodVisitor.visitMethodInsn(TCCLSetterVisitor.java:194)
>   at org.objectweb.asm.ClassReader.readCode(ClassReader.java:1416)
>   at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1017)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:693)
>   at org.objectweb.asm.ClassReader.accept(ClassReader.java:506)
>   at 
> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
>   at 
> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>   ... 16 more
> {code}



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

Re: [VOTE] Release Aries transaction blueprint 2.2.0

[David Bosschaert]

+1

David

On 15 May 2018 at 14:25, Christian Schneider 
wrote:

> This release of Aries transaction blueprint mainly fixes issues.
>
> I've staged the release at
> https://repository.apache.org/content/repositories/orgapachearies-1131/
>
> For a list of issues resolved see:
> https://issues.apache.org/jira/projects/ARIES/versions/12340653
>
> Release Notes - Aries - Version transaction-blueprint-2.2.0
>
> ** Bug
> * [ARIES-1690] - Ignored rollbackOn element of Transactional annotation
> * [ARIES-1800] - rollbackOn element of Transactional annotation ignored
> when set on class level
>
>
> Please review and vote
>
> Here is my
> +1
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Blueprint maven plugin 1.10.0

[David Bosschaert]

+1

David

On 10 May 2018 at 20:30, Dominik Przybysz  wrote:

> Hi,
>
> I have release artifact:
>
> - blueprint-maven-plugin-1.10.0
>
> Release notes:
>
> [Bug
> [ARIES-1791] - blueprint-maven-plugin generate mojo is not threadSafe
> Improvement
> [ARIES-1792] - blueprint-maven-plugin slows down compilation
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/orgapachearies-1130
>
> Please review and vote
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

Re: [VOTE] Release Aries Component-DSL 1.0.0

[David Bosschaert]

+1

David

On 30 April 2018 at 20:47, Carlos Sierra Andrés 
wrote:

> Hello all,
>
> As discussed in an earlier mail thread, Aries Component DSL 1.0 is a
> dependency for Aries JAX-RS Whiteboard 1.0, which will be the reference
> implementation for the JAX-RS Whiteboard from OSGi R7.
>
> The module is tagged at
> https://svn.apache.org/repos/asf/aries/tags/org.apache.
> aries.component-dsl.parent-1.0.0
>
> Artifacts are in one staged repo,
> https://repository.apache.org/content/repositories/orgapachearies-1129
>
> Instructions for verifying the release are at
> http://aries.apache.org/development/verifyingrelease.html. Alternately,
> cut and paste the following to run a full check:
>
> -
>
> wget --no-check-certificate
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1129 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> -
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Bests,
>
> Carlos Sierra.
>
>

Re: [VOTE] Release Aries JPA 2.7.0

[David Bosschaert]

+1

David

On 26 April 2018 at 11:48, Timothy Ward  wrote:

> As discussed in an earlier mail thread, Aries JPA will be the reference
> implementation for the JPA Service 1.1 from OSGi R7. This requires a
> release of the Aries JPA container, but the whole project has moved to Git
> and started using the OSGi contract namespace since its previous release.
> I’ve therefore staged a release candidate for the whole Aries JPA project.
> The module is staged and tagged in https://git-wip-us.apache.org/
> repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
> Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1125/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1125/org/apache/aries/jpa/org.apache.
> aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours, but as that takes us into a
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ]
> +1 [ ] 0 [ ] -1
>
>

Re: [VOTE] Release Aries Tx Control 1.0.0

[David Bosschaert]

+1

David

On 30 April 2018 at 18:45, Timothy Ward  wrote:

> As discussed in an earlier mail thread, Aries Tx Control will be the
> reference implementation for the Transaction Control Service 1.0 from OSGi
> R7. This marks the first proper release of Tx Control at 1.0.0. I’ve
> therefore staged a release candidate for the whole Aries Tx Control
> project. The module is staged and tagged in https://gitbox.apache.org/
> repos/asf?p=aries-tx-control.git;a=tag;h=refs/tags/1.0.0.
>
> Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1128 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1128/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1128/org/apache/aries/tx-control/tx-
> control/1.0.0/tx-control-1.0.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours. [ ] +1 [ ] 0 [ ] -1
>
> Best Regards,
>
> Tim Ward
>

Re: [VOTE] Release Apache Aries Remote Service Admin 1.12.0 (OSGi R7) take 2

[David Bosschaert]

+1

David

On 30 April 2018 at 13:46, Christian Schneider 
wrote:

> I added the missing license headers and made sure rat runs on all builds.
> ---
>
> This release of Aries RSA is the reference implementation of Remote
> Services and Remote Service Admin from the OSGi R7 spec. It was tested
> against the TCK and passes all tests.
>
> See here for the specs we implement:
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteservices.html
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteserviceadmin.
> html
>
> Keep in mind though that at the moment only the TCP transport fully
> supports the new spec.
>
> Some highlights are:
>
>- Support for async return types like: Future, CompletableFuture,
> CompletionStage,
>Promises
>- Can transport all primitive types including the OSGi DTO types
>- Zookeeper discovery now creates a lot less nodes and needs only one
>listener
>
> I've staged the release at
>
> https://repository.apache.org/content/repositories/orgapachearies-1127
>
> For a list of issues resolved see:
>
> https://issues.apache.org/jira/projects/ARIES/versions/12341022
>
>
> Release Notes - Aries - Version rsa-1.12.0
>
> ** Bug
> * [ARIES-1759] - Fastbin fails to bind if a configuration exists with
> the same port
> * [ARIES-1760] - Primitive type do not work as parameters in TCP
> transport
> * [ARIES-1763] - Upgrade capabilities and API for remote service admin
> 1.1.0 spec
>
>
> ** New Feature
> * [ARIES-1756] - Support osgi.basic.timeout
> * [ARIES-1757] - Implement osgi.async intent
> * [ARIES-1758] - Support osgi.basic intent
> * [ARIES-1764] - Also send events using eventadmin
>
>
> ** Improvement
> * [ARIES-1769] - Make sure services with unsupported intents are not
> exported
> * [ARIES-1771] - Support modification events
> * [ARIES-1774] - Refactor Zookeeper discovery to use only one listener
> for all zk endpoints
> * [ARIES-1775] - Remove DiscoveryPlugin
> * [ARIES-1776] - Fixes for tck secure tests
> * [ARIES-1778] - Use endpoint id as path in zookeeper
>
>
> Please review and vote
>
> Here is my
> +1
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Release Apache Aries Remote Service Admin 1.12.0 (OSGi R7)

[David Bosschaert]

+1

David

On 27 April 2018 at 09:31, Christian Schneider 
wrote:

> This release of Aries RSA is the reference implementation of Remote
> Services and Remote Service Admin from the OSGi R7 spec. It was tested
> against the TCK and passes all tests.
>
> See here for the specs we implement:
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteservices.html
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteserviceadmin.
> html
>
> Keep in mind though that at the moment only the TCP transport fully
> supports the new spec.
>
> Some highlights are:
>
>- Support for async return types like: Future,
>CompletableFuture, CompletionStage, Promises
>- Can transport all primitive types including the OSGi DTO types
>- Zookeeper discovery now creates a lot less nodes and needs only one
>listener
>
> I've staged the release at
>
> https://repository.apache.org/content/repositories/orgapachearies-1113/
>
> For a list of issues resolved see:
>
> https://issues.apache.org/jira/projects/ARIES/versions/12341022
>
>
> Release Notes - Aries - Version rsa-1.12.0
>
> ** Bug
> * [ARIES-1759] - Fastbin fails to bind if a configuration exists with
> the same port
> * [ARIES-1760] - Primitive type do not work as parameters in TCP
> transport
> * [ARIES-1763] - Upgrade capabilities and API for remote service admin
> 1.1.0 spec
>
>
> ** New Feature
> * [ARIES-1756] - Support osgi.basic.timeout
> * [ARIES-1757] - Implement osgi.async intent
> * [ARIES-1758] - Support osgi.basic intent
> * [ARIES-1764] - Also send events using eventadmin
>
>
> ** Improvement
> * [ARIES-1769] - Make sure services with unsupported intents are not
> exported
> * [ARIES-1771] - Support modification events
> * [ARIES-1774] - Refactor Zookeeper discovery to use only one listener
> for all zk endpoints
> * [ARIES-1775] - Remove DiscoveryPlugin
> * [ARIES-1776] - Fixes for tck secure tests
> * [ARIES-1778] - Use endpoint id as path in zookeeper
>
>
> Please review and vote
>
> Here is my
> +1
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>

Re: [VOTE] Release Aries JPA 2.7.0

[David Bosschaert]

+1

David

On 26 April 2018 at 11:48, Timothy Ward  wrote:

> As discussed in an earlier mail thread, Aries JPA will be the reference
> implementation for the JPA Service 1.1 from OSGi R7. This requires a
> release of the Aries JPA container, but the whole project has moved to Git
> and started using the OSGi contract namespace since its previous release.
> I’ve therefore staged a release candidate for the whole Aries JPA project.
> The module is staged and tagged in https://git-wip-us.apache.org/
> repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
> Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1125/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1125/org/apache/aries/jpa/org.apache.
> aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours, but as that takes us into a
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ]
> +1 [ ] 0 [ ] -1
>
>

Re: [VOTE] Release Blueprint bundles

[David Bosschaert]

+1

David

On 5 February 2018 at 16:46, Guillaume Nodet  wrote:

> I've staged the following releases:
>Blueprint Parser 1.5.0
>Blueprint Core 1.9.0
>Blueprint CM 1.2.0
>Blueprint Spring 0.6.0
>Blueprint Spring Extender 0.4.0
>
> The staging repo is available at:
>   https://repository.apache.org/content/repositories/orgapachearies-1124
>
> Please review and vote !
>
> Here's the full log:
>
> 9daed4f7a Remove unneeded file
>
> 4d3c8d659 [ARIES-1770] Spring schemas can not be validated offline
>
> c76afdc1e [ARIES-1106] Injection to support fluent setter methods
>
> ae4bde3d5 [ARIES-1129] Implement a null proxy element
>
> c9ca94f34 Fix indentation / formatting
>
> f8c5297e4 [ARIES-1138] Fix broken unit test
>
> 8088d3832 [ARIES-1098] BeanRecipe.findMatchingMethods does not support
> "varargs"
>
> ba817a73b [ARIES-1116] Blueprint loses bounds for 
> constructors
>
> 29fd4c8c4 [ARIES-1138] Disable Blueprint Schema Validation via System
> Property
>
> 77128d7de Add constants to the BlueprintConstants interface
>
> 610c3b965 [ARIES-1282] BeanRecipe.findMatchingMethods is not able to filter
> out overridden method signatures
>
> b42d19d5c [ARIES-1248] Add test for threadpool creation with generics
>
> 06d3a60b9 [ARIES-1436] cm:managed-component destroy-method will only be
> called when it has a single integer argument
>
> 1ddc6292f [ARIES-1544] Blueprint property resolution fails for setters with
> derived type
>
> 01182e980 [ARIES-1607] Add a flag to enable raw conversion when using
> generics
>
> e8c6217d5 [ARIES-960] Improve generics support to support type inference
>
> d1b7347e2 Simplify ExtNamespaceHandler
>
> dc3675240 [ARIES-1668] Support null values inside property-placeholders
>
> 597e787df [ARIES-1738] BeanProcessor are not removed when a namespace is
> restarted
>
> 33811d686 [ARIES-1535][ARIES-1536] Implement new policies for reference
> lifecycle and damping
>
> f05631bf5 Fix various versions in poms
>
> 60803fca7 [ARIES-1717] Untie Aries Blueprint Spring (extender) to specific
> Spring version
>
> 81693822a [ARIES-1768] BlueprintDomainCombiner should not be holding a
> reference to BundleContext
>
> 1d1574030 Use generics for the ServiceTracker in BlueprintEventDispatcher
>
> 1f2ba7a65 EventAdmin events should be posted synchronously
>
>
> Cheers,
> Guillaume Nodet
>
> --
> 
> Guillaume Nodet
>

[jira] [Resolved] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert resolved ARIES-1766.
-
Resolution: Fixed

Fixed with 
https://github.com/apache/aries/commit/e31a947fee0843ce8f09d01d9139ee837db77681

> Configure log severity for Whiteboard JMX registration exceptions
> -
>
> Key: ARIES-1766
> URL: https://issues.apache.org/jira/browse/ARIES-1766
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-1.1.5
>Reporter: David Bosschaert
>    Assignee: David Bosschaert
>Priority: Major
> Fix For: jmx-whiteboard-1.2.0
>
>
> When Aries JMX Whiteboard registers MBeans (in 
> {{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
> including {{InstanceAlreadyExistsException}} are caught and logged at 
> {{error}} level. 
> Depending on the context these messages may not really be errors, but rather 
> warnings. It would be good to be able to configure Aries JMX wrt to how these 
> exceptions are logged, allowing certain ones to appear as warnings in the log 
> instead.



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

[jira] [Updated] (ARIES-1321) NPE when calling ServiceLoader.load with a variable

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1321:

Fix Version/s: spifly-1.0.12

> NPE when calling ServiceLoader.load with a variable
> ---
>
> Key: ARIES-1321
> URL: https://issues.apache.org/jira/browse/ARIES-1321
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.2
>Reporter: Olivier NOUGUIER
>    Assignee: David Bosschaert
>Priority: Critical
> Fix For: spifly-1.0.12
>
> Attachments: ARIES-1321.diff
>
>
> When ServiceLoader is called with a variable (aka not a constant):
> aMethod(Class type ){
>   ServiceLoader.load(type).
> }
> Then the weaver result in a NPE in TCCLMethodVisitor because lastLDCType is 
> null.
> Patch provided.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ARIES-1752) Upgrade to ASM 6.0

[David Bosschaert (JIRA)]

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

David Bosschaert resolved ARIES-1752.
-
Resolution: Fixed

> Upgrade to ASM 6.0
> --
>
> Key: ARIES-1752
> URL: https://issues.apache.org/jira/browse/ARIES-1752
> Project: Aries
>  Issue Type: Dependency upgrade
>  Components: SPI Fly
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: spifly-1.0.10
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1321) NPE when calling ServiceLoader.load with a variable

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1321:

Fix Version/s: (was: spifly-1.0.10)

> NPE when calling ServiceLoader.load with a variable
> ---
>
> Key: ARIES-1321
> URL: https://issues.apache.org/jira/browse/ARIES-1321
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.2
>Reporter: Olivier NOUGUIER
>    Assignee: David Bosschaert
>Priority: Critical
> Attachments: ARIES-1321.diff
>
>
> When ServiceLoader is called with a variable (aka not a constant):
> aMethod(Class type ){
>   ServiceLoader.load(type).
> }
> Then the weaver result in a NPE in TCCLMethodVisitor because lastLDCType is 
> null.
> Patch provided.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ARIES-1321) NPE when calling ServiceLoader.load with a variable

[David Bosschaert (JIRA)]

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

David Bosschaert resolved ARIES-1321.
-
   Resolution: Fixed
Fix Version/s: spifly-1.0.10

> NPE when calling ServiceLoader.load with a variable
> ---
>
> Key: ARIES-1321
> URL: https://issues.apache.org/jira/browse/ARIES-1321
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.2
>Reporter: Olivier NOUGUIER
>    Assignee: David Bosschaert
>Priority: Critical
> Fix For: spifly-1.0.10
>
> Attachments: ARIES-1321.diff
>
>
> When ServiceLoader is called with a variable (aka not a constant):
> aMethod(Class type ){
>   ServiceLoader.load(type).
> }
> Then the weaver result in a NPE in TCCLMethodVisitor because lastLDCType is 
> null.
> Patch provided.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ARIES-1321) NPE when calling ServiceLoader.load with a variable

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1321:
---

Assignee: David Bosschaert

> NPE when calling ServiceLoader.load with a variable
> ---
>
> Key: ARIES-1321
> URL: https://issues.apache.org/jira/browse/ARIES-1321
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.2
>Reporter: Olivier NOUGUIER
>    Assignee: David Bosschaert
>Priority: Critical
> Attachments: ARIES-1321.diff
>
>
> When ServiceLoader is called with a variable (aka not a constant):
> aMethod(Class type ){
>   ServiceLoader.load(type).
> }
> Then the weaver result in a NPE in TCCLMethodVisitor because lastLDCType is 
> null.
> Patch provided.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1766:

Fix Version/s: jmx-whiteboard-1.2.0

> Configure log severity for Whiteboard JMX registration exceptions
> -
>
> Key: ARIES-1766
> URL: https://issues.apache.org/jira/browse/ARIES-1766
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-1.1.5
>Reporter: David Bosschaert
>    Assignee: David Bosschaert
> Fix For: jmx-whiteboard-1.2.0
>
>
> When Aries JMX Whiteboard registers MBeans (in 
> {{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
> including {{InstanceAlreadyExistsException}} are caught and logged at 
> {{error}} level. 
> Depending on the context these messages may not really be errors, but rather 
> warnings. It would be good to be able to configure Aries JMX wrt to how these 
> exceptions are logged, allowing certain ones to appear as warnings in the log 
> instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1630) jmx core fails if configadmin is not present

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1630:

Fix Version/s: jmx-whiteboard-1.2.0

> jmx core fails if configadmin is not present
> 
>
> Key: ARIES-1630
> URL: https://issues.apache.org/jira/browse/ARIES-1630
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-core-1.1.7
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: jmx-core-1.1.8, jmx-whiteboard-1.2.0
>
>
> JMX core claims it has an optional dependency to config admin. In the 
> Activator though it directly accesses StateConfig which depends on config 
> admin. 
> So the fix is to make config admin spec mandatory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1707) The BlueprintMetadata.getBlueprintContainer throws inconsistent exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1707:

Fix Version/s: (was: jmx-1.2.0)
   jmx-blueprint-core-1.2.0
   jmx-blueprint-api-1.2.0

> The BlueprintMetadata.getBlueprintContainer throws inconsistent exceptions
> --
>
> Key: ARIES-1707
> URL: https://issues.apache.org/jira/browse/ARIES-1707
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Reporter: Hao Zhong
>Assignee: Guillaume Nodet
> Fix For: jmx-blueprint-api-1.2.0, jmx-blueprint-core-1.2.0
>
> Attachments: aries.patch
>
>
> The BlueprintMetadata_getBlueprintContainer method throws 
> IllegalArgumentException as follow:
> {code:title=BlueprintMetadata.java|borderStyle=solid}
>  if (serviceReferences == null || serviceReferences.length <1) {
> throw new IllegalArgumentException("Invalid BlueprintContainer 
> service id: " + containerServiceId);
> }
> {code}
> However, the FrameworkUtils_resolveService method throws IOException for the 
> same condition:
> {code:title=FrameworkUtils.java|borderStyle=solid}
> if (references == null || references.length < 1) {
> throw new IOException("Service with id [" + serviceId + "] 
> not found");
> } else {
> result = references[0];
> }
> {code}
> This is confusing. Indeed, I notice that the buggy code of ARIES-333 throws 
> IllegalArgumentException, but the fixed code throws IOException.
> The current BlueprintMetadata.java shall be modified to eliminate the 
> confusing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[RESULT][VOTE] Release Aries JMX components (take 2)

[David Bosschaert]

This vote is now concluded, with
3 binding +1s
1 non-binding +1
one -1 which is not meant to be a veto and was resolved on this thread.

I'll promote the artifacts.

David


On 2 January 2018 at 13:10, David Bosschaert <david.bosscha...@gmail.com>
wrote:

> Hi all,
>
> I'm calling a vote on various Aries JMX components, now with versions
> updated from 1.2 to 1.2.0.
> The org.apache.aries.jmx.api component has not changed since the last
> release and is thus not included in this set.
>
> org.apache.aries.jmx.core version 1.1.8
> org.apache.aries.jmx.core.whiteboard version 1.1.6
> [ARIES-1630] jmx core fails if configadmin is not present
>
> org.apache.aries.jmx.blueprint.api version 1.2.0
> org.apache.aries.jmx.blueprint.core version 1.2.0
> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
> exceptions
>
> org.apache.aries.jmx.whiteboard version 1.2.0
> [ARIES-1766] Configure log severity for Whiteboard JMX registration
> exceptions
> [ARIES-1630] jmx core fails if configadmin is not present
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1123
>
> Please vote:
>
>  +1 Approve the release
>  -1 Do not approve the release (please explain why)
>
> This vote will be open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

Re: [VOTE] Release Aries JMX components (take 2)

[David Bosschaert]

Anyone else voting? We need one more binding vote...

Cheers,

David

On 4 January 2018 at 06:29, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

> +1 (binding)
>
> Agree to not release uber bundles anymore (it's some changes to do in
> Karaf, but not a big deal).
>
> Regards
> JB
>
>
> On 01/02/2018 02:10 PM, David Bosschaert wrote:
>
>> Hi all,
>>
>> I'm calling a vote on various Aries JMX components, now with versions
>> updated from 1.2 to 1.2.0.
>> The org.apache.aries.jmx.api component has not changed since the last
>> release and is thus not included in this set.
>>
>> org.apache.aries.jmx.core version 1.1.8
>> org.apache.aries.jmx.core.whiteboard version 1.1.6
>> [ARIES-1630] jmx core fails if configadmin is not present
>>
>> org.apache.aries.jmx.blueprint.api version 1.2.0
>> org.apache.aries.jmx.blueprint.core version 1.2.0
>> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
>> exceptions
>>
>> org.apache.aries.jmx.whiteboard version 1.2.0
>> [ARIES-1766] Configure log severity for Whiteboard JMX registration
>> exceptions
>> [ARIES-1630] jmx core fails if configadmin is not present
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachearies-1123
>>
>> Please vote:
>>
>>   +1 Approve the release
>>   -1 Do not approve the release (please explain why)
>>
>> This vote will be open for at least 72 hours.
>>
>> Best regards,
>>
>> David Bosschaert
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Aries JMX components (take 2)

[David Bosschaert]

Here's my +1

David

On 2 January 2018 at 13:10, David Bosschaert <david.bosscha...@gmail.com>
wrote:

> Hi all,
>
> I'm calling a vote on various Aries JMX components, now with versions
> updated from 1.2 to 1.2.0.
> The org.apache.aries.jmx.api component has not changed since the last
> release and is thus not included in this set.
>
> org.apache.aries.jmx.core version 1.1.8
> org.apache.aries.jmx.core.whiteboard version 1.1.6
> [ARIES-1630] jmx core fails if configadmin is not present
>
> org.apache.aries.jmx.blueprint.api version 1.2.0
> org.apache.aries.jmx.blueprint.core version 1.2.0
> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
> exceptions
>
> org.apache.aries.jmx.whiteboard version 1.2.0
> [ARIES-1766] Configure log severity for Whiteboard JMX registration
> exceptions
> [ARIES-1630] jmx core fails if configadmin is not present
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1123
>
> Please vote:
>
>  +1 Approve the release
>  -1 Do not approve the release (please explain why)
>
> This vote will be open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

Re: [VOTE] Release Aries JMX components (take 2)

[David Bosschaert]

Hi Dominik,

Nothing has changed in jmx-api, that's why I didn't release that one.

The jmx-bundle and jmx-blueprint-bundle you are referring to are 'uber'
bundles that are a combination of other bundles. Since we agreed on this
list to do modular releases for Aries JMX [1] these uber bundles aren't
really compatible with that... I guess they can still be released but they
would need some sort of aggregate version number.

Personally I don't see a strong reason to release these aggregate bundles,
as using them is really an OSGi anti-pattern IMHO. However if anyone feels
that these should be released they can be released separately.

@Dominik, I hope your -1 is not a 'veto', if it is please let us know.
Otherwise I think we can continue this release vote and, as mentioned those
bundles can still be released later.

Best regards,

David

[1]
https://lists.apache.org/thread.html/1f870e20c5f13da6dd0995f501e9ee279a30532efa77125203307ecd@%3Cdev.aries.apache.org%3E

On 2 January 2018 at 16:17, Dominik Przybysz <alien11...@gmail.com> wrote:

> -1
>
> Versions are ok, but you have still missed two bundles which also should be
> released together in this release.
> I saw your message that nothing in them wasn't changed but they shouldn't
> change - they are bundles which shade those ones you have released:
> https://github.com/apache/aries/blob/trunk/jmx/jmx-
> blueprint-bundle/pom.xml
> https://github.com/apache/aries/blob/trunk/jmx/jmx-bundle/pom.xml
>
> 2018-01-02 16:05 GMT+01:00 Francois Papon <francois.pa...@openobject.fr>:
>
> > +1 (non-binding)
> >
> > François
> >
> >
> > Le 02/01/2018 à 17:10, David Bosschaert a écrit :
> > > Hi all,
> > >
> > > I'm calling a vote on various Aries JMX components, now with versions
> > > updated from 1.2 to 1.2.0.
> > > The org.apache.aries.jmx.api component has not changed since the last
> > > release and is thus not included in this set.
> > >
> > > org.apache.aries.jmx.core version 1.1.8
> > > org.apache.aries.jmx.core.whiteboard version 1.1.6
> > > [ARIES-1630] jmx core fails if configadmin is not present
> > >
> > > org.apache.aries.jmx.blueprint.api version 1.2.0
> > > org.apache.aries.jmx.blueprint.core version 1.2.0
> > > [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws
> inconsistent
> > > exceptions
> > >
> > > org.apache.aries.jmx.whiteboard version 1.2.0
> > > [ARIES-1766] Configure log severity for Whiteboard JMX registration
> > > exceptions
> > > [ARIES-1630] jmx core fails if configadmin is not present
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachearies-1123
> > >
> > > Please vote:
> > >
> > >  +1 Approve the release
> > >  -1 Do not approve the release (please explain why)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Best regards,
> > >
> > > David Bosschaert
> > >
> >
> >
>
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

Re: [VOTE] Release Aries JMX components

[David Bosschaert]

Here's my +1

David

On 29 December 2017 at 22:28, David Bosschaert <david.bosscha...@gmail.com>
wrote:

> Hi,
>
> I'm calling a vote on various Aries JMX components
>
> org.apache.aries.jmx.core version 1.1.8
> org.apache.aries.jmx.core.whiteboard version 1.1.6
> [ARIES-1630] jmx core fails if configadmin is not present
>
> org.apache.aries.jmx.blueprint.api version 1.2
> org.apache.aries.jmx.blueprint.core version 1.2
> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
> exceptions
>
> org.apache.aries.jmx.whiteboard version 1.2
> [ARIES-1766] Configure log severity for Whiteboard JMX registration
> exceptions
> [ARIES-1630] jmx core fails if configadmin is not present
>
> Staging repositories (Nexus chose to split it into separate repos):
> https://repository.apache.org/content/repositories/orgapachearies-1120
> https://repository.apache.org/content/repositories/orgapachearies-1121
> https://repository.apache.org/content/repositories/orgapachearies-1122
>
> Please vote:
>
>  +1 Approve the release
>  -1 Do not approve the release (please explain why)
>
> This vote will be open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

[VOTE] Release Aries JMX components

[David Bosschaert]

Hi,

I'm calling a vote on various Aries JMX components

org.apache.aries.jmx.core version 1.1.8
org.apache.aries.jmx.core.whiteboard version 1.1.6
[ARIES-1630] jmx core fails if configadmin is not present

org.apache.aries.jmx.blueprint.api version 1.2
org.apache.aries.jmx.blueprint.core version 1.2
[ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
exceptions

org.apache.aries.jmx.whiteboard version 1.2
[ARIES-1766] Configure log severity for Whiteboard JMX registration
exceptions
[ARIES-1630] jmx core fails if configadmin is not present

Staging repositories (Nexus chose to split it into separate repos):
https://repository.apache.org/content/repositories/orgapachearies-1120
https://repository.apache.org/content/repositories/orgapachearies-1121
https://repository.apache.org/content/repositories/orgapachearies-1122

Please vote:

 +1 Approve the release
 -1 Do not approve the release (please explain why)

This vote will be open for at least 72 hours.

Best regards,

David Bosschaert

Releasing Aries JMX

[David Bosschaert]

Hi all,

I would like to release Aries JMX soon. In the past we released the Aries
all bundles together using a single version, i.e. Aries JMX 1.1.5 was a
release of all the bundles, but I see that jmx-core has since been release
individually, which from a modularity point of view makes more sense.

Therefore I propose to release the following bundles which have some
changes since the last release soon:
jmx-core: 1.1.8
jmx-blueprint-api: 1.1.6
jmx-blueprint-core: 1.1.6
jmx-core-whiteboard: 1.1.6
jmx-whiteboard: 1.2 (increase minor version since there is a new
feature ARIES-1766)

Or, alternatively I could release all of them under 1.2, but I would prefer
the individual modular release.

Thoughts anyone?

Cheers,

David

[jira] [Commented] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290718#comment-16290718
 ] 

David Bosschaert commented on ARIES-1766:
-

I implemented a fix in: 
https://svn.apache.org/viewvc?view=revision=1818103

This fix uses an extra service registration property {{warning.exceptions}}. 
Set the exception class names on that service registration property that are 
considered warnings to get them logged as warning.

> Configure log severity for Whiteboard JMX registration exceptions
> -
>
> Key: ARIES-1766
> URL: https://issues.apache.org/jira/browse/ARIES-1766
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-1.1.5
>Reporter: David Bosschaert
>    Assignee: David Bosschaert
>
> When Aries JMX Whiteboard registers MBeans (in 
> {{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
> including {{InstanceAlreadyExistsException}} are caught and logged at 
> {{error}} level. 
> Depending on the context these messages may not really be errors, but rather 
> warnings. It would be good to be able to configure Aries JMX wrt to how these 
> exceptions are logged, allowing certain ones to appear as warnings in the log 
> instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1766:
---

Assignee: David Bosschaert

> Configure log severity for Whiteboard JMX registration exceptions
> -
>
> Key: ARIES-1766
> URL: https://issues.apache.org/jira/browse/ARIES-1766
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-1.1.5
>Reporter: David Bosschaert
>    Assignee: David Bosschaert
>
> When Aries JMX Whiteboard registers MBeans (in 
> {{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
> including {{InstanceAlreadyExistsException}} are caught and logged at 
> {{error}} level. 
> Depending on the context these messages may not really be errors, but rather 
> warnings. It would be good to be able to configure Aries JMX wrt to how these 
> exceptions are logged, allowing certain ones to appear as warnings in the log 
> instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

David Bosschaert created ARIES-1766:
---

 Summary: Configure log severity for Whiteboard JMX registration 
exceptions
 Key: ARIES-1766
 URL: https://issues.apache.org/jira/browse/ARIES-1766
 Project: Aries
  Issue Type: Bug
  Components: JMX
Affects Versions: jmx-1.1.5
Reporter: David Bosschaert


When Aries JMX Whiteboard registers MBeans (in 
{{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
including {{InstanceAlreadyExistsException}} are caught and logged at {{error}} 
level. 

Depending on the context these messages may not really be errors, but rather 
warnings. It would be good to be able to configure Aries JMX wrt to how these 
exceptions are logged, allowing certain ones to appear as warnings in the log 
instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Aries Spi-fly 1.0.10

[David Bosschaert]

+1, thanks Guillaume!

David

On 22 November 2017 at 10:43, Guillaume Nodet  wrote:

> I've staged a release candidate for spi-fly 1.0.10 which includes the
> following changes:
>   [ARIES-1584] Do not spam messages for each considered and skipped bundle
>   [ARIES-1646] Improve upward compatibility of SPI Fly to ASM Version 6.x
>
> The staging repository is available at:
>   https://repository.apache.org/content/repositories/orgapachearies-1119
>
> Please review and vote !
>
> Cheers,
> Guillaume Nodet
>

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209590#comment-16209590
 ] 

David Bosschaert commented on ARIES-1746:
-

[~Thusitha] do you think you have time to contribute such a separate bundle as 
mentioned in my previous comment to SPI-Fly?

> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ARIES-1746) SPIFly support for InitialContextFactory

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1746:
---

Assignee: (was: David Bosschaert)

> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203669#comment-16203669
 ] 

David Bosschaert commented on ARIES-1746:
-

Hi [~Thusitha], I agree that it could be a feature that could benefit others, 
but it would be specific to using SPI-Fly in combination with JNDI. What we 
*could* do is create a separate module in the SPI-Fly codebase for the 
SPI-Fly/JNDI integration, where we could put such code for others to reuse.

It would still be a separate bundle though, I think it should not be mixed in 
with the core SPI-Fly component.

Feel free to contribute such a bundle, if you have the time to this :)

> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>Assignee: David Bosschaert
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ARIES-1746) SPIFly support for InitialContextFactory

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned ARIES-1746:
---

Assignee: David Bosschaert

> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>Assignee: David Bosschaert
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[David Bosschaert (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203572#comment-16203572
 ] 

David Bosschaert commented on ARIES-1746:
-

That change is very specific to the javax.naming.spi.InitialContextFactory and 
does not belong in SPI-Fly IMHO.

A more generic way to do this would be to get your own bundle to do this. 
Basically you have a service tracker or something like this listen for the 
service that is registered by SPI-Fly. The you can register the same service 
object in your own code under the {{javax.naming.spi.InitialContextFactory}} 
interface.

Something like this:

{code}
List<ServiceReference> handled = new 
CopyOnWriteArrayList<>();

public void start() {
BundleContext context = null;
ServiceTracker<InitialContextFactory, InitialContextFactory> tracker = 
new ServiceTracker<InitialContextFactory, InitialContextFactory>(context, 
InitialContextFactory.class, null) {
@Override
public InitialContextFactory 
addingService(ServiceReference reference) {
InitialContextFactory svc = super.addingService(reference);
if (!handled.contains(reference)) { // only process services 
once
handled.add(reference);

String implClass = svc.getClass().getName();
String[] objClass = (String[]) 
reference.getProperty("objectClass");
List newObjClasses = Arrays.asList(objClass);
newObjClasses.add(implClass);

context.registerService(newObjClasses.toArray(new String [] 
{}), svc, reference.getProperties());
}
return svc;
}
};
tracker.open();
}
{code}

Hope this works for you?

> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Blueprint maven plugin 1.9.0

[David Bosschaert]

+1

David

On 7 October 2017 at 08:08, Dominik Przybysz  wrote:

> Hi,
>
> I have release artifacts:
>
> - blueprint-maven-plugin-annotation-1.3.0
> - blueprint-maven-plugin-pax-cdi-handlers-1.0.0
> - blueprint-maven-plugin-1.9.0
>
> Release notes:
>
> [ARIES-1740] - blueprint-maven-plugin should generate 
> instead of  for a
> @OsgiService List ?
> [ARIES-1741] - Move handlers for pax-cdi-api annotations to separate module
> in BMP
> [ARIES-1742] - Create annotation and handler for reference generation in
> BMP
> [ARIES-1743] - Create annotation and handler for service generation in BMP
> [ARIES-1745] - Name beans from factories after method name in BMP
>
> Version on jira:
>
> https://issues.apache.org/jira/projects/ARIES/versions/12341362
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/orgapachearies-1117/
>
> Please review and vote
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>