Maven 3 and updateReleaseInfo=false

2011-06-29 Thread Henika Tekwani
Hi All, I am trying to deploy an artifact using maven 3 but I don't want to update the RELEASE tag in the maven-metadata.xml. I am using maven-deploy-plugin:2.6:deploy-file and while calling the deploy command I am setting -DupdateReleaseInfo=false. Still the RELEASE tag in metadata is getting

Re: Pom changes

2011-06-29 Thread Benson Margulies
If they update to new versions of the thing with the pom. At least for polemic purposes, imagining a world in which the decision to make use of a new pom feature has the effect of forcing these sticks-in-the-mud to stick to old versions. Let me be more specific about why I don't like the

Re: Pom changes

2011-06-29 Thread Stephen Connolly
On 29 June 2011 12:20, Benson Margulies bimargul...@gmail.com wrote: If they update to new versions of the thing with the pom. At least for polemic purposes, imagining a world in which the decision to make use of a new pom feature has the effect of forcing these sticks-in-the-mud to stick to

Re: Pom changes

2011-06-29 Thread Benson Margulies
Telling people to edit and maintain two poms is also likely to lead to widespread derision. Here's another thought experiment in design. This may merely be me recapitulating Steven's idea. Say that for Maven 3.1 we wanted to fix this issue once and for all. So, we make maven 3.1 default to

Re: Maven 3 and updateReleaseInfo=false

2011-06-29 Thread Benson Margulies
I think that you should create a JIRA. On Wed, Jun 29, 2011 at 7:11 AM, Henika Tekwani htekw...@adobe.com wrote: Hi All, I am trying to deploy an artifact using maven 3 but I don't want to update the RELEASE tag in the maven-metadata.xml. I am using maven-deploy-plugin:2.6:deploy-file and

Re: Pom changes

2011-06-29 Thread Nigel Magnay
If tools validate against the schema, they know when a POM is, in fact, valid for its declared model. Thus, any elements that the tool does not recognize are proved to be 'messengers from the future'. It would help enormously if 'messengers from the future' used an appropriate XML

Re: Pom changes

2011-06-29 Thread Benson Margulies
I'm opposed to namespaces for two reasons. One is a global reason, the other applies only to 'core' configuration. The global reason: read all the very cogent writing from the HTML5 process as to why they have run screaming away from namespaces. The more local reason: Consider what started this

Re: Pom changes

2011-06-29 Thread Nigel Magnay
I'm not sure the HTML analogy flies (in particular, I'm not convinced that, say, schema.org isn't just re-invention of namespaces or RDFa via another mechanism). I have no argument that XML namespaces are somewhat klunky, but they are at least standardised and have well understood transformations

Re: scopeperi/scope

2011-06-29 Thread Jesse Glick
On 06/27/2011 06:54 PM, Stephen Connolly wrote: Critically missing from my PoV are: Consider also 'endorsed' (a serious issue for EE projects especially): http://jira.codehaus.org/browse/MNG-4752 Also some notes on a non-transitive compile scope: for NetBeans module development, module -

RE: why Maven 3 is divided into eleven eclipse project?

2011-06-29 Thread Martin Gainty
these are the eclipse (sub)projects i have thus far: apache cdt core equinox jdt text wst if my base eclipse version is 3.7 (for eclipse version 3.7) and if i implement a new algorithm for EditText or UndoText I would refactor

Re: scopeperi/scope

2011-06-29 Thread Stephen Connolly
optionaltrue/optional should get you the non-transitive. hard to digest the rest of your post with my son pulling out of me ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the

Re: scopeperi/scope

2011-06-29 Thread Stephen Connolly
yes i forgot about endorsed... it is definitely required... complicates plugins that run in the same jvm though... eg jetty, surefire in no fork mode, etc - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using

Re: why Maven 3 is divided into eleven eclipse project?

2011-06-29 Thread Benson Margulies
What are you two talking about. In what respect is Maven 3 divided into this set of eclipse projects? On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty mgai...@hotmail.com wrote: these are the eclipse (sub)projects i have thus far:          apache          cdt          core          equinox  

Re: why Maven 3 is divided into eleven eclipse project?

2011-06-29 Thread Wendy Smoak
On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty mgai...@hotmail.com wrote: make ¢? No. Where did that list come from? I thought maybe the OP was asking about the many modules in the Maven source code: http://svn.apache.org/repos/asf/maven/maven-3/trunk/ -- Wendy

Re: why Maven 3 is divided into eleven eclipse project?

2011-06-29 Thread Tamás Cservenák
Sorry, did not noticed the OOM in the logs! Bot restarted, try again please... Thanks, ~t~ On Wed, Jun 29, 2011 at 9:34 PM, Wendy Smoak wsm...@gmail.com wrote: On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty mgai...@hotmail.com wrote: make ¢? No.  Where did that list come from?

Re: Re: why Maven 3 is divided into eleven eclipse project?

2011-06-29 Thread jameslordhz
after i use mvn eclipse:eclipse, eleven eclipse projects are generated for maven 3, that is [maven-aether-provider] [maven-artifact][maven-compat] [maven-core][maven-embedder] [maven-model] [maven-model-builder] [maven-plugin-api]