Re: Maven does not find existing artifacts in local repository because it looks in central where they are not?

Running Maven with -x and including the relevant part of the log might help. We are all guessing what you have screwed up. Of course Maven has to be able to use stuff that is not in Maven Central otherwise none of us could ever develop a library or a project with more than one piece. You

Re: Maven does not find existing artifacts in local repository because it looks in central where they are not?

Hi Christian, Christian Eugster wrote: Hi as I understand, there is a central repository for maven artifacts: central (http://repo.maven.apache.org/maven2 http://repo.maven.apache.org/maven2) and a local one (${user.home}/.m2/repository. What I do not understand is, why after a mvn test

Re: Aggregating Javadocs in an assembly

I'd probably configure the asciidoc plugin to run at the site phase, and change its output directory to target/site. That is, unless you really want to package the html as an a separate artifact in addition to putting it on the site. In that case, I might use exec-maven-plugin (or another plugin)

[ANN] Exec Maven Plugin 1.4.0 Released

Hi, The Mojo team is pleased to announce the release of the Exec Maven Plugin version 1.4.0. The plugin helps with execution of system and Java programs. http://mojo.codehaus.org/exec-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin

Using a file that was pulled in via maven

Hi all, I am trying to use a file I believe has been pulled in to the system via Maven dependency. This is a JSON file. I am using this JSON file to do a simple Schema Validation using Rest Assured. The validation steps I believe I have down no problem, however, I cannot seem to validate against

Proper way to have my Mojo instrument both main and test classes

I've written a Maven plugin. When it runs, I want it to process both main classes and test classes. I originally thought that setting my mojo's defaultPhase to PROCESS_CLASSES would handle this, but I've come to find out that PROCESS_CLASSES is only for main classes. There seems to be separate

maven-release-plugin / SVN credentials

Hello, I have a problem with the maven-release-plugin using the SVN credentials (details below). I always get an SVN authorization error. It seems that the release plugin does not use the existing credentials. Unfortunately I'm even not sure whether it is a problem of the maven-release-plugin

Re: Aggregating Javadocs in an assembly

Christopher, Thanks for the info. I am going with the approach of generating my javadocs as part of the mvn site. This works great. Now the next problem: Under my top level project I have a project called docs. It is a collection of asciidoc source files that I use the asciidoc plugin

Re: Plugin dependency resolution from plugin pom?

Hi Gary, I'm trying to patch a third-party plugin at the moment as a temporary workaround for a problem. (I don't want to get into details because it's not important) Since the workaround is temporary, could you not simply clone the plugin's SCM repository to a local Git repository, then

RE: Plugin dependency resolution from plugin pom?

plugin.xml requiresDependencyResolution String Flags this Mojo as requiring the dependencies in the specified class path to be resolved before it can execute: compile, runtime, test,