If you're not using version 2.0-beta-5 of the site plugin then I recommend
you try it. I had problems with module and parent links with a similar
configuration to yourself but it all worked fine once I started using
beta-5. I would also recommend the latest version of the project reports
plugin
I would differentiate between building an ear for the purposes of deploying
the war for integration testing, and building an ear for distribution /
release. The latter I would create a separate project for, whilst the
former I would bind to the pre-integration-test phase of the war project
(using
This works for all situations although we mainly use it to include build
information on our demo web apps.
Create a properties file e.g. build.properties where any build variable
properties can be accessed by the java/jstl etc. Have your maven.xml build
update this file using the ant
You can override project properties on the maven command line:
maven -Dmaven.test.skip=false
If you have one environment where you want testing on by default and
another where you want it off set maven.test.skip as appropriate in
build.properties rather than project.properties.
Andy
You should just be able to use multiproject:site. It works for me.
Andy
For the latest data on the economy and society
consult National Statistics at http://www.statistics.gov.uk
**
Please Note: Incoming and outgoing
The artifact plugin does this. I changed my jar plugin to use
artifact:deploy instead of deploy:artifact so I could deploy jars to the
file system.
Andy
1. If you look at the war plugin docs you'll see the war.bundle dependency
property e.g:
dependency
groupIdjdom/groupId
artifactIdjdom/artifactId
versionb9/version
properties
war.bundletrue/war.bundle
/properties
/dependency
2. There may be a better
, this is a local repository with the jars of our interest. Is it
enough to declare a maven.repo.local in the .properties file pointing to a
local directory on my PC containing what I need?
Marco
- Original Message -
From: Andrew Chapman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 02
The maven-jar-plugin-1.3.jar that ships with maven rc1 uses deploy:artifact
to deploy the jar which does not generate the md5 file. If you change the
jar plugin to use artifact:deploy - not only will it generate the md5 file
for you it also allows more flexible deployment methods e.g. file system
