> I also think if the root problem is test framework doesn't properly handle
> using the most recent code from peer projects then that is the thing that
> is broken...
Addressing this problem is what the 'build with most recent versions' build did
- it would ratchet the versions of all internal
The snapshot build should be giving us coverage of testing with all the latest
snapshots. For the product, there's a clear requirement to have the main build
build with the minimum level of dependencies, but for testing it's a bit less
clear. Testing with minimum levels gives better coverage,
If we do an incremental release (that is, release a limited number of modules
at a time, and do multiple releases in dependency order), and deploy the new
snapshots to the snapshots repo, trunk should continue to build during a
release.
Doing an incremental release is not always convenient,
Our release instructions also include the deployment step:
http://aries.apache.org/development/releasingaries.html
In the discussion of the release strategy (incremental vs trunk-breaking)
they don't include the detail about preferring to depend on releases, which
might be worth adding.
Holly
is that artifacts being released use the parent 2.0.0 which is
not publicly available yet.
Anyway, I've moved those bundles to use parent 2.0.1-SNAPSHOT so everything
should be sorted.
2014-07-01 10:45 GMT+02:00 Holly Cummins holly.k.cumm...@googlemail.com:
Our release instructions also
the staging repos.
Tom
Holly Cummins ---07/01/2014 01:16:07 PM---This is perhaps where my point
about over-use of the snapshot dependencies and the versioning applie
From: Holly Cummins holly.k.cumm...@googlemail.com
To: dev@aries.apache.org dev@aries.apache.org
Date: 07/01/2014 01:16
The snapshot build is intended to test whether the latest versions of all
of our modules work with one another. This makes it pretty important. :)
The reason we can't test this in our normal build is that the normal build
tests modules against the *minimum* level of their dependencies. (This is
On 16 Dec 2013, at 22:01, Daniel Kulp dk...@apache.org wrote:
On Dec 13, 2013, at 7:48 PM, Holly Cummins holly.k.cumm...@googlemail.com
[...]
It should be that the main build tests the released versions, so über-1.0
and its back-level constituents. Then the snapshot build tests
Another thing that concerns me about this is that it's exactly the sort of
problem which the 'withlatestanapshot' build is supposed to catch. It clearly
hasn't caught it, so either it's not working as I hoped, or something about the
uber bundle makes things pass even if we're running all the
I'm afraid I still don't understand the requirement to release everything,
even after your detailed explanation, Tim. (Sorry!)
Our maven build very deliberately always depends on 'minimum required'
released versions, unless there's a functional requirement for a snapshot
dependency. So if we want
+1 to modifying the policy. I think we need to use the minimal version
increment until proven otherwise. Otherwise we risk breaking implementors
of interfaces in the snapshot build every time we do a release.
The 1.2.0-SNAPSHOT is defaulted by the release plugin, but it's easy enough
to override
Hi all,
As you may have noticed, I've failed to fix the snapshot build. Even though it
doesn't produce releasable artifacts, I think this build is important to
validate the interoperability of our codebase, and I'd like to get it fixed.
The problem is a cyclic dependency between the semantic
Alternatively, it may not be fixed at all yet, even with fix 2 (see other
thread). :)
On 1 Feb 2013, at 18:47, Apache Jenkins Server jenk...@builds.apache.org
wrote:
See https://builds.apache.org/job/AriesWithSnapshotDependencies/348/changes
Changes:
[dkulp] [ARIES-1013] Fix import
On Fri, Feb 1, 2013 at 8:08 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
My only concern is that we're rapidly going to have a scaling problem,
with the number of bundles we have. a while ago, I wondered about using
just a numeric version in the version list. in combination
I've tried a few things to fix the issue without luck so far, including
changing all the parts of the build which don't require maven 2 to maven 3.
I'll have another look tomorrow and see if I can figure out a solution.
On 3 Jan 2013, at 12:47, John W Ross jwr...@us.ibm.com wrote:
Note
+1
On 17 Dec 2012, at 12:32, Jeremy Hughes hugh...@apache.org wrote:
Since we're now using the versioning plugin during the build I feel we
should add it to the pom.xml dependencies. Any objections?
Cheers,
Jeremy
I've changed the main build step of the snapshots build to use Maven 3, and
kicked off a test build, so we shall see if we can get away with a partial
migration to maven 3. (The pre-build steps are still using an occult mix of
Maven 2.2.1 and Maven 3.)
On Fri, Dec 7, 2012 at 12:50 PM, John W Ross
The behaviour of the versions plugin is different in mavens 2 and 3,
so the main build part of the snapshots build can be run in maven 3,
but not the updating of some of the dependencies (either properties or
plugins, but I'd have to check to confirm). If we update the snapshots
build to
Hi all,
As promised, I've started work on our next batch of releases. This one
should be way easier than the last batch I did, because it's way smaller.
However, one thing which is harder is that last time I knew what the
package and bundle versions were (1.0.0 across the board). This time I have
Hi all,
I'm about to start the work to do another batch of releases. My intention
is to release the proxy, util, api-fly, and jmx projects. I think we've
already achieved general consensus that these projects should be released,
but now would be a good time to speak up if you disagree, and don't
On Thu, Nov 22, 2012 at 11:23 AM, David Bosschaert
david.bosscha...@gmail.com wrote:
..., api-fly,
I think you mean spi-fly.
Yes, I do! Auto-correct has a lot to answer for. :)
Holly
Shall we get cracking on the 1.0.1 proxy and util releases, so that we
make sure they're ready when we do want to a subsystems release?
On Mon, Oct 22, 2012 at 2:27 PM, John W Ross jwr...@us.ibm.com wrote:
The OSGi Enterprise RI/CT release is scheduled for early November. Aries
will be the
Hi all,
One last piece of release work I haven't done yet is the JIRA cleanup.
One reason for this is that I don't think I have the JIRA authority to
create new versions. A more fundamental blocker is that I'm not sure
our current JIRA strategy for releases is going to scale. At the
moment we
[
https://issues.apache.org/jira/browse/ARIES-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-640.
-
Resolution: Duplicate
Fix Version/s: 1.0
This has almost certainly been fixed by moving
Holly Cummins created ARIES-926:
---
Summary: Application install doesn't notice applications already
in load directory when framework starts
Key: ARIES-926
URL: https://issues.apache.org/jira/browse/ARIES-926
Hi Jeremy,
I was also asked to remove those files. :) It looks like the .asc.md5
and .asc.sha1 files are produced by an interaction between the GPG
plugin and the maven release plugin. I found a few Apache projects
whose release instructions said the files should be deleted, so I went
ahead and
actually
got released! The updated list of bundles is included below.
On Wed, Sep 5, 2012 at 10:14 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
I've staged a release candidate for the itests and the samples. I
think this is the last of the epic 1.0.0 Aries release process,
except
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 included below.
On Wed, Sep 5, 2012 at 10:14 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
I've staged
I did notice a similar OOM on the weekend, before spi-fly went in. I
increased the maven heap but I guess that wasn't the underlying issue.
Holly
On 6 Sep 2012, at 14:37, John W Ross jwr...@us.ibm.com wrote:
I see that the subsystem itests have gone nuts starting with build
1674.
The
I was wondering that too. :) I've just had a look and I think
whichever build it was has rolled off the bottom of the list, since
we've had a lot of builds lately. If it happens again and we're quick
about mailing bui...@apache.org they may be able to rescue the heap
dump off the machine.
Holly Cummins created ARIES-919:
---
Summary: Blueprint HelloWorld sample broken
Key: ARIES-919
URL: https://issues.apache.org/jira/browse/ARIES-919
Project: Aries
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ARIES-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-919.
-
Resolution: Fixed
Blueprint HelloWorld sample broken
I've just been investigating the recent failures in the snapshot
build. It turns out they're caused by the fact that the build was
moving the org.apache.openwebbeans dependency from version 1.1.1 to
1.1.5. The build isn't supposed to change the version of non-Aries
dependencies, so I've fixed the
I've staged a release candidate for the itests and the samples. I
think this is the last of the epic 1.0.0 Aries release process, except
for one ejb test bundle which escaped. :)
WHAT'S BEEN RELEASED?
The modules are staged and tagged as follows:
samples:
I think the reason we get the multiple messages about stable and
unstable is that different tests are failing. So the *sub-build* for a
particular test went stable, while a different sub-build started
failing. I'm not sure if that level of detail in the emails is helpful
or not - what do people
When I was looking at the builds, I noticed that the subsystem itests
depend on proxy-1.0.1-SNAPSHOT, rather than proxy-1.0.0. Is there
something in the 1.0.1 proxy which the subsystem tests need, John? If
not it would be better to depend on the released version of the proxy
bundle, 1.0.0. This
-scopetest/scope
subsystem-scope-itests/pom.xml:version0.3/version
On Sat, Sep 1, 2012 at 10:45 AM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
When I was looking at the builds, I noticed that the subsystem itests
depend on proxy-1.0.1-SNAPSHOT, rather than proxy-1.0.0
[
https://issues.apache.org/jira/browse/ARIES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444976#comment-13444976
]
Holly Cummins commented on ARIES-911:
-
Sorry, this is my fault! The version should
[
https://issues.apache.org/jira/browse/ARIES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins reassigned ARIES-911:
---
Assignee: Holly Cummins
application-modeller-common-test pom should depend
[
https://issues.apache.org/jira/browse/ARIES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-911.
-
Resolution: Fixed
I've switched the dependencies so they depend on the recently released
Guillaume,
It looks like the latest changes for ARIES-899 have caused several
test failures. They don't show up in trunk, where we test with
released versions, but if you look at the
AriesWithSnapshotDependencies build you can see several tests which
exercise the interaction of other
blueprint comp namespace works test, and one of the blog tests.
On 29 Aug 2012, at 07:15, Guillaume Nodet gno...@gmail.com wrote:
Do you have a pointer to the AriesWithSnapshotDependencies test ?
On Wednesday, August 29, 2012, Holly Cummins wrote:
Guillaume,
It looks like the latest changes
the approved bundles to maven repositories, the Apache
download site, and the Aries download web pages.
Cheers,
Holly
On Tue, Aug 21, 2012 at 9:57 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
I've staged a release candidate for some last few stragglers - a few
application bundles which
, Stuart
On 15 August 2012 11:33, Holly Cummins holly.k.cumm...@googlemail.com
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
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:
application-modeller-standalone
Holly Cummins created ARIES-905:
---
Summary: Test failures (with current snapshots):
Key: ARIES-905
URL: https://issues.apache.org/jira/browse/ARIES-905
Project: Aries
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ARIES-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins updated ARIES-905:
Description:
See https://builds.apache.org/job/AriesWithSnapshotDependencies/196. Now
[
https://issues.apache.org/jira/browse/ARIES-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins reassigned ARIES-905:
---
Assignee: Holly Cummins
Test failures (with current snapshots
[
https://issues.apache.org/jira/browse/ARIES-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-905.
-
Resolution: Fixed
I've fixed this by adding Thread.sleep() calls in the test. It's not elegant
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?
The modules are staged and tagged as follows:
fix it (or fix it even) that would be nice.
On Tuesday, August 14, 2012, Holly Cummins (JIRA) wrote:
[
https://issues.apache.org/jira/browse/ARIES-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434166#comment-13434166]
Holly Cummins commented
[
https://issues.apache.org/jira/browse/ARIES-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins reopened ARIES-899:
-
I've had to back out the original fix, since it didn't compile and broke the
build, so re-opening
Hi Guillaume,
The Hudson builds have been red since this change was committed - see
https://builds.apache.org/job/Aries/ and
https://builds.apache.org/job/Aries/1628/, the first build with the
change. John and I discussed the failure on the mailing list, but I
guess you missed those mails. The
[
https://issues.apache.org/jira/browse/ARIES-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434166#comment-13434166
]
Holly Cummins commented on ARIES-899:
-
See https://builds.apache.org/job/Aries/1628
Hi all,
Our builds are still poorly, now because of corrupt maven metadata in the
maven local repo. Jenkins was rebooted this evening and I wonder if
something went awry because of that. I'm not totally sure how to fix it,
but I've mailed the builds mailing list to see if they have any ideas.
Yes, the builds have been failing since last Wednesday. It seems to be
because of ARIES-896, ARIES-897, or ARIES-899, maybe a bad merge? It
would be good to get them cleared up again - are you working on a fix,
Guillaume?
Holly
On Mon, Aug 6, 2012 at 11:14 PM, John W Ross jwr...@us.ibm.com
. It
will probably take about six hours for the bundles to be mirrored from
Nexus to Maven Central.
Cheers,
Holly
On Mon, Aug 6, 2012 at 7:46 PM, David Bosschaert
david.bosscha...@gmail.com wrote:
+1
David
On 1 August 2012 12:59, Holly Cummins holly.k.cumm...@googlemail.com wrote:
I've staged
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 module is staged and tagged as follows:
proxy-bundle
Hi Mark,
It looks like something's gone funny there. I'm also seeing issues with a
clean maven repo. My subversion had got into an inconsistent state locally,
which may not be helping. ('svn up' reports no changes, deleting my pom and
then doing 'svn up' gives me a different file back ...)
I
Hi Thomas,
That's exactly the policy we're aiming for. We weren't able to do it
effectively when our versions were below 1.0.0, so what we're doing now is
moving to a 1.0.0 platform. Once we have released versions of all our 1.0.0
bundles we expect we'll almost always have the case that aries-foo
:00:28 +0200
Subject: Re: [VOTE] Apache Aries blueprint bundle, proxy bundle, and
jndi bundle releases, plus ejb, application, and transaction bundles
From: gno...@gmail.com
To: dev@aries.apache.org
+1
On Sun, Jul 29, 2012 at 10:33 PM, Holly Cummins
holly.k.cumm...@googlemail.com
Hi Graham,
The snapshot dependencies are a side-effect of moving to 1.0.0. We
shouldn't have anything like as many again until we move to 2.0.0
bundles, which might be never. :)
In principle there shouldn't be anything which depends on proxy-impl
1.0.0-SNAPSHOT anymore, now that we have a 1.0.0
I've just had a successful build in a clean workspace from a clean
checkout. I did, however, need to re-deploy the application.modeller
jar, since the deployed snapshot was incomplete. (Obviously that's a
one-off thing, since we'd normally expect deployed things not to be
corrupt!)
I also
I've staged a release candidate for the next set of bundles. This
release is the big one - it gets blueprint-bundle released, along with
proxy and jndi uber-bundles. There are only a few bits of Aries
function and the itests left to go out. This release also has the
respun transaction.blueprint
[
https://issues.apache.org/jira/browse/ARIES-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-886.
-
Resolution: Fixed
Blog assembly should use OSGi 4.3
[
https://issues.apache.org/jira/browse/ARIES-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424300#comment-13424300
]
Holly Cummins commented on ARIES-886:
-
I've now updated the blog assembly. We'll want
at a complete functional set yet (but we're really close!)
Cheers,
Holly
On Sat, Jul 28, 2012 at 6:58 AM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
Darn. :(
Thank you for checking the manifests so thoroughly. Comments inline.
On Fri, Jul 27, 2012 at 6:41 PM, Timothy Ward timothyjw
Polling for one more +1 ... any takers? :)
On Wed, Jul 25, 2012 at 11:25 PM, Holly Cummins
holly.k.cumm...@googlemail.com 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
/
org.apache.aries.application.modelling.ServiceModeller
It's in org.apache.aries.ejb.modeller-1.0.0.
The file appears to have no license-header.
kind regards,
christoph
On 26/07/12 00:25, Holly Cummins wrote:
I've staged a release candidate for the next set of application
bundle, transaction bundles, ejb
I've just checked and # can be used for comments in the
META-INF/services file, so I *could* add in a license. I'm not sure
it's worth bothering, but it also might not hurt anything, and it
would keep RAT happy. What do people think?
On Thu, Jul 26, 2012 at 3:12 PM, Holly Cummins
holly.k.cumm
Holly Cummins created ARIES-886:
---
Summary: Blog assembly should use OSGi 4.3
Key: ARIES-886
URL: https://issues.apache.org/jira/browse/ARIES-886
Project: Aries
Issue Type: Improvement
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 release almost all of blueprint except for the uber-bundle and its
compatibility bundle. I've got
Any other +1s on this? Looking for one more vote ... :)
On Sat, Jul 21, 2012 at 12:12 AM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
I've staged a release candidate for the next set of application
bundles and blueprint-core (yay!).
WHAT'S BEEN RELEASED?
The modules are staged
. I won't update links on the Aries download page yet,
since we haven't released anything which uses these bundles yet.
Cheers,
Holly
On Tue, Jul 24, 2012 at 5:20 PM, Daniel Kulp dk...@apache.org wrote:
+1
Dan
On Saturday, July 21, 2012 12:12:19 AM Holly Cummins wrote:
I've staged
seeing these?
On 21 July 2012 00:12, Holly Cummins holly.k.cumm...@googlemail.com wrote:
I've staged a release candidate for the next set of application
bundles and blueprint-core (yay!).
WHAT'S BEEN RELEASED?
The modules are staged and tagged as follows:
blueprint-core
https
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 holly.k.cumm...@googlemail.com
wrote:
I've staged a release candidate for the next set of application
bundles and blueprint-core (yay!).
WHAT'S BEEN
On Mon, Jul 23, 2012 at 11:16 AM, Christian Schneider
ch...@die-schneider.net wrote:
Hi all,
first many thanks to Holly for organizing the Aries release. This is
really a lot of work and she is doinga great job making it possible. Btw. I
hope aries can switch to a simpler release concept
thing? Still something that needs to be fixed, of
course ...
Holly
On Mon, Jul 23, 2012 at 12:53 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
On Mon, Jul 23, 2012 at 11:16 AM, Christian Schneider
ch...@die-schneider.net wrote:
Hi all,
first many thanks to Holly for organizing
[
https://issues.apache.org/jira/browse/ARIES-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins reassigned ARIES-584:
---
Assignee: Holly Cummins
Blueprint Managed Service Factory Instantiates Duplicate Service
wrote:
+1
On Fri, Jul 20, 2012 at 11:28 AM, Mark Nuttall mnutt...@apache.org wrote:
+1
Again, everything checks out as per the script.
-- Mark
On 18 July 2012 12:20, Holly Cummins holly.k.cumm...@googlemail.com
wrote:
I've staged a release candidate for the next set of jmx bundles
[
https://issues.apache.org/jira/browse/ARIES-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419842#comment-13419842
]
Holly Cummins commented on ARIES-584:
-
Fixed in the nick of time, before
[
https://issues.apache.org/jira/browse/ARIES-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-584.
-
Resolution: Fixed
Fix Version/s: 1.0
Blueprint Managed Service Factory Instantiates
On Fri, Jul 20, 2012 at 7:28 AM, Graham Charters gchart...@gmail.com wrote:
[snip]
Error transferring file: RSA pr
emaster secret error
[INFO] Repository 'apache.snapshots' will be blacklisted
Gosh, that bit about blacklisting apache.snapshots doesn't bode well
for your subsequent builds
: david.bosscha...@gmail.com
Date: Thu, 19 Jul 2012 11:12:05 +0100
Subject: Re: [VOTE] Apache Aries eba-maven-plugin and blueprint-parser
release candidate
To: dev@aries.apache.org
+1
David
On 19 July 2012 10:42, Holly Cummins holly.k.cumm...@googlemail.com
wrote:
Any other votes
Resending with the correct subject. :)
On Fri, Jul 20, 2012 at 9:22 AM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
Thanks everyone for your votes on these bundles. The
vote has been running for about five days, and has enough support.
Here are the results:
[+1] 4 There are 4 binding
It looks to me like jmx-core has the same issue, unfortunately, and
it's already been released. However, I agree we should fix this where
we can, so I'll remove jmx-bundle from the release, roll all the tags
back, and fix up its pom. I don't think that will push back the date
when we have the
On Wed, Jul 18, 2012 at 12:20 PM, Holly Cummins
holly.k.cumm...@googlemail.com 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
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 follows:
jpa-container
I've added version ranges to the JMX package imports. The version of
the org.osgi.jmx.framework package, which we implement, changed from
1.5 to 1.7 between r4.2 and r5 of the enterprise spec. This means
version 1.0.0 of our jmx-bundle won't resolve against r5 enterprise
APIs. Is this what you
And, finally, Nexus has synced with Maven Central. Builds should go
through fine again now.
On Fri, Jul 20, 2012 at 12:15 PM, Holly Cummins
holly.k.cumm...@googlemail.com wrote:
Hi Mark,
The good news is that I've done the update!
The bad news is that the main build, which was passing, is now
-maven-plugin version 1.0.0-SNAPSHOT lurking in the poms, and that these
are causing the failure. Since we never built eba-maven-plugin at
1.0.0-SNAPSHOT, we don't have a copy of that in our local repository :(
-- Mark
On 20 July 2012 14:49, Holly Cummins holly.k.cumm...@googlemail.com wrote
I'm *sure* maven central has been updated. :)
Cheers,
Holly
On Fri, Jul 20, 2012 at 11:20 AM, Mark Nuttall mnutt...@apache.org wrote:
+1
Verified as per the instructions below. Thank you, Holly!
Regards,
Mark
On 18 July 2012 00:17, Holly Cummins holly.k.cumm...@googlemail.com wrote
the org.osgi.jmx.framework version 1.5
should be usable with a 1.7 org.osgi.framework (it just won't provide
the new bits over JMX). I think the correct dependency for it on
org.osgi.framework would be [1.5, 2).
Best regards,
David
On 20 July 2012 13:31, Holly Cummins holly.k.cumm...@googlemail.com wrote
...@gmail.com wrote:
+1
David
On 20 July 2012 12:24, Holly Cummins holly.k.cumm...@googlemail.com 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
I've staged a release candidate for the next set of application
bundles and blueprint-core (yay!).
WHAT'S BEEN RELEASED?
The modules are staged and tagged as follows:
blueprint-core
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.core-1.0.0
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
holly.k.cumm...@googlemail.com wrote:
I've staged a release candidate
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 and tagged as follows:
jmx-blueprint-core:
Thanks everyone for your votes on these bundles. The
vote has been running for about four days, and has enough support (yay!).
Here are the results:
[+1] 7 There are 3 binding votes from PMC members (David
Bosschaert,Graham Charters, Jeremy Hughes, and Emily Jiang), and 4
non-binding votes
[
https://issues.apache.org/jira/browse/ARIES-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-874.
-
Resolution: Fixed
Fix Version/s: 1.0
Blueprint should treat value-type on a map
I've had a look at these failures and as far as I can tell my released
artifacts haven't made it from Nexus to Maven Central. I'll keep an
eye on Maven Central in the hope they're mirrored across soon.
Sent from my iPhone
On 17 Jul 2012, at 18:47, Apache Jenkins Server
1 - 100 of 221 matches
Mail list logo
