I solved the problem adding in the pom.xml under <build>:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<executions>
<execution>
<id>default-install</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</pluginManagement>
This disables the plugin for the js module.
Tomas Alabes wrote:
>
> This is my output after concatenation:
>
> [INFO] 1-min.js minified from 504502 to 211110 bytes (41% of original
> size)
> [INFO]
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @
> composer.ba.js ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-install-plugin:2.3.1:install from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-install-plugin:2.3.1,
> parent: sun.misc.Launcher$AppClassLoader@43be2d65]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-install-plugin:2.3.1:install' with basic
> configurator -->
> [DEBUG] (f) artifact = company:composer.ba.js:js:12.1.1.0.0
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) createChecksum = false
> [DEBUG] (f) localRepository = id: local
> url: file:///Users/talabes/.local_soa_repository/repository/
> layout: none
>
> [DEBUG] (f) packaging = js
> [DEBUG] (f) pomFile = moduleDir/composer/ba/js/pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
>
> [...]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.3.1:install
> (default-install) on project composer.ba.js: The packaging for this
> project did not assign a file to the build artifact -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install
> (default-install) on project composer.ba.js: The packaging for this
> project did not assign a file to the build artifact
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:463)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:185)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:139)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: The packaging
> for this project did not assign a file to the build artifact
> at
> org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:124)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> [ERROR]
>
>
> That is the most significant part of the output, I'm also not using the
> AMD part of the plugin, I didn't use require.js, can this be a problem?
>
> Thanks!
>
>
> Christopher Hunt-2 wrote:
>>
>> Hi there,
>>
>> If you can provide me with a reproducible test case then I can take a
>> look.
>>
>> Kind regards,.
>> Christopher
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/question-on-javascript-maven-plugin-usage-for-simple-js-file-concatenation-tp33660574p34537144.html
Sent from the mojo - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
