The number of steps required to configure a Tapestry Component library are too
numerous; a single contribution so a new service should configure classpath,
prefix, etc.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TAP5-975
URL: https://issues.apache.org/jira/browse/TAP5-975
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
I was just updating the documentation on creating a component library, and
there's now seven steps.
It seems to me that some thing:
public void contributeComponentLibrary(Configuration<ComponentLibraryDef>
configuration)
{
configuration.add(new ComponentLibraryDef("happy", "org.example.happylib",
"1.0"));
}
... could cover it all (with perhaps alternate constructors for more precise
control over whitelisted assets).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
