Hi,
I'm planning to roll out 6 or 7 new or updated plugins on the codeczar site. Before I do this I want to make sure I have the naming conventions correct.
Pretty much every plugin is named 'maven-foobar-plugin'
the problem I have is what to name plugins where a plugin with the same name has been released by other someone else and how to avoid such conflicts in the future.
e.g. maven-weblogic-plugin maven-tomcat-plugin maven-sql-plugin
I think this is likely to lead to confusion with people installing plugins with the same name from different places.
I think there are three options:
1) leave things the way they are
2) replace the 'maven' bit of the name with source domain (in my case that would lead to 'codeczar-tomcat-plugin')
3) add the domain to the plugin name 'codeczar-maven-tomcat-plugin' which would lead to all 3rd party plugins having 4 parts to the name and plugins hosted at apache having 3 parts 'maven-test-plugin'
before I release the plugins I'd prefer to follow the standard. If there isn't a standard I'd be grateful if we could establish one. The last thing I want to do is create confusion by releasing plugins only to re-release them later with different names.
I brought this up a while ago and it seems that some people have their own informal conventions that they follow for internal or project-oriented plugins
http://www.mail-archive.com/[EMAIL PROTECTED]/msg05289.html
I accept that it would be better if there were only one plugin for each functional area. ie only one weblogic plugin. The situation I am in is that I have established maven with a number of clients who are now using un-released plugins. I would like to formally release these plugins so these clients have a means of obtaining updates without there being the possibility of conflicts with someone elses plugins in the future. I would also like to make this work available to the wider community without conflicting with other people's work.
other concerns...
Leave names as they are:
I don't want to appear to be stepping on anyones toes by releasing work that is similar to and has the same name as someone elses. I also don't want to end up with name conflicts in the future.
Change the name to something like codeczar-tomcat-plugin:
In this case, the 'maven' prefix should become reserved in the same way the you don't create java classes called java.lang.FooBar. If I create a plugin called codeczar-tomcat-plugin, it will seem less official than one created by someone else who named theirs maven-tomcat-plugin.
cheers Nathan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
