|
»
»
idea: automatic component repo
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
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 |
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
uh, this library is of course a web site... ;-)
|
|
|
Re: idea: automatic component repo
by Nino.Martinez
::
Rate this Message:
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 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 >> >> >> >> >> >> > > -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Hbiloo
::
Rate this Message:
+1
On Wed, Jun 18, 2008 at 1:28 PM, Nino Saturnino Martinez Vazquez Wael < nino.martinez@...> 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:) > > Jonathan Locke wrote: > >> 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 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 >>> >>> >>> >>> >>> >>> >>> >> >> >> > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Azzeddine Daddah www.hbiloo.com |
|
|
Re: idea: automatic component repo
by Martijn Dashorst
::
Rate this Message:
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 Locke <jonathan.locke@...> wrote: > > 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 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-tp17979177p17980575.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Nino.Martinez
::
Rate this Message:
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 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 Locke > <jonathan.locke@...> wrote: > >> 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 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-tp17979177p17980575.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > > > -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by John Krasnay
::
Rate this Message:
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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Nino.Martinez
::
Rate this Message:
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: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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 get things published to. As we work, we'll be publishing some of it to a public repo that others can reference, however we're not there yet. I think most other groups using maven use their own repo (but that might be a pipe dream)... so what we really need is a place to publish our open repos that contain wicket related stuff (assuming wicket-stuff isn't suitable). - Brill Pappin On 18-Jun-08, at 5:49 AM, 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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
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
|
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
why not crawl a whole list of repos? or as many as we can find?
|
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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 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: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> >> -- >> -Wicket for love >> >> Nino Martinez Wael >> Java Specialist @ Jayway DK >> http://www.jayway.dk >> +45 2936 7684 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > 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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
bingo! we just need to get the metadata right.
|
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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 better if there was some way to add indexing information to the Maven metadata that already resides in the repos. e.g. see: http://repo1.maven.org/maven2/activemq/activemq-axis/maven-metadata.xml Failing that, the POM which is more likely possible without making changes to Maven. There is also something that Archiva does with repos where it adds some sort of index... some of that work might be utilized as a scraper. Anyway, interesting idea. - Brill On 18-Jun-08, at 9:56 AM, Jonathan Locke wrote: > > > 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 it might be nice to have a repo that can publish all this to >> (the repo1 server is a pain to get things published to. >> >> As we work, we'll be publishing some of it to a public repo that >> others can reference, however we're not there yet. I think most other >> groups using maven use their own repo (but that might be a pipe >> dream)... so what we really need is a place to publish our open repos >> that contain wicket related stuff (assuming wicket-stuff isn't >> suitable). >> >> - Brill Pappin >> >> On 18-Jun-08, at 5:49 AM, 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: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17983260.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>> >>>> -- >>>> -Wicket for love >>>> >>>> Nino Martinez Wael >>>> Java Specialist @ Jayway DK >>>> http://www.jayway.dk >>>> +45 2936 7684 >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> >>> >>> -- >>> 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: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > 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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
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.
|
|
|
Re: idea: automatic component repo
by Jonathan Locke
::
Rate this Message:
there is already pom meta data in the repo isn't there?
|
|
|
Re: idea: automatic component repo
by John Krasnay
::
Rate this Message:
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: > > > > > > 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: users-unsubscribe@... > >>>>>>>> For additional commands, e-mail: users-help@... > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> --------------------------------------------------------------------- > >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... > >>>>>>> For additional commands, e-mail: users-help@... > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> -- > >>>>>> -Wicket for love > >>>>>> > >>>>>> Nino Martinez Wael > >>>>>> Java Specialist @ Jayway DK > >>>>>> http://www.jayway.dk > >>>>>> +45 2936 7684 > >>>>>> > >>>>>> > >>>>>> --------------------------------------------------------------------- > >>>>>> To unsubscribe, e-mail: users-unsubscribe@... > >>>>>> For additional commands, e-mail: users-help@... > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> -- > >>>>> 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: users-unsubscribe@... > >>>>> For additional commands, e-mail: users-help@... > >>>>> > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: users-unsubscribe@... > >>>> For additional commands, e-mail: users-help@... > >>>> > >>>> > >>>> > >>> > >>> -- > >>> 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: users-unsubscribe@... > >>> For additional commands, e-mail: users-help@... > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@... > >> For additional commands, e-mail: users-help@... > >> > >> > >> > > > > > > -- > 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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: idea: automatic component repo
by Brill Pappin
::
Rate this Message:
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: users-unsubscribe@... >>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -Wicket for love >>>>>>> >>>>>>> Nino Martinez Wael >>>>>>> Java Specialist @ Jayway DK >>>>>>> http://www.jayway.dk >>>>>>> +45 2936 7684 >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>> For additional commands, e-mail: users-help@... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> 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: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>>> >>>> >>>> -- >>>> 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: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >>> >> >> > > -- > 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: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
