maven-2

I have to use Annotation Processing (apt) and AspectJ in the same Maven project. Both work for themselves, but I need to create aspects based on code created by apt. So I would need binary weaving (the original source files are extended by apt). How can I enable binary weaving within a maven project? I know the only standard option is to supply a dependency using the weaveDependencies parameter, but this is awful. Is there any other way? OK, I could embed the AspectJ ant tasks using the Maven Antrun Plugin but I'd hate to resort to that. I am apparently the only one who can answer my own

I am working on a collection MATLAB, Java, and C/C++ components that all inter-operate, but have distinctly different compilation/installation steps. We currently don't compile anything for MATLAB, use maven2 for our Java build and unit tests, and use autotools for our C/C++ build and unit tests. I would like to move everything to a single build and unit test system, using maven2, but have not been able to find a plugin that will allow the C/C++ codestream to remain autotools-based and simply wrap it in a maven build. Having to rip out autotools support and recreate all the dependencies in

How do I check from within a Mojo if an artifact already exists in the local repository? I'm installing large binaries into the local Maven repository and I need to know if they already exist before attempting to download them. Solved with the help of http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook /** * The local maven repository. * * @parameter expression="${localRepository}" * @required * @readonly */ @SuppressWarnings("UWF_UNWRITTEN_FIELD") private ArtifactRepository localRepository; /** * @parameter default-value="${project.remoteArtifactRepositories}" * @required *

The version-numbers for our jars have to be longer them x.x.x. We would rather need x.x.x.x to integrate some old-fashioned self-made mechanism. This is, because we tag our software with x.x.x and as soon as we have a delivery to a customer one specific jar has to be build exactly at this point of time to fit to another backend, which communicates with our program. For that reason this one jar has the version 2.3.4.1, when generated and in next delivery of the same Version it is build and named 2.3.4.2. Now artifactory cannot handle this an doesn't save more than x.x.x.2 in some cases. So we

I am having problem building my project (using maven 2) which references some jars from a maven 1 repository. The scenario: My company has a private maven 1 repository that has the following info: <url>http://my-company-maven1-repo/maven-repository<url> It has the layout of: maven-repository |_repository |_ .... |_ .... |_vectorgraphics |_jars |_freehep_swing-2.0.3.jar |_freehep_io-2.0.2.jar What I have tried: 1. Following the guide here: relevant maven official docs My mvn2 pom.xml: <repository> <snapshots> <enabled>true</enabled> </snapshots> <id>my-repo</id> <-- I made up a temporary id

I use maven in my java project, and I don't understand how to add in native libraries. In my non-maven project I did it via CLASSPATH. I use NetBeans and maven in my current java project. If you just want to add the native libraries to the class path, try to put them in src/main/resources . Update: You can specify where resources exist in the POM: <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"> <build> ... <resources> <resource> <filtering