Hi Carsten,
On 13 July 2015 at 15:50, Carsten Ziegeler cziege...@apache.org wrote:
However you are right that no Apache release should contain
provisional OSGi API. Currently the Enterprise R6 release is available
as Proposed Final Draft [1]. It is highly unlikely that the
specification will
Hi David, it seems the async release that was cancelled has ended up
in the aries/tags dir. Is this by mistake? I don't think it's an issue
for now, but when you do the 1.0.0 release I think you'll need to
remove that tag. I guess the 'cancelling a release' didn't undo the
tag.
On 7 July 2015 at
Hi Jeremy,
This is what mvn release:prepare does. It creates a tag in SVN. If the
release doesn't succeed for some reason later on the tag stays left
behind.
When I'll re-spin the release I'll use 1.0.1. There are no 1.0.0
artifacts available in maven. I personally don't see the need to
remove
Well that's a Felix policy and not an Aries one ;)
However you are right that no Apache release should contain
provisional OSGi API. Currently the Enterprise R6 release is available
as Proposed Final Draft [1]. It is highly unlikely that the
specification will change while it's being voted on by
I don't plan to spoil the fun, but shouldn't we wait with a release
until there is a released final API of the OSGi stuff?
In the Felix project we do this (see
http://felix.apache.org/documentation/development/provisional-osgi-api-policy.html)
Carsten
Am 13.07.15 um 16:08 schrieb David
Am 13.07.15 um 16:43 schrieb David Bosschaert:
Well that's a Felix policy and not an Aries one ;)
Absolutely
However you are right that no Apache release should contain
provisional OSGi API. Currently the Enterprise R6 release is available
as Proposed Final Draft [1]. It is highly unlikely
Am 13.07.15 um 16:57 schrieb David Bosschaert:
Hi Carsten,
On 13 July 2015 at 15:50, Carsten Ziegeler cziege...@apache.org wrote:
However you are right that no Apache release should contain
provisional OSGi API. Currently the Enterprise R6 release is available
as Proposed Final Draft [1].
Hi David,
I think I’m right in saying that the Apache release process needs the source
headers for approval. :(
https://www.apache.org/dev/release.html#full-copy-for-each-source-file
Regards,
Tim
On 6 Jul 2015, at 08:27, David Bosschaert david.bosscha...@gmail.com wrote:
Hi Tim,
I
Ok - then let's cancel the vote.
I should be able to restart it some time next week.
On 7 July 2015 at 09:42, Timothy Ward timothyjw...@apache.org wrote:
Hi David,
I think I’m right in saying that the Apache release process needs the source
headers for approval. :(
Hi Tim,
I think that's pretty much always how it happens for something that is
in the process of being released. You can add the staging repository
to your maven repos and then you should be able to rebuild from
sources. Does someone have a better way of doing this?
If people think I should
+1
Sergey
On 03/07/15 12:55, dav...@apache.org wrote:
Here's my +1
David
On 3 July 2015 at 11:36, dav...@apache.org wrote:
Hi all,
I'm calling a vote on the first release of the Aries Asynchronous OSGi
Services implementation. This implements the OSGi Asynchronous
Services specification
Hi,
So the good news is that the release versions all pass the relevant compliance
tests for their respective specifications, but I have noted two issues…
I’m unable to build from source unless I re-version all of the bundles to
1.0.0-SNAPSHOT and do a mvn clean install first. If I fail to do
Hi all,
I'm calling a vote on the first release of the Aries Asynchronous OSGi
Services implementation. This implements the OSGi Asynchronous
Services specification (chapter 138) and the OSGi Promises
specification (chapter 705) of the upcoming OSGi Enterprise R6
specifications, which are
Here's my +1
David
On 3 July 2015 at 11:36, dav...@apache.org wrote:
Hi all,
I'm calling a vote on the first release of the Aries Asynchronous OSGi
Services implementation. This implements the OSGi Asynchronous
Services specification (chapter 138) and the OSGi Promises
specification
14 matches
Mail list logo
