cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-1791) [cocoon-deployer-core] Make exclusive mode settable by the client library (e.g. the maven-plugin)
Date Sun, 05 Mar 2006 14:43:39 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1791?page=all ]
     
Reinhard Poetz closed COCOON-1791:
----------------------------------

    Resolution: Fixed

attribute "exclusive" was removed from cocoon-deploy.xml schema; adapted all block.xml files
(that I found) so that they validate against the new schema again. I also adapted code that
relies on the generated Java sources

> [cocoon-deployer-core] Make exclusive mode settable by the client library (e.g. the maven-plugin)
> -------------------------------------------------------------------------------------------------
>
>          Key: COCOON-1791
>          URL: http://issues.apache.org/jira/browse/COCOON-1791
>      Project: Cocoon
>         Type: Sub-task
>   Components: - Build System: Maven
>     Reporter: Reinhard Poetz
>     Assignee: Reinhard Poetz

>
> Currently the "exclusive mode" is set as attribute of the <cocoon>-element in the
deployment descriptor. I think that's wrong as this shouldn't be part of the deployment descriptor
(describes WHAT has to be deployed but not HOW) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message