Hi,
Just confirmed that the difference in effective POM in 2 cases is here -
junit
junit
3.8.1
test
The properties are correctly resolved to -
4.8.2
I am suspecting that there is some plugin that is responsible for
evaluating the properties and the version
On 25/06/2011 5:28 PM, Nick Olsen wrote:
>>> Detected Maven Version: 2.2.1 is not in the allowed range 3.0-RC1.
Looks like one of your plug-ins has a requirement for 3.0-RC1
I hope that this helps a bit.
Ron
-
To unsubscrib
I found the enforcer rules page. I added the following to my pom:
org.apache.maven.plugins
maven-enforcer-plugin
1.0.1
enforce-maven
enforce
I'm a bit confused. I can't find anything in the pom reference that would
allow me to require a particular version of maven. This is my first time
using maven, I've only started reading the book.
mvn -v says I'm using Maven 2.2.1
Why would "mvn install" require a different version of maven than "
It looks like you are using Maven 3 but the example is asking for a
version 2 of Maven or vice versa.
Try changing your POM to require the version of Maven that you are in
fact using.
Ron
On 25/06/2011 4:35 PM, Nick Olsen wrote:
I'm reading a book about maven. The book appears to be somewhat
I'm reading a book about maven. The book appears to be somewhat outdated but
it hasn't been too difficult yet.
Anyways, I've created a project using the "simple" archetype. I have not
added or edited any files. I typed "mvn install" and the following was the
output:
[INFO] Scanning for projects..
ship is focused on having a script or wagon url that you ship your releases
to, and being able to run that script against a specified release of your
project, even if your project on disk is a different version
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
Thanks Stephen, these are good leads. I had seen both of these projects some
time in the past, but hadn't strongly considered them.
A primary concern is reusing existing maven plugins. Ship seems focused on
general script execution, no? I'm still left with getting a groovy script to
execute
On Sat, Jun 25, 2011 at 3:09 AM, Olivier Lamy wrote:
> The configuration from reporting section will be used only when you will
> use site plugin.
>
Thank you. So I must maintain two identical configurations? I don't mean
this to sound rude.
Best,
Laird
Hello,
The configuration from reporting section will be used only when you
will use site plugin.
2011/6/24 Laird Nelson :
> Good afternoon,
>
> It was my understanding that if I configured the maven-javadoc-plugin in my
> pom.xml's section, that this configuration would also configure
> the plugi
1. have a look at the ship-maven-plugin (i wrote it, but i think it has some
good ideas for continuous delivery as well as delivery in general... i call
it ship to have a different term from deploy so as not to confuse the maven
lifecycle)
2. you might have some luck with, eg the maven-invoker-plu
11 matches
Mail list logo
