Maven 3.3.1 Config Error in IntelliJ Idea 14
Open up the IntelliJ settings dialog. In Maven–>Runner options set a following VM option: -Dmaven.multiModuleProjectDirectory=project root
Open up the IntelliJ settings dialog. In Maven–>Runner options set a following VM option: -Dmaven.multiModuleProjectDirectory=project root
Since version 2.10 of the Versions Maven Plugin you can simply do: mvn versions:set -DremoveSnapshot
Since version 3.0, Maven uses a consistent system to compare version numbers for both individual versions and version ranges. The system now makes a lot of sense, once you’ve understood a few gotchas. All comparisons are now done by ComparableVersion, which says: mixing of ‘-‘ (dash) and ‘.‘ (dot) separators, transition between characters and digits … Read more
There is a simple thing. A dependencyManagement does not declare a dependency which is really used it’s only defining versions etc. which can be used. If you define something like this it will not result in a change. <properties> <guava.version>18.0</guava.version> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>${guava.version}</version> </dependency> </dependencies> </dependencyManagement> If you really like to … Read more
It is done only for the artifacts or dependencies referenced by your project. The last check timestamp is stored within local artifact metadata (in your local Maven repository), so Maven can apply different strategies how often to check for updates based on that. The default update interval for snapshots is “daily”. Also see updatePolicy for … Read more
This is easily achieved by revoking the “Delete” permission from the deploying users\groups on the target repository; the delete permission is required for both artifact removal and artifact re-deployment. All user\group permissions are editable within the UI at Admin->Security->Permissions. Also see Managing Permissions
you have to setup mirror <mirror> <id>nexus</id> <mirrorOf>*</mirrorOf> <url>http://internal/nexus/content/repositories/thirdparty</url> </mirror> <mirror> <id>google</id> <mirrorOf>google</mirrorOf> <url>http://google-maven-repository.googlecode.com/svn/repository</url> </mirror> then add internal & external repo <profile> <id>nexus</id> <repositories> <repository> <id>central</id> <name>central</name> <url>http://internal/nexus/content/repositories/thirdparty</url> </repository> <repository> <id>google</id> <name>google</name> <url>http://google-maven-repository.googlecode.com/svn/repository</url> </repository> </repositories> </profile>
You can try MavenXpp3Reader which is part of maven-model. Sample code: MavenXpp3Reader reader = new MavenXpp3Reader(); Model model = reader.read(new FileReader(mypom));
The bug seems to be still present in the maven-archetype-plugin v3.0.1 . For those who do not want to downgrade the maven-resource-plugin. I managed to establish a more or less ugly workaround. First you rename the archetype-resources/.gitignore to __gitignore__ then inside the archetype-metadata.xml add <requiredProperties> <requiredProperty key=”gitignore”> <defaultValue>.gitignore</defaultValue> </requiredProperty> </requiredProperties> <fileSets> <fileSet> <directory></directory> <includes> <include>__gitignore__</include> … Read more
There is no scope that does exactly what you want here; test is the best available option. A test-runtime scope has been requested before (Re: Need for a test-runtime scope?) and the suggested workaround is exactly the ignoreNonCompile configuration you’ve already discovered. dependency:analyze already has some limitations (“some cases are not detected (constants, annotations with … Read more