Re: Plugin resolution

Hi Mark, The new plugin works great. The old plugin was definitely declared in my project's pom, so I'm not sure why it resolved the new one. In case it helps, it was actually declared in a parent pom and inherited. Thanks, -Evan On Thu, Jun 19, 2008 at 2:12 AM, Mark Hobson <[EMAIL PROTECTED]>

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (28 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques htt

Re: maven artifact issues before release

Paul Gier wrote: Oleg, are there any overview type docs on the wiki of how the new resolver will work? I'd like to see an overview before I start digging through the code. I'm specifically interested in how version ranges are handled in transitive dependencies. Like if you have multiple p

use highest version available ? Version Ranges ?

Initially posted this on the users list but didn’t get a response – so apologies for cross posting. Hi, Is there any way of forcing a dependency to use the highest version available ? For example : Does "[4.0,)" grab the highest version above 4.0, or does it still use a “best f

Re: maven artifact issues before release

Oleg, are there any overview type docs on the wiki of how the new resolver will work? I'd like to see an overview before I start digging through the code. I'm specifically interested in how version ranges are handled in transitive dependencies. Like if you have multiple paths to the same arti

Re: Plugin resolution

2008/6/18 Evan Worley <[EMAIL PROTECTED]>: > Thanks for all the info Mark, I greatly appreciate it. > > We will move onto the codehaus plugin immediately. Cool, let me know if you have any problems with the new version by raising an issue. > I'm still curious how "apt" can suddenly resolve to a n

Re: maven artifact issues before release

I have a concern about the conflict resolution piece. SAT based resolver in the sandbox branch works differently from the old one, and as such - it may break a few builds that rely on bugs in the old resolver. Secondly - I am trying to build up the test foundation for it - try it on really big

maven archetype couldn't download

Hi, I'm trying to download jboss archetype by running the command, mvn archetype:create -DarchetypeGroupId=org.richfaces.cdk -DarchetypeArtifactId=maven-archetype-jsf-component -DarchetypeVersion= 3.1.2.GA -DartifactId=mylib It's trying to download maven-archetype-jsf-component-3.1.2.GA.jar from

Re: maven artifact issues before release

SAT based resolver in the sandbox branch works differently from the old one, and as such - it may break a few builds that rely on bugs in the old resolver. And we need to test is more thoroughly. The next release will still use old resolver, but the intermediate, pre-SAT graph-based solution w

regarding Unable to download the artifact from any reposit and Error building POM (may not be this project's POM).

Hi I trying to create local repository in maven and I tried some commands like mvn clean install for default projetc but i getting this error message : I have realy no idea what the cause could be ? Could you please help me giving some idea ? Thx a lot for your help C:\ >mvn clean

RE: Fatal Error on pluggin clean

HI, I could't able to create proper repository and define pom.xml, settings.xml. So please let me know how to create sample project management using maven2.x. So please send proper documentation. I am getting the following error while executing this command : mvn clean install Thanks in adva

Re: Maven Release Plugin - 2.0-beta-7 and MRELEASE-326

Any updates on this? hirowla wrote: > > Is anybody working on this but not updated in JIRA? This problem prevents > any automated use of the plugin. > > Thanks, > > Ian > > > > > Disclaimer: The information transmitted is intended only for the person or > entity to which it is addressed