my RSI is bad so please forgive the terseness. the idea: - make an automated wicket component library - define packaging structure for wicket library components - structure of package would define component metadata like svn, faq, help, etc (probably in meta.inf created from maven pom info by maven guru) - (only signed) jars could be automatically picked up by some naming pattern from maven repos and deployed as live demos - container would be simple to write (no db hassles... just use maven and packaging) - everyone makes their components and demos in a standard way so we can stop asking around about what functionality exists
-- View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17979177.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
