Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Erik Hatcher
Again, please move this thread to the repository@ list. Thank you! Erik On May 3, 2005, at 6:07 PM, Jeffrey Liu wrote: Hi Mark, Thanks for the clarification. If I understand it correctly, this means potentially I can put plugin distributions into this repository, host a site.xml file somewhe

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Jeffrey Liu
Hi Mark, Thanks for the clarification. If I understand it correctly, this means potentially I can put plugin distributions into this repository, host a site.xml file somewhere and point to these plugin distributions? Also, this is probably a dumb question, but I'll ask anyways. Who is responsib

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Jeffrey Liu
Hi Milos, I agree, sharing plugins is nice because you can decrease the file size. Another drawback of having multiple private copies of the same jar is that you may run into class loading issues. In Eclipse, each plugin has its own class loader. And the same fully qualified class loaded by dif

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Mark Diggory
Slow down, to clarify, the repository is not just for "Jar's", it is for any release distributions. An Eclipse plugin for, lets say, Ant, would be a distributable, just like any other binary or src distribution in the repository. In Eclipse, a plugin archive is "poorly" prefixed with the extens

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Milos Kleint
if I want to use commons-logging as a Netbeans module/Eclipse plugin (meaning my own module/plugin references commons-logging codebase), then I need to bundle it myself a either part of my plugin or as a separate one. Having it as separate plugin has the advantage that multiple plugins can reuse th

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Milos Kleint
it would be nice to have a similar feature for Netbeans. Milos Kleint On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote: > Hi Dion, > > Thanks for your response. The existing repository won't work. Unlike a > Java application, putting JARs on the classpath is not sufficient to make > Eclipse aw

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread J Aaron Farr
On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote: > Hi Dion, > > Thanks for your response. The existing repository won't work. Unlike a > Java application, putting JARs on the classpath is not sufficient to make > Eclipse aware of these libraries. Eclipse needs to work with something > known as an

RE: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Noel J. Bergman
Guys, This is an interesting discussion, but PLEASE move it to [EMAIL PROTECTED] It is not an Incubator matter, at least at this time. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mai

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Sanjiva Weerawarana
Hi Jeffrey, > Thanks for your response. The existing repository won't work. Unlike a > Java application, putting JARs on the classpath is not sufficient to make > Eclipse aware of these libraries. Eclipse needs to work with something > known as an Eclipse plug-in, which is really the JARs thems

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread J Aaron Farr
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? Somethin

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread David Jencks
I'm not really familiar with eclipse. Could you please explain what advantages your proposal has over building your project with maven? From your description I would guess that using maven as your build system provides all the features you want with more automation. many thanks, david jencks

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Jeffrey Liu
Hi Dion, Thanks for your response. The existing repository won't work. Unlike a Java application, putting JARs on the classpath is not sufficient to make Eclipse aware of these libraries. Eclipse needs to work with something known as an Eclipse plug-in, which is really the JARs themselves plus

RE: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Noel J. Bergman
Dion Gillard wrote: > Is there a reason we can't reuse the existing repository at > http://www.apache.org/dist/java-repository/ ? And for further discussion, please use [EMAIL PROTECTED] --- noel - To unsubscribe, e-ma

Re: Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Dion Gillard
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? On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote: > Hi, > > I want

Proposal for a centralized Eclipse update manager site for Apache projects/software

2005-05-03 Thread Jeffrey Liu
Hi, I want to propose a centralized Eclipse update manager site for Apache projects/software. This may not be the correct place to ask this, but I can find a better place to do it, so I decided to start here. If this is not the right place, can somebody point me to the correct location? Thanks