Re: [ALL] Parent Pom almost ready for snapshot deploy

On 18/06/2010, Niall Pemberton wrote: > On Fri, Jun 18, 2010 at 4:38 PM, sebb wrote: > > I think the parent pom is almost ready for a snapshot deploy if anyone > > (e.g. Niall?) wants to do this: > > > I don't believe theres any need to deploy a snapshot. Anyone who wants > to test can just do

Re: [ALL] Parent Pom almost ready for snapshot deploy

On 18/06/2010, Dennis Lundberg wrote: > On 2010-06-18 17:38, sebb wrote: > > I think the parent pom is almost ready for a snapshot deploy if anyone > > (e.g. Niall?) wants to do this: > > > > mvn -N deploy [-Ptest-deploy] > > > > Use the "test-deploy" profile to create the output under targe

[g...@vmgump]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-jelly-tags-jaxme has an issue affecting its community integration

Re: [ALL] Parent Pom almost ready for snapshot deploy

On 2010-06-18 17:38, sebb wrote: > I think the parent pom is almost ready for a snapshot deploy if anyone > (e.g. Niall?) wants to do this: > > mvn -N deploy [-Ptest-deploy] > > Use the "test-deploy" profile to create the output under target/deploy. > > Not sure why, but the site.xml seems to be

[g...@vmgump]: Project commons-configuration-test (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integrati

Re: [ALL] Parent Pom almost ready for snapshot deploy

On Fri, Jun 18, 2010 at 4:38 PM, sebb wrote: > I think the parent pom is almost ready for a snapshot deploy if anyone > (e.g. Niall?) wants to do this: I don't believe theres any need to deploy a snapshot. Anyone who wants to test can just do mvn install on the parent pom and then switch a compon

[ALL] Parent Pom almost ready for snapshot deploy

I think the parent pom is almost ready for a snapshot deploy if anyone (e.g. Niall?) wants to do this: mvn -N deploy [-Ptest-deploy] Use the "test-deploy" profile to create the output under target/deploy. Not sure why, but the site.xml seems to be deployed along with the pom.xml. At least with N

RE: [ALL] Specification version

> -Original Message- > From: Emmanuel Bourg [mailto:ebo...@apache.org] > Sent: Friday, June 18, 2010 05:12 > To: Commons Developers List > Subject: Re: [ALL] Specification version > > Le 18/06/2010 12:57, Jörg Schaible a écrit : > > > since Sebb is going to modify the parent pom, I want a

[ALL] Commonssite JIRA fixes

I'm trying to resolve the outstanding Parent Pom JIRAs. Please let me know if you think I've resolved any incorrectly ... - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@comm

Re: [ALL] Specification version

Emmanuel Bourg wrote: > Le 18/06/2010 12:57, Jörg Schaible a écrit : > >> since Sebb is going to modify the parent pom, I want also have your >> opinion about the current values of the Specification-Version in the >> manifests. Currently Maven generates uses the current version of the >> artifact

Re: [ALL] commons parent plugin versions

Agreed. If it ain't broke, don't fix it. On Fri, Jun 18, 2010 at 10:22 AM, Niall Pemberton wrote: > On Fri, Jun 18, 2010 at 11:11 AM, sebb wrote: >> If we are updating parent to fix the deployment URLs, we should >> probably update plugin versions too. >> >> The following plugin updates are ava

Re: [ALL] commons parent plugin versions

On Fri, Jun 18, 2010 at 11:11 AM, sebb wrote: > If we are updating parent to fix the deployment URLs, we should > probably update plugin versions too. > > The following plugin updates are available: >  org.apache.felix:maven-bundle-plugin . 1.4.3 -> 2.1.0 >  maven-antrun-plugin ...

Re: [ALL] Specification version

Le 18/06/2010 12:57, Jörg Schaible a écrit : since Sebb is going to modify the parent pom, I want also have your opinion about the current values of the Specification-Version in the manifests. Currently Maven generates uses the current version of the artifact for "Specification-Version" and "Imp

Re: [ALL] Specification version

On 18/06/2010, Jörg Schaible wrote: > Guys, > > since Sebb is going to modify the parent pom, I want also have your opinion > about the current values of the Specification-Version in the manifests. > Currently Maven generates uses the current version of the artifact for > "Specification-Versio

[ALL] Specification version

Guys, since Sebb is going to modify the parent pom, I want also have your opinion about the current values of the Specification-Version in the manifests. Currently Maven generates uses the current version of the artifact for "Specification-Version" and "Implementation-Version" i.e. ".- SNAPSHOT

[ALL] commons parent plugin versions

If we are updating parent to fix the deployment URLs, we should probably update plugin versions too. The following plugin updates are available: org.apache.felix:maven-bundle-plugin . 1.4.3 -> 2.1.0 maven-antrun-plugin .. 1.3 -> 1.4 maven-c

Re: [Math] Privilege upgrade on JIRA

On Fri, Jun 18, 2010 at 9:09 AM, Gilles Sadowski wrote: > Hi. > > Could someone raise my privileges on JIRA so that I can assign and resolve > issues not created by me? I've added you to the commons developers group. Niall > Then, I'll handle MATH-378, if everyone agrees that the code can be ad

[Math] Privilege upgrade on JIRA

Hi. Could someone raise my privileges on JIRA so that I can assign and resolve issues not created by me? Then, I'll handle MATH-378, if everyone agrees that the code can be added (with some modifications, namely due to the recent changes). Thanks, Gilles -