Don't bother with the comments... at least not in the metadata... once
you can identify a wicket component you can get everything else you
need from the POM (name, description, site etc).
All you really need to be able to do is tag a wicket module thats easy
for a crawler to get at.
In fact you could even just attach your wicket meta tag as an artifact
and deploy it along with the module itself. say a "text" artifact that
deployed along with the module and would reside next to it (use the
same name as the artifact, only with a classifier of "wicketstuff" or
something else useful).
- Brill
On 18-Jun-08, at 3:21 PM, Jonathan Locke wrote:
let's start a wiki page listing all the metadata people can think of
that
might be useful and then vote on the initial list...
only thing i can think of to "mix in" would be comments and
ratings. that
could come later.
Brill Pappin wrote:
Yes, and there is repo metadata as well...
that lists things like version etc.
- Brill
On 18-Jun-08, at 10:16 AM, Jonathan Locke wrote:
there is already pom meta data in the repo isn't there?
Jonathan Locke wrote:
why not? you just do it slowly like google crawler. stuff might
not show
up for hours or days, but at least it is all there.
Brill Pappin wrote:
Well I could write a plugin easily enough....
I think the issue is where the metadata is stored and how your
going
to find them... you don't want to have to download every library
from
every repo just to find them.
- Brill
On 18-Jun-08, at 10:03 AM, Jonathan Locke wrote:
bingo!
we just need to get the metadata right.
Brill Pappin wrote:
Now that is an interesting idea...
Use standard maven modules, but write a plugin that adds a
little
extra info for the "wicket stuff site" ??
- Brill
On 18-Jun-08, at 9:53 AM, Jonathan Locke wrote:
also, locating components automatically via crawling
means no central point of organization creating an admin
bottleneck
the web IS the component db and all components published to
maven repos just get picked up if they have the right metadata
Nino.Martinez wrote:
Not much, but currently there arent such an effort.. And
making it
available via an website just makes it more accessible.
John Krasnay wrote:
How would this be different than just deploying a bunch of
fine-
grained
JARs via Maven?
jk
On Wed, Jun 18, 2008 at 02:49:06AM -0700, Jonathan Locke
wrote:
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: users-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17983192.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17983422.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17983672.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17989855.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
