NMaven has been the first/official effort to provide Apache Maven for .NET; the project failed to clear the high bar of requirements for an official Apache project and was retired from the Apache Incubator in November 2008. There have been several efforts to fork and survive the project, but only one of them (NPanday) managed … Read more
use ${session.executionRootDirectory} For the record, ${session.executionRootDirectory} works for me in pom files in Maven 3.0.3. That property will be the directory you’re running in, so run the parent project and each module can get the path to that root directory. I put the plugin configuration that uses this property in the parent pom so that … Read more
This command will generate the dependencies tree of your maven project: $ mvn dependency:tree I am sure that you will like the result 🙂
I’m sure that if you only talk about storing binaries from “mvn deploy” both will do fine. We use Artifactory very extensively with all upgrades along the way. Lots of projects, numerous snapshots deployed and external repos proxied. Not a single problem. I find it hard to explain how other people experience issues with its … Read more
Also, you can use -o or –offline in the mvn command line which will put maven in “offline mode” so it won’t check for updates. You’ll get some warning about not being able to get dependencies not already in your local repo, but no big deal.
You can do this by defining a custom lifecycle and invoking that lifecycle before your Mojo is executed via the execute annotation. In your Mojo, declare in the Javadoc the lifecycle to be executed: /** * Invoke the custom lifecycle before executing this goal. * * @goal my-goal * @execute lifecycle=”my-custom-lifecycle” phase=”process-resources” */ public class … Read more
The default way to make an annotation processor available to the compiler is to register it in a file in META-INF/services/javax.annotation.processing.Processor. The file can contain a number of processors: each the fully-qualified class name on its own line, with a newline at the end. The compiler will default to using processors found in this way … Read more
Ok, I think the following might do what you need. The drawback of this approach is that there will be an interval between each deployment as the subsequent build is executed. Is this acceptable? Define a profile in each project with the same name (say “publish”). Within that profile you can define a configuration to … Read more
The Maven way to do this is not to change the finalName of the artifact but to use a classifier. For example: <project> … <build> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <classifier>${envClassifier}</classifier> </configuration> </plugin> </plugins> </build> … <profiles> <profile> <id>jdk16</id> <activation> <jdk>1.6</jdk> </activation> <properties> <envClassifier>jdk16</envClassifier> </properties> </profile> <profile> <id>jdk15</id> <activation> <jdk>1.5</jdk> </activation> <properties> <envClassifier>jdk15</envClassifier> </properties> </profile> </profiles> … Read more
The other thing that could be going wrong is that your machine is behind a firewall or proxy so your box is not able to hit http://repo1.maven.org/maven2. Try accessing this URL directly in a browser or something to test if you are able to make the request.