maven-2

I would like my eclipse PMD plugin configuration to access the same standard ruleset files as the maven-pmd-plugin . You can configure the maven pmd plugin to use a custom set of rule sets like this: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-pmd-plugin</artifactId> <version>2.5</version> <configuration> <rulesets> <!-- Two rule sets that come bundled with PMD --> <ruleset>/rulesets/braces.xml</ruleset> <ruleset>/rulesets/naming.xml</ruleset> <!-- Custom local file system rule set --> <ruleset>d:\rulesets\strings.xml</ruleset> <!-- Custom remote rule set accessed

I'd like to embed Maven or the library that does all the magic into my Java application. The keypoints : They are two tasks I want to perform : 1/ Publishing a jar in local repository 2/ Publishing a jar in a private enterprise repository (Nexus) All required jars MUST be located in a public Maven repository The jars SHOULD be Maven version agnostic (ie not specific to Maven 2 or 3) If you can , please provide a snippet with your response. Brett Porter Here is an example embedding Maven 2 libraries: CentralRepositoryService.java pom.xml Instead of looking up the project builder, you can look

I tried to convert a project to a maven one... it has its .java files in other location than /src/main/java , when i run maven install, all the files (.hbm , .xml) except those .class occurs in my jar. This is build part from pom.xml : <build> <resources> <resource> <directory>${basedir}/src</directory> <excludes> <exclude>**/*.java</exclude> </excludes> </resource> </resources> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> <fork>true</fork> <compilerVersion>1.5</compilerVersion> <compilerArguments> <encoding>UTF-8<

I suppose this is kinda obvious, but I still judge it as a shortcoming... I have 23 Mavenized projects. I'm now adding the <scm> bit because I've started using the release plugin. Here was my thought process: I'll add the <scm> section only in my company base POM, and parameterise the URLs with properties, e.g. <scm> <connection>${scmBaseConnection}/${scm.module}/${scm.edition}</connection> <developerConnection>${scmBaseConnection}/${scm.module}/${scm.edition}</developerConnection> <url>${fisheyeBaseUrl}/${scm.module}</url> </scm> Then each project root (aggregator) POM need only declare its

I have to generate sources using wsimport and i assume that it should go to /target/generated-sources/wsimport rather than /src/main/java. The problem is that wsimport needs target folder created before execution and it fails. Can I create that dir first using any maven plugin. I can do it using ant but i prefer to keep it in POM. I have to generate sources using wsimport and i assume that it should go to /target/generated-sources/wsimport rather than /src/main/java. This is a correct assumption. The problem is that wsimport needs target folder created before execution and it fails. Can I