Yay! I can see 1.0 on the horizon :)
Thanks for all the hard work, Holly!
David
On 20 June 2012 23:13, Holly Cummins wrote:
> I've staged a release of the test support bundle. This release is
> required to eliminate snapshot dependencies in more functional
> bundles. I'm doing the releases incre
+1
David
On 20 June 2012 23:12, Holly Cummins wrote:
> I've staged a release candidate for the Aries 1.0.0 test support module. The
> module is staged and tagged in
> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.testsupport.unit-1.0.0/.
>
> The artifacts are in one staged repo,
>
+1
David
On 22 June 2012 17:09, Daniel Kulp wrote:
>
> This is a vote to release versions 0.3.1 and 0.4.1 of the proxy impl and
> bundle. The only real change is a fix for ARIES-861 to allow the class
> based proxies to have any chance of working with JDK6 update 33 and JDK7
> update 5.
>
> St
Hi Holly,
I'm very much in favour of doing frequent releases without too many
obstacles. While I would hope that the release quality is generally
very good, I always think that if doing them is relatively easy that
if a release turns out to be bad that we can always do another release
afterwards t
Hi Holly,
> The vote will be open for 72 hours - it should end late Tuesday evening.
>
> [ ] +1
> [ ] 0
> [ ] -1
Is this an actual vote email? Should it not have the [VOTE] prefix in
that case? Or are you running an example?
Cheers,
David
Ok - I'm blaming gmail. It had coerced your VOTE email with your
[VERIFICATION-RESULTS] email in a single thread and was showing the
wrong subject for me.
+1 on releasing these artifacts from me.
David
On 25 June 2012 09:19, David Bosschaert wrote:
> Hi Holly,
>
>> The vote wi
This is a slight tangent on the discussion here, but I'd like to share
my thoughts re versioning...
I personally think that it's not really that important what the bundle
version is and I do like the convenience of having the same version
number of all the bundles that logically belong together as
+1 from me.
David
On 27 June 2012 18:22, Holly Cummins wrote:
> Hi all,
>
> This is a re-post of a vote which googlemail has helpfully threaded in
> with other emails, completely hiding it. :(
>
> I've staged a release candidate for some 1.0.0 Aries API bundles (the
> ones with no dependencies).
Hi all,
I think that the SPI-Fly subproject [1] is getting close to ready for
inclusion in the main Aries build. It is the Reference Implementation
of the OSGi Enterprise R5 'ServiceLoader Mediator' specification [2],
but supports more SPI-style APIs than just ServiceLoader.
I was thinking that i
+1 from me, thank you Holly!
David
On 5 July 2012 22:20, Holly Cummins wrote:
> I've staged a second release candidate for the Aries 1.0.0 util and
> blueprint.api bundles. The difference between this candidate and the
> first candidate is that the javadoc for the org.apache.aries.util
> bundle
I think Holly simply published them when the vote concluded:
http://mail-archives.apache.org/mod_mbox/aries-dev/201207.mbox/%3C06E2B3A4-FA7A-4685-B3E4-17F1DD9AE636%40googlemail.com%3E
Cheers,
David
On 13 July 2012 14:35, Daniel Kulp wrote:
>
> Holly,
>
> Did something go wrong? I'm already see
r obligations). We can then see where to go from
> there. I'd be happy to help with the spec however I can. I guess my code
> will at least be a useful additional discussion base.
>
> Thanks,
> Jeremias Maerki
>
>
> On 12.06.2012 14:47:01 David Bosschaert wrote:
>> H
Although I didn't have time to verify the artifacts, I would very much like
to see these bundles released.
So +1 from me.
David
On Friday, 13 July 2012, Holly Cummins
wrote:
> I've staged a release candidate for the next round of Aries bundles.
> This set of releases is now starting to get into
+1 from me.
David
On 18 July 2012 00:17, Holly Cummins wrote:
> I've staged a release candidate for the set of Aries jars, proxy-impl,
> application-noop-resolver, and application-utils.
>
> WHAT'S BEEN RELEASED?
>
> The modules are staged and tagged as follows:
>
> proxy-impl:
> https://svn.apa
+1 (Yay!)
David
On 18 July 2012 12:20, Holly Cummins wrote:
> I've staged a release candidate for the next set of jmx bundles. This
> round gets *almost* the whole jmx component released - just the
> blueprint uber-bundle and the itests to go.
>
> WHAT'S BEEN RELEASED?
>
> The modules are staged
+1
David
On 19 July 2012 10:42, Holly Cummins wrote:
> Any other votes for this set of releases? It's currently got just one
> +1, which is probably my fault for having three vote threads going at
> the same time and causing confusion. :)
>
> On Sun, Jul 15, 2012 at 9:41 PM, Holly Cummins
> wro
On 19 July 2012 23:05, Timothy Ward wrote:
>
> Hi,
>
> All four build fine, and the poms/manifests for three of them are fine.
> Unfortunately the manifest for jmx-bundle doesn't use version ranges in most
> of its imports:
>
> Import-Package: javax.management,javax.management.openmbean,org.apac
+1
David
On 20 July 2012 12:24, Holly Cummins wrote:
> I've staged a release candidate for the next set of jpa bundles. This
> gets almost all of the jpa component released - only the blueprint
> integration and itests to go.
>
> WHAT'S BEEN RELEASED?
>
> The modules are staged and tagged as fol
Hi Holly,
Yes, JMX is a bit of interesting spec in that the packages are not
versioned on their own, but rather follow the version of the packages
that they mirror over JMX.
So for example org.osgi.jmx.framework mirrors org.osgi.framework and
org.osgi.jmx.service.cm mirrors org.osgi.service.cm an
Hi Holly,
On 20 July 2012 17:03, Holly Cummins wrote:
> Thanks David, that helps me understand what's going on. Based on your
> explanation, though, it seems to me like jmx actually needs to be
> fairly closely coupled to the framework version. Backwards
> compatibility isn't enough, since the jm
+1 on getting these released.
It would be good to fix the remaining compliance failures but that can
be done as part of a subsequent release. Now that we're releasing
modular we should be able to release as often as we like...
David
On 21 July 2012 00:12, Holly Cummins wrote:
> I've staged a re
Awesome, Holly!
+1 on releasing these.
David
On 25 July 2012 23:25, Holly Cummins wrote:
> I've staged a release candidate for the next set of application
> bundle, transaction bundles, ejb bundles, jndi-url bundle, jmx
> uber-bundles, and proxy uber-bundle. This is a big one. I've managed
> to
+1
David
On 1 August 2012 12:59, Holly Cummins wrote:
> I've staged a release candidate for the respun proxy bundle from the
> last release. The only difference from the previous candidate is that
> the org.osgi.util.tracker package import has a version range.
>
> WHAT'S BEEN RELEASED?
>
> The m
+1
David
On 15 August 2012 11:33, Holly Cummins wrote:
> I've staged a release candidate for the application uber-bundle and a few
> left-over blueprint bundles. I am hoping this release gets the last few
> bits out the door which enable the release of Karaf 3.0.0.
>
> WHAT'S BEEN RELEASED?
>
>
+1
David
On 21 August 2012 21:57, Holly Cummins wrote:
> I've staged a release candidate for some last few stragglers - a few
> application bundles which aren't part of the uber-bundle and the
> jmx-blueprint-bundle.
>
> WHAT'S BEEN RELEASED?
>
> The modules are staged and tagged as follows:
>
>
a case that
> I might explore eventually. But frankly, OSGi Connect doesn't create too
> much attraction for me since I will usually want to work in a full OSGi
> environment. And when I can't do that I'm likely happy with plain
> META-INF/services. I guess I can't c
Hi Charles,
SPI Fly is pretty much ready to go. It was not part of the main build
and I left it out while the 1.0.0 release was being done because I
didn't want to introduce changes during this process. But as Holly
says this vote is for the last bits and pieces of Aries 1.0.0, I'll
add SPI Fly to
+1 on releasing these artifacts.
Thank you Holly!
David
On 6 September 2012 08:59, Holly Cummins wrote:
> I've removed the remaining ejb itest from the release - both EJB
> itests shared the same scm data, so I'm not sure which one actually
> got released! The updated list of bundles is include
Hi all,
I've added the spi-fly module to the main Aries build just now and
would like to get a 1.0.0 release of it out.
If anyone who has experience with doing Aries releases has time to do
the release that would be great, but I would also be happy to try to
do this myself if someone can point me
FWIW I don't think the addition of the spi-fly module can have
anything to do with it as it is built/tested after subsystems, so the
build hasn't even hit that yet...
David
On 6 September 2012 14:37, John W Ross wrote:
>
> I see that the subsystem itests have gone nuts starting with build 1674.
+1
David
On 25 September 2012 16:35, Guillaume Nodet wrote:
> I've uploaded 4 bug fix bundles.
>* blueprint-core 1.0.1 :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981&version=12322492
>* jmx-core 1.0.1 :
> https://issues.apache.org/jira/secure/ReleaseNote.js
+1
David
On 25 September 2012 16:46, Guillaume Nodet wrote:
> I've staged two new modules for release.
> The first one, transaction-jms is a JMS connection factory with
> auto-enlistment and recovery for use with the Aries transaction-manager.
> The second one, transaction-jdbc, is the previous
gt;> > virtualizable, yet, but that's a different story). Use case 4.2 (WARs)
>> > in the RFP draft makes a lot of sense, though. There you don't usually
>> > have any service dynamics. Or a command-line application that uses some
>> > code that usually runs in
egards,
David
On 1 October 2012 14:24, David Bosschaert wrote:
> Thanks for reminding me, Jeremias. I downloaded it but then I got
> distracted. Hope to have a look soon.
>
> David
>
> On 1 October 2012 03:27, Jeremias Maerki wrote:
>> Hi David,
>> did you have any
Hi Jeremias,
On 5 October 2012 14:58, Jeremias Maerki wrote:
>> Next question is would it make sense to add this functionality to Aries?
>> I think it does. To me many of the ideas in here match with the OSGi
>> Connect RFP 145 (http://www.osgi.org/bugzilla/show_bug.cgi?id=145) and
>> I think tha
ifly.discovery
> - org.apache.aries.discovery
> - org.apache.aries.plugin.discovery
> - org.apache.aries.spi.catch ;-)
> - other ideas?
>
> Cheers,
> Jeremias Maerki
>
>
> On 08.10.2012 10:02:32 David Bosschaert wrote:
>> Hi Jeremias,
>>
>> On 5 October
s a cheeky touch and still retains the
> relationship with SPI Fly.
>
> WDYT? Better ideas?
>
> Cheers,
> Jeremias Maerki
>
>
> On 08.10.2012 11:03:30 David Bosschaert wrote:
>> Sounds good to me.
>>
>> Just one note, I think it should not necessarily be
How about mentioning the fact that Jeremias Maerki is proposing a new
contribution to the Aries code base:
http://issues.apache.org/jira/browse/ARIES-938
and http://markmail.org/thread/qsfxgj2mkw5zybiu
Cheers,
David
On 10 October 2012 10:21, Jeremy Hughes wrote:
> Does anyone have anything they
Just curious - is anyone using this through the Github mirrors? I see
that most of the apache projects (including Aries) are mirrored on
github. It would be nice to use that infrastructure for doing commits
(pushes to the trunk), but I guess there's the issue of github vs
apache account IDs. Is the
>> >
>> > David
>> >
>> > On 8 October 2012 10:34, Jeremias Maerki wrote:
>> > > Agreed. So, let's narrow down the name suggestions to two:
>> > >
>> > > - org.apache.aries.discovery
>> > > - org.apache.aries.spica
SPI Fly (which is the RI of the ServiceLoader Mediator spec) is now
also ready to be released. Would it be possible to make it part of
this upcoming batch?
Thanks,
David
On 23 October 2012 12:02, Holly Cummins wrote:
> Shall we get cracking on the 1.0.1 proxy and util releases, so that we
> mak
t; if this is preferred. After all, I've guided a larger contribution
> through back in 2006 already.
>
>
> Jeremias Maerki
>
>
> On 22.10.2012 17:26:12 Jeremy Hughes wrote:
>> On 22 October 2012 11:01, David Bosschaert
>> wrote:
>> > I'm not
Hi Emily,
I wrote those tests and looked at them again, but to me it seems that
the order cannot actually be significant. The testclient that produces
this string is as follows:
ServiceLoader loader = ServiceLoader.load(MySPI.class);
for (MySPI mySPI : loader) {
sb.append(mySPI.someMethod(
Hi Emily,
I fixed this issue with the tests in r1404891. Would you like to try it again?
Best,
David
On 2 November 2012 08:09, David Bosschaert wrote:
> Hi Emily,
>
> I wrote those tests and looked at them again, but to me it seems that
> the order cannot actually be sign
As nobody has voiced any concerns I'm going to do this soon.
BTW thanks Felix for the +1.
Best regards,
David
On 12 November 2012 15:08, Felix Meschberger wrote:
> +1 (non binding).
>
> Thanks and Regards
> Felix
>
> Am 12.11.2012 um 13:05 schrieb David Bosschaert:
&g
I have done this now. The contents of sandbox/jmx-next has been moved back
into jmx (with SVN history).
See: http://svn.apache.org/viewvc?view=revision&revision=1409307
I hope I didn't mess up things :)
Cheers,
David
On 14 November 2012 18:55, David Bosschaert wrote:
> As nobod
batch too.
BTW when do we think this release train will roughly go?
Cheers,
David
On 23 October 2012 20:01, Holly Cummins wrote:
> Hi David,
>
> That thought had crossed my mind too. :)
>
> On Tue, Oct 23, 2012 at 2:47 PM, David Bosschaert
> wrote:
> > SPI Fly
I'm currently looking at this...
David
On 14 November 2012 20:02, Apache Jenkins Server
wrote:
> See <
> https://builds.apache.org/job/AriesWithSnapshotDependencies/290/changes>
>
> Changes:
>
> [davidb] Move the updated JMX implementation from sandbox/jmx-next back to
> jmx.
>
> The code being
Yay! Holly that's great news!
> ..., api-fly,
I think you mean spi-fly.
Many thanks for taking this on.
Cheers,
David
On 22 November 2012 11:18, Holly Cummins wrote:
> Hi all,
>
> I'm about to start the work to do another batch of releases. My intention
> is to release the proxy, util, api-f
Hi Holly,
On 26 November 2012 15:46, Holly Cummins wrote:
> (b) Longer term, wouldn't it be great to get the tool integrated into the
> release plugin? I know we've discussed this before, so I'm mostly chipping
> in again with a "yes please, +1" :)
>
It would be great if we had a tool that could
I think it would be better to fail the build and suggest the proper version
to the user in all cases where version information is incorrect. It could
be the case that the user unintentionally made a change that would bump the
version and may want to review those changes in the code instead of bumpi
Just reading my mail again and notice that I wasn't too clear in cases
where version information is missing. In any case I would not be so much in
favour of autocorrection and think that failing the build with suggested
fixes would be better.
On 29 November 2012 16:03, David Bosschaert
ually change the version and then commit. I am trying to
> understand why you prefer to do it yourself instead of relying on the tool
> and you just review/commit it.
>
> Thanks
> Emily
>
> On Thu, Nov 29, 2012 at 4:22 PM, David Bosschaert <
> david.bosscha...@gmail.com&g
Just wondering where we are with this... When do we expect the release
train to go?
BTW - I know this is a volunteer effort (and much appreciated!), so if
something has come up that's fine. Just trying to figure out whether there
are any issues...
Cheers,
David
On 22 November 2012 15:17, Daniel
There was an email about a second release train sent a few weeks ago [1].
It should definitely include spi-fly and possibly also subsystems. However
this release has not yet been cut AFAIK.
Cheers,
David
[1]
http://mail-archives.apache.org/mod_mbox/aries-dev/201212.mbox/%3CCAMit8SoZkL-PVTwafXZWd
Hi Jeremy,
The following two items were finalized in November (not sure whether they
made the previous board report or not):
* The SPI Fly component now fully implements the ServiceLoader Mediator
Specification 1.0 from the OSGi Enterprise R5 spec (chapter 133). It is the
Reference Implementation
Excellent! Kudos to Emily and others who were involved in this!
One question, does it only work with package-info.java or does it also work
with packageinfo text files? AFAIK BND works with either...
Looking forward to seeing my builds fail ;)
Cheers,
David
On 3 January 2013 12:04, Emily Jiang
ssed your preferrence not to set it as default:).
>
> Thanks
> Emily
>
> On Wed, Jan 9, 2013 at 10:09 AM, Jeremy Hughes wrote:
>
> > I'll echo that. Thanks Emily!!
> >
> > David, I had thought it used the versions in the generated manifest. I
> > could b
+1 from me.
Cheers,
David
On 16 January 2013 18:45, Jean-Baptiste Onofré wrote:
> +1 (non binding)
>
> It looks good to me.
>
> Regards
> JB
>
>
> On 01/16/2013 07:19 PM, Daniel Kulp wrote:
>
>>
>> This is a vote to release the 0.1.0 version of the checker plugin as a
>> precursor to getting
Hi Dan,
Any chance of including SPI Fly [1]? Simple all the modules under the
spi-fly directory...
This would be the 1.0.0 release of SPI Fly which is the Reference
Implementation of the OSGi Service Loader mediator spec [2].
Thanks!
David
[1] http://aries.apache.org/modules/spi-fly.html
[2] Ch
On 22 January 2013 18:21, Daniel Kulp wrote:
>
> On Jan 22, 2013, at 1:16 PM, David Bosschaert
> wrote:
>
> > Hi Dan,
> >
> > Any chance of including SPI Fly [1]? Simple all the modules under the
> > spi-fly directory...
> > This would be the 1.0.0
I would have thought that it should be version 1.1.0-SNAPSHOT. That's what
I used when I committed the file from jmx-next.
However I see that the version has been bumped to 2.0.0-SNAPSHOT by Emily
in revision 1424200:
Revision: 1424200
Author: ejiang
Date: 19 December 2012 22:57:24
Message
Excellent, +1 from me.
David
On 23 January 2013 20:33, Daniel Kulp wrote:
>
> This is a vote to release all the new JMX 1.1.0 based bundles which
> updates the JMX stuff to the 1.1.0 spec.
>
> Tags:
> jmx-api:
> http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx.api-1.1.0/
> jmx-c
Thanks Dan, +1 from me.
David
On 23 January 2013 16:18, Daniel Kulp wrote:
>
> This is a vote for some of the updated bundles needed by some of the
> downstream projects like Karaf. This vote includes util-1.1.0,
> proxy-impl/bundle-1.0.1, blueprint-core/bundle-1.1.0, blueprint-cm-1.0.1,
> t
+1 to 1.1.1-SNAPSHOT from me too.
David
On 5 February 2013 21:46, Emily Jiang wrote:
> +1 to 1.1.1-SNAPSHOT. It is not necessary to bump up minor version for no
> reason. By the way, the semantic versioning tool is ok for greedy version
> increase:).
>
> On Tue, Feb 5, 2013 at 9:05 PM, John W
+1, Many thanks Dan!
David
On 8 February 2013 18:05, Daniel Kulp wrote:
>
> This is a vote to release the 1.0.0 versions of all the spi-fly things.
>
>
> Staging area:
> https://repository.apache.org/content/repositories/orgapachearies-220/
>
> Tags:
>
> http://svn.apache.org/repos/asf/aries/t
+1
David
On 8 February 2013 18:03, Daniel Kulp wrote:
>
> This is a vote to release 1.1.1 versions of the various parts of JMX that
> did not have a wide enough version range in their imports for a couple of
> the OSGi imports. There aren't any code changes, just pom.xml changes to
> affect
FYI I have updated the SPI Fly documentation to include links to the
release at Maven Central: http://aries.apache.org/modules/spi-fly.html
There is also another page listing the Aries releases:
http://aries.apache.org/downloads/currentrelease.html
I noticed that all the elements in that list poin
+1
More documentation is always good!
David
On 26 February 2013 14:59, Matei Dragu wrote:
> Hi there,
>
> I would be interested in contributing to the Apache Aries project -
> specifically the documentation of Aries Blueprint.
>
> Which is the easiest wat to get started with that [assuming th
Big +1 from me on getting a Subsystems release out!
David
On 1 March 2013 13:05, John W Ross wrote:
>
>
> I have recently been asked a few times about when the first Subsystems
> release will occur. I am currently, and unfortunately, in no position to
> make any commitments in terms of a defin
Hi John,
On 20 March 2013 12:22, John W Ross wrote:
>
>
> I have a few questions regarding the Aries release process (
> http://aries.apache.org/development/releasingaries.html).
>
> (1) I presume we've already had the required discussion of the release and
> its contents? Does anyone object to
Hi all,
Jenkins pretty much got my inbox to explode...
I think it just sent me about 200 emails in the last hour. Is that the
intention? I hope not ;)
Cheers,
David
+1 from me - very happy to see this being released!
David
On 28 March 2013 04:45, Guillaume Sauthier (OW2) wrote:
> I'm really happy to see a 1.0.0 release of subsystems :)
> Thanks
>
> Can we also have the subsystem-bundle (all-in-one packaging) released ?
>
> --G
>
>
> 2013/3/27 John W Ross
Would there be any way to kick off the release process for the resolver?
You say that the resolver is a 'soft' reference, I guess that means that
the Subsystem implementation uses the Resolver service. Just curious, will
it be able to function at all without the resolver?
Cheers,
David
On 28 M
Hmm, if it doesn't do anything without the Resolver service I would not
really call it an optional dependency. While the bundles might resolve
without if the functionality doesn't work I would consider it a mandatory
dependency from a logical point of view. Is this the resolver from the
Felix proje
I understand that, they are free to use any Resolver impl they wish, but
since the Felix one is the only one that's there right now, they don't have
many options, right? So while it's technically optional, from a user's
point of view the Felix one is the only option people have ;)
I've started a t
+1
David
On 2 April 2013 10:04, Guillaume Nodet wrote:
> I've uploaded a release of those two new modules at
>https://repository.apache.org/content/repositories/orgapachearies-048/
> The release also contains a blueprint-sample-war which shows how it can be
> used.
>
> For more information
Thanks John. Was actually just playing with this component. I guess this
makes it easier to get started with subsystems, but I think in real
deployments people would probably be better off using the embedded
components by themselves. Would you agree?
In any case, here's my +1 to releasing this com
The uber-bundle approach was always a way to get started quickly with OSGi
technologies that were comprised of a number of bundles, but they really
don't work well when you are combining multiple technologies in a single
OSGi framework, so people generally move off the uber-bundle once they
start d
+1
David
On 25 April 2013 20:53, John W Ross wrote:
>
>
> This is the second vote for the release of subsystem-bundle 1.0.0, an uber
> bundle containing subsystem-api 1.0.0 and subsystem-core 1.0.0. It
> encompasses the same content as in the previous vote but for the
> org.apache.aries.subsys
+1 from me too.
David
On 4 May 2013 05:29, Tang Yong wrote:
> forgot to say about vote,
>
> +1(updating maven-compiler-plugin to 3.1)
>
> Thanks
> --Tang
>
> Tang Yong wrote:
> >> 2) updating org.osgi.core to 4.3.1 because of an issue using jdk7
> > about the point, if updating org.osgi.core t
Hi all,
Following a question on the Aries User list I started a page about the JMX
component in Aries: http://aries.apache.org/modules/jmx.html
While working with the Aries CMS system I have the following questions:
* How do I make this page appear in the modules navbar on the left?
* I'd like to
FYI - BTW this now also contains the CTs for the Enterprise 5.0 specs.
Cheers,
David
-- Forwarded message --
From: Felix Meschberger
Date: 27 May 2013 14:38
Subject: [ANN] OSGi CT License for ASF
To: jcp-o...@apache.org
Hi all
You may have heard elsewhere on this list that th
integration and the Whiteboard
features of Aries JMX work. If someone has intimate knowledge of these
please fill in the TODOs :)
Cheers,
David
On 27 May 2013 11:56, David Bosschaert wrote:
> Hi all,
>
> Following a question on the Aries User list I started a page about the JMX
> compon
Hi all,
I had a quick browse through the Aries website and noticed that there are
quite a number of outdated pages. In some cases it was easy to update the
pages to more recent info (e.g. for the latest OSGi specs) but in other
cases I would propose the simply remove the outdated information. If
t; Felix
>
> Am 27.05.2013 um 15:56 schrieb David Bosschaert:
>
> > Answering my own question, I found the information I needed here:
> > http://aries.apache.org/development/maintainingthewebpages.html
> > For the screen shot, I simply added it to the images/ directory
I was trying this out on entirely different machines (e.g. my phone). I
think it must have been an intermediate proxy problem because they're
showing things fine today...
Cheers,
David
On 28 May 2013 12:54, Felix Meschberger wrote:
> Hi
>
> Am 27.05.2013 um 17:28 schrieb Da
On 28 May 2013 14:43, Daniel Kulp wrote:
>
> On May 27, 2013, at 10:18 AM, David Bosschaert
> wrote:
> > Downloads
> > * This page was last updated for the 1.0.0 release train and I wonder
> > whether we need it. All this info is available in Maven Central, can we
On 28 May 2013 14:43, Daniel Kulp wrote:
>
> On May 27, 2013, at 10:18 AM, David Bosschaert
> wrote:
> > Downloads
> > * This page was last updated for the 1.0.0 release train and I wonder
> > whether we need it. All this info is available in Maven Central, can we
available in Aries:
http://aries.apache.org/documentation/ariesprogrammingmodel.html
Anyone: feel free to make additional changes...
Cheers,
David
On 4 June 2013 13:53, Jeremy Hughes wrote:
> Hi David,
>
> I made some comments and votes largely in line with what's been
> discussed...
>
&g
hit th publish link? I ask this, because I have had problems
> > > with the 'overview' directory recently and updates not getting
> > > published properly.
> > >
> > > Cheers,
> > > Jeremy
> > >
> > > On 5 June 2013 11:10, Davi
Hi Graham,
That sounds very useful to me!
Cheers,
David
On 5 August 2013 10:15, Graham Charters wrote:
> A user has asked for the esa-maven-plugin to be released. I'm aware of a
> few people using it, and it's based on the already released
> eba-maven-plugin so I think it's ready to go. An
Hi all,
The OSGi service registry hooks provide a powerful way to influence
how clients view the OSGi service registry. To give a few examples
that you can do with the hooks:
* Hide certain services from certain clients
* Extend or otherwise alter the service registration properties the client see
+1
David
On 2 October 2013 17:36, Daniel Kulp wrote:
>
> The Karaf community needs new releases of blueprint parser/core so they can
> do their new 3.0 release.It's been about 9 months since the last releases
> anyway so we should try and get some fixes out there.
>
> Tags:
> http://svn.ap
Hi Sergey,
I think I understand what you are proposing for [1]. A programmatic
API to create Blueprint Containers. Once you have such container, can
you then also programmatically add beans etc? In other words will you
be able to do via code all the things that you would normally do in a
blueprint
Thanks Sergey,
sounds reasonable to me...
Cheers,
David
On 8 October 2013 11:01, Sergey Beryozkin wrote:
> Hi David
>
> Thanks for the feedback,
>
> On 08/10/13 09:34, David Bosschaert wrote:
>
>> Hi Sergey,
>>
>> I think I understand what you are proposi
+1 from me.
David
On 9 October 2013 19:48, Daniel Kulp wrote:
>
> This vote is to release blueprint-cm 1.0.2. The only change is to update
> the manifest to allow the import of the 1.2 version of the blueprint-core
> classes so it works with the latest core release.
>
> Tag:
> http://svn.apa
+1
David
On 22 October 2013 17:20, Daniel Kulp wrote:
> This is a vote to release some more artifacts to get some more fixes and
> enhancements available for Karaf 3.x:
>
> proxy-impl 1.0.2:
> Fixes a bunch of problems if the WovenClass passed in has a null
> BundleWiring. The resulting NPE
+1
David
On 5 November 2013 12:29, Sergey Beryozkin wrote:
> Hi All,
>
> I'd like to start a vote to get blueprint-web-osgi 1.0.1 released.
>
> This release fixes the issue at [1] to do with blueprint-web-osgi 1.0.0
> depending on blueprint-core 1.3.0 and having a related import version range
>
+1
David
On 17 December 2013 21:27, Daniel Kulp wrote:
>
> This is a vote to release blueprint-parser 1.2.0 and blueprint-core 1.4.0.
>
> There are two major things in this release:
> 1) ARIES-1141 - custom namespace extensions to allow a service reference to
> implement multiple interfaces
>
1 - 100 of 707 matches
Mail list logo
