Re: idea: automatic component repo
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 in and add ideas to the list, we can pare it down later brian.diekelman wrote: 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 component(s) bundle into the OSGi framework, have a listener for new bundle registrations (http://felix.apache.org/site/apache-felix-tutorial-example-1.html) - deploy the application to http://sitename/appName/ (have a dispatcher servlet filter that reads the app name, trims it, and forwards to the appropriation WebApplication within a bundle) - when a new version of the module is released just de-activate the old bundle and activate the new one (versions based on maven artifact/group ids) I have only been playing with OSGi for jar deployments in a very narrow scope, but it seems like a good option. It should allow you to avoid restarting anything for app deployments. -- -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]
Re: idea: automatic component repo
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 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 component(s) bundle into the OSGi framework, have a listener > for new bundle registrations > (http://felix.apache.org/site/apache-felix-tutorial-example-1.html) > - deploy the application to http://sitename/appName/ (have a dispatcher > servlet filter that reads the app name, trims it, and forwards to the > appropriation WebApplication within a bundle) > - when a new version of the module is released just de-activate the old > bundle and activate the new one (versions based on maven artifact/group > ids) > > I have only been playing with OSGi for jar deployments in a very narrow > scope, but it seems like a good option. It should allow you to avoid > restarting anything for app deployments. > -- View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p18024576.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]
Re: idea: automatic component repo
TOTALLY! simple, easy, slick, pretty. Daniel Frisk wrote: > > 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" http://jalbum.net/skins > > It has been a HUGE success and it's dead easy to install new skins for > the end users. We as developers are of course more advanced users and > could just as easy do a cvs/svn checkout. But it's not as easy and > available, and even developers are as lazy (and not to mention busy) > as everyone else. I for one would love to browse this component > marketplace and checkout demos of fancy stuff! > > // Daniel Frisk > jalbum.net > > > On 2008-06-19, at 10:17, 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... crawler adds components and the demos just >>> appear on >>> the site automagically via OSGi. >>> mebbe we need cheeser's transparent OSGi first though? >>> >>> > > - > 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-tp17979177p18002973.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]
Re: idea: automatic component repo
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" http://jalbum.net/skins It has been a HUGE success and it's dead easy to install new skins for the end users. We as developers are of course more advanced users and could just as easy do a cvs/svn checkout. But it's not as easy and available, and even developers are as lazy (and not to mention busy) as everyone else. I for one would love to browse this component marketplace and checkout demos of fancy stuff! // Daniel Frisk jalbum.net On 2008-06-19, at 10:17, 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... crawler adds components and the demos just appear on the site automagically via OSGi. mebbe we need cheeser's transparent OSGi first though? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idea: automatic component repo
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... 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: >>> >>> - (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 component(s) bundle into the OSGi framework, have a listener >> for new bundle registrations >> (http://felix.apache.org/site/apache-felix-tutorial-example-1.html) >> - deploy the application to http://sitename/appName/ (have a dispatcher >> servlet filter that reads the app name, trims it, and forwards to the >> appropriation WebApplication within a bundle) >> - when a new version of the module is released just de-activate the old >> bundle and activate the new one (versions based on maven artifact/group >> ids) >> >> I have only been playing with OSGi for jar deployments in a very narrow >> scope, but it seems like a good option. It should allow you to avoid >> restarting anything for app deployments. >> > > -- View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17999625.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]
Re: idea: automatic component repo
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: >> >> - (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 component(s) bundle into the OSGi framework, have a listener > for new bundle registrations > (http://felix.apache.org/site/apache-felix-tutorial-example-1.html) > - deploy the application to http://sitename/appName/ (have a dispatcher > servlet filter that reads the app name, trims it, and forwards to the > appropriation WebApplication within a bundle) > - when a new version of the module is released just de-activate the old > bundle and activate the new one (versions based on maven artifact/group > ids) > > I have only been playing with OSGi for jar deployments in a very narrow > scope, but it seems like a good option. It should allow you to avoid > restarting anything for app deployments. > -- View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17999577.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]
Re: idea: automatic component repo
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 component(s) bundle into the OSGi framework, have a listener for new bundle registrations (http://felix.apache.org/site/apache-felix-tutorial-example-1.html) - deploy the application to http://sitename/appName/ (have a dispatcher servlet filter that reads the app name, trims it, and forwards to the appropriation WebApplication within a bundle) - when a new version of the module is released just de-activate the old bundle and activate the new one (versions based on maven artifact/group ids) I have only been playing with OSGi for jar deployments in a very narrow scope, but it seems like a good option. It should allow you to avoid restarting anything for app deployments. -- View this message in context: http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17992991.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]
Re: idea: automatic component repo
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 > 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] >>> >
Re: idea: automatic component repo
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-t
Re: idea: automatic component repo
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: [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-tp17979177p179
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [EMAIL PROTECTED] > For additional commands, e-mail: [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] > >>> > >> > >>
Re: idea: automatic component repo
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: [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 com
Re: idea: automatic component repo
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: [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-tp17979177p17983656.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]
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [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-tp17979177p17983260.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]
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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]
Re: idea: automatic component repo
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: [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-tp17979177p17983260.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]
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idea: automatic component repo
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: [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]
Re: idea: automatic component repo
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: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idea: automatic component repo
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 <[EMAIL PROTECTED]> 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: [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]
Re: idea: automatic component repo
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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idea: automatic component repo
+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:) > > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Azzeddine Daddah www.hbiloo.com
Re: idea: automatic component repo
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idea: automatic component repo
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
