Hi,
the plugin causing this problem must be .... the maven-javadoc-plugin :)
the release:perform isn't that magic, you can do the same steps by hand:
- check out the code from tag (created by release:prepare)
- go to target/checkout
- execute "mvn deploy site-deploy" (site-deploy depends on the
availability of a site under distributionManagement)
If you still have the target/checkout folder, run 'mvn site' and you'll
see your project failing for the same reason as you mentioned.
There's a small difference between calling javadoc:javadoc and site. The
first one will only get its configuration from the javadoc-plugin as
specified in the build-section.
However, if the javadoc generation is generated as part of the site phase,
the configuration is picked up from the reporting-section in the pom.xml.
This can lead to different results.
Hope this helps you figuring out the real problem.
thanks,
Robert
Op Wed, 03 Sep 2014 09:22:33 +0200 schreef Sylvain Roulet
<[email protected]>:
Hello all,
I've a project since several years and I had not problem to build it.
I recently installed JDK1.7 on my Windows 7 and now my build fail during
mvn
release:perform !
The build fail saying "unmappable character for encoding utf-8".
That's true as my source file are encoded in ISO-8859-1.
So I've added <encoding> ISO-8859-1</encoding> => no change
I try to use env variable : JAVA_TOOL_OPTIONS =
-Dfile.encoding=ISO-8859-1
=> no change
<skip>true</skip> to not generate javadoc => no change...
...
and a lot of other tests
I finally realized that the option file generated in the folder
/target/checkout/target/apidocs
contains options saying that encoding is UTF-8 !
I don't think it is a maven javadoc plugin problem as if I run mvn
javadoc:javadoc, I runs successfully !
Finnaly if I use JDK 1.6 it runs perfectly... But that's not what I want
to
do.
Does any one have any idea why options are not taking into account when
maven release:perform is executed
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
