On 1/5/07, Donald Woods <[EMAIL PROTECTED]> wrote:
How do we update the contents of the http://geronimo.apache.org/plugins/geronimo-2.0/repository/ directory? Everything except the /repository directory is in svn under http://svn.apache.org/viewvc/geronimo/site/trunk/docs/plugins/ which currently contains 1.2-SNAPSHOT and 2.0-M1-SNAPSHOT binaries....
site/trunk/docs/plugins/geronimo-2.0/.htaccess contains this rewrite rule: RewriteRule ^repository/(.*) http://people.apache.org/maven-snapshot-repository/$1 This rule makes requests to the URL you mentioned above get redirected to the maven snapshot repository. Publishing a Geronimo snapshot updates the content of that repository. When 2.0 is released then we will update that rewrite rule to redirect to the permanent (non-snapshot) repository location.
Can we update the build/release process on gbuild to automatically remove the existing release directory (currently 2.0-SNAPSHOT) and push the latest org.apache.geronimo build artifacts over at least once a week?
I think that would be a great idea because it would ensure that any changes made to the plugin metadata under server/trunk/configs is available from the plugins in the snapshot repository on a more predictable schedule. Eventually I think that we'll also need to automate creation of the repository catalogs. I do that by hand right now (good old vim) and have been meaning to write a perl script to automate it. Maybe that could be hooked into gbuild. BTW, in case you're looking at this plugin stuff right now you should be aware that after making the changes below I found that the 2.0-M1-SNAPSHOT plugins published in the maven snapshot repo don't work with 2.0-SNAPSHOT because of the serialVersionUID change made to GOperationInfo.java. Grrrrrr. So far we don't have a good track record for maintaining plugin compatibility across Geronimo releases, which is the reason why there's basically a catalog for every release. I'm hoping to cut down on the number of catalogs by enhancing the plugin schema to allow multiple download locations per plugin, based on the geronimo version. (I'll start a discuss thread on that before making any changes) Best wishes, Paul
Paul McMahan (JIRA) wrote: > [ https://issues.apache.org/jira/browse/GERONIMO-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Paul McMahan closed GERONIMO-2670. > ---------------------------------- > > Resolution: Fixed > >> Update geronimo plugin repository version >> ----------------------------------------- >> >> Key: GERONIMO-2670 >> URL: https://issues.apache.org/jira/browse/GERONIMO-2670 >> Project: Geronimo >> Issue Type: Task >> Security Level: public(Regular issues) >> Components: Plugins >> Affects Versions: 2.0-M1, 2.0 >> Reporter: Paul McMahan >> Assigned To: Paul McMahan >> Fix For: 2.0-M1, 2.0 >> >> >> Update the geronimo plugin repository version number in geronimo-plugin.xml files. Also update assemblies to point at new repository list. >
