Re: [VOTE] Release Karaf 1.4.0

2010-02-26 Thread Jean-Baptiste Onofré

+1

Guillaume Nodet wrote:

+1

On Wed, Feb 24, 2010 at 19:57, Chris Custine ccust...@apache.org wrote:

The Karaf 1.4.0 artifacts have been staged for release.

These release artifacts contain updated copyright year in all NOTICE files
and includes an updated RELEASE-NOTES file which was not updated in the
previous release vote.  As requested by Richard, I have noted that the vote
will be open for *at least* 72 hours in order to allow time for proper
review.

Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100styleName=Htmlversion=12314410

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

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 015 /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 at least 72 hours.


--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org







Re: [VOTE] Release Karaf 1.4.0 - Take 3

2010-03-03 Thread Jean-Baptiste Onofré
+1

Regards
JB

On Wed 03/03/10 10:15, Chris Custine ccust...@apache.org wrote:
 The Karaf 1.4.0 artifacts have been staged for release.
 
 This release build includes some missing headers as pointed out by
 Karl in
 the previous vote, as well as some additional ones discovered after
 upgrading to a newer Rat version. There is one known Rat failure in
 manual/src/styles/print.css because rat does not recognize the MIT
 license
 text, but this file is now properly noted in the manual NOTICE file
 so the
 rat failure can be safely ignored. I have also fixed the duplicate
 .asc.asc
 signatures.
 
 As with the previous vote, I have noted that the vote will be open
 for *at
 least* 72 hours in order to allow time for proper review. Thanks for
 your
 patience.
 
 Release notes are here:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100s
 tyleName=Htmlversion=12314410[1]
 
 Staging repository:
 https://repository.apache.org/content/repositories/orgapachefelix-003/
 [2]
 
 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
 [3]
 
 Usage:
 sh check_staged_release.sh 003 /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 at least 72 hours.
 
 --
 Chris Custine
 FUSESource :: http://fusesource.com [4]
 My Blog :: http://blog.organicelement.com [5]
 Apache ServiceMix :: http://servicemix.apache.org [6]
 Apache Felix :: http://felix.apache.org [7]
 Apache Directory Server :: http://directory.apache.org [8]
 
 
 
 Links:
 --
 [1]
 http://webmail.nanthrax.net/parse.php?redirect=https%3A%2F%2Fissues.apache.
 org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12310100%26styleName%3
 DHtml%26version%3D12314410[2]
 http://webmail.nanthrax.net/parse.php?redirect=https%3A%2F%2Frepository.apa
 che.org%2Fcontent%2Frepositories%2Forgapachefelix-003%2F[3]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fsvn.apache.org%
 2Frepos%2Fasf%2Ffelix%2Ftrunk%2Fcheck_staged_release.sh[4]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Ffusesource.com
 [5]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fblog.organicele
 ment.com[6]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fservicemix.apac
 he.org[7]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Ffelix.apache.or
 g[8]
 http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fdirectory.apach
 e.org
 




Re: [VOTE] Utils, BundleRepository Web Console, Event Plugin, Memory Usage Plugin, UPNP Plugin Release

2010-03-26 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

Felix Meschberger wrote:

Hi,

As promised, here is a bunch of releases, I would like to vote on for
release:

Apache Felix Utils, 1.0.0
  Initial Release
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314864
  https://issues.apache.org/jira/browse/FELIX/component/12313470

Apache Felix Bundle Repository, 1.6.0
  29 Issues fixed/implemented
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314767
  https://issues.apache.org/jira/browse/FELIX/component/12311316

Apache Felix Web Console, 3.0.0
  63 issues fixed/implemented
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314526
  https://issues.apache.org/jira/browse/FELIX/component/12312330

Apache Felix Web Console Event Plugin, 1.0.2
  3 issues fixed/implemented
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314750
  https://issues.apache.org/jira/browse/FELIX/component/12312330

Apache Felix Web Console Memory Usage Plugin, 1.0.0
  Initial Release
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314848
  https://issues.apache.org/jira/browse/FELIX/component/12312330

Apache Felix Web Console UPnP Plugin, 1.0.0
  Initial Release
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314851
  https://issues.apache.org/jira/browse/FELIX/component/12312330


All proposed bundles are available from the staging repository:
  https://repository.apache.org/content/repositories/orgapachefelix-022

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 022 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ]  0 Don't care
[ ] -1 Don't release, because...

This vote will be open for 5 days (accounting for weekend and the big
number of bundles to release) until Wednesday, 31. March.

Thanks and Regards
Felix


Re: [VOTE] Felix framework and main 2.0.5 subproject releases

2010-04-12 Thread Jean-Baptiste Onofré

+1 (non binding).

Regards
JB

Felix Meschberger wrote:

+1

Regards
Felix

On 12.04.2010 01:18, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  2.0.5
main 2.0.5
main.distribution 2.0.5

We solved the following issues in this release:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12314881

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

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 013 /tmp/felix-staging

Please vote to approve this release:

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



Re: [VOTE] Felix iPOJO 1.6.0 releases

2010-04-23 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 04/23/2010 09:40 PM, Richard S. Hall wrote:

+1

Minor issue: Although I know the content of our NOTICE file needs to be
revamped, the license summary for the iPOJO runtime only lists Apache,
not BSD.

Otherwise, it looks like a pretty significant release!

- richard

On 4/16/10 11:26, Clement Escoffier wrote:

I would like to call a vote on the following iPOJO subproject releases:

maven-ipojo-plugin 1.6.0
org.apache.felix.ipojo 1.6.0
org.apache.felix.ipojo.annotations 1.6.0
org.apache.felix.ipojo.ant 1.6.0
org.apache.felix.ipojo.api 1.6.0
org.apache.felix.ipojo.arch 1.6.0
org.apache.felix.ipojo.composite 1.6.0
org.apache.felix.ipojo.manipulator 1.6.0
org.apache.felix.ipojo.online.manipulator 1.6.0

We solved the following issues in this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100styleName=Htmlversion=12314134

Each artifact contains it's own changelog too.
Staging repository:

https://repository.apache.org/content/repositories/orgapachefelix-031/

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 031 /tmp/felix-staging

Please vote to approve this release:

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

Thanks and regards,

Clement

PS: The web console plugin, the event admin handler and the temporal
dependency handler will be release once this one is done.


Re: [VOTE] Release fileinstall 3.0.0

2010-04-29 Thread Jean-Baptiste Onofré

+1 (non binding).

Regards
JB

On 04/29/2010 09:07 PM, Guillaume Nodet wrote:

I would like to call a vote on the following subproject releases:

fileinstall 3.0.0

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

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 035 /tmp/felix-staging

Please vote to approve this release:

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



Re: Maven groupId question

2010-05-05 Thread Jean-Baptiste Onofré
Hi Richard,

I prefer to have seperated groupId to avoid to have too much jar in the same 
directory on the maven repo.
I think that it's easier and more well sorted using groupId directory.

Regards
JB
-Original Message-
From: Richard S. Hall he...@ungoverned.org
Date: Wed, 05 May 2010 11:20:01 
To: devdev@felix.apache.org
Subject: Maven groupId question

I noticed while poking around Gogo that its Maven groupId is:

 org.apache.felix.gogo

While most other subprojects are:

 org.apache.felix

Apparently, Karaf also creates its own groupId. I guess I was under the 
assumption that all subprojects were using the same groupId. It doesn't 
seem necessary, even if you have multiple modules, since for example 
iPOJO has multiple modules, but still uses org.apache.felix.

I realize the groupId doesn't really have much impact, but it does make 
it somewhat confusing to know which is the correct groupId to use for a 
given subproject. So, from that perspective it seems easier and more 
consistent if every subproject just used the same groupId. Are there any 
benefits of having separate groupIds?

- richard


Re: [DISCUSS] Move Karaf as a TLP

2010-05-14 Thread Jean-Baptiste Onofré

Hi,

We got lot of benefits to move ServiceMix Kernel to Felix Karaf: more 
contributors, new horizons and features, etc.


I think that moving Karaf as a TLP will give the same. It will be appear 
more clearly for the users as a complete and very wide OSGi kernel.


So totally agree to move Karaf as a TLP.

Regards
JB

On 05/14/2010 12:20 PM, Guillaume Nodet wrote:

Karaf has been brought into the Felix TLP nearly one year ago.
Things have not been too bad, but I still see the karaf community as
being very disjoint from the other felix community, as it looks that none
of the existing felix committers did really get involved in Karaf.  I
really
don't blame anyone, i think it's just that the interest are not the same
(not sure
where they actually diverge though).
I don't really see what benefit Karaf would have in continuing being part of
Felix, so
I'd like to open the discussion about moving it to a TLP.



--
Jean-Baptiste Onofré
-
 HomePage
http://www.nanthrax.net
-
 Contacts
jbono...@apache.org
j...@nanthrax.net
-
 OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
---
PGP : 17D4F086


Re: [VOTE] Release Apache Felix Karaf 1.6.0

2010-05-19 Thread Jean-Baptiste Onofré

+1

All tests performed were working fine for me.

Regards
JB

Guillaume Nodet wrote:

We solved a bunch of issues for 1.6.0
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100styleName=Htmlversion=12314791

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

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 003 /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.


--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com


Re: [VOTE] Release Karaf 1.6.0 (2nd try)

2010-05-21 Thread Jean-Baptiste Onofré
+1

Regards
JB
-Original Message-
From: Guillaume Nodet gno...@gmail.com
Date: Thu, 20 May 2010 23:21:54 
To: devdev@felix.apache.org
Subject: [VOTE] Release Karaf 1.6.0 (2nd try)

Second try.  The karaf manual should be ok now and this release also
includes FELIX-2280 (Too much code duplication in DefaultJDBCLock,
OracleJDBCLock and MySQLJDBCLock).  No other changes.

We solved a bunch of issues for 1.6.0
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100styleName=Htmlversion=12314791

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

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 003 /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.



-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com


Re: [DISCUSS] Move Karaf as a TLP

2010-05-27 Thread Jean-Baptiste Onofré
+1 to contribute.

Regards
JB
-Original Message-
From: Guillaume Nodet gno...@gmail.com
Date: Fri, 28 May 2010 07:40:05 
To: devdev@felix.apache.org
Subject: Re: [DISCUSS] Move Karaf as a TLP

It seems there is a consensus to move Karaf as a TLP, at least amongst
people involved in Karaf (the other felix committers haven't really
expressed any opinion).

I think the next steps would be to draft a proposed resolution to the board,
which would include:
  * the project goal
  * the project PMC (including the chair)

In order to create an open community from the start, I'd like to invite
anyone with an Apache account willing to contribute to Karaf to raise hands
so that we can build this list.  I don't think opening it wider for now
would be wise, but I do thing we should have a very low entry bar for
committership (but that can be discussed later).

I'll try to come up with a proposal for Karaf's project goal asap, but
anyone is welcome to give it a try and propose some wording.

FWIW, it would like the following, we just need to fill the :

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software related to a machine learning platform
   for distribution at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Karaf Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Karaf Project be and hereby is
   responsible for the creation and maintenance of software
   related to XXX; and be it further

   RESOLVED, that the office of Vice President, Apache Karaf be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Karaf Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Karaf Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Karaf Project:

 * xxx x...@apache.org
 * ...

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that X
   be appointed to the office of Vice President, Apache Karaf, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache Karaf PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Mahout Project; and be it further

   RESOLVED, that the Apache Karaf Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Felix Karaf sub-project; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Felix Karaf sub-project encumbered upon the
   Apache Felix Project are hereafter discharged.



On Fri, May 14, 2010 at 12:20, Guillaume Nodet gno...@gmail.com wrote:

 Karaf has been brought into the Felix TLP nearly one year ago.
 Things have not been too bad, but I still see the karaf community as
 being very disjoint from the other felix community, as it looks that none
 of the existing felix committers did really get involved in Karaf.  I
 really
 don't blame anyone, i think it's just that the interest are not the same
 (not sure
 where they actually diverge though).
 I don't really see what benefit Karaf would have in continuing being part
 of Felix, so
 I'd like to open the discussion about moving it to a TLP.

 --
 Cheers,
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/
 
 Open Source SOA
 http://fusesource.com





-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com



Re: [VOTE] Propose Karaf as a TLP

2010-06-04 Thread Jean-Baptiste Onofré
+1

Regards
JB
-Original Message-
From: Guillaume Nodet gno...@gmail.com
Date: Thu, 3 Jun 2010 08:24:53 
To: devdev@felix.apache.org
Subject: [VOTE] Propose Karaf as a TLP

I think it's time start a vote about moving Karaf as a TLP as we
recently discussed.
The vote is about submitting the following proposal to the next board meeting:

[ ] +1 send this proposal to the board
[ ] -1 do not

The vote will be opened for 72 hours

=

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to an OSGI based runtime for
creating enterprise servers for distribution at no charge
to the public.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Karaf Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Karaf Project be and hereby is
responsible for the creation and maintenance of software
related to an OSGI based runtime for creating enterprise
servers; and be it further

RESOLVED, that the office of Vice President, Apache Karaf be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Karaf Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Karaf Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Karaf Project:

 * Chris Custine ccust...@apache.org
 * Freeman Fang ff...@apache.org
 * Jarek Gawor ga...@apache.org
 * Jamie Goodyear jgoody...@apache.org
 * David Jencks djen...@apache.org
 * Alex Karasulu akaras...@apache.org
 * Charles Moulliard cmoulli...@apache.org
 * Guillaume Nodet gno...@apache.org
 * Jean-Baptiste Onofré jbono...@apache.org
 * Gert Vanthienen ge...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Guillaume Nodet

be appointed to the office of Vice President, Apache Karaf, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Karaf PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Karaf Project; and be it further

RESOLVED, that the Apache Karaf Project be and hereby
is tasked with the migration and rationalization of the Apache
Felix Karaf sub-project; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Felix Karaf sub-project encumbered upon the
Apache Felix Project are hereafter discharged.

===



-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com


Re: [VOTE] Felix framework 3.0.0 and Gogo 0.6.0 subproject releases (take2)

2010-06-08 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/08/2010 07:21 PM, Derek Baum wrote:

+1 (non-binding)

Derek

On 7 June 2010 17:42, Karl Paulskarlpa...@gmail.com  wrote:


I would like to call a new vote on the following subproject releases:

gogo 0.6.0
gogo.runtime 0.6.0
gogo.shell 0.6.0
gogo.command 0.6.0
framework  3.0.0
framework.security 1.2.0
main 3.0.0
main.distribution 3.0.0

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

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 040 /tmp/felix-staging

Please vote to approve this release:

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





--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
j...@nanthrax.net
PGP : 17D4F086


Re: [DISCUSS] Release webconsole 3.0.2 and Karaf 1.6.2 soon

2010-06-10 Thread Jean-Baptiste Onofré

It sounds good to me. Including bundlerepository is good idea too.

Regards
JB

On 06/09/2010 06:15 PM, Guillaume Nodet wrote:

I'd like to release webconsole and karaf later this week or next week.
If there is any issue with that (or anything that would like to be included
in those releases),
please speak up!



Re: [VOTE] webconsole-3.0.2, bundlerepository-1.6.4 and karaf-1.6.2

2010-06-12 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 06/12/2010 08:43 AM, Guillaume Nodet wrote:

I would like to call a new vote on the following subproject releases:

webconsole 3.0.2
bundlerepository 1.6.4
karaf 1.6.2

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

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 049 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 There's a problem (please provide specific comments)



Re: [jira] Commented: (FELIX-2409) javax.annotation not exported

2010-06-14 Thread Jean-Baptiste Onofré

Thanks for the update Bengt,

but I'm a little bit surprised as we have two standard package set: one 
for jre-1.5 and one for jre-1.6.


Note that javax.transaction is exported with a mandatory attribute:
javax.transaction; javax.transaction.xa; partial=true;mandatory:=partial, \
in both jre 1.5 and 1.6.

Regards
JB

On 06/14/2010 03:43 PM, Bengt Rodehav wrote:

I had the same problem a while back. I was informed that since Karaf also
supports Java 1.5 (which doesnt have these packages), they should not by
default be imported by Karaf.

See the following:

http://old.nabble.com/Karaf-1.4.0-and-ActiveMQ-5.3.1-td28191404.html

/Bengt

2010/6/14 Jean-Baptiste Onofré (JIRA)j...@apache.org



[
https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12878569#action_12878569]

Jean-Baptiste Onofré commented on FELIX-2409:
-

It sounds good for me.


javax.annotation not exported
-

 Key: FELIX-2409
 URL: https://issues.apache.org/jira/browse/FELIX-2409
 Project: Felix
  Issue Type: Bug
  Components: Karaf
Affects Versions: karaf 1.6.0
 Environment: Windows / jre-1.6
Reporter: Jean-Philippe CLEMENT

Karaf config.properties does not export jre-1.6 javax.annotation and

javax.annotation.processing standard packages.

As they are part of the java 1.6 API it sounds normal to have them

imported by default:

  javax.annotation, \
  javax.annotation.processing, \
Would it be possible to fix this?
Thanks.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.






Re: [VOTE] Release webconsole 3.1.0 bundlerepository 1.6.4, karaf 1.6.2 (3rd try)

2010-06-15 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 06/15/2010 01:42 PM, Guillaume Nodet wrote:

I would like to call a new vote on the following subproject releases:

webconsole 3.1.0
bundlerepository 1.6.4
karaf 1.6.2

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

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 054 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 There's a problem (please provide specific comments)




Re: [ANNOUNCE] Karaf is moving to top level

2010-06-17 Thread Jean-Baptiste Onofré

Thanks Guillaume,

If you need any help (for example to move Jira tasks to the new 
location, etc), don't hesitate to ping me.


Regards
JB

On 06/17/2010 07:48 PM, Guillaume Nodet wrote:

The Apache Software Foundation has approved yesterday the move of
Karaf as a top level project.
The whole community is thrilled and will strive to make the project
even better and more successful.

It will take some time to move all the infrastructure, so we'll keep
everyone posted.



Re: [VOTE] Release Karaf 1.6.2 (4th try)

2010-06-18 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 06/18/2010 03:17 PM, Guillaume Nodet wrote:

I would like to call a new vote on karaf 1.6.2.
The only change since the 3thd attempt is the fix for the bug Gert
found in the features service.

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

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 004 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 There's a problem (please provide specific comments)




Re: Karaf infrastructure (was Re: [ANNOUNCE] Karaf is moving to top level)

2010-06-25 Thread Jean-Baptiste Onofré

Subscription done. Ready to work.

Regards
JB

On 06/25/2010 02:31 PM, Guillaume Nodet wrote:

I think mostly everything has been set up thx to infra (see
https://issues.apache.org/jira/browse/INFRA-2800).
Mailing lists are available at:
   https://cwiki.apache.org/KARAF/mailing-lists.html
Plus the private one which isn't listed there.

So I welcome everyone to subscribe to those lists so that we can start
working there ...

On Thu, Jun 17, 2010 at 19:48, Guillaume Nodetgno...@gmail.com  wrote:

The Apache Software Foundation has approved yesterday the move of
Karaf as a top level project.
The whole community is thrilled and will strive to make the project
even better and more successful.

It will take some time to move all the infrastructure, so we'll keep
everyone posted.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com







Re: [VOTE] Apache Felix File Install 3.0.2

2010-08-03 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 08/03/2010 04:19 PM, Richard S. Hall wrote:



This release addresses the following issues:

https://issues.apache.org/jira/browse/FELIX/fixforversion/12315224

Staging repository:

https://repository.apache.org/content/repositories/orgapachefelix-
http://repository.apache.org/content/repositories/orgapachefelix-053/

You can usethis UNIX script to download the release and verify the
signatures:

http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:

sh check_staged_release.sh 053 /tmp/felix-staging

Please vote to approvethis release:

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



Re: [VOTE] Felix framework, framework.security, and main 3.0.2 subproject releases

2010-08-23 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 08/23/2010 05:28 PM, Karl Pauls wrote:

+1

regards,

Karl

On Wed, Aug 18, 2010 at 11:17 PM, Karl Paulskarlpa...@gmail.com  wrote:

I would like to call a vote on the following subproject releases:

framework  3.0.2
framework.security 1.4.0
main 3.0.2
main.distribution 3.0.2

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

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 125 /tmp/felix-staging
sh check_staged_release.sh 126 /tmp/felix-staging

Please vote to approve this release:

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

p.s.: There are two staging repos because my ip changed during the
release so make sure you check both.







Re: [VOTE] Release Apache Felix Configuration Admin Service 1.2.8

2010-09-08 Thread Jean-Baptiste Onofré

+1 (non binding).

Regards
JB

On 09/08/2010 08:49 PM, Richard S. Hall wrote:

+1

Not a big deal, but the DEPS file was not included in all artifacts.
This needs to be done explicitly...it's not clear if we can modify our
parent POM to do this automatically.

- richard

On 9/8/10 8:56, Felix Meschberger wrote:

Hi,

Here s the Apache Felix Configuration Admin Service 1.2.8 release.
Needless to say that this release also passes the OSGi CT for
Configuration Admin.

We solved 11 issues in this release:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12314190

There are three outstanding improvement proposals and no known bugs:
https://issues.apache.org/jira/browse/FELIX/component/12310342

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

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 045 /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.

Thanks and Regards
Felix






Re: [VOTE] Release Apache Felix Remote Shell 1.1.2

2010-09-28 Thread Jean-Baptiste Onofré

+1 (non binding).

Regards
JB

On 09/28/2010 05:29 PM, Richard S. Hall wrote:



Resolved an NPE:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12315259

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

You can usethis 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 019 /tmp/felix-staging

Please vote to approvethis release:

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



Re: [VOTE] Release fileinstall-3.1.0 and utils-1.1.0

2010-11-03 Thread Jean-Baptiste Onofré
+1 (non binding)

Regards
JB
-Original Message-
From: Guillaume Nodet gno...@gmail.com
Date: Wed, 3 Nov 2010 14:18:34 
To: devdev@felix.apache.org
Reply-To: dev@felix.apache.org
Subject: [VOTE] Release fileinstall-3.1.0 and utils-1.1.0

We've fixed a number of issues in fileinstall:
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12314993

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

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 017 /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.

-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com


Re: [VOTE] Release Apache Felix EventAdmin version 1.2.8

2010-12-02 Thread Jean-Baptiste Onofré

+1 (non binding).

On 12/02/2010 04:26 PM, Karl Pauls wrote:

+1

regards,

Karl

On Thu, Dec 2, 2010 at 3:39 PM, Carsten Ziegelercziege...@apache.org  wrote:

+1

Carsten

Sahoo  wrote

Hi,

We solved 1 issue in this release:

** Improvement
 * [FELIX-2655] - allow event admin log level to be configurable

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

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 031 /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.

Thanks,
Sahoo




--
Carsten Ziegeler
cziege...@apache.org







Re: [VOTE] Release fileinstall-3.1.2

2010-12-22 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/21/2010 09:21 AM, Guillaume Nodet wrote:

+1

On Mon, Dec 20, 2010 at 15:28, Guillaume Nodetgno...@gmail.com  wrote:

Hi,

We solved N issues in this release:
   
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310100fixfor=12315912component=12312204

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

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  038 /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.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com







Re: [VOTE] Felix framework 3.0.7 and releated subproject releases

2010-12-26 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/26/2010 10:38 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  3.0.7
framework.security 1.4.1
main 3.0.7
main.distribution 3.0.7

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

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 042 /tmp/felix-staging

Please vote to approve this release:

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


Re: [VOTE] Release fileinstall-3.1.4

2011-01-03 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 01/03/2011 09:58 AM, Guillaume Nodet wrote:

Hi,  Happy new year everyone!

We solved 1 blocking issues in this release:
   https://issues.apache.org/jira/browse/FELIX/fixforversion/12316013

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

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  066 /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.



Re: [VOTE] Release fileinstall-3.1.4

2011-01-04 Thread Jean-Baptiste Onofré

Hmmm weird,

I didn't get the issue about signatures.

Let me try again.

Regards
JB

On 01/04/2011 12:04 PM, Andreas Pieber wrote:

I've tested it with karaf and various other projects; works again; thank you

+1 (non binding)

btw, if I use the script to verify the signatures I get:


   CHECK SIGNATURES AND DIGESTS

/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/maven-metadata.xml
gpg:  
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4-project.zip
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4-bin.tar.gz
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4-project.tar.gz
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4-sources.jar
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4-bin.zip
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4.pom
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/org/apache/felix/org.apache.felix.fileinstall/3.1.4/org.apache.felix.fileinstall-3.1.4.jar
gpg:  BAD
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/.index/nexus-maven-repository-index.properties
gpg:  
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/.index/nexus-maven-repository-index.gz
gpg:  
md5:  BAD
sha1: BAD
/tmp/felix-staging/066/.meta/repository-metadata.xml
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/.meta/p2-metadata.properties
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/folder-trigger.png
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/leaf-nexus.png
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/folder-nexus.png
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/images/default/grid/loading.gif
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/bullet_star.png
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/Sonatype-content.css?1.8.0.1
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/folder-open-nexus.png
gpg:  
md5:  
sha1: 
/tmp/felix-staging/066/arrow_refresh.png
gpg:  
md5:  
sha1: 



On Mon, Jan 3, 2011 at 9:58 AM, Guillaume Nodetgno...@gmail.com  wrote:

Hi,  Happy new year everyone!

We solved 1 blocking issues in this release:
  https://issues.apache.org/jira/browse/FELIX/fixforversion/12316013

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

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  066 /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.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com



Re: [VOTE] Release fileinstall-3.1.8

2011-01-25 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 01/25/2011 02:10 PM, Guillaume Nodet wrote:

This release fixes two issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310100fixfor=12316099
   * FELIX-2799 FileInstall creates multiple configurations for factory
configurations on windows
   * FELIX-2798 ArtifactListener services are not ordered according to
the OSGi ranking

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

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 075 /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.



Re: [VOTE] Release Apache Felix Http Service 2.2.0

2011-01-26 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 01/26/2011 04:12 PM, Felix Meschberger wrote:

Hi,

As promised, here is the long awaited 2.2.0 release of the Apache Felix
Http Service implementation where the NOTICE and DEPENDENCIES files have
been fixed since the 2.1.0 RC.

This release fixes the following 18 issues:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12314431

Of course we still have a few issues open:
https://issues.apache.org/jira/browse/FELIX/component/12310340

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

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 082 /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 at least 72 hours.


Regards,
Felix



Re: Request for release of maven-bundle-plugin

2011-01-31 Thread Jean-Baptiste Onofré

+1 to kick off the release.

Regards
JB

On 01/31/2011 04:19 PM, Guillaume Nodet wrote:

Sure, I've seen some of those commits and I had some of them on my todo list ;-)
I'll start a 2.3.0 release asap as the use of optional dependencies is
really a must-have feature.

On Mon, Jan 31, 2011 at 16:16, Hiram Chirinohi...@hiramchirino.com  wrote:

Hi,

I applied a few changes[1] to the maven-bundle-plugin last week which
I need to use in a build which I need to release soon.  Could some
once kick off a release build of the plugin?

Thanks,
Hiram

FuseSource
Web: http://fusesource.com/

1: https://issues.apache.org/jira/browse/FELIX-2812
https://issues.apache.org/jira/browse/FELIX-2811
https://issues.apache.org/jira/browse/FELIX-2809
https://issues.apache.org/jira/browse/FELIX-2808







Re: [VOTE] Release webconsole 3.1.8

2011-02-01 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 02/01/2011 09:16 AM, Guillaume Nodet wrote:

This release fixes several issues
 * [FELIX-2713] - Problem in HtmlConfigurationWriter
 * [FELIX-2729] - Webconsole - Configuration fails to print
configuration for bundles without MetatypeService config
 * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter
 * [FELIX-2793] - Plugin request is not detected as html request if
context path contains a dot
 * [FELIX-2795] - Parameters are not removed from symbolic name
when installing a bundle

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

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 023 /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.



--
Jean-Baptiste Onofré
-
 HomePage
http://www.nanthrax.net
-
 Contacts
jbono...@apache.org
j...@nanthrax.net
-
 OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
---
PGP : 17D4F086


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

2011-02-02 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 02/02/2011 10:41 AM, Guillaume Nodet wrote:

  I would like to call another vote on the maven-bundle-plugin 2.3.0 release:

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

Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8d589633a054278ec7f36db6fcb02560518a1b8fversion=12316061styleName=TextprojectId=12310100Create=Create

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 025 /tmp/felix-staging

Please vote to approve this release:

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



Re: [VOTE] Release fileinstall-3.1.10

2011-02-02 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 02/02/2011 03:37 PM, Guillaume Nodet wrote:

Vote on fileinstall .3.1.10

This release fixes three issues
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8159ff149eb3d70fdca9490b559e5269f0ea79d8version=12316134styleName=TextprojectId=12310100Create=Create
 * [FELIX-2798] - ArtifactListener services are not ordered
according to the OSGi ranking
 * [FELIX-2799] - FileInstall creates multiple configurations for
factory configurations on windows
 * [FELIX-2818] - File Install does not support empty configuration
when no configuration already exists

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

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 026 /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.



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

2011-02-02 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 02/02/2011 06:09 PM, Guillaume Nodet wrote:

I would like to call another vote on the maven-bundle-plugin 2.3.4 release:

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

Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12316061

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 029 /tmp/felix-staging

Please vote to approve this release:

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




Re: [VOTE] Versioning after a failed release

2011-02-04 Thread Jean-Baptiste Onofré

+1 for A.

Regards
JB

On 02/04/2011 09:50 AM, Guillaume Nodet wrote:

Following the discussion, I'm starting a vote to decide on a policy
for failed releases.

  [ ] A - Releases following a failed release can reuse the same version
  [ ] B - Releases following a failed release must use a different version

The vote will be opened for at least 72 hours.
Happy voting!



Re: [VOTE] Versioning after a failed release

2011-02-05 Thread Jean-Baptiste Onofré
Agree.

Regards
JB
-Original Message-
From: Guillaume Nodet gno...@gmail.com
Date: Sat, 5 Feb 2011 13:21:15 
To: dev@felix.apache.org
Reply-To: dev@felix.apache.org
Subject: Re: [VOTE] Versioning after a failed release

As long has the release has not been approved, the tag does not match
an official release, so it can be freely deleted.
Once the release is voted, I think everyone agree the tag becomes immutable.

FWIW, Git is much better as a tag really correspond to a moment in the
history, not a branch (which actually makes more sense if you think
about it).

On Sat, Feb 5, 2011 at 11:04, Felix Meschberger fmesc...@adobe.com wrote:
 Hi,

 Am Samstag, den 05.02.2011, 09:52 + schrieb Sahoo:
 On Friday 04 February 2011 04:48 PM, Stuart McCulloch wrote:
  it is easy to retag releases in svn
 
 
 What exactly do you mean by retag releases in svn? Rename an existing
 tag or using the same tag name to tag a different snapshot of the source
 code base? Neither should be done in my IMHO.

 Agreed, both is far too easy ...

 Regards
 Felix





-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com


Re: [VOTE] Felix framework 3.0.9 and related subproject releases

2011-02-23 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 02/23/2011 10:32 AM, Felix Meschberger wrote:

+1

Regards
Felix

Am Montag, den 21.02.2011, 22:10 + schrieb Karl Pauls:

I would like to call a vote on the following subproject releases:

framework  3.0.9
main 3.0.9
main.distribution 3.0.9

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

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 035 /tmp/felix-staging

Please vote to approve this release:

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





Re: [VOTE] Felix framework 3.2.0 and related subproject releases

2011-03-30 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 03/30/2011 09:09 PM, Carsten Ziegeler wrote:

+1

Carsten

Rob Walker  wrote

+1

-- Rob

On 28/03/2011 10:54 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  3.2.0
framework.security 1.4.2
main 3.2.0
main.distribution 3.2.0

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

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 050 /tmp/felix-staging

Please vote to approve this release:

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







Re: [VOTE] framework 3.2.1 and related subproject releases

2011-04-20 Thread Jean-Baptiste Onofré

+1 (non binding)

However, we have an issue in Karaf which seems related to Felix framework:
https://issues.apache.org/jira/browse/KARAF-534

I don't think that the issue is specific to 3.2.1 (I suspect it's more 
global).


I'm working to have a better understanding of the behavior and submit a 
Jira/patch.


Regards
JB

On 04/18/2011 11:51 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  3.2.1
main 3.2.1
main.distribution 3.2.1

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

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 098 /tmp/felix-staging

Please vote to approve this release:

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


Re: [VOTE] framework 3.2.1 and related subproject releases (take2)

2011-04-27 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 04/26/2011 11:21 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  3.2.1
main 3.2.1
main.distribution 3.2.1

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

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 117 /tmp/felix-staging

Please vote to approve this release:

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


Re: [VOTE] Release Felix Deployment Admin version 0.9.0, AutoConf 0.1.0, Dependency Manager 3.0.0 (3rd attempt)

2011-05-02 Thread Jean-Baptiste Onofré

+1 (non-binding)

It looks good for me also.

Regards
JB

On 05/02/2011 02:28 PM, Andreas Pieber wrote:

Looks fine and works :)

+1 (non-binding)

Kind regards,
Andreas

On Mon, May 2, 2011 at 2:25 PM, Clement Escoffier
clement.escoff...@gmail.com  wrote:

+1,

Great work !

Regards,

Clement

On 01.05.11 17:02, Marcel Offermansmarcel.offerm...@luminis.nl  wrote:


Hi all,

This is a release of the Deployment Admin and AutoConf Resource Processor
bundles,
combined with the Dependency Manager, which consists of 5 bundles.

It's the third attempt, after the first and second votes were cancelled
because of a
few missing header files in the source code.

For Deployment Admin and AutoConf, it's the first release and we're not
claiming they
fully implement the spec yet. They are however in a usable state, so we'd
like to
solicit more feedback with this release.

For the Dependency Manager, release 3.0.0 represents a huge leap in
functionality
that has been under development for some time and has reached the point
where
it is in our view stable enough for a release.

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

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 008 /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.

Greetings, Marcel







Re: [VOTE] framework 3.2.2 and related subproject

2011-05-18 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 05/18/2011 09:36 AM, Pierre De Rop wrote:

+1 (non binding)

regards;
/Pierre

On Tue, May 17, 2011 at 11:04 PM, Karl Paulskarlpa...@gmail.com  wrote:


I would like to call a vote on the following subproject releases:

framework  3.2.2
main 3.2.2
main.distribution 3.2.2

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

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 020 /tmp/felix-staging

Please vote to approve this release:

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





Re: Deprecating the bundleall goal

2011-06-16 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 06/16/2011 07:49 PM, Stuart McCulloch wrote:

Hi folks,

I'm planning to deprecate the bundleall goal since it has several faults, 
produces low quality bundles, and was never meant to be used by everyday projects.

Any objections?  The goal will still be available in the next minor release, 
but marked as deprecated with a warning - the next major release would remove 
it.

--
Cheers, Stuart

Begin forwarded message:


From: mccu...@apache.org
Date: 16 June 2011 18:41:19 GMT+01:00
To: comm...@felix.apache.org
Subject: svn commit: r1136563 - 
/felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java
Reply-To: dev@felix.apache.org

Author: mcculls
Date: Thu Jun 16 17:41:18 2011
New Revision: 1136563

URL: http://svn.apache.org/viewvc?rev=1136563view=rev
Log:
Deprecate the bundleall goal

Modified:

felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java

Modified: 
felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java
URL: 
http://svn.apache.org/viewvc/felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java?rev=1136563r1=1136562r2=1136563view=diff
==
--- 
felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java
 (original)
+++ 
felix/trunk/bundleplugin/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java
 Thu Jun 16 17:41:18 2011
@@ -64,7 +64,9 @@ import aQute.lib.osgi.Jar;
  * @phase package
  * @requiresDependencyResolution test
  * @description build an OSGi bundle jar for all transitive dependencies
+ * @deprecated The bundleall goal is no longer supported and may be removed in 
a future release
  */
+@Deprecated
public class BundleAllPlugin extends ManifestPlugin
{
 private static final String LS = System.getProperty( line.separator );
@@ -174,6 +176,9 @@ public class BundleAllPlugin extends Man
  */
 protected BundleInfo bundleAll( MavenProject project, int maxDepth ) 
throws MojoExecutionException
 {
+getLog().warn( 

 );
+getLog().warn( ! The bundleall goal is no longer supported and may be 
removed in a future release ! );
+getLog().warn( 

 );

 if ( alreadyBundled( project.getArtifact() ) )
 {







Re: [VOTE] Release Felix Bundle Repository version 1.6.6

2011-06-30 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 06/30/2011 01:27 AM, Stuart McCulloch wrote:

Hi folks,

We solved 4 issues in this release:


https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22bundlerepository-1.6.6%22

There are still several outstanding issues:


https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+FELIX+AND+component+%3D+%22Bundle+Repository+%28OBR%29%22+AND+status+%3D+Open

Staging repository:

https://repository.apache.org/content/repositories/orgapachefelix-008/

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 008 /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.

--
Cheers, Stuart



Re: [VOTE] Release Apache Felix EventAdmin 1.2.14

2011-07-25 Thread Jean-Baptiste Onofré
+1 (non-binding),

Regards
JB




On Mon 25/07/11 10:20 , Carsten Ziegeler  wrote::

I would like to call a vote on the following subproject release:

eventadmin 1.2.14

This release fixes an NPE on shutdown

https://issues.apache.org/jira/browse/FELIX-2997

and includes FELIX-3002: Embed the OBR specific information for the
EventAdmin bundle in the manifest

The release passes the TCK

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

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 028 /tmp/felix-staging

Please vote to approve this release:

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


Regards
Carsten
-- 
Carsten Ziegeler
cziege...@apache.org





Re: [VOTE] Release Apache Felix EventAdmin 1.2.14

2011-08-09 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 08/03/2011 10:36 AM, Carsten Ziegeler wrote:

I would like to call a vote on the following subproject release:

eventadmin 1.2.14

This release fixes an NPE on shutdown and two potential deadlocks:

https://issues.apache.org/jira/browse/FELIX-2997
https://issues.apache.org/jira/browse/FELIX-3053
https://issues.apache.org/jira/browse/FELIX-3055

and includes FELIX-3002: Embed the OBR specific information for the
EventAdmin bundle in the manifest

The release passes the TCK

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

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 002 /tmp/felix-staging

Please vote to approve this release:

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


Regards
Carsten



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


Re: [VOTE] framework 4.0.0 and related subproject releases

2011-09-22 Thread Jean-Baptiste Onofré

+1 (non-binding)

Standalone tests performed without problem.

I'm working to use it on Karaf but it requires some core classes update.

Regards
JB

On 09/22/2011 05:47 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  4.0.0
framework.security 2.0.0
main 4.0.0
main.distribution 4.0.0
gogo.command 0.12.0


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

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 089 /tmp/felix-staging

Please vote to approve this release:

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


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


Re: [VOTE] Release Felix maven-bundle-plugin version 2.3.6

2011-11-28 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 11/29/2011 08:00 AM, Carsten Ziegeler wrote:

+1

Carsten

2011/11/29 Stuart McCullochmccu...@gmail.com:

On 28 Nov 2011, at 17:31, Stuart McCulloch wrote:

Hi folks,

We solved 17 issues in this release:

   
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22maven-bundle-plugin-2.3.6%22

There are still some outstanding issues:

   https://issues.apache.org/jira/browse/FELIX/component/12311143

Staging repository:

   https://repository.apache.org/content/repositories/orgapachefelix-264/

Maven site docs:

   
http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.3.6/doc/site/index.html

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 264 /tmp/felix-staging

Please vote to approve this release:

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


+1


This vote will be open for 72 hours.

--
Cheers, Stuart









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


Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.2

2011-12-04 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/03/2011 09:40 AM, Richard S. Hall wrote:

+1

- richard

p.s. I noticed that there was a discrepancy between calling it Light
HTTP Service vs Lightweight HTTP Server in the NOTICE/DEPS files, so
I updated trunk to use Lightweight HTTP Service for both.

On 12/1/11 2:35, Ken Gilmer wrote:

Hi,

We solved a few packaging issues not recorded in jira.

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

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 282 /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.



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


Re: [VOTE] Release Felix maven-bundle-plugin version 2.3.7

2012-02-14 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 02/13/2012 04:34 PM, Andrei Pozolotin wrote:

 Stuart:

 you mentioned before that maven-bundle-plugin
 how has some default bindings for m2e
 for incremental manifest build in eclipse;

 can you please elaborate a little on
 how to setup pom to use this feature properly?

 in 2.3.7?

 (my current concert is incremental build speed)

 Thank you,

 Andrei


 Original Message  
Subject: [VOTE] Release Felix maven-bundle-plugin version 2.3.7
From: Stuart McCullochmccu...@gmail.com
To: dev@felix.apache.org
Date: Sat 11 Feb 2012 01:42:52 PM CST

Hi folks,

We solved 5 issues in this release:

   
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22maven-bundle-plugin-2.3.7%22

There are still some outstanding issues:

   https://issues.apache.org/jira/browse/FELIX/component/12311143

Staging repository:

   https://repository.apache.org/content/repositories/orgapachefelix-221/

Maven site docs:

   
http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.3.7/doc/site/index.html

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 221 /tmp/felix-staging

Please vote to approve this release:

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

This vote will be open for 72 hours.

--
Cheers, Stuart





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


Re: [VOTE] Release Felix Utils 1.1.2

2012-02-14 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 02/14/2012 04:08 PM, Guillaume Nodet wrote:

Hi folks,

We solved 4 issues in this release:

  
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22utils-1.1.2%22

Staging repository:

  https://repository.apache.org/content/repositories/orgapachefelix-228/

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 228 /tmp/felix-staging

Please vote to approve this release:

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

This vote will be open for 72 hours.




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


Re: File Install Imrovements

2012-03-11 Thread Jean-Baptiste Onofré

Thanks Jacobs,

it sounds interesting, I will take a look on the Jiras.

Regards
JB

On 03/11/2012 06:50 PM, JBert wrote:



jgoodyear wrote:


Thank you for raising the issues and providing patches.

Could you attach the patches to the related Jiras and set the ASL
license grant? Generally most projects like to keep there patches with
their related Jiras for book keeping (makes it easier to find said
patches than searching email threads if we had to go back looking for
them).


Ok, done.

See the following issues:
https://issues.apache.org/jira/browse/FELIX-3373
https://issues.apache.org/jira/browse/FELIX-3346
https://issues.apache.org/jira/browse/FELIX-3386


With best regards,

Bert Jacobs



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


Re: [VOTE] Release FileInstall 3.2.0

2012-03-19 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 03/19/2012 03:07 PM, Guillaume Nodet wrote:

Hi,

Given the number of improvements, I've chosen to upgrade to a new
minor release instead of a micro one.

Please take some time to test as there has been important improvements
that could (hopefully not) lead to regressions.

We solved 18 issues in this
release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316135styleName=HtmlprojectId=12310100
There are still 6 outstanding
issues:https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+FELIX+AND+component+%3D+%22File+Install%22+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-091/
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 091 /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 at least 72 hours.




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


Re: [VOTE] Release FileInstall 3.2.2

2012-04-18 Thread Jean-Baptiste Onofré

+1 (non binding)

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


Re: [VOTE] Release Felix Configuration Admin version 1.4.0

2012-06-04 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/04/2012 11:06 AM, Karl Pauls wrote:

+1

regards,

Karl

On Sun, Jun 3, 2012 at 5:13 PM, Jamie G.jamie.goody...@gmail.com  wrote:

+1 (non-binding)

cheers,
Jamie

On Fri, Jun 1, 2012 at 6:42 PM, Felix Meschbergerfmesc...@adobe.com  wrote:

Hi,

Am 01.06.2012 um 20:20 schrieb Richard S. Hall:


+1

Not that it matters too much to me, but don't we normally include a
Maven source JAR in our releases? I don't see one here.


Yes, we do.. Hmm, will look into why this happened.

Regards
Felix



-  richard

On 5/30/12 09:20 , Felix Meschberger wrote:

Hi,

This is a vote on version 1.4.0 of the Felix Configuration Admin Service 
implementation. The corner stones of this release a re compliance with the 
latest Configuration Admin Service specification (version 1.4 as published in 
Compendium 4.3 specification).

At the same time, this is basically the same code, which is also used as the 
reference implementation for the Configuration Admin 1.4 specification. As such 
this release, of course also passes the CT for the Configuration Admin 1.4.

The main big difference to earlier releases of this bundle is, that this build requires a 
Java 5 or newer platform to run because the embedded OSGi classes are compiled for Java 5 
and are using generics. Great care has nevertheless been taken to not actually require 
Java 5 platform or API features. So, after recompiling the OSGi classes and this bundle 
using the target jsr14 this bundle is expected to run on Java 1.4 compliant 
platforms.

The next release coming soon will implement version 1.5 of the Configuration 
Admin specification to be published in the upcoming Compendium 5 specification.

We solved 22 issues in this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12316414

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

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 157 /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.

Regards
Felix








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


Re: [VOTE] Release Felix Utils 1.2.0 and Felix FileInstall 3.2.4

2012-06-12 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/12/2012 09:14 AM, Guillaume Nodet wrote:

I've uploaded those two releases to the following staging area:
   https://repository.apache.org/content/repositories/orgapachefelix-225/

In Utils, there has been one improvement and one new feature
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12319940styleName=HtmlprojectId=12310100Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7Cd88ae502b88bad1700dff41293afe539ea654a26%7Clin


In FileInstall, we've fixed 3 bugs and one improvement:
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12320776styleName=HtmlprojectId=12310100Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7Cd88ae502b88bad1700dff41293afe539ea654a26%7Clin

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 225 /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.




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


Re: [VOTE] framework 4.0.3 and related subproject releases

2012-07-02 Thread Jean-Baptiste Onofré

+1 (non binding)

Tested with Karaf.

Regards
JB

On 07/02/2012 10:08 PM, Richard S. Hall wrote:

+1

- richard

On 7/1/12 17:06, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  4.0.3
main 4.0.3
main.distribution 4.0.3


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

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 001 /tmp/felix-staging

Please vote to approve this release:

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





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




Re: [VOTE] Accept the UserAdmin donation by Jan Willem Janssen

2012-08-06 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 08/06/2012 09:48 PM, David Bosschaert wrote:

+1 (non binding)

David

On 3 August 2012 16:57, Marcel Offermans marcel.offerm...@luminis.nl wrote:

A little while ago, Jan Willem Janssen donated a complete implementation of the 
UserAdmin compendium service [1] to our project. I would like to start a formal 
vote on accepting this code.

Please vote:

[   ] +1 Accept this donation.
[   ] 0 Don't care.
[   ] -1 Don't accept this donation (please motivate your vote).

Greetings, Marcel

[1] https://issues.apache.org/jira/browse/FELIX-3600



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


Re: [VOTE] Release Apache Felix EventAdmin 1.3.0

2012-09-12 Thread Jean-Baptiste Onofré

+1 (non-binding)

Tested in Karaf.

Regards
JB

On 09/12/2012 07:54 AM, Carsten Ziegeler wrote:

Hi,

It's nearly a year since the last release and we solved 5 issues in
this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12317341

and this is the first release supporting the 1.3 version of the spec.
This implementation passed
the OSGi EventAdmin CT.

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

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 057 /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.

Carsten



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


Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Jean-Baptiste Onofré

Hi,

My preference would be to 2, more than pollute the original config 
with an extra attribute.


My 0.02€

Regards
JB

On 09/17/2012 11:47 AM, Christian Schneider wrote:

Hi all,

felix config admin behaves differently if the config originated from a
file or was directly created in config admin. For most cases this is good.

Sometimes I would like the behaviour to create a config by hand (shell
or mbean) or programatically but make sure it is also created in etc in
Karaf. So I would like to have a way to tell felix config admin to
persist the config to etc.

I see two possible solutions:

1. Have a special config property like
felix.configadmin.persistToFile=true. When this property is set to true
the config admin service would create a file pid.cfg in a configurable
default config directory.
2. Have a special API in form of an OSGi service that allows to
initially persist a config like configAdminExt.persist(String pid)

We are also discussing this feature on the karaf list but I think it
would be more suitable to solve this in felix config admin service. What
do you think?

Christian



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


Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Jean-Baptiste Onofré
I think that Christian is talking about the behavior inside Karaf where 
we mix FileInstall and ConfigAdmin.


Regards
JB

On 09/17/2012 12:45 PM, Marcel Offermans wrote:

On Sep 17, 2012, at 11:47 AM, Christian Schneider ch...@die-schneider.net 
wrote:


felix config admin behaves differently if the config originated from a file or 
was directly created in config admin. For most cases this is good.


Maybe I missed something, but how does the Felix implementation of ConfigAdmin 
behave differently? As far as I'm aware, the ConfigAdmin spec says nothing at 
all about where a configuration originated from (a file or whatever).

Greetings, Marcel



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


Re: [VOTE] Release Apache Felix Configuration Admin 1.6.0

2012-10-20 Thread Jean-Baptiste Onofré

+1 (non binding)

Tested in Apache Karaf.

Regards
JB

On 10/20/2012 12:36 PM, Felix Meschberger wrote:

Hi,

Here is the Apache Felix Configuration Admin 1.6.0 release implementing the 
most recent Configuration Admin Specification Version 1.5.

The issues completed in this release are listed in the release notes at (also 
attached at the end of this message):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12320945

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

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 144 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Release
[ ] -1 Don't release, because ...

This vote will be open for at least 72 hours.

Regards
Felix

** Bug
* [FELIX-3532] - Source artifact is not being generated
* [FELIX-3596] - Config Admin should track
  SynchronousConfigurationListeners
* [FELIX-3721] - Configuration not always provided upon
  initial service registration
** Improvement
* [FELIX-3577] - Refactor helpers and service trackers
* [FELIX-3622] - ConfigurationManager.listConfigurations
  may not always properly log the
  configuration PID
** Task
* [FELIX-3479] - [Config Admin 1.5] Implement
  Configuration.getChangeCount()
* [FELIX-3480] - [Config Admin 1.5] Implement support for
  SynchronousConfigurationListener
* [FELIX-3481] - [Config Admin 1.5] Implement support for
  Targeted PIDs
* [FELIX-3483] - [Config Admin 1.5] Export cm API at version 1.5
* [FELIX-3554] - Prevent same configuration to be delivered
  multiple times
* [FELIX-3562] - Use OSGi Configuration Admin 1.5 API classes
* [FELIX-3578] - ConfigAdmin Maven build does not have Maven
  convention *-sources.jar artifacts



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


Re: Fwd: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7

2012-10-29 Thread Jean-Baptiste Onofré

FYI,

the 4.3.1 artifacts have not yet been deployed on Central.

Regards
JB

On 10/29/2012 09:00 AM, Felix Meschberger wrote:

FYI in case you missed it.

In short: The OSGi R 4.3 libraries have been recompiled with Java 5 target and 
republished as version 4.3.1 to maven. So to use OSGi R 4.3 libraries in a Java 
5 (and up) environment you should use the 4.3.1 version dependency.

Nothing to be done when using older (4.2.0 and before) dependencies because 
they are compiled for Java 1.4.

Regards
Felix

Anfang der weitergeleiteten E-Mail:

Von: BJ Hargrave b...@bjhargrave.commailto:b...@bjhargrave.com
Betreff: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7
Datum: 26. Oktober 2012 21:06:11 MESZ
An: osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org 
osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org
Antwort an: Private list for OSGi blog discussion 
osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org

Starting in version 4.3, OSGi started to use generics in some of the API including the Core 
specification. Generics were 
introducedhttps://en.wikipedia.org/wiki/Generics_in_Java to the Java language in 
Java 5. However, OSGi needed to continue to support embedded use cases which use the 
CDC/Foundation 1.1 runtime which is still based upon the Java 1.4 language level and JVM. 
To address this issue, OSGi compiled the APIs with -target 
jsr14http://www.ibm.com/developerworks/java/library/j-jtp02277/index.html; an 
undocumented javac flag introduced before Java 5 was final. So we had the best of both 
worlds: we can use generics and still compile to run on Java 1.4 based runtimes.

This worked for Java 5 and Java 6. But when Java 7 shipped, two things changed: javac 
no longer understood the jsr14 option to -target and javac refused to recognize the 
attributes containing the generics information in class files already compiled with 
-target jsr14. The change to no longer support creating -target jsr14 class files was 
ok; we could continue to compile with Java 6 javac. But the change to the javac to 
cease to recognize the class file attributes with the generics information in 
existing class files was a bigger problem. It meant that the 4.3 API jars published 
by OSGi were not useable by people who need to compile with Java 7 javac. By not 
useable, I mean javac treated the classes as if they did not contain any generics 
information: they were raw. A 
bughttp://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7078419 was filed 
against Java to see if this was some mistake or oversight. The reply was that the 
change was intentional.

At the time this was first 
noticedhttps://mail.osgi.org/pipermail/osgi-dev/2011-August/003223.html, Java 7 was new and not 
too widely used. OSGi also included the source code in the jars so you could recompile the code yourself 
if you needed. Later, when it came time to ship Core R5, we changed to compile the API classes with 
-target 1.5 and so they work fine on Java 7. So problem solved; the new release's jars don't use -target 
jsr14! Except some of the current OSGi implementations (I'm looking at you 
Felixhttps://felix.apache.org/ and Karafhttps://karaf.apache.org/) are still based upon 
Core 4.3 and thus people using those implementations still need to use the Core 4.3 API. And if they also 
want to use Java 7, they need to recompile the OSGi API source. So after some prodding by a few folks, 
OSGi rebuilt the Core and Compendium API jars as Core 
4.3.1http://www.osgi.org/Download/File?url=/download/r4v43/osgi.core-4.3.1.jar and Compendium 
4.3.1http://www.osgi.org/Download/F

ile?url=/download/r4v43/osgi.cmpn-4.3.1.jar. The new jars have the same 
packages at the same package versions having the same API signatures. They are 
just not compiled with -target jsr14 so they work fine with Java 7.


So if you need to use the 4.3 API with Java 7, pick up these new 4.3.1 jars. They 
should also be available on mavenhttp://mvnrepository.com/artifact/org.osgi 
shortly.

--
Posted By BJ Hargrave to OSGi Alliance 
Bloghttp://blog.osgi.org/2012/10/43-companion-code-for-java-7.html at 
10/26/2012 07:06:00 PM ___
osgi-blog mailing list
osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-blog




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


Re: [VOTE] Release Apache Felix Metatype Service 1.0.6

2012-10-29 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 10/29/2012 04:54 PM, Felix Meschberger wrote:

Hi,

Here is the Apache Felix Metatype Service 1.0.6 release implementing the most 
recent MetaType Service Specification Version 1.2.

The issues completed in this release are listed in the release notes at (also 
attached at the end of this message):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144

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

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 177 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Release
[ ] -1 Don't release, because ...

This vote will be open for at least 72 hours.

Regards
Felix

** Bug
* [FELIX-2094] - AttributeDefinition with an empty default value
  must attribute must result in a single (empty
  string) entry string array
* [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not
  reuturn an empty string entry
* [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs
  to check return of findEntries
* [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset
  iteration incorrect
* [FELIX-2868] - Icon only works if absolute path specified, but
  specification allows for relative urls
* [FELIX-3183] - Attribute requirement is not validated
* [FELIX-3364] - MetaDataReader exposes a private exception class on
  the public API
* [FELIX-3720] - Designate's pid attribute is optional and not mandatory
* [FELIX-3730] - AD.validate of string attributes must validate the
  string length
* [FELIX-3732] - service.pid properties of ManagedServiceFactory services
  must be used as factory PIDs
* [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle
** Improvement
* [FELIX-3167] - Add support for new PASSWORD attribute type
* [FELIX-3338] - Add support for optional attributes in the
  MetaDataReader as defined in the XML schema for metatype
* [FELIX-3736] - Add support for MetaTypeProvider service modifications
* [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the
  MetaTypeService
** New Feature
* [FELIX-2719] - Add name space support to the meta type implementation
** Task
* [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String,
  String) specification compliance
* [FELIX-3182] - Update to use parent POM 2.1
* [FELIX-3184] - Add support for metatype extension by MetatypeProvider services
* [FELIX-3731] - Multi-Value service.pid service properties must be supported
* [FELIX-3733] - Clarify icon location



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


Re: java 7 osgi core compendium

2012-10-30 Thread Jean-Baptiste Onofré

Thanks David,

I gonna make a try in Karaf.

I keep you posted.

Regards
JB

On 10/30/2012 11:24 AM, David Bosschaert wrote:

I've uploaded the 4.3.1 jars to the Maven Central staging area. It
would be great if someone could check that they are indeed working
fine and properly signed.

See: https://www.osgi.org/bugzilla/show_bug.cgi?id=153#c13

Thanks,

David

On 8 October 2012 20:45, Andrei Pozolotin andrei.pozolo...@gmail.com wrote:

David:

great! thank you.

I answered back on https://www.osgi.org/bugzilla/show_bug.cgi?id=153

Andrei.


 Original Message 
Subject: Re: java 7 osgi core  compendium
From: David Bosschaert david.bosscha...@gmail.com
To: dev@felix.apache.org
Date: Mon 08 Oct 2012 03:05:18 AM CDT

Hi Andrei,

I left a comment on that bug and reassigned it to me, as I have been
the one who uploaded OSGi Artifacts to Maven in the recent past.
I would be happy to help getting OSGi 4.3 artifacts in maven that work
with Java 7.

Best regards,

David

On 5 October 2012 20:03, Andrei Pozolotin andrei.pozolo...@gmail.com
wrote:

 *Felix and Jean-Baptiste*:

 since osgi alliance does not want to take responsibility for this
 https://www.osgi.org/bugzilla/show_bug.cgi?id=153

 1) do you think it would be appropriate for felix or karaf to step in,
 and to produce and maintain shared java 7 osgi core  compendium
 jars for all of us?

 2) or else should everyone continue to bake their own?

 3) if shared, can you agree who should lead?

 Thank you,

 Andrei




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


Re: java 7 osgi core compendium

2012-11-01 Thread Jean-Baptiste Onofré

Hi,

I will work on it tonight.
I keep you posted.

Regards
JB

On 11/01/2012 05:50 PM, Andrei Pozolotin wrote:

JB:

https://www.osgi.org/bugzilla/show_bug.cgi?id=153

I tried to migrate karaf trunk to new osgi 4.3.1
https://github.com/carrot-garden/carrot-apache-karaf/tree/osgi-4.3.1

so far compile fails. I hope JB has better luck.


 Original Message 
Subject: Re: java 7 osgi core  compendium
From: Jean-Baptiste Onofré j...@nanthrax.net
To: dev@felix.apache.org
Date: Tue 30 Oct 2012 05:26:53 AM CDT

Thanks David,

I gonna make a try in Karaf.

I keep you posted.

Regards
JB

On 10/30/2012 11:24 AM, David Bosschaert wrote:

I've uploaded the 4.3.1 jars to the Maven Central staging area. It
would be great if someone could check that they are indeed working
fine and properly signed.

See: https://www.osgi.org/bugzilla/show_bug.cgi?id=153#c13

Thanks,

David

On 8 October 2012 20:45, Andrei Pozolotin
andrei.pozolo...@gmail.com wrote:

David:

great! thank you.

I answered back on https://www.osgi.org/bugzilla/show_bug.cgi?id=153

Andrei.


 Original Message 
Subject: Re: java 7 osgi core  compendium
From: David Bosschaert david.bosscha...@gmail.com
To: dev@felix.apache.org
Date: Mon 08 Oct 2012 03:05:18 AM CDT

Hi Andrei,

I left a comment on that bug and reassigned it to me, as I have been
the one who uploaded OSGi Artifacts to Maven in the recent past.
I would be happy to help getting OSGi 4.3 artifacts in maven that work
with Java 7.

Best regards,

David

On 5 October 2012 20:03, Andrei Pozolotin andrei.pozolo...@gmail.com
wrote:

 *Felix and Jean-Baptiste*:

 since osgi alliance does not want to take responsibility for this
https://www.osgi.org/bugzilla/show_bug.cgi?id=153

 1) do you think it would be appropriate for felix or karaf to
step in,
 and to produce and maintain shared java 7 osgi core  compendium
 jars for all of us?

 2) or else should everyone continue to bake their own?

 3) if shared, can you agree who should lead?

 Thank you,

 Andrei








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


Re: java 7 osgi core compendium

2012-11-05 Thread Jean-Baptiste Onofré

Hi David,

I tested these artifacts on Karaf trunk without problem. The signatures 
look good as well.


You have my +1 to promote it to Central.

Thanks,
Regards
JB

On 10/30/2012 11:24 AM, David Bosschaert wrote:

I've uploaded the 4.3.1 jars to the Maven Central staging area. It
would be great if someone could check that they are indeed working
fine and properly signed.

See: https://www.osgi.org/bugzilla/show_bug.cgi?id=153#c13

Thanks,

David

On 8 October 2012 20:45, Andrei Pozolotin andrei.pozolo...@gmail.com wrote:

David:

great! thank you.

I answered back on https://www.osgi.org/bugzilla/show_bug.cgi?id=153

Andrei.


 Original Message 
Subject: Re: java 7 osgi core  compendium
From: David Bosschaert david.bosscha...@gmail.com
To: dev@felix.apache.org
Date: Mon 08 Oct 2012 03:05:18 AM CDT

Hi Andrei,

I left a comment on that bug and reassigned it to me, as I have been
the one who uploaded OSGi Artifacts to Maven in the recent past.
I would be happy to help getting OSGi 4.3 artifacts in maven that work
with Java 7.

Best regards,

David

On 5 October 2012 20:03, Andrei Pozolotin andrei.pozolo...@gmail.com
wrote:

 *Felix and Jean-Baptiste*:

 since osgi alliance does not want to take responsibility for this
 https://www.osgi.org/bugzilla/show_bug.cgi?id=153

 1) do you think it would be appropriate for felix or karaf to step in,
 and to produce and maintain shared java 7 osgi core  compendium
 jars for all of us?

 2) or else should everyone continue to bake their own?

 3) if shared, can you agree who should lead?

 Thank you,

 Andrei




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


Re: java 7 osgi core compendium

2012-11-05 Thread Jean-Baptiste Onofré

Awesome,

thanks a lot, I will update in Karaf.

Regards
JB

On 11/05/2012 08:13 PM, David Bosschaert wrote:

I've released them to central now:
http://search.maven.org/#artifactdetails%7Corg.osgi%7Corg.osgi.core%7C4.3.1%7Cjar

http://search.maven.org/#artifactdetails%7Corg.osgi%7Corg.osgi.compendium%7C4.3.1%7Cjar

Cheers,

David

On 5 November 2012 11:57, Jean-Baptiste Onofré j...@nanthrax.net wrote:

Hi David,

I tested these artifacts on Karaf trunk without problem. The signatures look
good as well.

You have my +1 to promote it to Central.

Thanks,

Regards
JB

On 10/30/2012 11:24 AM, David Bosschaert wrote:


I've uploaded the 4.3.1 jars to the Maven Central staging area. It
would be great if someone could check that they are indeed working
fine and properly signed.

See: https://www.osgi.org/bugzilla/show_bug.cgi?id=153#c13

Thanks,

David

On 8 October 2012 20:45, Andrei Pozolotin andrei.pozolo...@gmail.com
wrote:


David:

great! thank you.

I answered back on https://www.osgi.org/bugzilla/show_bug.cgi?id=153

Andrei.


 Original Message 
Subject: Re: java 7 osgi core  compendium
From: David Bosschaert david.bosscha...@gmail.com
To: dev@felix.apache.org
Date: Mon 08 Oct 2012 03:05:18 AM CDT

Hi Andrei,

I left a comment on that bug and reassigned it to me, as I have been
the one who uploaded OSGi Artifacts to Maven in the recent past.
I would be happy to help getting OSGi 4.3 artifacts in maven that work
with Java 7.

Best regards,

David

On 5 October 2012 20:03, Andrei Pozolotin andrei.pozolo...@gmail.com
wrote:

  *Felix and Jean-Baptiste*:

  since osgi alliance does not want to take responsibility for this
  https://www.osgi.org/bugzilla/show_bug.cgi?id=153

  1) do you think it would be appropriate for felix or karaf to step
in,
  and to produce and maintain shared java 7 osgi core  compendium
  jars for all of us?

  2) or else should everyone continue to bake their own?

  3) if shared, can you agree who should lead?

  Thank you,

  Andrei




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


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


Re: [VOTE] Release Apache Felix Declarative Services 1.6.2

2012-11-07 Thread Jean-Baptiste Onofré
 down a component due to service already 
removed
 * [FELIX-3676] - [DS] misleading logging on first immediate component 
getService call
 * [FELIX-3681] - [DS] Dependencies are not dropped when implemention 
object is discarded
 * [FELIX-3697] - [DS] create all the components in a bundle before 
enabling them
 * [FELIX-3698] - [DS] code simplification for 
BundleComponentActivator.getSelectedComponents
 * [FELIX-3704] - [DS] ds shutdown should wait for ComponentActorThread 
task queue to complete before finishing
 * [FELIX-3710] - [DS] don't try to activate for a service event for an 
optional reference
 * [FELIX-3717] - [DS] unbind method might not have correct parameters
 * [FELIX-3718] - [DS] deactivate might not move component state to 
unsatisfied
 * [FELIX-3719] - [DS]  disabling a dependency manager should not reset the 
service count
 * [FELIX-3723] - ClassCastException on ConfigurationAdmin service creating 
components
 * [FELIX-3724] - [DS] concurrent getService calls may return null
 * [FELIX-3725] - [DS] hidden dependency on spring junit wrapper from pax 
exam
 * [FELIX-3726] - Reference target filters defined as component properties 
are ignored
 * [FELIX-3727] - [DS] NPE during shutdown
 * [FELIX-3744] - [DS] Component should set implementation object before 
propagating changed service properties



** Improvement
 * [FELIX-2895] - Allow the use of a property to tell SCR to always 
discover Service Component files even if there's no wildcard in the name
 * [FELIX-3016] - Activator log level cannot be changed dynamically through 
Configuration Admin
 * [FELIX-3232] - Re-Import SCR Service API
 * [FELIX-3371] - update scr build to recent pax components
 * [FELIX-3377] - Allow a component to update its own service properties
 * [FELIX-3506] - SCR bind/unbind/update methods should be able to return a 
map of service properties like the activate/deactivate/modified methods.s
 * [FELIX-3569] - Improve configured method handling for ComponentFactory 
instances
 * [FELIX-3662] - [DS] use backport-util-concurrenct instead of concurrent 
for pre java 5 compatibility
 * [FELIX-3677] - [DS] in the scr command info operation, show the bound 
service references

** New Feature
 * [FELIX-2712] - [SCR] Add Gogo command support
 * [FELIX-3507] - scr greedy and reluctant policy options from compendium 
4.3
 * [FELIX-3524] - SCR configuration-pid from compendium 4.3






** Task
 * [FELIX-2539] - Include DEPENDENCIES file in distributables
 * [FELIX-2553] - Reconsider logging/log levels
 * [FELIX-2903] - Inline required KXml classes
 * [FELIX-3158] - Upgrade to Felix parent POM 2.1 and use managed ant 
plugin version
 * [FELIX-3527] - Add Java API usage check
 * [FELIX-3668] - Revert Rev. 1381440 restore previous behavior when a bind 
method cannot be found
 * [FELIX-3679] - Component names need not be globally unique any more
 * [FELIX-3747] - Cleanup maven project setup





** Wish
 * [FELIX-1747] - Use Remote Resources Plugin to generate the legal files




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


Re: [VOTE] framework 4.2.0 and related subproject releases

2013-02-05 Thread Jean-Baptiste Onofré
+1 (non binding)

Tested in Karaf 2.3.1-SNAPSHOT.

Regards
JB

Karl Pauls karlpa...@gmail.com a écrit :

I would like to call a vote on the following subproject releases:

framework  4.2.0
main 4.2.0
main.distribution 4.2.0


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

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 201 /tmp/felix-staging

Please vote to approve this release:

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


Re: [VOTE] SCR Tooling Release

2013-02-13 Thread Jean-Baptiste Onofré
+1 (non binding)

Regards
JB

Carsten Ziegeler cziege...@apache.org a écrit :

Hi,

This vote is about an update to our SCR tooling, it fixes some major
bugs and adds some nice features

SCR Generator 1.4.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12323599

Maven SCR Plugin 1.10.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12323601

SCR Ant Task 1.4.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12323599

SCR Annotations 1.8.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12322946

SCR DS Annotations 1.2.2
https://issues.apache.org/jira/browse/FELIX/fixforversion/12322950

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

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 231 /tmp/felix-staging


Please vote to approve this release:

 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...

This vote will be open for 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
cziege...@apache.org


Re: OSGi manifest information for org.apache.commons.logging

2013-02-23 Thread Jean-Baptiste Onofré
AFAIR, all commons-* already inherit POM with felix-bundle-plugin 
configuration.


I don't think the main issue is on the OSGi statement itself.

Regards
JB

On 02/23/2013 09:51 AM, Christian Schneider wrote:

I have created a patch to add the maven bundle plugin to the pom. You
can find it in the jira issue.
While the headers look good then I am not sure if this is enough to
really use commons logging in OSGi.

I typically use pax logging for logging in OSGi. It already supports all
big logging APIs including commons logging and makes sure they can also
be configured using a log4j config file.
So as there is a nice solution I am not sure how much we should invest
to make commons logging working standalone. On the other hand if the
commons logging API jar is a bundle then perhaps the commons logging
api can be removed from pax logging and just deployed as a bundle.

Christian

Am 22.02.2013 20:22, schrieb Benedikt Ritter:

Hi Felix community,

we are trying to fix our OSGi manifest information for o.a.c.logging as
requested in Jira [1]. We don't know yet how a correct manifest for
[logging] would look like. We have looked at rebundled versions from
felix
and spring [2].
Can someone join our ML and help out a bit? Here [3] is what we have
found
out so far :-)

TIA!
Benedikt

[1] https://issues.apache.org/jira/browse/LOGGING-124
[2]
http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.org.apache.commons.loggingversion=1.1.1searchType=bundlesByNamesearchQuery=logging

[3] http://markmail.org/message/277c5mrpdpcfj4wr





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


Re: [VOTE] framework 4.2.1 and related subproject releases

2013-03-09 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 03/09/2013 06:56 PM, Jamie G. wrote:

+1 (non-binding)

Cheers,
Jamie Goodyear

On Sat, Mar 9, 2013 at 11:04 AM, Sahoo sanjeeb.sa...@oracle.com wrote:

+1

Thanks,
Sahoo

On Saturday 09 March 2013 03:28 AM, Karl Pauls wrote:


I would like to call a vote on the following subproject releases:

framework  4.2.1
framework.security 2.2.0
main 4.2.1
main.distribution 4.2.1


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

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 007 /tmp/felix-staging

Please vote to approve this release:

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





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


Re: [VOTE] Release Apache Felix Configuration Admin 1.8.0

2013-09-25 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 09/25/2013 04:26 PM, Felix Meschberger wrote:

Hi,

Here is the Apache Felix Configuration Admin 1.8.0 release containing a small 
number of bug fixes since the last Configuration Admin 1.6.0 release.

The issues completed in this release are listed in the release notes at (also
attached at the end of this message):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12323461

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

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 099 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Release
[ ]  0 Don't care
[ ] -1 Don't release, because ...

This vote will be open for at least 72 hours.

Regards Felix



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


Re: [VOTE] Release Felix HTTP v2.2.1

2013-09-27 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 09/25/2013 04:47 PM, Felix Meschberger wrote:

+1

Regards
Felix

Am 18.09.2013 um 16:13 schrieb Jan Willem Janssen:


Signierter PGP Teil
Hi,

After some initial struggles preparing the release, it is time to cast
a vote on a new release of Felix HTTP.

We solved the following issues since the 2.2.0 release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20component%20%3D%20%22HTTP%20Service%22%20AND%20resolved%20%3E%3D%202011-01-26%20AND%20resolved%20%3C%3D%202013-09-18

There are still some outstanding issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22HTTP%20Service%22

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

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 072

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.

- --
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01





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


Re: [VOTE] Release Felix HTTP v2.2.2

2013-12-06 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/06/2013 09:34 AM, Guillaume Nodet wrote:

+1


2013/12/3 Jan Willem Janssen janwillem.jans...@luminis.eu


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

We solved 13 issues in this release, amongst which one fixing a broken
bundle (FELIX-4282). See [1] for a complete list.

There are still a couple of outstanding issues, see [2].

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

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 009

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 (at least).


1.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20%22http-2.2.2%22%20AND%20component%20%3D%20%22HTTP%20Service%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC

2.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20%22http-2.2.2%22%20AND%20component%20%3D%20%22HTTP%20Service%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC


- --
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSnfsdAAoJEKF/mP2eHDc4vzcQAKff/43Z20t1Qg9ESpzNYC8v
iye/kj7I175P2z+45Ax/d5OfMWPG5w8eoW7CTSugm+voaJ48kROCJGmHRIQ2Qsfy
83CIWqm6fRSFUNjTAvQ79CiOOcjCP4NSxeVpgFI9hJCIBMm7FCoWREg12CjocCz6
T9QX5LCIZQcxPypxwKYUiplEhbDaOXc3dR14NXi9z5Umei5BfrJnJjZpbHQNZZOF
eGCyhhi+z+E0wh7e8idHTmegkFguxnDxHffNYG3VjDgNY4BRASD7cXEaQitRtTLM
+IKUVU2Cyk7r5fg00msiyRq25DU7ki3vHP8KYPiLbscwBGikyfsq65GkZR1L1Ly+
NOZ9go2bGaHc7ZVU3AT5/sCv2fRpnYvQ3T9duH+5YtHTIaikAgzeFtcmlS39xWqR
8WeRYv4omfgeZ12timzpiuCEl2FGfyRARnx8sgtezev4NkGXYitTBDj6HW+/wqBA
Jq3Qp2jqpLBSV/ml+CxA08IeDSa4rXEo6pI+nc2AcwYIF/YG3CilaTUNefxHbNiw
se1tVW0+X7uqv3+G6BqjJ+uqH+93Yh7mGAk484WpFAx0cByzxSZ4RxYGROFQpYID
qnqgIuYl8LICe8OC34gyi+ZgCJJN4OqZdxL2Sbwj3X8aONK3VUIJnPLiVLOk9dqW
c1heDRJZtcN0RBYKj1bn
=ewbu
-END PGP SIGNATURE-





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


Re: [VOTE] Release DeploymentAdmin 0.9.5 and AutoConf Processor 0.1.5

2013-12-06 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/06/2013 09:34 AM, Guillaume Nodet wrote:

+1


2013/12/3 Jan Willem Janssen janwillem.jans...@luminis.eu


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

We solved the following issues:

DeploymentAdmin release 0.9.5
- ---
- - FELIX-4184 Temporary resolver errors while updating bundles with
deploymentadmin;
- - FELIX-4167 DeploymentAdmin tries to start/stop fragment bundles.

AutoConf Processor release 0.1.5
- 
- - FELIX-4314 Split service registration to solve visibility issue in
autoconf;
- - FELIX-3355 Autoconf can't find Metatype service.

There are still some outstanding issues, see [1].

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

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 011

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 (at least).


1.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20component%20%3D%20%22Deployment%20Admin%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

- --
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSnfsZAAoJEKF/mP2eHDc4y1AP/2h5ieVtrymcDx1xsvGAXLdU
7627m7OLKW9hRj516eaEhrAffTpUia/HVSAVi75ABNqS95vAATMu0qC/oc3xaKh9
+f4k0RMkgmmXVJhiXkCsoqBmSkAfolwLMEoEcF0G8mHUZYqxGLwUMkoFGWpNNALK
eeS8Es3I5YQOkDn6NTHoMWjshMJfR5yfI5NjhYozjqOuFVro5bMPwWAmR0YQdJDL
eDmJbHztS9Q89gk3pL1Vu+RvE1iAClA3BzETNYfALGeqoXSZFTHfgRD4q7KzwM/o
Oj01h0bWYT6u++KhJV+M//fKYK3GTkdJn2JgG8ErfCbHg65is3cI5tFnH0AnzNmw
IZmJ+b5aJ91VMnSwbm+7yg/6/MxYwkz6Ny2V1fNAKsJA+g6wn4nncIIeUMr+KeQO
6p3U5Bs1K0xDZkd9RdhcvSm4oHgBKlwIiNsk1EhLo0PTvyQC31UclHs7r/Iw8oQL
4OgOaAT2HP+NQUboeg8tFH9LKBcuznqeIIX03zkGSUwzu22yMlXWMHPC2SXy2CXZ
PLBQdXEPs8EIM1MtH4EMo7cLXRxP3OYSA6ofDbfxE3z/cbe5GWWvm12mPApcMFFt
HA6yDNOw/Y+TZruOJmJiIsmenygSCyTxEuLmgKaugvcLSlb7UjmXaLHhYlbrJ4Tm
19fNaL7TIRFesyr+FI8V
=sqwi
-END PGP SIGNATURE-





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


Re: [VOTE] Release Utils 1.4.2 and FileInstall 3.2.8

2013-12-09 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 12/09/2013 09:48 AM, Guillaume Nodet wrote:

I'd like to propose a release of FileInstall 3.2.8, which also requires a
utils release.  These releases are mostly bug fixes.

The artifacts are located in

https://repository.apache.org/content/repositories/orgapachefelix-027/

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 027 /tmp/felix-staging

Please vote to approve these releases:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for 72 hours (at least).

Cheers,
Guillaume



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


Re: Provide an option to persist a config to a file in e.g. etc

2014-01-12 Thread Jean-Baptiste Onofré

Hi Ivan,

yes, I created a Jira about that:
https://issues.apache.org/jira/browse/KARAF-2656

As reminder, in previous Karaf release (Karaf 2.x), Karaf itself was 
responsible of the creation of files in the etc folder.
Christian removed it for Karaf 3.0.0, probably he expected to delegate 
the behaviour to Felix ConfigAdmin. However the new configurations are 
not created in the etc folder (as explained by Felix, Felix ConfigAdmin 
only flush back the config in the configuration file if the 
felix.fileinstall property is known).
I think that Christian planned to submit a patch but he didn't and now 
we have a kind of regression in Karaf 3.0.0 as we removed the previous 
behaviour.


I will re-add the creation of the configuration file for new config in 
Karaf waiting the support directly in ConfigAdmin.

I will be available in Karaf 3.0.1.

Regards
JB

On 01/12/2014 06:06 PM, odb wrote:

Hi,

Any follow-up on this?
As far as I can tell, new configuration items are still not created in the
etc/ directory (Karaf 3.0).

Ivan




--
View this message in context: 
http://apache-felix.18485.x6.nabble.com/Provide-an-option-to-persist-a-config-to-a-file-in-e-g-etc-tp4999348p5006735.html
Sent from the Apache Felix - Dev mailing list archive at Nabble.com.



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


Re: Maybe a Felix Framework release sometime soon?

2014-01-17 Thread Jean-Baptiste Onofré

+1 (non-binding)

Regards
JB

On 01/17/2014 04:44 PM, David Bosschaert wrote:

Hi all,

Just wondering what people think... Would it make sense to do a Felix
Framework release in the near future?
Quite a lot of work has gone into moving Felix towards Core R5
support. While we're not 100% there yet (the remaining issues are in
the Resolver and ResolverHooks area [1]) I think it's definitely moved
on, as for example you can now run Subsystems on Felix.

Thoughts, anyone? I'm happy to help get that release out, if needed :)

Cheers,

David

[1] https://issues.apache.org/jira/browse/FELIX-4128



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


Re: [VOTE] Felix SCR/DS 1.8.2

2014-01-20 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 01/20/2014 06:18 PM, David Bosschaert wrote:

+1

David

On 18 January 2014 04:13, David Jencks david_jen...@yahoo.com wrote:

We've fixed a number of bugs since 1.8.0 and would like to get out a release 
before adding new R6/rfc 190 features, and we aren't aware of any major 
existing bugs.

Changes since 1.8.0:

** Bug
 * [FELIX-4309] - SCR leaves some components in DISABLED state
 * [FELIX-4313] - Bad synchronization in scr where a lock is held while 
ungetting a service
 * [FELIX-4322] - [DS] Prevent activation attempts until all dependency 
managers are set up with trackers
 * [FELIX-4323] - [DS] ScrService.getComponents may return a null array 
element
 * [FELIX-4325] - [DS] Synchronization issue when activating component
 * [FELIX-4326] - Possible Invalid BundleContext exception when shutting 
down the extender
 * [FELIX-4348] - [DS] locateService calls race with component 
reconfiguration
 * [FELIX-4349] - Synchronization issue in ComponentRegistry
 * [FELIX-4350] - Component wrongly activated

** Improvement
 * [FELIX-4316] - Packages imported dynamically should also be imported 
statically with an optional flag
 * [FELIX-4317] - SCR implementation should avoid using 
bundleContext.getBundle()
 * [FELIX-4343] - [DS] rationalize log levels

Staging area:

https://repository.apache.org/content/repositories/orgapachefelix-1002/

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 1002  /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.


thanks
david jencks




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


Re: Fwd: OSGi and JDK8 Status?

2014-01-24 Thread Jean-Baptiste Onofré

Hi Felix,

as I said to JP on the Karaf mailing list, in Karaf, we don't want to 
upgrade to ASM 5 now as it's a beta (and it's a bit risky on our stable 
branches).


Just my $0.02

Regards
JB

On 01/24/2014 10:24 AM, Felix Meschberger wrote:

Hmm, given that ASM 5 BETA is available and supposedly supports Java 8 class 
files, should we update the SCR plugin to use ASM 5 BETA ?

Regards
Felix

Anfang der weitergeleiteten Nachricht:


Von: CLEMENT Jean-Philippe jean-philippe.clem...@fr.thalesgroup.com
Betreff: RE: OSGi and JDK8 Status?
Datum: 23. Januar 2014 09:39:12 MEZ
An: us...@felix.apache.org us...@felix.apache.org
Antwort an: us...@felix.apache.org

Karaf which is based on Felix works for me but with a lot of strange traces in 
the log.

As per ASM team, ASM 5 will be released when Java8 would be. However, ASM 5 
beta is ok ready to be used.

I don't have any trouble with the Maven scr plugin, but the Eclipse plugin does 
not support new Java8 syntax. Neither Checkstyle.

Eclipse itself partly supports Java8 but with a patch. I experienced strange 
behaviors, but, it works.

Note that Java8 itself does also contain bugs, especially in JavaFX.

JP


De : Mark Derricutt [mailto:m...@talios.com]
Envoyé : mercredi 22 janvier 2014 20:57
À : us...@felix.apache.org
Objet : OSGi and JDK8 Status?


Hey there,

Has anyone tracked what the status of Felix/OSGi is under JDK8 (targetted 
bytecode) etc. is yet?

So far AFAIK:

*   maven-scr-plugin broken due to ASM 5 not being released, so doesn't support 
new bytecode
*   maven-bundle-plugin broken due to BND also not supporting JDK8 bytecode, or 
source code

Any one know if Pax-CDI works? iPojo?

Felix/Karaf itself all seems to work fine running UNDER JDK8 once I added the 
jre exports tho.

Has anyone built up -SNAPSHOTS of the above two plugins with SNAPSHOTS of 
dependencies to get something working so that once JDK8 is officially released 
( or better, once the RC is released ) that broader testing of OSGi based apps 
can go forth.

Mark




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


Re: [VOTE] Apache Felix Webconsole 4.2.2

2014-01-28 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 01/28/2014 02:04 PM, David Bosschaert wrote:

+1

David

On 28 January 2014 08:52, Carsten Ziegeler cziege...@apache.org wrote:

+1


2014-01-28 Carsten Ziegeler cziege...@apache.org


It's time for a new web console 4.2.2 release

We fixed 5 issues:

https://issues.apache.org/jira/browse/FELIX/fixforversion/12323897https://issues.apache.org/jira/browse/FELIX-4078

The artifacts are located in

https://repository.apache.org/content/repositories/orgapachefelix-1005/

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 1005 /tmp/felix-staging

Please vote to approve the  release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)



This vote will be open for 72 hours (at least).

Thanks
Carsten


--
Carsten Ziegeler
cziege...@apache.org





--
Carsten Ziegeler
cziege...@apache.org


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


Re: Maybe a Felix Framework release sometime soon?

2014-02-23 Thread Jean-Baptiste Onofré

Hi David,

I'm analysing a potential issue about a bundle cache corruption.
I should be able to get back to you very soon (with a Jira and a patch).

Regards
JB

On 02/23/2014 05:14 PM, David Bosschaert wrote:

Hi all,

It's been a while since this thread was started. I see that there is a
desire to improve on the locking, but nothing has happened in that
area over the past month.
I was thinking to start putting together a release early March, since
it will be nice to have R5 core support in a release. If we can get
the locking code improved before that then great, but was thinking
that if nothing has happened there we should postpone
FELIX-3687/FELIX-4190 to a later release?

Thought anyone?
Cheers,

David

On 30 January 2014 08:53, Guillaume Nodet gno...@apache.org wrote:

I don't have any problem reverting my fix if you have a better one ;-)


2014-01-18 David Jencks david_jen...@yahoo.com


I hope that someone cleans up the mess around
https://issues.apache.org/jira/browse/FELIX-3687
and
https://issues.apache.org/jira/browse/FELIX-4190
before a release candidate.

In the first issue I proposed a patch, Richard pointed out a problem, and
I suggested a possible solution and haven't gotten any comments.

In the 2nd issue Guillaume committed a fix that is invalid and AFAIK it
has not been corrected.

thanks
david jencks

On Jan 17, 2014, at 8:40 AM, David Bosschaert david.bosscha...@gmail.com
wrote:


On 17 January 2014 16:16, Carsten Ziegeler cziege...@apache.org wrote:

+1 for a new framework release, it would be great to have full R5

support,

but if that is not supposed to happen soon


Full disclosure:
  I tried my hand on those resolver related open issues, but had the
feeling that I didn't understand the Felix code well enough for it.
The resolver is a pretty complex beast, especially since it's
recursive/re-entrant and I found that fixing one little issue would
cause tons of other things to fall over elsewhere ;) In the end I
often came up with a patchwork of fixes for one resolver CT test
failure where I had the feeling that it could be done more elegantly.

so in the end I abandoned my attempts here... I think those remaining
resolver issues are for someone who really knows the felix resolver
code inside out :)

Cheers,

David





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


Re: [VOTE] Release Felix Utils 1.6.0

2014-02-26 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 02/26/2014 12:12 PM, Guillaume Nodet wrote:

I'm calling a vote on Felix Utils.

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

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 1007 /tmp/felix-staging

Changes:
** Improvement
 * [FELIX-4433] - Provide more control over the substitution
 * [FELIX-4434] - Require JDK 5
 * [FELIX-4435] - Add a method to do substitution without any callback


Please vote to approve this release:

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

Cheers,
Guillaume



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


Re: [VOTE] Release Apache Felix Gogo Runtime 0.12.0

2014-02-26 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 02/26/2014 12:14 PM, Guillaume Nodet wrote:

I'm calling a vote on Felix Gogo Runtime.

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

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 1008 /tmp/felix-staging

Changes:
** Bug
 * [FELIX-4336] - The use of inheritable thread locals in ThreadIO can
cause problems
** Improvement
 * [FELIX-3590] - Add system property resolution to CommandSessionImpl
 * [FELIX-4363] - The CommandSession get/set methods are not thread safe

Please vote to approve this release:

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

Cheers,
Guillaume



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


Re: [VOTE] Apache Felix Inventory 1.0.4

2014-02-27 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 02/27/2014 02:05 PM, Carsten Ziegeler wrote:

I'm calling a vote on Felix Inventory 1.0.4 which fixes one regression:
https://issues.apache.org/jira/browse/FELIX-4437

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

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 1009 /tmp/felix-staging

Changes:
Please vote to approve this release:

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

Regards
Carsten



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


Re: [VOTE] Accept PojoSR code donation

2014-03-05 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 03/05/2014 03:49 PM, Guillaume Nodet wrote:

Karl Pauls is willing to donate PojoSR (https://code.google.com/p/pojosr/)
to Felix.

This vote is about officially accepting the donation.

[ ] +1  Accept PojoSR code into Felix
[ ] -1 Do not

Cheers,
Guillaume Nodet



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


Re: [VOTE] framework 4.4.0 and related subproject releases

2014-03-21 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 03/20/2014 11:13 PM, Karl Pauls wrote:

I would like to call a vote on the following subproject releases:

framework  4.4.0
framework.security 2.4.0
main 4.4.0
main.distribution 4.4.0


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

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 1013 /tmp/felix-staging

Please vote to approve this release:

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



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


Re: [VOTE] Release Felix DeploymentAdmin 0.9.6

2014-04-01 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 03/28/2014 11:20 AM, Jan Willem Janssen wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I would like to call a vote on the release of DeploymentAdmin v0.9.6.

We solved 6 issues in this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20deploymentadmin-0.9.6%20AND%20component%20%3D%20%22Deployment%20Admin%22%20ORDER%20BY%20priority%20DESC

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

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 1014 /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.

- --
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTNU0IAAoJEKF/mP2eHDc4nOwP/31JLXBzZobqibaapeNJFHl3
3tvuLgJQfkP5UlcpZaMLXZHyKg54kTSXdJVX4/pQmrvhO/buGIhwqi3wJYRBdveD
+jT4h8+qYMNB4doydMmSYwEj9cSo2nhmCp2rmMZ/lDxZwkZDHhnGaNRCeo1VytfV
kE83LcMMbMD7EL16HCRTe/NoDwc5+YgY+2aVXIk8miNHCZkNir8JTmdpzV2GDpVp
ELVxCI9fAOKeQcFnehTF4QoidnMvhHJ08QK5t4uoO/n2lKc+9+u65oMhLabD/Exa
kUhjbSPEHtx1F01+2KmWPR2P9AIQ/4Jc32//WxUbX/SXDMICtj1wOQZ1rUOB15pw
JRcXQ2SAFB8sVDM8YVhTv4Ro+E8e9UyjDJUDbb1G2W0m1EJbX2EQ31v7yvqeeSn4
FrR1jp87qg9c9QmSFJOkj6uhW3uX5MF0inpyvUsmdTyfLjmkWc24aGLFQNb5kqeu
zydLiy4qudq69I1CzzKLQdRMbVEuXDituRHwCS4/aOq9huWrwekwjfj6DGVAkqfw
5+SSJFWv6tlEcHA0SKHOKfxQORqX71jwSW6J+6AgnhWp3fgmladczgC2K6qao+Ac
uRsn9yhZAanoMCI9SLIcPlUCLW8NzMWplL0apzivnc/ZK3omOkulPVSb8ijIaSoV
sxcZOAs70Ci6luX+b0/U
=c5mH
-END PGP SIGNATURE-



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


Re: Handling of provisional OSGi API?

2014-05-16 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 05/16/2014 11:24 PM, Richard S. Hall wrote:

There was thought that went into that policy, it wasn't just pulled out
of the air...further, from experience of working on that specs that
didn't make the cut (original OBR and Gogo), I can say the policy does a
good job of avoiding the confusion/complication created in those cases.

So, working around the policy based on personal whim, doesn't seem like
a good idea...that sort of makes it not a policy.

However, all policies can be improved. You could argue that the policy
should simply be modified, as David suggests, to say only released
subprojects must not contain provisional API.

I'd personally be fine with that, but such a subproject would still have
to be fine with not having an official release until the specs are final.

- richard

On 5/16/14, 13:59 , David Jencks wrote:

Well, I pretty much disagree with the existing policy being good or
nice, but I think I agree with your proposal.

I think that there should be very different policy for the svn tree
and for releases.  I don't think it's a very good idea to have a
release with a provisional osgi api, whether or not it's had its
packages shaded.  However if we decide we need to do this I think
_either_ renaming the packages _or_ marking the packages provisional
should be sufficient, not both.

For the svn tree, I think it's fine to just copy the osgi draft source
into some appropriate location and build it as part of the project.
The svn tree is not for general consumption, if you use it you are
supposed to know what you are doing and you certainly aren't supposed
to rely on it for production without doing your own deternimation that
it is entirely suitable, since it comes with no assurances of anything
from apache.  We just shouldn't release anything in this state: either
the spec gets released first, or we mark the spec packages provisional
or rename them.

I have the same problem with  the felix ds/rfc 190 work, with the new
runtime and dto packages, and realistically for me the options are
either changing the policy, or keeping my work visible on github until
the spec is released.

I don't have time or interest to investigate, but it might be possible
to use the maven shade plugin to rename the packages in byte code.  I
imagine we'd have to run bnd after this step.  I don't know if the
shading can be done to integration tests as well so the instructions
to bnd don't have to be duplicated with and without the mangled
package names so we can create an unshaded bundle for unshaded
integration tests.

thanks for reminding me to think about this before I committed :-)

david jencks

On May 15, 2014, at 11:14 PM, Carsten Ziegeler cziege...@apache.org
wrote:


Hi,

right now we have a policy for handling provisional OSGi API (API
that is
currently drafted in the OSGi expert groups but not final or officially
released yet):
http://felix.apache.org/documentation/development/provisional-osgi-api-policy.html


While the policy is good and nice, it requires to rename the packages
from
an OSGi namespace to an Apache one for the reasons stated in the policy.
However, this creates a burden for people using this stuff, e.g. when
writing tests as these need to be refactored later on anyway.

The reference implementation of the new Http Service (RFC 189) will
be done
as part of Apache Felix and we would like to start working on this in
the
open. Therefore we need to commit the current version of the API draft
somewhere. I think if we do this in the whiteboard section, it should be
clear enough that the API is provisional and we don't need to rename the
packages. We can also add all kinds of disclaimers/readmes etc.
But before doing so, I would like to get the general feeling about this.

So, wdyt?

Thanks
Carsten
--
Carsten Ziegeler
cziege...@apache.org




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


Re: [VOTE] Release Felix HTTP version 2.3.0

2014-06-10 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/10/2014 02:53 PM, Jamie G. wrote:

+1 (non-binding)

On Fri, Jun 6, 2014 at 1:27 PM, Jan Willem Janssen
janwillem.jans...@luminis.eu wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

We solved 13 issues in this release, see [1] for a complete list.

There are still some outstanding issues, see [2].

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

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 1019 /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 (at least).


1.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http-2.3.0%20AND%20component%20%3D%20%22HTTP%20Service%22

2.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20%3D%20%22HTTP%20Service%22

- --
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTkeTrAAoJEKF/mP2eHDc4iGkQANaTdHwv3Kx81Aiuw94H3hLT
RtVpSCA0q8jlGzq93t6SndSBMbcuqV6dVRpbJDzcMfae/naxnN+HHivxsIeZ1WlC
4mDats1vDinJIyaMZDTTVWp+fayNsZDZs/AtjgpZkJVSic7s3nyXbZi2esge9DUJ
3xdZkq1rslVysBK9qtpzlxJQTm8gdXhW9vwH9L++CWyNOlf17dytdpKP+QTCIQ/D
cp98cwv6kXRX8pRu0d8H3Y4Yy02oOKk42tblRYaJQtNTIedJOAKg/fOBJIwq5kj5
h3tLnBY780SNejX7ZCNtuWXE6Zy7VV48ukhfV7x7HjHPaAprBBn7WMCDHO42w5dl
oc2rSQ5oVUX550gvtapKXgZLChKHjo1ZgxfbHLkJKTG+DBVvI1PqVXd5FbA8njas
TYX3DY2URpCS0+pZQTxE/FLp79P13+zCrXW4onnDfuDNmQ+lsFc1kGHWLLyiWc8k
7qvfbMueUf6GY/aX0/0Vn1gJIVVV6O6w8XMAHa+LYyRyceFJR/H/9j44WH3SQzbp
0YEtNiLJ2B+mbAGf3ARydfZiZkgSc9P4AiKSNNxbVmZ49Pc+FiJPYt5WNukM76M0
m4KD+ejxe0RUHlx9eDhNxLzLnlBrCwYle0C5d/63hJITioVuJYZQ7BldBBL96mRb
6s8zNVElG8+fxy4+d/cK
=Yl2h
-END PGP SIGNATURE-


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


Re: [VOTE] Release Apache Felix Gogo Runtime 0.12.1

2014-06-14 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/14/2014 11:09 AM, Guillaume Nodet wrote:

I'm calling a vote on Felix Gogo Runtime 0.12.1.

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

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 1020 /tmp/felix-staging

Changes:
** Bug
 * [FELIX-4533] - Gogo runtime does not advertise published services

Please vote to approve this release:

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

Cheers,
Guillaume



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


Re: [VOTE] Release Felix Gogo Command bundle version 0.14.0

2014-06-17 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/17/2014 01:45 PM, dav...@apache.org wrote:

Hi,

I'm calling a vote on Felix Gogo Command 0.14.0.

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

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 1021 /tmp/felix-staging

Changes:
* This release fixes a NullPointerException in the obr:info command.

Please vote to approve this release:

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

This vote will be open for at least 72 hours.

Thanks,

David Bosschaert



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


Re: maven-bundle-plugin respin to fix manifest writing bug

2014-06-23 Thread Jean-Baptiste Onofré
I think I didn't follow you, but if you didn't promote the release on 
Nexus, the artifacts won't be released, so the current staging 2.5.0 
won't be promoted.
So, you can drop the staging repo, remove the tag, fix your issue and 
redo the release again.


If you already promoted the staging repo, I agree with you.

Regards
JB

On 06/23/2014 02:30 PM, Stuart McCulloch wrote:

On 23 Jun 2014, at 13:28, Jean-Baptiste Onofré j...@nanthrax.net wrote:


Hi Stuart,

No problem, but I don't see why to cancel the 2.5.0 release. When we cancel, 
it's especially to remove the tag, and redo the release with the same version 
number.


Do you really want a plugin version out there that doesn’t work for the basic 
case?  This would be a really bad experience for users who didn’t know that 
2.5.0 was a bad release.


Regards
JB

On 06/23/2014 02:13 PM, Stuart McCulloch wrote:

Hi,

Mark found a bug in the staged maven-bundle-plugin 2.5.0 release, so I’ve 
cancelled the release vote and fixed it in trunk.

I’m considering staging the next release as 2.5.1 rather than re-using 2.5.0 
(and having to change the tag in svn, etc.) … any thoughts/preferences?

—
Cheers, Stuart



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




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


Re: [VOTE] Release Felix maven-bundle-plugin version 2.5.0 (second attempt)

2014-06-23 Thread Jean-Baptiste Onofré

+1 (non binding)

Just tested, it looks good to me.

Regards
JB

On 06/23/2014 04:05 PM, Stuart McCulloch wrote:

Hi,

I’ve fixed the issue reported in 
http://www.mail-archive.com/users@felix.apache.org/msg15423.html and have 
restaged the 2.5.0 release...

We solved 7 issues in this release, the major ones being the bndlib 2.3.0 
upgrade to support Java 8 bytecode and a new baselining feature:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324606styleName=HtmlprojectId=12310100

There are still several outstanding issues which people can contribute towards 
fixing :)


https://issues.apache.org/jira/issues/?jql=component+%3D+%22Maven+Bundle+Plugin%22+AND+project+%3D+FELIX+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC

Release source tag:


https://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/

Staging repository:

https://repository.apache.org/content/repositories/orgapachefelix-1024/

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 1024 /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.

—
Cheers, Stuart



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


Re: [VOTE] Release Felix maven-bundle-plugin version 2.5.0 (second attempt)

2014-06-23 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 06/23/2014 04:05 PM, Stuart McCulloch wrote:

Hi,

I’ve fixed the issue reported in 
http://www.mail-archive.com/users@felix.apache.org/msg15423.html and have 
restaged the 2.5.0 release...

We solved 7 issues in this release, the major ones being the bndlib 2.3.0 
upgrade to support Java 8 bytecode and a new baselining feature:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324606styleName=HtmlprojectId=12310100

There are still several outstanding issues which people can contribute towards 
fixing :)


https://issues.apache.org/jira/issues/?jql=component+%3D+%22Maven+Bundle+Plugin%22+AND+project+%3D+FELIX+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC

Release source tag:


https://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/

Staging repository:

https://repository.apache.org/content/repositories/orgapachefelix-1024/

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 1024 /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.

—
Cheers, Stuart



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


  1   2   3   4   5   >