I think that document provides the solution - packaging must be "js", not "javascript" as with version 1. I may also need to re-release the JavaScript artifacts that I'm depending on.
I had started to release, but there were about four JAR artifacts and some three parent POMs in the dependency tree that I needed to release. After adjusting all the POMs (replacing -SNAPSHOT with -mycompany), I was greeted by the error that the JAR files themselves contained a copy of the POM that still said -SNAPSHOT. Faced with the prospect of editing four or five JARs, I decided to find the right way to do this. I will try this and post back with my results. On Wed, Mar 6, 2013 at 12:22 AM, Christopher Hunt <hu...@internode.on.net>wrote: > Hi Mihai, > > Version 2 is an entirely different approach to that taken with version 1. > Here's the best place to start: > > http://mojo.codehaus.org/javascript-maven-tools/ > > Alternatively are you able to release the version 1 plugin to your own > repo? > > Kind regards, > Christopher > > On 06/03/2013, at 4:19 PM, Mihai Danila <virid...@gmail.com> wrote: > > 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 . > > >
