[
https://issues.apache.org/jira/browse/TAP5-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716623#comment-13716623
]
Denis Stepanov commented on TAP5-2112:
--
Main use-case is to build WARs for different environments just by including a
new module.
task customWar1(type: War) {
manifest {
attributes 'Tapestry-Module-Classes': "x.y.z.CustomModule1"
}
}
task customWar2(type: War) {
manifest {
attributes 'Tapestry-Module-Classes': "x.y.z.CustomModule2"
}
}
> Support autoloading modules from app.war/META-INF/MANIFEST.MF
> -
>
> Key: TAP5-2112
> URL: https://issues.apache.org/jira/browse/TAP5-2112
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
>Affects Versions: 5.3.6
>Reporter: Denis Stepanov
>Priority: Minor
> Attachments:
> 0001-TAP5-2112-Autoload-should-load-MANIFEST.MF-from-the-.patch
>
>
> Correct manifest location for WAR is .war/META-INF/MANIFEST.MF
> Use-case is to support manifest generated by gradle:
> task customWar(type: War) {
> manifest {
> attributes 'Tapestry-Module-Classes': "x.y.z.TapModule"
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira