tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-394) Add a JVM system property to allow additional modules to be loaded at Registry startup
Date Mon, 01 Dec 2008 18:35:44 GMT

     [ https://issues.apache.org/jira/browse/TAP5-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship updated TAP5-394:
--------------------------------------

    Summary: Add a JVM system property to allow additional modules to be loaded at Registry
startup  (was: Add a JVM system property to allow additional modules to be loaded Registry
Startup)

> Add a JVM system property to allow additional modules to be loaded at Registry startup
> --------------------------------------------------------------------------------------
>
>                 Key: TAP5-394
>                 URL: https://issues.apache.org/jira/browse/TAP5-394
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Sometimes, often in the context of a unit test suite, we can't rely on the Tapestry Manifest
entry to specify which classes to load; it would be nice if there was a command-line option,
a JVM system property, that could be used in concert with the maniest entry to identify additional
classes to load.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message