Using site even if build fails

Hi all, Please excuse me if this is a double post - I couldn't be sure the first one went through. I am trying this command line: mvn --fail-at-end -Plocal verify site And I find that if an integration test fails, site is *not* being run at all - even with --fail-at-end. This is my reporting el

Re: How to run multiple rounds of integration tests in one build

Separate attract build from integration tests. In the integration test: -Set up your system (cleanup, install) - run with the flag disabled - run again with the flag disabled I would use Jenkins build steps rather than maven profiles On Mar 27, 2015 3:15 PM, "Stefan" wrote: > Hi guys, > > I've

How to run multiple rounds of integration tests in one build

Hi guys, I've been banging my head over the following problem lately and wasn't able to find a solution at all on the interwebs. So, here's some context. I'm working on multiple RESTful APIs within a microservices architecture. Some of these applications can form separate stand alone sub-sys

Re: AW: maven-release-plugin / SVN credentials

Hi Sebastian, this is first of all more an svn commandline issue rather than a Maven / maven-release-plugin issue. For that reason you should start by calling svn directly from the commandline. In the end, that's exactly what maven-release-plugin (actually the scm-svn-provider) does. Once i

[ANN] Apache Maven Compiler Plugin Version 3.3 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Compiler Plugin, version 3.3 The Compiler Plugin is used to compile the sources of your project. http://maven.apache.org/plugins/maven-compiler-plugin/ You should specify the version in your project's plugin configura

Re: Integration Test: Dependency problem

After moving the dependencies to the parent pom and add them in the itest pom without version tag, I get in the itest pom following error for the following three depeondencies: org.apache.camel.karaf apache-camel

Re: Integration Test: Dependency problem

type is not quite the same as packaging - packaging defines the lifecycle used to build the project (what plugins get called for each phase) whereas type is more about the final artifact and defines the extension amongst other things. The bundle lifecycle does define a type called 'bundle' with an

Re: Integration Test: Dependency problem

So I can remove the type tag from dependencies. Is then tag type only used once, when introducing a new artifact in tag packaging? Regards Christian Christian Eugster Grissian 14 I-39010 Tisens I: +39 0473 420 873 CH: +41 79 107 92 27 christian.eugs...@gmx.net > Am 27.03.2015 um 17:50 schri

Re: Integration Test: Dependency problem

I see you're declaring dependencies with bundle whereas you should just leave them with the default type (jar). While the packaging type is "bundle" (to activate the different packaging lifecycle) the artifacts produced are declared as type jar and can be referenced as dependencies with the default

Re: Integration Test: Dependency problem

I changed the type of the bundles to jar. It does not help. Regards Christian Christian Eugster Grissian 14 I-39010 Tisens I: +39 0473 420 873 CH: +41 79 107 92 27 christian.eugs...@gmx.net > Am 27.03.2015 um 17:35 schrieb Christian Eugster : > > Hi, > > but as I understand, the bundles h

Re: Integration Test: Dependency problem

Hi, but as I understand, the bundles have - as the normal jars - the extension jar, the unique difference are some extra entries in the MANIFEST.MF file. Is that wrong? I added the frequently used dependencies to the parents pom as managed dependencies and added those required for itest in th

Re: Integration Test: Dependency problem

The log shows that it’s looking for artifacts with an extension of ‘bundle’, whereas the bundle packaging type actually produces artifacts with an extension of ‘jar’ - this suggests that the bundle lifecycle extension has not been installed for the itest project. What does the sip-detection pom

AW: maven-release-plugin / SVN credentials

Hi Robert, - I have looked at the Maven SCM project but do not get my problem solved or more hints on it - The maven-release-plugin is locked (with version 2.5, not 2.5.1) - If running maven with -X according to console no credentials are provided when accessing the SVN - If running maven with -

Using site even if build fails

Hi all, I am trying this command line: mvn --fail-at-end -Plocal verify site And I find that if an integration test fails, site is *not* being run at all - even with --fail-at-end. This is my reporting element in pom.xml: org.apache.maven.plugins maven-surefire-re

Integration Test: Dependency problem

Hi, I am quite new to maven and I have the following problem: I have a project with several modules (api and impl) and one of them is an integration test module, that contains only a test class. The pom of this module references (as I see) all dependencies. When I run the parents pom all modul

Re: Proper way to have my Mojo instrument both main and test classes

You should have two separate goals (sharing most of hte same code/functionality though). The end user could specify one single execution block but specifying both goals in it. You shouldn't need to know which phase you're in. The onyl thing you're interested in (in the goal) is the classes to proc

Re: maven-release-plugin / SVN credentials

Hi Sebastian, since your issue has to do with svn, one needs to look at the Maven SCM project.[1] That's what the maven-release-plugin is using to the commits, tags and checkouts. First ensure you've locked the version of the maven-release-plugin, preferably the lastest (i.e. 2.5.1). If you