On 5/3/05, Dion Gillard <[EMAIL PROTECTED]> wrote: > Is there a reason we can't reuse the existing repository at > http://www.apache.org/dist/java-repository/ ? > > In your example, Eclipse could be configured to check > http://www.apache.org/dist/java-repository/axis/jars/ for an update?
Something like that might work. Eclipse checks for a 'site.xml' file that references one or more plugins to download and install. The update site URL needs to be stable, so if a user picks a particular mirror initially that user will always use that mirror for future updates. Also the plugins are more than just a jar and minimally require a plugin.xml file zipped together into a single archive. Currently, Derby is the only ASF project I know of which distributes its releases in Eclipse plugin format [1] in addition to traditional binary and source releases. So it's slightly more than just making ASF jars available on the repository and pointing Eclipse to them. There's also the question of having a single site.xml file for all ASF Eclipse plugins versus a separate one for each PMC or even subproject. A single site would be far easier for users but more complicated for ASF developers. While we could reuse the java-repository location for Eclipse updates, I would prefer to see a new separate location such as: http://www.apache.org/dist/updates or something like that. Finally, unless we wanted all those Eclipse clients hitting our main distribution site, we would have to instruct users to pick a mirror. It's all feasible and I would love to see more Eclipse plugins for ASF projects. An update site would definitely help. -- jaaron [1] http://incubator.apache.org/derby/integrate/derby_plugin.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
