well, i have thought about this for about 90 seconds, but we need to start
somewhere:
http://cwiki.apache.org/confluence/display/WICKET/Wicket+Component+JAR+Metadata
if people could pitch in and add ideas to the list, we can pare it down
later
brian.diekelman wrote:
Jonathan Locke
Looking good, I just added metadata about javascript libraries (versions
etc)...
Jonathan Locke wrote:
well, i have thought about this for about 90 seconds, but we need to start
somewhere:
http://cwiki.apache.org/confluence/display/WICKET/Wicket+Component+JAR+Metadata
if people could pitch
was thinking the same thing and would be the icing on the cake. website
never shuts down... crawler adds components and the demos just appear on the
site automagically via OSGi.
mebbe we need cheeser's transparent OSGi first though?
brian.diekelman wrote:
Jonathan Locke wrote:
-
this sort of marketplace might give JSF's claim to have lots of prefab
components a real run for the money... i think with some effort, we could do
this in a few weeks...
Jonathan Locke wrote:
was thinking the same thing and would be the icing on the cake. website
never shuts down...
A friend of mine has a motto Appearence is everything. If this
component marketplace also get a reasonably sexy frontend it could be
a real winner. We have developed a kind of Theme marketplace for our
photo album software but since we are tech guys we suitably named it
Skin repository
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
uh, this library is of course a web site... ;-)
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
Exactly what I meant with the mail to dev a week ago. So I think it's
all good. And actually could raise the wicketstuff standard.
+1!, I guess binding since im a wicketstuff developer:)
Jonathan Locke wrote:
uh, this library is of course a web site... ;-)
Jonathan Locke wrote:
my RSI
+1
On Wed, Jun 18, 2008 at 1:28 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Exactly what I meant with the mail to dev a week ago. So I think it's all
good. And actually could raise the wicketstuff standard.
+1!, I guess binding since im a wicketstuff developer:)
This is the original idea of wicket-library.com iirc. Perhaps we
should try to revive this effort and implement it using your ideas.
Unfortunately I'm strung for time with Wicket in Action and getting a
social life back when that is completed.
Martijn
On Wed, Jun 18, 2008 at 1:15 PM, Jonathan
I'd be very happy to do some effort at it, I dont have much of a social
life and im not writing a book. So I have time:)
But I do need some pointers getting started.
Martijn Dashorst wrote:
This is the original idea of wicket-library.com iirc. Perhaps we
should try to revive this effort and
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
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
Don't we already have that with Maven?
I like the idea but I think that the minor extra step of turning your
shared components into their own module is a good thing, keeps
everything sane.
However it might be nice to have a repo that can publish all this to
(the repo1 server is a pain to
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
why not crawl a whole list of repos? or as many as we can find?
Brill Pappin wrote:
Don't we already have that with Maven?
I like the idea but I think that the minor extra step of turning your
shared components into their own module is a good thing, keeps
everything sane.
However
That was exactly my question... I think the process you go through to
do that is important so the rest of us are not tearing out our hear
trying to work with 3rd party components.
- Brill
On 18-Jun-08, at 9:16 AM, John Krasnay wrote:
How would this be different than just deploying a bunch
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
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,
got it... like the idea (useful for others besides wicket as well)
That is sort of done already with the groupId/artifactId structure,
but I get what you going for here.
It would be fairly trivial to add meta data to the library but its
much more of a pain to crawl that... what would be
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
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
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
Oh, I see now. You want to create something like
http://mvnrepository.com, right? That would be great. I use that site
all the time.
jk
On Wed, Jun 18, 2008 at 07:16:32AM -0700, Jonathan Locke wrote:
there is already pom meta data in the repo isn't there?
Jonathan Locke 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
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
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
of course not. comments and ratings are /mixed in/ on the site via some db
assoc. all else is metadata. thats what i meant.
Brill Pappin wrote:
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
Jonathan Locke wrote:
- (only signed) jars could be automatically picked up by some naming
pattern from maven repos and deployed as live demos
Once a signed jar is identified, what about something like OSGi to deploy
it?
- metadata would define an application name
- load the
29 matches
Mail list logo
