You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Daniel Kulp <dk...@apache.org> on 2014/05/19 19:15:14 UTC
[VOTE] Versioning plugin 0.2.0
This is a vote to release 0.2.0 of the versioning plugin.
The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
Tag:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
Staging repo:
https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [VOTE] Versioning plugin 0.2.0
Posted by David Bosschaert <da...@gmail.com>.
+1
David
On 25 May 2014 12:44, Daniel Kulp <dk...@apache.org> wrote:
>
> With my own vote, I only have two votes. Can I get another PMC member to look at this?
>
> Thanks!
>
> Dan
>
> On May 19, 2014, at 1:15 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> This is a vote to release 0.2.0 of the versioning plugin.
>>
>> The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
>>
>>
>> Tag:
>> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
>>
>>
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
Posted by Daniel Kulp <dk...@apache.org>.
On Jun 4, 2014, at 10:54 AM, Thomas Watson <tj...@us.ibm.com> wrote:
> Daniel Kulp has fixed the pom to point back to the 3.8.0 version so the build seems to work for me again. Thanks!
>
I think the tests are failing, but at least we can build. One step at a time…..
Dan
>
> Tom
>
>
>
> Thomas Watson---06/04/2014 08:06:44 AM---Hi David, I don't think that is the case here. This is blueprint and the pom was
>
> From: Thomas Watson/Austin/IBM@IBMUS
> To: dev@aries.apache.org
> Date: 06/04/2014 08:06 AM
> Subject: Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
>
>
>
> Hi David,
>
> I don't think that is the case here. This is blueprint and the pom was updated to simply refer to a new version of equinox. I suspect it built locally because the developers local m2 cache likely has the version configured manually. But shouldn't the aries build be setup to work without manual configuration of the local m2 cache? Is there not an aries maven repo we can use to place the dependencies we need such as equinox?
>
> Tom
>
>
>
> David Bosschaert ---06/04/2014 01:49:04 AM---It might be downloading it from somewhere (using something like a http get task) and then using a sy
>
> From: David Bosschaert <da...@gmail.com>
> To: "dev@aries.apache.org" <de...@aries.apache.org>
> Date: 06/04/2014 01:49 AM
> Subject: Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
>
>
>
> It might be downloading it from somewhere (using something like a http
> get task) and then using a system dependency to use it in Maven. Not
> sure this is the way its used in this particular place, but I think
> the subsystems subproject had certain Eclipse dependencies set up this
> way.
>
> John Ross might be able to give more details...
>
> Cheers,
>
> David
>
> On 3 June 2014 20:37, Thomas Watson <tj...@us.ibm.com> wrote:
> >
> > With the latest from trunk I am no longer able to build because of a
> > reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944
> >
> > Which repo is this supposed to exist? Here is the error.
> >
> > Failed to execute goal on project org.apache.aries.blueprint.itests: Could
> > not resolve dependencies for project
> > org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT:
> > Could not find artifact
> > org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink Repo
> > (http://download.eclipse.org/rt/eclipselink/maven.repo/)
> >
> > Tom
>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
Posted by Thomas Watson <tj...@us.ibm.com>.
Daniel Kulp has fixed the pom to point back to the 3.8.0 version so the
build seems to work for me again. Thanks!
Tom
From: Thomas Watson/Austin/IBM@IBMUS
To: dev@aries.apache.org
Date: 06/04/2014 08:06 AM
Subject: Re: Current build and org.eclipse.osgi version
3.8.2.v20130124-134944
Hi David,
I don't think that is the case here. This is blueprint and the pom was
updated to simply refer to a new version of equinox. I suspect it built
locally because the developers local m2 cache likely has the version
configured manually. But shouldn't the aries build be setup to work
without manual configuration of the local m2 cache? Is there not an aries
maven repo we can use to place the dependencies we need such as equinox?
Tom
David Bosschaert ---06/04/2014 01:49:04 AM---It might be downloading it
from somewhere (using something like a http get task) and then using a sy
From: David Bosschaert <da...@gmail.com>
To: "dev@aries.apache.org" <de...@aries.apache.org>
Date: 06/04/2014 01:49 AM
Subject: Re: Current build and org.eclipse.osgi version
3.8.2.v20130124-134944
It might be downloading it from somewhere (using something like a http
get task) and then using a system dependency to use it in Maven. Not
sure this is the way its used in this particular place, but I think
the subsystems subproject had certain Eclipse dependencies set up this
way.
John Ross might be able to give more details...
Cheers,
David
On 3 June 2014 20:37, Thomas Watson <tj...@us.ibm.com> wrote:
>
> With the latest from trunk I am no longer able to build because of a
> reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944
>
> Which repo is this supposed to exist? Here is the error.
>
> Failed to execute goal on project org.apache.aries.blueprint.itests:
Could
> not resolve dependencies for project
>
org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT:
> Could not find artifact
> org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink
Repo
> (http://download.eclipse.org/rt/eclipselink/maven.repo/)
>
> Tom
Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
Posted by Thomas Watson <tj...@us.ibm.com>.
Hi David,
I don't think that is the case here. This is blueprint and the pom was
updated to simply refer to a new version of equinox. I suspect it built
locally because the developers local m2 cache likely has the version
configured manually. But shouldn't the aries build be setup to work
without manual configuration of the local m2 cache? Is there not an aries
maven repo we can use to place the dependencies we need such as equinox?
Tom
From: David Bosschaert <da...@gmail.com>
To: "dev@aries.apache.org" <de...@aries.apache.org>
Date: 06/04/2014 01:49 AM
Subject: Re: Current build and org.eclipse.osgi version
3.8.2.v20130124-134944
It might be downloading it from somewhere (using something like a http
get task) and then using a system dependency to use it in Maven. Not
sure this is the way its used in this particular place, but I think
the subsystems subproject had certain Eclipse dependencies set up this
way.
John Ross might be able to give more details...
Cheers,
David
On 3 June 2014 20:37, Thomas Watson <tj...@us.ibm.com> wrote:
>
> With the latest from trunk I am no longer able to build because of a
> reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944
>
> Which repo is this supposed to exist? Here is the error.
>
> Failed to execute goal on project org.apache.aries.blueprint.itests:
Could
> not resolve dependencies for project
>
org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT:
> Could not find artifact
> org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink
Repo
> (http://download.eclipse.org/rt/eclipselink/maven.repo/)
>
> Tom
Re: Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
Posted by David Bosschaert <da...@gmail.com>.
It might be downloading it from somewhere (using something like a http
get task) and then using a system dependency to use it in Maven. Not
sure this is the way its used in this particular place, but I think
the subsystems subproject had certain Eclipse dependencies set up this
way.
John Ross might be able to give more details...
Cheers,
David
On 3 June 2014 20:37, Thomas Watson <tj...@us.ibm.com> wrote:
>
> With the latest from trunk I am no longer able to build because of a
> reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944
>
> Which repo is this supposed to exist? Here is the error.
>
> Failed to execute goal on project org.apache.aries.blueprint.itests: Could
> not resolve dependencies for project
> org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT:
> Could not find artifact
> org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink Repo
> (http://download.eclipse.org/rt/eclipselink/maven.repo/)
>
> Tom
Current build and org.eclipse.osgi version 3.8.2.v20130124-134944
Posted by Thomas Watson <tj...@us.ibm.com>.
With the latest from trunk I am no longer able to build because of a
reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944
Which repo is this supposed to exist? Here is the error.
Failed to execute goal on project org.apache.aries.blueprint.itests: Could
not resolve dependencies for project
org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT:
Could not find artifact
org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink Repo
(http://download.eclipse.org/rt/eclipselink/maven.repo/)
Tom
[RESULT][VOTE] Versioning plugin 0.2.0
Posted by Daniel Kulp <dk...@apache.org>.
For the record, my +1 (I seemed to have forgotten that).
We have 3 binding votes and 1 non-binding vote. This vote passes.
I’ll promote the artifact and then start updating poms once it’s synced to central.
Dan
On May 25, 2014, at 8:44 AM, Daniel Kulp <dk...@apache.org> wrote:
>
> With my own vote, I only have two votes. Can I get another PMC member to look at this?
>
> Thanks!
>
> Dan
>
> On May 19, 2014, at 1:15 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> This is a vote to release 0.2.0 of the versioning plugin.
>>
>> The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
>>
>>
>> Tag:
>> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
>>
>>
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [VOTE] Versioning plugin 0.2.0
Posted by Daniel Kulp <dk...@apache.org>.
With my own vote, I only have two votes. Can I get another PMC member to look at this?
Thanks!
Dan
On May 19, 2014, at 1:15 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> This is a vote to release 0.2.0 of the versioning plugin.
>
> The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
>
>
> Tag:
> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
>
>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [VOTE] Versioning plugin 0.2.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (non binding)
Regards
JB
On 05/19/2014 07:15 PM, Daniel Kulp wrote:
>
> This is a vote to release 0.2.0 of the versioning plugin.
>
> The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
>
>
> Tag:
> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Versioning plugin 0.2.0
Posted by Sergey Beryozkin <sb...@gmail.com>.
+1
Cheers, Sergey
On 19/05/14 18:15, Daniel Kulp wrote:
>
> This is a vote to release 0.2.0 of the versioning plugin.
>
> The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x by flipping from using Aether directly to using the Maven provided API’s. When released and rolled out throughout the rest of the build, we should hopefully be able to build Aries with a more modern version of Maven.
>
>
> Tag:
> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/
>
>
>