Make sure you Double-Check that the version you refer to in the child-pom is the same as that in the parent-pom. For me, I’d bumped version in the parent and had it as 3.1.0.0-RELEASE, but in the child-pom, I was still referring to the previous version via relativePath, and had it defined as 2.0.0.0-SNAPSHOT. It … Read more
It is only necessary to set the path to the Maven binary and to the JDK correctly: set PATH %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\Java\jdk1.7.0_04\bin;C:\Program Files\apache-maven-3.0.4\bin Furthermore you need to set the JAVA_HOME correctly which is done under windows like this: SET JAVA_HOME=C:\Program Files\Java\jdk1.7.0_04 Be aware of setting JAVA_HOME to the root of the installed JDK and not to … Read more
Below one worked for me ; Go to File > Settings > Build,Execution,Deployment> Build Tools > Maven > Importing . Change VM options for importer to -Didea.maven3.use.compat.resolver
What’s new in Maven 3? Here is a little compilation of what you can find around the net. Backward compatibility – Maven 3 is backward compatible, that is extremely important (especially for those who experienced the Maven 1 to Maven 2 transition). Versionless parent elements – Maven 3 will remove the need to specify the … Read more
As a workaround, add this to the <plugins> … </plugins> section inside your project’s pom.xml: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> <version>1.7</version> <executions> <execution> <phase>validate</phase> <goals> <goal>run</goal> </goals> <configuration> <tasks> <echoproperties /> </tasks> </configuration> </execution> </executions> </plugin> Now execute mvn validate. On the console, prefixed with [echoproperties], there will be the full list of system properties, including those … Read more
Using the same plugin, you can generate javadoc in a folder using mvn javadoc:javadoc It puts the help content under target/site/apidocs You can change the output folder by using the plugin configuration parameter reportOutputDirectory Please refer to: Apache Maven Javadoc Plugin
Assuming the MyEjbProject is not another Maven Project you own or want to build with maven, you could use system dependencies to link to the existing jar file of the project like so <project> … <dependencies> <dependency> <groupId>yourgroup</groupId> <artifactId>myejbproject</artifactId> <version>2.0</version> <scope>system</scope> <systemPath>path/to/myejbproject.jar</systemPath> </dependency> </dependencies> … </project> That said it is usually the better (and preferred … Read more
This link helped: https://stackoverflow.com/a/11199865/1307104 I edit my command by adding quotes for every parameter like this: mvn install:install-file “-DgroupId=org.mozilla” “-DartifactId=jss” “-Dversion=4.2.5” “-Dpackaging=jar” “-Dfile=C:\Users\AArmijos\workspace\componentes-1.0.4\deps\jss-4.2.5.jar” It’s worked.