Wicket Component JAR Metadata commented on by Antony Stubbs (Feb 09, 2009).

Comment:

A lot of components have their 'demo' or 'example' apps/panels in separate jars - see some of the wicket-stuff packages.
I would suggest adding an optional maven artifact identifier to locate the jar containing the demo class.

The dependencies for the component are going to have to be managed in some automated fashion. Isn't using existing Maven or Ivy dependency resolution /systems viable? (on contrast to your comment regarding maven)

Reply via email to