You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/23 19:10:48 UTC
[jira] [Commented] (TAP5-2112) Support autoloading modules from
app.war/META-INF/MANIFEST.MF
[ https://issues.apache.org/jira/browse/TAP5-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716615#comment-13716615 ]
Howard M. Lewis Ship commented on TAP5-2112:
--------------------------------------------
Work around: Use the @ImportModule annotation from your application's main module.
> 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