Re: How to settup a plugin site?
On 10/25/06, Hernan Cunico <[EMAIL PROTECTED]> wrote: Hi Jacek, I'm planning to set up a plugin site for testing (and learning ;-) ) and remembered you mentioned working on some docs. So I thought asking you first ;-) Did you have the chance to put some ideas together? At this point I have no much idea where to start so any help will be really useful. Hi, I have had no time working on it, so if you want to jump in and take care of it, I'd be very grateful (and more likely to be finished soon ;-)). Thanks Hernan! Jacek -- Jacek Laskowski http://www.jaceklaskowski.pl
Re: How to settup a plugin site?
Hi Jacek, I'm planning to set up a plugin site for testing (and learning ;-) ) and remembered you mentioned working on some docs. So I thought asking you first ;-) Did you have the chance to put some ideas together? At this point I have no much idea where to start so any help will be really useful. PS: not sure how stable the @apache.org dist lists are with the data moved so, just in case, I'm CCing you directly. Cheers! Hernan Jacek Laskowski wrote: On 10/9/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: Just like a Maven 2 repo, except with a geronimo-plugins.xml in the root directory. The only files that are actually used by the current plugin installer are the actual archives in question, the maven-metadata.xml files that list the available versions for each artifact, and the geronimo-plugins.xml in the root. Note that many plugins require separate JARs, which can either be on the same site or loaded from a secondary repo like ibiblio, but for versionless dependencies it's going to take the most recent version of the artifact in question from the first site that has any matching version at all. Is there a documentation page for it? If not, I'd like to create one, but I wonder where it should go. Jacek
Re: How to settup a plugin site?
Hey Jacek, thanks for jumping in on this one, it's very much needed ;-) how does the "Apache Geronimo Development" space sound to you? ( http://cwiki.apache.org/GMOxDEV ) We'll have to work on reorganizing the space's home page though. Cheers! Hernan Jacek Laskowski wrote: On 10/9/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: Just like a Maven 2 repo, except with a geronimo-plugins.xml in the root directory. The only files that are actually used by the current plugin installer are the actual archives in question, the maven-metadata.xml files that list the available versions for each artifact, and the geronimo-plugins.xml in the root. Note that many plugins require separate JARs, which can either be on the same site or loaded from a secondary repo like ibiblio, but for versionless dependencies it's going to take the most recent version of the artifact in question from the first site that has any matching version at all. Is there a documentation page for it? If not, I'd like to create one, but I wonder where it should go. Jacek
Re: How to settup a plugin site?
Jacek, This would be great! Jeff Jacek Laskowski wrote: > On 10/9/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > >> Just like a Maven 2 repo, except with a geronimo-plugins.xml in the >> root directory. The only files that are actually used by the current >> plugin installer are the actual archives in question, the >> maven-metadata.xml files that list the available versions for each >> artifact, and the geronimo-plugins.xml in the root. Note that many >> plugins require separate JARs, which can either be on the same site or >> loaded from a secondary repo like ibiblio, but for versionless >> dependencies it's going to take the most recent version of the >> artifact in question from the first site that has any matching version >> at all. > > Is there a documentation page for it? If not, I'd like to create one, > but I wonder where it should go. > > Jacek >
Re: How to settup a plugin site?
On 10/9/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: Just like a Maven 2 repo, except with a geronimo-plugins.xml in the root directory. The only files that are actually used by the current plugin installer are the actual archives in question, the maven-metadata.xml files that list the available versions for each artifact, and the geronimo-plugins.xml in the root. Note that many plugins require separate JARs, which can either be on the same site or loaded from a secondary repo like ibiblio, but for versionless dependencies it's going to take the most recent version of the artifact in question from the first site that has any matching version at all. Is there a documentation page for it? If not, I'd like to create one, but I wonder where it should go. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: How to settup a plugin site?
Ok...thanks...I'll give it a shot. Jeff Aaron Mulder wrote: > On 10/9/06, Jeff Genender <[EMAIL PROTECTED]> wrote: >> Could you give a quick email to explain how to set up a plugin site, >> what is needed, directory and xml layouts? > > Just like a Maven 2 repo, except with a geronimo-plugins.xml in the > root directory. The only files that are actually used by the current > plugin installer are the actual archives in question, the > maven-metadata.xml files that list the available versions for each > artifact, and the geronimo-plugins.xml in the root. Note that many > plugins require separate JARs, which can either be on the same site or > loaded from a secondary repo like ibiblio, but for versionless > dependencies it's going to take the most recent version of the > artifact in question from the first site that has any matching version > at all. > > Thanks, > Aaron
Re: How to settup a plugin site?
On 10/9/06, Jeff Genender <[EMAIL PROTECTED]> wrote: Could you give a quick email to explain how to set up a plugin site, what is needed, directory and xml layouts? Just like a Maven 2 repo, except with a geronimo-plugins.xml in the root directory. The only files that are actually used by the current plugin installer are the actual archives in question, the maven-metadata.xml files that list the available versions for each artifact, and the geronimo-plugins.xml in the root. Note that many plugins require separate JARs, which can either be on the same site or loaded from a secondary repo like ibiblio, but for versionless dependencies it's going to take the most recent version of the artifact in question from the first site that has any matching version at all. Thanks, Aaron
