Eclipse Community Forums: Eclipse Foundation » Plugins wrapping other Open Source components

Help

Home

Home » General (non-technical) » Eclipse Foundation » Plugins wrapping other Open Source components

Show: Today's Messages :: Show Polls :: Message Navigator

Plugins wrapping other Open Source components [message #27788]

Fri, 30 December 2005 18:00

Eclipse User

Originally posted by: bim2005.basistech.com

Apologies if this is the wrong place for this query.

The web services project packaged up Apache Axis as a plugin named
org.apache.axis. They didn't do a complete job; they only exported the
packages for development, not runtime. (This issue is resolved in bugzilla)
One might argue that they should have made two plugins; one for runtime and
one for development, even.

I have just set up the same thing for the Apache XML-RPC kit.

I'd be more than happy to contribute mine, then I'd feel better about
calling it org.apache.xmlrpc. Is it possible that there should be a naming
convention that leaves names like 'org.apache.*' unused until/unless the
owning open source projects choose to create a plugin? Perhaps the axis
plugin should have been org.eclipse.org.apache.axis, and I should do
something likwise with my own namespace?

Report message to a moderator

Re: Plugins wrapping other Open Source components [message #27827 is a reply to message #27788]

Fri, 30 December 2005 21:40

ted stockwell

Messages: 123
Registered: July 2009

Senior Member

Benson Margulies wrote:
> Apologies if this is the wrong place for this query.
>
> The web services project packaged up Apache Axis as a plugin named
> org.apache.axis. They didn't do a complete job; they only exported the
> packages for development, not runtime. (This issue is resolved in bugzilla)
> One might argue that they should have made two plugins; one for runtime and
> one for development, even.
>
> I have just set up the same thing for the Apache XML-RPC kit.
>
> I'd be more than happy to contribute mine, then I'd feel better about
> calling it org.apache.xmlrpc. Is it possible that there should be a naming
> convention that leaves names like 'org.apache.*' unused until/unless the
> owning open source projects choose to create a plugin? Perhaps the axis
> plugin should have been org.eclipse.org.apache.axis, and I should do
> something likwise with my own namespace?
>
>

The convention that I have adopted is to use a custom namespace for my third-party libraries.

A while back I took over the SourceForge 'plugins' project with the idea in mind that I would publish all my third-party Eclipse
plugins there. So all my plugins have names like net.sf.plugins.springframework-1.2.6.

Unfortunately I don't have the bandwidth to follow through with that idea...so if anybody out there would like to take over the
net.sf.plugins project for the purpose of publishing Eclipse plugins then let me know...

ted stockwell

Report message to a moderator

Previous Topic:	Re: Search on Eclipse web site is very poor
Next Topic:	Eclipse Seminars

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 17:44:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter