Ahhhhhhh, so the version contraints actually depend upon what kind of component you're specifying... I guess that makes sense as it helps determine how Maven itself works... Which also explains why the other gentlemen said that it breaks best practices...
Makes sense then. Thanks! -----Original Message----- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, December 06, 2013 1:12 PM To: Maven Users List Subject: Re: plugin version ranges errors with Maven 3.1.1 Hi John, > According to the examples and documentation I have seen, this should > work. At least in my quickly Googling around, I cannot find anything that says that version ranges actually work for plugins -- only for dependencies. Do you have a pointer to docs explicitly stating that it works with Maven plugins? If not, it might not be supported at all. I did a quick test on my system with Maven 3.1.1 and got the same error you did. Regards, Curtis On Fri, Dec 6, 2013 at 1:12 PM, John Dix <john....@amdocs.com> wrote: > I am trying to specify a version range in a pom.xml in order to > support our build by doing the following: > > <plugin> > <groupId> org.apache.maven.plugins</groupId> > <artifactId> maven-shade-plugin</artifactId> <version>[2.0, > )</version> </plugin> > > And I am getting this error: > > [ERROR] Plugin org.apache.maven.plugins:maven-shade-plugin:[2.0,) or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for org.apache.maven.plugins:maven-shade-plugin:jar:[2.0,): > Could not transfer artifact > org.apache.maven.plugins:maven-shade-plugin:pom:[2.0,) from/to > qpass-nexus-hosted-releases ( > http://xxxx:8081/nexus/content/repositories/releases): Illegal > character in path at index 115: > http://xxx:8081/nexus/content/repositories/releases/org/apache/maven/p > lugins/maven-shade-plugin/[2.0,)/maven-shade-plugin-[2.0,).pom-> [Help > 1] > > According to the examples and documentation I have seen, this should work. > > Any idea? > > > John "Caolan" Dix > Programming Sr. SME, Digital Commerce > Amdocs Mobile Financial Services Division > o: 206-288-0308 m: 425.351.7340 > AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS > > Did you know...? > A global consumer survey by Analysys Mason and Amdocs reveals that > cash is past its prime. Download the new white paper, "Mobile Financial > Services: > The Evolution of Payment" here<http://amdocs.com/mfs-wp>. > > Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs > blog network<http://blogs.amdocs.com/> - and follow us on Facebook< > https://www.facebook.com/AmdocsMobilePayments>, Twitter< > https://twitter.com/amdocsmpayments>, LinkedIn< > http://www.linkedin.com/company/amdocs>, YouTube< > http://www.youtube.com/amdocs> and Google+< > https://plus.google.com/+amdocs#+amdocs/posts> > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, you may > review at http://www.amdocs.com/email_disclaimer.asp > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
