...
http://www.nabble.com/idea%3A-automatic-component-repo-td17979177.html
(Note: Some of these may be duplicates of java or maven meta info... we could omit dups)
No Format |
---|
META-INF/components.xml:
<components>
<component name="component1"
version="0.9.0"
search-keywords="slider,ui,java">
<description>
This text describes the component.
</description>
<publisher name="my components"
site=" |
...
http://mycomponents.com/slider |
...
"
email="support@mycomponents.com"/>
<legal>
<copyright>
Copyright 2009-2010, John Q. Public. All Rights Reserved.
</copyright>
<license name="Apache 2.0">
Full license text goes here so it travels with the JAR.
</license>
</legal>
<requirements>
<library name="wicket" version="1.3"/>
<library name="YUI" version="4.0"/>
</requirements>
<resources>
<source-code url="component1-sources.jar"/>
<screenshots url="jar:META-INF/component1/screenshots"/>
<demo class="com.mycomponents.demo.DemoPanel"/>
</resources>
</component>
<component name="component2"/>
</components>
META-INF/component1/screenshots/1.jpg
META-INF/component1/screenshots/2.jpg
|
...
What else?
- Javascript-Libraries=YUI 4.0,DOJO 1.0
Should this be XML for better structure instead of using META-INF?
OSGi:
Some of the properties above would be better represented by OSGi (if you still want to use that)
...
reference: http://www.javaworld.com/javaworld/jw-03-2008/jw-03-osgi1.html?page=2
...
Wicket component jars should be fully self-describing, so i think wicket meta information has to be independent of any external technology such as maven or osgi. – Jonathan Locke