Re: Handle XSDs with Maven and Nexus?

Hi! Thanks for all suggestions. I will contemplate this and see what we come up with. Cheers Thomas On 8 April 2013 16:31, Wayne Fay wayne...@gmail.com wrote: How would you publish a XSD for a project and make it available for other Maven builds? I expect that MRRP would be a part of the

Re: Handle XSDs with Maven and Nexus?

FWIW, I also think this is a typical use case for maven remote resources plugin. I've used it in the past to store and version our checkstyle, pmd, and so config files, and it has been working fine for years. Cheers 2013/4/9 Thomas Sundberg t...@kth.se Hi! Thanks for all suggestions. I will

RE: Handle XSDs with Maven and Nexus?

I'll package custom XSDs and XSD extensions into the resources folder of my distro..for safekeeping ISO XSDs I'll leave alone and assume the client can contact the site directly for the XSD http://www.liquid-technologies.com/Tutorials/XmlSchemas/XsdTutorial_03.aspx Alternative Strategies?

Re: maven-compiler-plugin, fork, and Windows classpath length

uhm maybe with setting env var CLASSPATH (I think surefire do that) BTW add a jira entry (note: I don't have windauze to test the change :-) ) 2013/3/23 Laird Nelson ljnel...@gmail.com: I am using maven-compiler-plugin version 3.0. We use fork=true. We are seeing (I am pretty certain;

Re: maven-compiler-plugin, fork, and Windows classpath length

I think we solved all of that with the CLASSPATH env var in surefire; I believe it pushes the limit to 64K. 64K must be enough for everyone :) Kristian 2013/4/9 Olivier Lamy ol...@apache.org: uhm maybe with setting env var CLASSPATH (I think surefire do that) BTW add a jira entry (note: I

Re: maven-compiler-plugin, fork, and Windows classpath length

btw that will fix the issue for forked compilation only (not for in process compilations) 2013/4/9 Kristian Rosenvold kristian.rosenv...@gmail.com: I think we solved all of that with the CLASSPATH env var in surefire; I believe it pushes the limit to 64K. 64K must be enough for everyone :)

Alternative logging / xml output

Hi all, Is there a way to have maven log as xml to a file in addition to or instead of the default text logger? I want to easily create an end of build summary with reactor info, error and warning summary. Slurping xml will be easier that parsing raw text. Please let me know if maven does

Re: Alternative logging / xml output

Hi Peter, Is there a way to have maven log as xml to a file in addition to or instead of the default text logger? From the website, it sounds like Maven will switch to using SLF4J from Maven 3.1.0 onwards [1], which is great. In the meantime though, I'm not sure whether what you want is

How to create two projects, one of them is using the other ?

Hi, I want to create a project ServerA that need to use a jar project called shareJar , how to create a such construction using maven : --ServerA | ^ | | -shareJar Thanks, your help is appreciated. -- View this message in context:

Re: How to create two projects, one of them is using the other ?

I think you need this: http://www.sonatype.com/books/mvnex-book/reference/multimodule.html Alonso Isidoro Roman. Mis citas preferidas (de hoy) : Si depurar es el proceso de quitar los errores de software, entonces programar debe ser el proceso de introducirlos... - Edsger Dijkstra My

Re: How to disable “Test Source Xref” report generation

I think per default Maven simply executes all reports, in your case jxr and test-jxr. But you may configure specific reports: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId version${plugins.jxr.version}/version reportSets reportSet

Re: How to create two projects, one of them is using the other ?

Thank you very match, this was helpful . -- View this message in context: http://maven.40175.n5.nabble.com/How-to-create-two-projects-one-of-them-is-using-the-other-tp5753312p5753317.html Sent from the Maven - Users mailing list archive at Nabble.com.

Maven 3.0.5: site plugin or documentation broken?

I'm trying to get the maven site plugin to do my bidding but have gotten lost... Given the following simple POM's pom.xml: project modelVersion4.0.0/modelVersion groupIdch.pecunifex/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version packagingpom/packaging

release:perform goal fails on multi-module project

I have a multi-module Maven project which I am trying to execute the release:perform goal on and it is failing because it is trying to get a dependency for one of the modules from the central maven repo. The problem is the dependency it is trying to get is a different module from the same project

Re: release:perform goal fails on multi-module project

Here's the problem: maven-javadoc-plugin:2.9:aggregate (report:aggregate) This is executed as part of root pom, while its modules haven't been built yet. It is not a maven-release-plugin issue, it would also happen if you would run 'mvn site' as the first goal after the release, since the

RE: maven-compiler-plugin, fork, and Windows classpath length

Laird and Team yep..known issue ...push any environment variable such as CLASSPATH over 64k or any build-string over 2k do a cmd.exe /C java.exe %MASSIVE_CLASSPATH% MyFile.java and watch the fireworks My workaround surefire limited to 2.4.2 ..anything above that and surefire will attempt to

Re: How to disable “Test Source Xref” report generation

yes, see Selecting Reports from a Plugin: Configuring Report Sets in [1] notice you're using the new configuration format (ie reportPlugins inside maven-site-plugin), which is not recommended at the moment [2] Regards, Hervé [1]

Re: release:perform goal fails on multi-module project

Thanks Robert, I was starting to suspect it was actually the site goal causing the problem. I didn't find any goal called aggregateAtEnd, are you referring to the aggregate parameter [1]? [1] http://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html On Tue,

Re: Maven 3.0.5: site plugin or documentation broken?

1. warning if you don't define plugin version you can believe Maven 3 doc, version is taken from pluginManagement: coded here [1] But I must confess I never tried with CLI, since we use to continue defining plugin version directly to keep Maven 2.x compatibility I just tried and confirm this