Re: [platform-dev] question about plugin name convention

[Jim des Rivieres <Jim_des_Rivieres@xxxxxxxxxx>]

Hi jml, 

Regarding plug-in naming, when there is a particular library that we've 
obtained from another open source project (e.g., Ant, JUnit, Lucene, 
Xerces), we generally have put the library into its own plug-in and named 
it the way the owners would have (e.g., org.apache.ant, org.junit, ...) 
and set the plug-in version number to match what's in it. This keeps the 
library separate from other plug-ins, and makes it easy to independently 
upgrade it when required.

---jim





jml <jml@xxxxxxxx>
Sent by: platform-dev-admin@xxxxxxxxxxx
10/21/2003 09:32 PM
Please respond to platform-dev

 
        To:     platform-dev@xxxxxxxxxxx
        cc: 
        Subject:        [platform-dev] question about plugin name convention



I asked the question on the newsgroup, but got no response, so execuse 
me to ask it here again.

Hi,
I have a question about plugin name convention.

In our project, we use many third party libraries, many from apache. And 
in eclipse, there is several plugins also contain packages from apache, 
such as "org.apache.xerces". This suggested us to also put the third 
party libraries into separate plugin, and name them as 
"org.apache.commons", "org.apache.axis", etc.

Then come my quesiton: in this way, who is managing the "org.apache" 
namespace? And if a lot of people doing the same, they may put totally 
different files in the same named plugin, and I believe a lot of trouble.

Or I name the plugin as "com.mycom.apache.commons", but that make me 
feel terible, also I would believe common lib as apache will be used by 
a lot of people.

Is there any convention in how to handle this?

Thanks

jml


_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-dev