I wouldn't mind helping releasing a version 1.0 of this plugin if there were no objections. I just need to get familiar with the process. I'm currently a committer to the NaturalDocs plugin (http://mojo.codehaus.org/naturaldocs-maven-plugin), so it'd be good practice for me.
It seems that there is at least one other party that uses this plugin, and I wouldn't be surprised if there were more. http://jira.codehaus.org/browse/MJS-35 I just need to know the workflow. I believe it involves calling a public vote, and I'd like to get feedback from Nicolas De Loof to see if he has any comments. Thoughts? Tim ---- Anders Hammar <[email protected]> wrote: > You can always create your own internal release of it. Just get the source > and deploy a release to your internal repo manager. > However, if creating an internal release I suggest you use a different > version than what you would expect an official release to have. This will > prevent future issues due to version collision. I always put some name in > the version which I know will make it unique (such as my company name for > example). > > /Anders > > On Thu, Mar 3, 2011 at 22:33, Lei Wang <[email protected]> wrote: > > > Hi, > > > > My company's project uses maven-javascript-plugin. We run into a problem > > when trying to release the project by using mvn release:prepare. The > > release plugin complains the project is using a snapshot version of the > > maven-javascript-plugin, which is 1.0-alpha-1-SNAPSHOT. I checked the > > website and found there is no release version available. Can someone > > make a release version of maven javascript plugin? Or can I do it and > > how? > > > > Lei Wang > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
