Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

Hi Tom, Agree 100%, we want to always have a trunk that builds. The ways we can do this (IMO, in rough order of ease/desirability) are: 0. Always do a deploy during a release. 1. Avoid depending on snapshots except where, as you say, it is necessary. 2. Avoid doing releases of multiple bundles a

Re: [VOTE] Release Blueprint

blueprint-api Upgrade to parent 2.0.0 Change parent version to 2.0.0-SNAPSHOT Use latest versioning plugin release [ARIES-1006] Refactoring of the parent pom, upgrade to OSGi 4.3.1 and full Java7 compilation support Update to the release version of the plugin ARIES-979: Inte

Re: [VOTE] Release JMX Api 1.1.1 and Core 1.1.2

+1 (non binding) Christian Am 30.06.2014 20:14, schrieb Guillaume Nodet: 4th set ... This release contains: * JMX Api 1.1.1 * JMX Core 1.1.2 [ ] +1 Release those 2 bundles [ ] -1 Do not Cheers, Guillaume Nodet -- Christian Schneider http://www.liquid-reality.de Open Source Archi

Re: [VOTE] Release Blueprint

+1 (non binding) Christian Am 30.06.2014 20:13, schrieb Guillaume Nodet: Third set for Blueprint ... This release contains: * Blueprint API 1.0.1 * Parser 1.2.1 * Annotation API 1.0.1 * Annotation Impl 1.0.1 * CM 1.0.4 * Core 1.4.1 Staging repository at https://repository.

Re: [VOTE] Release Apache Aries Parent 2.0.0

+1 (non binding) Generally I am fine with the parent. My only concern is the use of the maven bundle plugin 2.5.0 which introduces the new osgi.ee capability requirement. This together with a karaf bug: https://issues.apache.org/jira/browse/KARAF-3069 causes all aries bundles to not install

Re: [VOTE] Release Aries Proxy Api 1.0.1 and Impl 1.0.3

+1 (non binding) Regards JB On 06/30/2014 08:11 PM, Guillaume Nodet wrote: Second release vote ... This one contains the proxy api and impl. Staging repo at https://repository.apache.org/content/repositories/orgapachearies-1003 [ ] +1 Release Aries Proxy 1.0.1 and Impl 1.0.3 [ ] -1 Do not

Re: [VOTE] Release JMX Api 1.1.1 and Core 1.1.2

+1 (non binding) Regards JB On 06/30/2014 08:14 PM, Guillaume Nodet wrote: 4th set ... This release contains: * JMX Api 1.1.1 * JMX Core 1.1.2 [ ] +1 Release those 2 bundles [ ] -1 Do not Cheers, Guillaume Nodet -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Tal

Re: [VOTE] Release Apache Aries Parent 2.0.0

+1 (non binding) Regards JB On 06/30/2014 08:10 PM, Guillaume Nodet wrote: This is the first release of a set. It contains the parent pom in version 2.0.0 Staging repository available at https://repository.apache.org/content/repositories/orgapachearies-1002 [ ] +1 Release parent 2.0.0 [ ]

Re: [VOTE] Release Blueprint

+1 (non binding) Regards JB On 06/30/2014 08:13 PM, Guillaume Nodet wrote: Third set for Blueprint ... This release contains: * Blueprint API 1.0.1 * Parser 1.2.1 * Annotation API 1.0.1 * Annotation Impl 1.0.1 * CM 1.0.4 * Core 1.4.1 Staging repository at https://repositor

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

Hi Holly, I appreciate your point, and agree that we should strive to build against the lowest possible version of our dependency artifacts. Otherwise I think we may end up with import ranges that exclude valid previous versions. But lets make the assumption that we will from time to time relea

[jira] [Created] (ARIES-1222) Should make osgi.ee and osgi.native capabilities available to all subsystems

Thomas Watson created ARIES-1222: Summary: Should make osgi.ee and osgi.native capabilities available to all subsystems Key: ARIES-1222 URL: https://issues.apache.org/jira/browse/ARIES-1222 Project: A

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

This is perhaps where my point about over-use of the snapshot dependencies and the versioning applies. For example, does blueprint core now need parser-1.2.1 rather than parser-1.2.0 to function correctly? > On 1 Jul 2014, at 15:13, Thomas Watson wrote: > > But that is not enough because ther

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

I haven't tried, but if you use the -Pdev option for maven (enabling the dev profile) when building , it should use the snapshot version of the dependencies. 2014-07-01 16:13 GMT+02:00 Thomas Watson : > But that is not enough because there are other dependencies on artifacts > that are not publ

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

But that is not enough because there are other dependencies on artifacts that are not publically available yet. For example, I still get this error building blueprint out of trunk: [ERROR] Failed to execute goal on project org.apache.aries.blueprint.core: Could not resolve dependencies for projec

Re: [VOTE] Release Blueprint

Hi Guillaume, As with the Proxy batch, I think this email (and the other vote) should also include what has been changed. I understand that this might be hard to figure out. If so then we should do something about that... David On 30 June 2014 19:13, Guillaume Nodet wrote: > Third set for Blue

Build failed in Jenkins: Aries #2002

See Changes: [gnodet] Use a snapshot for parent pom to keep the build working -- [...truncated 9106 lines...] Received 0 blocks and 11343 bytes Compression is 0.0% Took 0.22 sec [JENKINS] Archiving

Build failed in Jenkins: Aries » Apache Aries Blueprint Core #2002

See Changes: [gnodet] Use a snapshot for parent pom to keep the build working -- [INFO]

Build failed in Jenkins: AriesWithSnapshotDependencies #519

See Changes: [gnodet] Use a snapshot for parent pom to keep the build working -- [...truncated 7706 lines...] Downloading: http://download.eclipse.org/rt/eclipselink/maven.repo/org/

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

Again, deployment of a snapshot is not the issue here. The problem 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 : >

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

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 O

Re: [VOTE] Release Aries Proxy Api 1.0.1 and Impl 1.0.3

Thanks for providing the extra info, Guillaume. +1 Release Aries Proxy 1.0.1 and Impl 1.0.3 David On 1 July 2014 08:44, Guillaume Nodet wrote: > Jira is not really helpful for that. > Here's a list extract from the svn log > > API > === > Change parent version to 2.0.0-SNAPSHOT > More u

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

Deploying a snapshot would not help in that case, because the modification i've had to make for the release is about upgrading from snapshots to releases which are not available yet. I've fixed the build by uploading a 2.0.1-SNAPSHOT of parent and switching the being-released modules to it. 2014-

Re: [VOTE] Release Apache Aries Parent 2.0.0

On Jul 1, 2014, at 2:47 AM, Holly Cummins wrote: > > (In this particular case the build failures are caused not because of > interdependent bundles, but because nothing can find the 2.0.0-SNAPSHOT > parent pom - I'd expect that to be available in the snapshots repository. > Did we forget a dep

Re: [VOTE] Release Aries Proxy Api 1.0.1 and Impl 1.0.3

Jira is not really helpful for that. Here's a list extract from the svn log API === Change parent version to 2.0.0-SNAPSHOT More updates to latest version plugin [ARIES-1006] Upgrade to the "new" parent pom in proxy modules [aries-1006] Point poms back to version 1.0.0 of java5-par

Re: Top down build of trunk failing during release process (was: Re: [VOTE] Release Apache Aries Parent 2.0.0)

Yep - the Felix release process outlines this deployment of a snapshot just before doing the actual release. I think it would make sense for Aries to follow that too: http://felix.apache.org/documentation/development/release-management-nexus.html David On 30 June 2014 22:27, Daniel Kulp wrote: >

Re: [VOTE] Release Aries Proxy Api 1.0.1 and Impl 1.0.3

Hi Guillaume, I'm kinda missing in this vote (and in the others in the set) what has been changed since the last release. Also, I was wondering whether we should be using the odd-even release number scheme that is in use in the Felix project. That ensures that version ordering between snapshots a