interesting post.
there's also 
http://www.nabble.com/Open-wicket-component-collection-anywhere--td19450431.html

however sometimes 'automatic' doesn't work simply because people don't
mavenize their projects, it's just a bunch of files thrown in an svn
repo, or even a snippet of code. and you can't force them to use a
certain container, maven plugin, etc. imagine when it doesn't fit (a
snippet or an ide plugin).

depending on the projects' structure i'll take a look and try to find
the way to automatically pick up as much as possible.

i'm thinking of publishing wickethub's source code so it feels more of
a community project.

francisco


On Tue, Dec 16, 2008 at 10:08 AM, Maarten Bosteels
<[email protected]> wrote:
> On Mon, Dec 15, 2008 at 10:43 PM, Jonathan Locke
> <[email protected]>wrote:
>
>>
>>
>> oh yeah, there's a post where we started figuring out some details about
>> how
>> this would work somewhere on this list
>
>
> Here it is :
> http://www.nabble.com/idea:-automatic-component-repo-to17979177.html
>
> Maarten
>
>>
>>
>>
>> Jonathan Locke wrote:
>> >
>> >
>> > this is cool, although i still think this should be auto-updated through
>> a
>> > maven registry crawler. if everyone put the right meta information in
>> > their wicket jars, this resource registry would be entirely automatic,
>> > always fresh, running demos, etc...
>> >
>> >
>> > francisco treacy-2 wrote:
>> >>
>> >> i came up with an idea during the last weeks, having some trouble
>> >> finding wicket resources.
>> >>
>> >> although we have wicketstuff (which is great, and even more now with
>> >> jeremy's awesome job of reorganizing it)  i feel there are still lots
>> >> of components, plugins or tools that are lost in cyberspace. thought
>> >> it would be neat to keep a sort of "registry" with useful information
>> >> for wicket developers.
>> >>
>> >> so i decided to quickly put some bits together from an old project and
>> >> rebaptised it as "the wicket hub" - a simple prototype @
>> >> http://wickethub.org.
>> >> it's meant to be flexible, so except for the title there are no
>> >> required fields when you add/edit a "module". there are already some
>> >> examples.
>> >>
>> >> let me know what you think about features, its relation with
>> >> wicketstuff and if it's usable, etc. or even if the whole thing makes
>> >> no sense - any suggestions appreciated.
>> >>
>> >> francisco
>> >>
>> >> ps: goes without saying, but [disclaimer: it's completely
>> >> experimental] and be aware the place it's hosted is more like a
>> >> shoebox than a server :)
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [email protected]
>> >> For additional commands, e-mail: [email protected]
>> >>
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/wickethub.org-tp20995774p21022750.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]

Reply via email to