maven-failsafe-plugin implies some specific steps are required *before*
(pre-integration-test) and *after* (post-integration-test) the test
execution, which allows to do fire up a container then turn it off after
the tests (for example).
Then, only after these, the test results are evaluated durin
you mean 'verify', not 'validate'
Vincent
2013/11/14 Matthew Adams
> Here's a bit less philosophical, more practical description of Surefire v.
> Failsafe.
>
> Remember that if you use the maven-surefire-plugin, it's going to execute
> during the Maven "test" phase by default, and fail the bui
Suppose I have a parent pom that makes use of the maven-enforcer-plugin.
As a matter of fact I do, and it's public, so you can follow along at home:
org.sonatype.oss
oss-parent
7
Looking at that pom, there is this snippet in it:
org.apache.maven.plugins
maven-enforcer-plugi
On 7 November 2013 08:53, Mirko Friedenhagen wrote:
> Hello,
>
> say I have a parent pom, which defines:
>
>
> org.apache.maven.plugins
> maven-surefire-report-plugin
> 2.16
>
>
>
> report
Here's a bit less philosophical, more practical description of Surefire v.
Failsafe.
Remember that if you use the maven-surefire-plugin, it's going to execute
during the Maven "test" phase by default, and fail the build on errors
_during that phase_ if any tests fail.
The maven-failsafe-plugin ex
Given the 401 changed in 403 ,it seems to me that the credentials are
correct but you are still not allowed to access this artifact/repository.
I would suggest to contact the nexus administrator
On Thu, Nov 14, 2013 at 11:18 PM, Russell Gold wrote:
> OK, that narrows things down. While it is p
On Wed, Nov 13, 2013 at 10:39 AM, Ron Wheeler <
rwhee...@artifact-software.com> wrote:
> On 13/11/2013 11:16 AM, Matthew Adams wrote:
>
>> I don't think timing should be the heuristic here. The fact that unit
>> tests take less is a result of the fact that what you're testing, aka the
>> "unit",
OK, that narrows things down. While it is possible to work with a repo that
requires credentials to download artifacts, doing so will require you to supply
credentials in your settings.xml. Is there some reason you want to do this? I
know coherence is commercial rather than open-source. Are only
> -Original Message-
> From: Russell Gold [mailto:r...@gold-family.us]
> Sent: Thursday, November 14, 2013 1:44 PM
> To: Maven Users List
> Subject: Re: Access denied downloading artifact from nexus
>
> HI David. Try accessing
> http://nexusprohost.com:8084/nexus/content/groups/cditspoc/co
HI David. Try accessing
http://nexusprohost.com:8084/nexus/content/groups/cditspoc/com/oracle/coherence/coherence/12.1.2-0-0/coherence-12.1.2-0-0.pom
via your browser. That will test if it is a maven problem or a nexus problem.
On Nov 14, 2013, at 4:35 PM, KARR, DAVID wrote:
> (Sorry for the i
(Sorry for the initial blank body. Not sure what happened there.)
I'm having trouble downloading an artifact from a nexus pro repo in a Maven
build on a build server. I don't know if this is a Maven problem, or a Nexus
problem, although it's probably the former.
I'm working on a Maven build w
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
BTW, I ran your pom.xml through:
mvn dependency:tree
using Maven3 and the exclusions for those 2 maven-plugins were respected, which
suggests your exclusion issue might also be specific to Gradle.
On 14 Nov 2013, at 14:53, Stuart McCulloch wrote:
> You mean the "POM relocation to an ot
My understanding is that a POM schema change would require a major version
bump, so such a feature will *not* be in any version called 3.2
On 14 November 2013 14:53, Cemo wrote:
> http://jira.codehaus.org/browse/MNG-1977 :)
>
> Will be fixed in 3.2
>
>
> On 14 November 2013 16:51, Lyons, Roy w
Doh, sorry - worth a try :)
You could try forcing jaxen to 1.1.4 (using dependencyManagement) as that
version doesn't have those odd plugin dependencies
On 14 Nov 2013, at 14:36, Jason Tesser wrote:
> Also that doesn't work. Invalid POM
>
> cannot say
>
> maven-plugins
> maven-cobertura-plugi
http://jira.codehaus.org/browse/MNG-1977 :)
Will be fixed in 3.2
On 14 November 2013 16:51, Lyons, Roy wrote:
> Today the dependency exclude works on a artifact by artifact basis. I was
> just thinking that someone might want to do a blanket exclude without
> having to dependency:tree -Dverbo
You mean the "POM relocation to an other version number is not fully supported
in Gradle" message?
If you look at the pom it has a relocation element (bit like a symbolic link):
http://search.maven.org/remotecontent?filepath=xml-apis/xml-apis/2.0.2/xml-apis-2.0.2.pom
http://ma
I happened to have the same problem. However, in my case it was reproducible
both in Eclipse (with m2eclipse) and as command-line build.
The problem was resolved once I configured the maven compiler plugin to not
fork:
org.apache.maven.plugins
maven-compiler-plugin
2.5.1
Today the dependency exclude works on a artifact by artifact basis. I was just
thinking that someone might want to do a blanket exclude without having to
dependency:tree -Dverbose=true to see all the items which might have it...
Before submitting an enhancement request, I thought I would get th
Stuart McCulloch wrote:
> Try adding:
>
> plugin
>
> to those 2 dependency exclusions.
Nice try. Violates schema.
>
> ( the jaxen pom:
>
http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pom
> declares those dependencies to be of type "plugin" )
>
> On 14 Nov 2013
Also that doesn't work. Invalid POM
cannot say
maven-plugins
maven-cobertura-plugin
plugin
On Thu, Nov 14, 2013 at 9:32 AM, Jason Tesser wrote:
> you are referring to the maven-plugins I think
>
> But what about the xml-api thing?
>
>
> On Thu, Nov 14, 2013 at 9:29 AM, Stuart McCulloch wrot
you are referring to the maven-plugins I think
But what about the xml-api thing?
On Thu, Nov 14, 2013 at 9:29 AM, Stuart McCulloch wrote:
> Try adding:
>
> plugin
>
> to those 2 dependency exclusions.
>
> ( the jaxen pom:
> http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1
Try adding:
plugin
to those 2 dependency exclusions.
( the jaxen pom:
http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pom
declares those dependencies to be of type "plugin" )
On 14 Nov 2013, at 13:14, Jason Tesser wrote:
> I have the following POM http://
I have the following POM http://pastebin.com/P4TvzqJn but my exclusion for
abdera-client are not being respected. Actually
only 2 of them are not
the 2 not working are maven-plugins and maven-plugins
they are coming down anyways
see http://pastebin.com/c59HM8Bj
what am I missing
I have altered the
Hi,
This list is for Maven users. What you ask should be posted on the Jenkins
users mailing list : https://groups.google.com/forum/#!forum/jenkinsci-users
Cheers
2013/11/13 Anand Sudabattula
> Hi
>
> We like to mask the password that is provided thro’ cq.password parameter
> in Maven Goals us
25 matches
Mail list logo
