The feature simply doesn’t exist. The property activator uses the incoming properties, not anything set by the profiles (as otherwise it wouldn’t know what order to activate them in without some more complex logic). The solution you used, of have identical properties to activate the things you want to do together, is the best solution. … Read more
If your project has direct dependencies on B then you should keep it even if B is a transitive dependency of A. It can be that in the next version A won’t use B an you’ll have to restructure the pom.xml. Generally, Maven dependencies should reflect the logical project dependencies.
It work for me as the following. My setting.xml <server> <id>local_tomcat</id> <username>ray</username> <password>password</password> </server> My plugin configuration <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>tomcat-maven-plugin</artifactId> <configuration> <server>local_tomcat</server> <url>http://localhost:8080/manager/text</url> </configuration> </plugin> My tomcat-users.xml <role rolename=”manager-gui”/> <role rolename=”manager-script”/> <user password=”password” roles=”manager-gui, manager-script” username=”ray”/>
The org.eclipse.m2e:lifecycle-mapping plugin doesn’t exist actually. It should be used from the <build><pluginManagement> section of your pom.xml. That way, it’s not resolved by Maven but can be read by m2e. But a more practical solution to your problem would be to install the m2e build-helper connector in eclipse. You can install it from the Window … Read more
Answering your question I made a small investigation because I am also interested in the solution. Maven command line verbosity options According to http://books.sonatype.com/mvnref-book/reference/running-sect-options.html#running-sect-verbose-option -e for error -X for debug -q for only error Maven logging config file Currently maven 3.1.x uses SLF4J to log to the System.out . You can modify the logging settings … Read more
If you want to only download dependencies without doing anything else, then it’s: mvn dependency:resolve Or to download a single dependency: mvn dependency:get -Dartifact=groupId:artifactId:version If you need to download from a specific repository, you can specify that with -DrepoUrl=…
Weirdness is highly subjective, I just suggest to follow the official recommendation: Guide to naming conventions on groupId, artifactId and version groupId will identify your project uniquely across all projects, so we need to enforce a naming schema. It has to follow the package name rules, what means that has to be at least as … Read more
As of September 6th 2015 it appears there is, -Dsurefire.skipAfterFailureCount=1. As of October 19th 2015 version 2.19 has been released.
I found that there is an easy solution for this problem. You can add a <Class-Path> element to <manifestEntries> element, and set <addClassPath>true</addClassPath> to <manifest> element. So value of <Class-Path> element is added to class-path automatically. Example: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifest> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> <addClasspath>true</addClasspath> <mainClass>your.main.Class</mainClass> </manifest> <manifestEntries> <Class-Path>../conf/</Class-Path> </manifestEntries> </archive> </configuration> </plugin>
As of version 2.0.9 maven uses pom order for classpath, so you can actually manipulate it now. We mostly supress transitive dependencies to external libraries that we also include directly. From the release notes of maven 2.0.9: MNG-1412 / MNG-3111 introduced deterministic ordering of dependencies on the classpath. In the past, natural set ordering was … Read more