martijn, banning policies are issued by repository owners. i don't
know which repo you're referring to as "the maven repository".
central? apache?
i suggested setting up or reusing a repo that would be mainly for
wicket components, and owned by the project/ community. advantages:
- we simply don't ban wickethub's crawler
- we provide guidelines for wicket developers to easily publish their
artifacts (and possibly check if metadata is present, etc)
as for the rest ('non-compliant'), that would be maintained manually
so no crawling involved.
francisco
On Tue, Dec 16, 2008 at 8:55 PM, Martijn Dashorst
<martijn.dasho...@gmail.com> wrote:
> For perusing the maven repository, one should contact the guys from
> nexus. They have an api for reading/indexing the repository. Don't
> crawl the repository-that will surely get you banned.
>
> Martijn
>
> On Tue, Dec 16, 2008 at 8:51 PM, francisco treacy
> <francisco.tre...@gmail.com> wrote:
>> we could cover automatic updates of 'compliant' maven artifacts - and
>> the rest (non-compliant, svn source code, snippets) maintained
>> manually.
>>
>> [ compliant = stick to metadata described here:
>> http://cwiki.apache.org/confluence/display/WICKET/Wicket+Component+JAR+Metadata
>> ]
>>
>> from the app side this means developing the discovery process
>> mentioned in the "idea..." thread, which seems really feasible.
>>
>> however to start including the aforementioned 'compliant' artifacts,
>> it would be actually useful to know where to find already existing
>> ones. so, has anyone taken on the maven repo / metadata plugin / etc
>> side? is there something available for reuse?
>>
>> hopefully if we can provide a dead-easy procedure to package wicket
>> components *and* a place to store them (a maven repo -- how about
>> apache servers?) , then more and more components will become
>> 'compliant' ... which means more and more will be eventually
>> discovered and registered.
>> still, i think it's fair to support non-compliant components as well.
>> if people use the app, those are very likely to be modified and kept
>> up-to-date.
>>
>> francisco
>>
>>
>>
>>
>> On Tue, Dec 16, 2008 at 5:00 PM, Jonathan Locke
>> <jonathan.lo...@gmail.com> wrote:
>>>
>>>
>>> you have a point. but while it's true it's not completely general, i'm
>>> personally only interested in a library of components. and at present
>>> components delivered by maven.
>>>
>>>
>>> francisco treacy-2 wrote:
>>>>
>>>> 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
>>>> <mbosteels....@gmail.com> wrote:
>>>>> On Mon, Dec 15, 2008 at 10:43 PM, Jonathan Locke
>>>>> <jonathan.lo...@gmail.com>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: users-unsubscr...@wicket.apache.org
>>>>>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>>
>>>>>> --
>>>>>> 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: users-unsubscr...@wicket.apache.org
>>>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/wickethub.org-tp20995774p21035901.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
