You need just to follow those steps: Right Click on your project: Run (As) -> Maven clean Right Click on your project: Run (As) -> Maven install After which, if the build fails when you do Maven Install, it means there is no web.xml file under WEB-INF or some problem associated with it. it really … Read more
This is the exact thing I was looking for my automation test and I got it working. Command Line argument mvn clean test -Denv.USER=UAT -Dgroups=Sniff My Pom Xml <?xml version=”1.0″ encoding=”UTF-8″?> <project xmlns=”http://maven.apache.org/POM/4.0.0″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd”> <modelVersion>4.0.0</modelVersion> <groupId>TestNg</groupId> <artifactId>TestNg</artifactId> <version>1.0</version> <dependencies> <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>6.8</version> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.12.4</version> <configuration> … Read more
I wasn’t really satisfied with the accepted approach, so I simplified it a little. Basically set a default property in the normal properties block, and only override when appropriate (instead of an effective switch statement): <properties> <!– Sane default –> <buildNumber>0</buildNumber> <!– the other props you use –> </properties> <profiles> <profile> <id>ci</id> <activation> <property> <name>env.buildNumber</name> … Read more
I faced the same issue. Setting relative path of the parent in module projects solved the issue. Use <relativePath>../Parent Project Name/pom.xml</relativePath>
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
In order to resolve the parent project, these possible sources are checked: relativePath local repository remote repositories The relative path, if not given explicitly, defaults to .., i.e. the pom in the parent directory of the current project. So Maven checks whether a) there is a pom file in that directory and b) that pom … Read more
A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects. Examples for this is the build directory, which is target; the source directory, … Read more
UPDATE: since version 1.5 the default namespace prefix ‘_’ is available so the solution is reduced to this: xml sel -t -m _:project -v _:groupId -o : -v _:artifactId -o : -v _:version pom.xml Thanks @JamieNelson for the heads-up. Unfortunately, XMLStarlet is very picky about the default namespace. If the document has it declared (xmlns=), … Read more
Given the simple Maven Source Plugin configuration (as an example) you have a shared configuration across all of its executions (outside the executions element) and then a custom configuration per each execution, for the same phase, as requested by your question: <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <version>2.4</version> <configuration> <includePom>true</includePom> </configuration> <executions> <execution> <id>test-id1</id> <phase>verify</phase> <goals> … Read more
I just ran into a similar problem. I’m using IntelliJ IDEA Ultimate 2020.2. The version number 2.4.0 was red and the message was the same as yours. Selecting File -> Invalidate Caches / Restart… and choosing the Invalidate and Restart option fixed the issue. I guess it was just a stale cache.