JFox Service-Oriented Application Framework
General
Using Maven
Building Maven
Errors
This FAQ answers some frequent questions already, please read the Getting Started for a quick start guide.
The Reference section contain a comprehensive user guide and documentation about the various plugins that exist for maven. Furthermore there's a maven wiki. (Don't know what that is? Read What is wiki?)
If these resources don't help you with your problem, the Maven User List is a good source for help. Lots of problems have already been discussed there, you'll probably find a solution in the mailling list archive. Most of the maven developers are subscribed to the Maven User List.
Maven developers meet via IRC: irc.codehaus.org:6667, channel #maven But please don't ask for solutions to maven problems there, as maven user problems should be discussed at the mailing list for several good reasons (e.g. mail archive, more subscribers) and usually you get a quick answer on the mailing list.
${maven.junit.fork}
property to
yes.
cvs [log aborted]: there is no version here; do 'cvs checkout' first
ChangeLog found: 5 entries
When you run the cvs change log report in maven, the report hangs or the final output is blank.
This is typically caused by the cvs command not running correctly. The first port of call is to check maven.log, search the file for "SCM"
2003-02-26 06:42:04,975 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Working Directory: D:\Data\workspace\maven
2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Command Line[0]: cvs
2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Command Line[1]: -d
2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Command Line[2]: :pserver:bwalding@cvs.apache.org:/home/cvsroot
2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Command Line[3]: log
2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator - SCM Command Line[4]: -d 2003-01-27
Try running the command that you find in the log file manually. The results typically speak for themselves.
maven.test.skip and maven.test.failure.ignore.
Heed the warnings!
There is a bug in Maven Beta 9 that causes jars to be produced with invalid manifests. The problem with the manifests only comes to light when using the jars inside an Extension-aware program - eg. Tomcat.
If you are running beta-10 or later, you do not need to do this
http://projects.walding.com/maven-patches/maven-jar-plugin-1.0.jar resolves this issue and is built from CVS between beta 9 and 10.
Installation
rm -r $MAVEN_HOME/plugins/maven-jar-plugin-1.0
rm $MAVEN_HOME/plugins/maven-jar-plugin-1.0.jar
wget -P $MAVEN_HOME/plugins http://projects.walding.com/maven-patches/maven-jar-plugin-1.0.jar
A common symptom is that the Jelly or Ant tag are output instead of being processed. See MAVEN-156.
The solution is to add the JAXP system property via the Jelly script.
${systemScope.setProperty('javax.xml.transform.TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
<ant:style in="${basedir}/some.xml" out="${maven.build.dest}/other.xml" style="${basedir}/sheet.xsl" processor="trax"/>
Also make sure that Xalan is declared as dependencies in your project file:
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.3.1</version>
<url>http://xml.apache.org/xalan/</url>
</dependency>
maven -DartifactId=artifactID -DgroupID=GROUPID -Dversion=VERSION plugin:download
BUILD FAILED
null:58:46:
<x:parse> Invalid source argument. Must be a String, Reader,
InputStream or URL. Was type; java.io.File with value:
/home/jvanzyl/js/com.werken/drools/target/jdepend-raw-report.xml
Total time: 12 seconds
This problem has been observed when a version of Jelly used as a dependency is different than the one distributed with Maven. This is the version of Jelly that is distributed with Maven 1.0-beta-8. If you align your versions of Jelly you should be able to generate your site. We hope to alleviate these problems with real ClassLoader isolation using Classworlds.
ant -f build-bootstrap.xml