On Thu, 5 May 2005, Mark R. Diggory wrote:
> >I think I belong to a group who is not totally Eclipse savvy/friendly, and
> >somewhat negative to an explicit support of Eclipse and not for other IDEs.
> I think that as long as we maintain that an Eclipse plugin is just a
> distributable artifact,
Niclas Hedhman wrote:
On Wednesday 04 May 2005 21:26, Mark R. Diggory wrote:
Sorry if my response sounded abrasive, I'm not trying to be.
No problem. And ditto sorry.
I think I belong to a group who is not totally Eclipse savvy/friendly, and
somewhat negative to an explicit support of Ecli
On Wednesday 04 May 2005 21:26, Mark R. Diggory wrote:
> Sorry if my response sounded abrasive, I'm not trying to be.
No problem. And ditto sorry.
I think I belong to a group who is not totally Eclipse savvy/friendly, and
somewhat negative to an explicit support of Eclipse and not for other IDEs
On 5/4/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Wednesday 04 May 2005 19:54, Milos Kleint wrote:
> > > Milos, didn't Netbeans itself devise some funky system for the
> > > non-distributables and click-thru license approvals??
> >
> > AFAIK such dependencies are scrambled and during the bu
Good stuff, maybe it'd be good to start a separate thread from the
Eclipse plugin artifact topic. -Mark
Steve Loughran wrote:
On 5/4/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Wednesday 04 May 2005 19:34, Steve Loughran wrote:
maven repositories are fun because every JAR is on a URL
On 5/4/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Wednesday 04 May 2005 19:34, Steve Loughran wrote:
>
> > maven repositories are fun because every JAR is on a URL; you can pass
> > them to a URL classloader as is if you want. The .pom also declares
> > dependencies for transitive work; a
Brett Porter wrote:
On 5/5/05, Dion Gillard <[EMAIL PROTECTED]> wrote:
Where do you see the Eclipse version number (not the artifact version)
fitting in?
I was under the impression this would be captured within the archive itself.
But should it need to be part of the path, it is probably se
On 5/5/05, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Where do you see the Eclipse version number (not the artifact version)
> fitting in?
I was under the impression this would be captured within the archive itself.
But should it need to be part of the path, it is probably sensible to
make it part
Where do you see the Eclipse version number (not the artifact version)
fitting in?
e.g.
/eclipse2-plugins/
/eclipse3-plugins/
/eclipse-plugins/
And what of eclipse features which are a bundling of related plugins
and resources?
On 5/5/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > Btw, is ther
> Btw, is there any rules that govern what a project
> can drop or not drop into the respository?
Anything otherwise distributable should be fine.
As far as I'm concerned, the repository is still the right place for
these - perhaps under /eclipse-plugins/ (or some more suitable name)
instead of
lease respond to
repository
To
[EMAIL PROTECTED]
cc
Subject
Re: Proposal for a centralized
Eclipse update manager site for Apache projects/software
Before the conversation continues on a little, I think
we need to
clarify how things work in Eclipse.
First off, there are two types of
Before the conversation continues on a little, I think we need to
clarify how things work in Eclipse.
First off, there are two types of dependencies in Eclipse. One is the
traditional IDE project dependency. For example, let's say I'm
developing a Struts application. I'll need the Struts jars a
Niclas Hedhman wrote:
On Wednesday 04 May 2005 20:06, Mark Diggory wrote:
Thats a little pretentious, so Eclipse should support Maven, but not the
other way around? This is not about "every" Apache project having to
release Eclipse plugin format, just those that want to. Its trivial for
a projec
On Wednesday 04 May 2005 20:06, Mark Diggory wrote:
> Thats a little pretentious, so Eclipse should support Maven, but not the
> other way around? This is not about "every" Apache project having to
> release Eclipse plugin format, just those that want to. Its trivial for
> a project to organize an
Niclas Hedhman wrote:
On Wednesday 04 May 2005 04:12, Jeffrey Liu wrote:
I want to propose a centralized Eclipse update manager site for Apache
projects/software. Reason I propose an Eclipse update manager site for
Apache projects/software
IIUYC, and perhaps others have not expressed this d
On 5/4/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Wednesday 04 May 2005 19:54, Milos Kleint wrote:
> > > Milos, didn't Netbeans itself devise some funky system for the
> > > non-distributables and click-thru license approvals??
> >
> > AFAIK such dependencies are scrambled and during the bu
Niclas Hedhman wrote:
On Wednesday 04 May 2005 04:12, Jeffrey Liu wrote:
I want to propose a centralized Eclipse update manager site for Apache
projects/software. Reason I propose an Eclipse update manager site for
Apache projects/software
IIUYC, and perhaps others have not expressed this d
On Wednesday 04 May 2005 19:54, Milos Kleint wrote:
> > Milos, didn't Netbeans itself devise some funky system for the
> > non-distributables and click-thru license approvals??
>
> AFAIK such dependencies are scrambled and during the build process a
> special ant task shows a dialog with license an
On 5/4/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Wednesday 04 May 2005 19:34, Steve Loughran wrote:
>
> > Incidentally, one pressing problem with the maven repositories is
> > there is no easy way to fetch Sun stuff. That is, if I want to use
> > Axis with mail.jar and activation,jar,
On Wednesday 04 May 2005 19:34, Steve Loughran wrote:
> maven repositories are fun because every JAR is on a URL; you can pass
> them to a URL classloader as is if you want. The .pom also declares
> dependencies for transitive work; a bit like debian apt-get.
I have missed this progress. Can you
On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote:
>
> Hi Steve,
>
> Configure in this case means the user goes to the Eclipse perference page,
> choose the version of Tomcat that was downloaded, and point Eclipse to the
> location where it was unzipped. Nothing major, but not obvious to novice
On Tue, 3 May 2005, Jeffrey Liu wrote:
> I want to propose a centralized Eclipse update manager site for Apache
> projects/software. Reason I propose an Eclipse update manager site for
Would be excelent if it can be tied up with the existing dist/mirrored
infrastructure for anything 'bulk' down
On Wednesday 04 May 2005 04:12, Jeffrey Liu wrote:
> I want to propose a centralized Eclipse update manager site for Apache
> projects/software. Reason I propose an Eclipse update manager site for
> Apache projects/software
IIUYC, and perhaps others have not expressed this distinctly enough;
It s
)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
[EMAIL PROTECTED]
Mark Diggory <[EMAIL PROTECTED]>
05/03/2005 03:58 PM
Please respond to
general
To
general@incubator.apache.org
cc
Subject
Re: Proposal for a centralized Eclipse update manager site for Apache
projects/software
Slow
Brett Porter wrote:
I echo David's sentiments on this. I'd be interested to know what is
in the eclipse metadata you want to attach to the various artifacts in
the repository, and whether any of it coincides with existing metadata
formats in use here, such as the following for parts of jakarta
comm
Brett Porter wrote:
I echo David's sentiments on this. I'd be interested to know what is
in the eclipse metadata you want to attach to the various artifacts in
the repository, and whether any of it coincides with existing metadata
formats in use here, such as the following for parts of jakarta
comm
200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
[EMAIL PROTECTED]
Mark Diggory <[EMAIL PROTECTED]>
05/03/2005 03:58 PM
Please respond to
general
To
general@incubator.apache.org
cc
Subject
Re: Proposal for a centralized Eclipse update manager site for Apache
projects/
huge and users do not want that. It's better to install things on the
> > fly when it's needed. That's why I think end users will benefit from
> > this update site as well.
> >
> > Thanks,
> >
> > Jeffrey Liu
> > IBM Rational Software - Perfo
PROTECTED]
Steve Loughran <[EMAIL PROTECTED]>
05/03/2005 04:54 PM
Please respond to
repository
To
[EMAIL PROTECTED]
cc
Subject
Re: Proposal for a centralized
Eclipse update manager site for Apache projects/software
On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]>
wrote:
e - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
[EMAIL PROTECTED]
J Aaron Farr <[EMAIL PROTECTED]>
05/03/2005 04:34 PM
Please respond to
repository
To
[EMAIL
PM
Please respond to
repository
To
[EMAIL PROTECTED]
cc
Subject
Re: Proposal for a centralized
Eclipse update manager site for Apache projects/software
Hello all.
I'm also copying over this reply I made from [EMAIL PROTECTED]
On 5/3/05, Jeffrey Liu <[EMAIL P
On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote:
> This is not easy. If there's an Eclipse update manager site for Apache
> software, then when the user finds out s/he needs Tomcat and Axis, all s/he
> needs to do now is launch the Eclipse update manager (URL to the Apache
> update site will be p
Hello all.
I'm also copying over this reply I made from [EMAIL PROTECTED]
On 5/3/05, Jeffrey Liu <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> This message was originally posted to the general@incubator.apache.org
> mailing list. Someone pointed out that such discussion should be carried out
> here
33 matches
Mail list logo
