Not possible. Maven checks the repositories in their declaration order until a given artifact gets resolved (or not). Some repository manager can do something approaching this though. For example, Nexus has a routes feature that does something equivalent.
You need to indicate the groupId, the artifactId and the version for your artifact: mvn install:install-file \ -DgroupId=javax.transaction \ -DartifactId=jta \ -Dpackaging=jar \ -Dversion=1.0.1B \ -Dfile=jta-1.0.1B.jar \ -DgeneratePom=true
The problems are to do with your paths. Make sure that the directory “E:\java resources\apache-maven-2.2.0\bin” is on your command search path. Make sure that the JAVA_HOME variable refers to the home directory for your Java installation. If you are executing Java from “E:\Sun\SDK\jdk\bin”, then the JAVA_HOME variable needs to point to “E:\Sun\SDK\jdk”. NB: JAVA_HOME should … Read more
If you want just the local repo, try this: mvn help:evaluate -Dexpression=settings.localRepository | grep -v ‘\[INFO\]’ EDIT I’m revisiting this after years because recent versions of the Maven help plugin introduced a useful parameter for the evaluate goal called forceStdout that allows us to remove the need to grep the output: mvn help:evaluate -Dexpression=settings.localRepository -q … Read more
I looked into maven about six months ago. We were starting a new project, and didn’t have any legacy to support. That said: Maven is all-or-nothing. Or at least as far as I could tell from the documentation. You can’t easily use maven as a drop-in replacement for ant, and gradually adopt more advanced features. … Read more
It seems to be fixed in current version of maven-war-plugin, so just specifying: <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.3</version> </plugin> fixed it for me. (See the last answer (20/Sep/12 4:37 AM) from Anders Hammar on https://issues.apache.org/jira/browse/MWAR-248.)
I’ve come across that situation several times and, after a lot of attempts, I found the solution. Check your project build-path and enable specific output folders for each folder. Go one by one though each source-folder of your project and set the output folder that maven would use. For example, your web project’s src/main/java should … Read more
<build> <plugins> <plugin> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-sources</id> <phase>deploy</phase> <goals><goal>jar-no-fork</goal></goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-javadoc-plugin</artifactId> <executions> <execution> <id>attach-javadocs</id> <phase>deploy</phase> <goals><goal>jar</goal></goals> </execution> </executions> </plugin> <plugin> <!– explicitly define maven-deploy-plugin after other to force exec order –> <artifactId>maven-deploy-plugin</artifactId> <executions> <execution> <id>deploy</id> <phase>deploy</phase> <goals><goal>deploy</goal></goals> </execution> </executions> </plugin> </plugins> </build> See Sonatype’s OSS parent POM for a complete example.
You create a new project. The new project is your EAR assembly project which contains your two dependencies for your EJB project and your WAR project. So you actually have three maven projects here. One EJB. One WAR. One EAR that pulls the two parts together and creates the ear. Deployment descriptors can be generated … Read more
Ken, good question. I should be more explicit in the The Definitive Guide about the difference. “install” and “deploy” serve two different purposes in a build. “install” refers to the process of installing an artifact in your local repository. “deploy” refers to the process of deploying an artifact to a remote repository. Example: When I … Read more