Hey.
Thanks for the reply.
We have a couple of snapshot repositories in the
settings.xml. But for some reason they do not show up in
the output of mvn help:effective-settings. We also specify
that our local Nexus installation is a mirror of central
(and some other public repos).
Running a
On 18 February 2011 09:27, Kristoffer Peterhaensel
kristof...@codedivision.com wrote:
Hey.
Thanks for the reply.
We have a couple of snapshot repositories in the settings.xml. But for some
reason they do not show up in the output of mvn help:effective-settings. We
also specify that our
On Fri, 18 Feb 2011 10:06:15 +
Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On 18 February 2011 09:27, Kristoffer Peterhaensel
kristof...@codedivision.com wrote:
Hey.
Thanks for the reply.
We have a couple of snapshot repositories in the
settings.xml. But for some
reason
Kristoffer Peterhaensel wrote:
So it is trying to resolve released a dependency on a
snapshot repository because the dependency that requires
it is a snapshot? And why does that not happen when I lock
down the dependency version of coreapi to 1.0.1-SNAPSHOT.
Shouldn't that do exactly the same?
Hello, I need a help to setting maven. I wanna use the
plugin-coverage-maven-plugin to analyse the coverage of functional tests.
I use also the cargo plugins, selenium and surefire. Without using these
plugins, I can do the coverage of unit tests with no problem.
But with functional tests does
I'm running into this too. I tried to create a test project but unfortunately
the problem didn't reproduce there.
Some background:
- dependency to artifact with version range [1.0.1, 2.0), matching versions
[1.0.1, 1.0.2, 1.0.3-SNAPSHOT].
- problems occurs when 1.0.3-SNAPSHOT tries to load it's
Perhaps it might be helpful in giving a solution, if we had the root
problem better described.
What are the particular properties of your application that makes it
unlike anything that has ever been built with Maven?
Maven is incredibly flexible and the technical expertise in this forum
is
that sounds like a bug. can you please raise a jira
- 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
screen
On 18 Feb 2011 13:05, Syvalta syva...@yahoo.com wrote:
I'm running into
Already there by Kristoffer: http://jira.codehaus.org/browse/MNG-5006
that sounds like a bug. can you please raise a jira
- Stephen
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-seem-to-like-version-ranges-tp3389402p3391152.html
Sent from the Maven -
I just created a project with an interesting dependency situation: my
existing code uses jetty 7, while hector from cassandra-land uses
jetty 6.
This should be fine; the group IDs are different.
However, my build fails as follows below. The actual cassandra-all pom
in my local repo, on the other
Running with m3, it still fails, and I see
[DEBUG] org.mortbay.jetty:jetty:jar:7.2.0.v20101020:compile
(version managed from 6.1.21)
in the log. So I need to figure out where this 'management' is coming from.
On Fri, Feb 18, 2011 at 10:25 AM, Benson Margulies
bimargul...@gmail.com wrote:
OK, mystery solved. I found the relevant dependencyManagement
statement in a distant parent, leftover from long ago.
On Fri, Feb 18, 2011 at 10:27 AM, Benson Margulies
bimargul...@gmail.com wrote:
Running with m3, it still fails, and I see
[DEBUG]
On 18 February 2011 04:06, Ewerton Vale Leal ewerto...@gmail.com wrote:
Hello, I need a help to setting maven. I wanna use the
plugin-coverage-maven-plugin to analyse the coverage of functional tests.
I use also the cargo plugins, selenium and surefire. Without using these
plugins, I can do
Sorry the question was not about parent element supporting versionless .
But was good to know , about this .
My question was -- The build fails to run if we run a maven Component
build with below parent element in place. The below parent element uses
the relativePath element to refer , as it
On Fri, Feb 18, 2011 at 1:39 PM, chandra.c49 chandramohan@gmail.com wrote:
My question was -- The build fails to run if we run a maven Component
build with below parent element in place. The below parent element uses
the relativePath element to refer , as it is located at different
I did what you recommended and did not work.
The cargo and selenium plugins must be executed before run the coverage .
When I execute the install the coverage does not work and when I execute
the coverage, the cargo , selenium and unit tests don’t execute.
I’m sending in annex the log of install
On 18 February 2011 11:06, Ewerton Vale Leal ewerto...@gmail.com wrote:
I did what you recommended and did not work.
The cargo and selenium plugins must be executed before run the coverage .
When I execute the install the coverage does not work and when I execute
the coverage, the cargo ,
Hi all guys,
I'm facing a wired issue, I don't understand if it concerns the
maven-site-plugin or the deploy plugin, btw every time I try to deploy
the site, the ${project.artifactId} is always appended to the
distributionManagement.site.url
i.e. if the url is
My directory structure is this:
src/main/java
src/main/resources
src/main/webapp
src/test/java/unitTest
src/test/java/functionalTest
I have unit tests and integration tests in the same project.
I running the commands mvn install.
Why are you using skiptrueskip? Isn't the whole point to
run
This is expected and documented [1]: 'If subprojects inherit the site
URL from a parent POM, they will automatically append their artifactId
to form their effective deployment location'. If you want to overide
that, you need to declare a site.url in the sub-project.
HTH,
-Lukas
[1]
gotcha, looks like I overlooked that part.
KUDOS for you Lukas! thanks a lot, it worked :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Feb 18, 2011 at 9:47 PM, Lukas Theussl ltheu...@apache.org wrote:
This is expected and documented [1]: 'If subprojects
On 18 February 2011 12:45, Ewerton Vale Leal ewerto...@gmail.com wrote:
My directory structure is this:
src/main/java
src/main/resources
src/main/webapp
src/test/java/unitTest
src/test/java/functionalTest
This is unusual. I would suggest src/test/java for your unit tests and
something else
You might also want to look into the maven-failsafe-plugin for your integration
tests.
-Original Message-
From: Hilco Wijbenga [mailto:hilco.wijbe...@gmail.com]
Sent: Friday, February 18, 2011 3:34 PM
To: Ewerton Vale Leal
Cc: Maven Users List
Subject: Re: Help to use plugin coverage
I'm trying to set up my maven2 project to deploy to my local tomcat.
In the pom I added:
...
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
configuration
servertomcat/server
urlhttp://localhost:8081/manager/url
path/freecologic/path
Perhaps try adding a default-cli execution as below:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
executions
execution
iddefault-cli/id
configuration
servertomcat/server
urlhttp://localhost:8081/manager/url
path/freecologic/path
How do I create another directory for integration testing in maven?
2011/2/18 Shay Thompson sthom...@adobe.com
You might also want to look into the maven-failsafe-plugin for your
integration tests.
-Original Message-
From: Hilco Wijbenga [mailto:hilco.wijbe...@gmail.com]
Sent:
On Sat, Feb 19, 2011 at 2:01 AM, Benson Margulies bimargul...@gmail.comwrote:
OK, mystery solved. I found the relevant dependencyManagement
statement in a distant parent, leftover from long ago.
Can you see if there is already a bug filed that says we should do more to
help the user track
Standard testing, which uses the surefire plugin and is done at the test
lifecycle, use the naming convention like this:
* **/Test*.java - includes all of its subdirectories and all java
filenames that start with Test.
* **/*Test.java - includes all of its subdirectories and all java
28 matches
Mail list logo
