Thanks Christopher. My Maven build works with version 1 configured as a plugin. It does not, however, work with version 2 configured as an extension. Nor can I configure version 2 as a plugin to mimic the version 1 configuration in my POM. Am I missing something? Do I have to become a proficient *Maven*er to get to the bottom of this? If you could at least point me to the right documentation for the extension, it would be much appreciated .
On Wed, Mar 6, 2013 at 12:12 AM, Christopher Hunt <hu...@internode.on.net>wrote: > Hi Mihai, > > Version 1 of the library is deprecated and there is no plan to release it > so far as I know. > > Version 2 is incompatible with version 1. > > Kind regards, > Christopher > > On 06/03/2013, at 4:09 PM, Mihai Danila <virid...@gmail.com> wrote: > > > Hi guys, > > One of our applications uses the javascript-maven-plugin plugin. > Unfortunately, I can't find a release version of this plugin, so that I can > use Maven's release process to release the application. Could we create > one, or is this superseded by some other compatible plugin? > > The plugin is: > org.codehaus.mojo.javascript:javascript-maven-plugin:1.0-alpha-1-SNAPSHOT > > I've also tried using the extension with the same artifact ID, currently > org.codehaus.mojo:javascript-maven-plugin:2.0.0-alpha-1. However, when > using the extension, Maven complains that the javascript type is not > recognized. > > Not sure what to do about this, and I can't release our library. > > Thank you, > Mihai > > >
