It should be kept with Cocoon. If a plugin has very specific functionaliyt like this one, then it should be kept with the project as they would be best positioned to maintain it in the long run. Additionally, while right now people may look to maven.apache.org for plugins, the plugins page will eventually function more as a pointer to the correct repository versus function as the actual repository.
Eric > -----Original Message----- > From: Martin Dulisch [mailto:[EMAIL PROTECTED] > Sent: Monday, December 22, 2003 3:30 PM > To: [EMAIL PROTECTED] > Subject: Where to host new plugin: cocoonapp > > > Hello, > > I have developed a plugin for web applications that use > Apache Cocoon. It > can be used together with the WAR plugin. > > Now I would like to contirbute this plugin to the community. > But I could not > find anything in the archives how this should be done. So I am asking. > > Where is the right place for such a plugin? Optional plugins or > maven-plugins at sourceforge? I do not use any third party > jars. So there > should be no problem with licences. > > Please let me know if you have interest in the plugin and > what I have to do > to contribute it. I can also provide documentation for the > plugin in the > same way as other optional plugins (xdocs). > > Regards > Martin > > --------------- > Martin Dulisch > Open Source Group, S&N AG > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
