You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/03/27 17:48:44 UTC
[jira] Commented: (MPCASTOR-11) automated builds hang when castor
warnings are on
[ http://jira.codehaus.org/browse/MPCASTOR-11?page=comments#action_62077 ]
Lukas Theussl commented on MPCASTOR-11:
---------------------------------------
Please note that the castor plugin is currently not maintained by the Maven team anymore. It has been deprecated after Maven-1.1-beta2 and will not be distributed with Maven-1.1 anymore. See http://maven.apache.org/maven-1.x/reference/backwards-compatibility.html.
> automated builds hang when castor warnings are on
> -------------------------------------------------
>
> Key: MPCASTOR-11
> URL: http://jira.codehaus.org/browse/MPCASTOR-11
> Project: maven-castor-plugin
> Type: Bug
> Environment: running from anthill pro 2.5 on solaris
> Reporter: jake pezaro
> Priority: Minor
>
>
> enabling castor warnings causes castor to prompt the user when overwriting generated source files. in situations where the source directory cannot be cleaned (eg when running the clover report plugin) this causes the automated build to hang.
> this can be worked aroud by turning the warnings off, however this causes castor overwrite files with name clashes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira