maven-install-plugin: Why it does not install the artifacts
Hi I have a pom project that is is using the maven-instal-plugin to install 3 artifacts in my local repository. But when running mvn install, none are installed. What's wrong with this pom.xml [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building maven 1.0.0 [INFO] [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ maven --- [INFO] Installing C:\Users\fandre\Documents\MXW\MI-4.3\maven\pom.xml to C:\Users\fandre\.m2\repository\fr\swisslife\archiev3\maven\1.0.0\maven-1.0.0.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 0.577 s [INFO] Finished at: 2018-03-12T10:10:17+01:00 [INFO] Final Memory: 6M/150M [INFO] http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 fr.swisslife.archiev3 maven 1.0.0 org.apache.maven.plugins maven-install-plugin 2.5.2 archieutils install fr.swisslife.archiev3 archieutils 0.0.1-SNAPSHOT archieutils-0.0.1-SNAPSHOT.jar jar true archiedm install fr.swisslife.archiev3 archiedm 0.0.1-SNAPSHOT archiedm-0.0.1-SNAPSHOT.jar jar true archieft install fr.swisslife.archiev3 archieft 0.0.1-SNAPSHOT archieft-0.0.1-SNAPSHOT.jar jar true pom
Re: maven-install-plugin: Why it does not install the artifacts
There is a fundamental issue here. You're trying to do this the wrong way.
* The install goal is not for installing arbitrary files in the repo. For
that you should use install-file. But the install-file goal is not intended
to be bound to the build lifecycle, but for executing from the command line
("mvn install:install-file ...")
* If you want to have a Maven project which installs three artifacts during
the build lifecycle you should register the artifacts during the build. In
your case where you seem to have some pre-build artifacts you could do this
with maven-buildhelper-plugin [1]. Then they will be installed when you
execute "mvn install".
But probably the most simple way to do this is to add the artifacts to your
company's repo manager just once and then you're done with it. Nexus, for
example, provides a GUI interface to do this.
[1]
http://www.mojohaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
/Anders
On Mon, Mar 12, 2018 at 2:51 PM, Zos Rothko wrote:
> Hi
>
> I have a pom project that is is using the maven-instal-plugin to install 3
> artifacts in my local repository. But when running mvn install, none are
> installed. What's wrong with this pom.xml
>
>
> [INFO] Scanning for projects...
>
> [INFO]
> [INFO]
>
> [INFO] Building maven 1.0.0
> [INFO]
>
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ maven
> ---
> [INFO] Installing C:\Users\fandre\Documents\MXW\MI-4.3\maven\pom.xml to
> C:\Users\fandre\.m2\repository\fr\swisslife\archiev3\maven\
> 1.0.0\maven-1.0.0.pom
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.577 s
> [INFO] Finished at: 2018-03-12T10:10:17+01:00
> [INFO] Final Memory: 6M/150M
> [INFO]
>
>
>
>
> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> fr.swisslife.archiev3
> maven
> 1.0.0
>
>
>
>
> org.apache.maven.plugins
> maven-install-plugin
> 2.5.2
>
>
> archieutils
>
> install
>
>
> fr.swisslife.archiev3
> archieutils
> 0.0.1-SNAPSHOT
> archieutils-0.0.1-SNAPSHOT.jar
> jar
> true
>
>
>
> archiedm
>
> install
>
>
> fr.swisslife.archiev3
> archiedm
> 0.0.1-SNAPSHOT
> archiedm-0.0.1-SNAPSHOT.jar
> jar
> true
>
>
>
> archieft
>
> install
>
>
> fr.swisslife.archiev3
> archieft
> 0.0.1-SNAPSHOT
> archieft-0.0.1-SNAPSHOT.jar
> jar
> true
>
>
>
>
>
>
> pom
>
>
>
>
Re: maven-install-plugin: Why it does not install the artifacts
Hi, On 12/03/18 14:51, Zos Rothko wrote: Hi http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 fr.swisslife.archiev3 maven 1.0.0 If I take a look at your pom file...just remove the whole configuration for maven-install-plugin... and just try to do: mvn clean install If you are artifacts installed fine if not ...there is something else wrong.. Please at best a link to a project github/bitbucket etc... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-install-plugin: Why it does not install the artifacts
I think you've missed one of the last lines: pom That also explains why no other plugin is called before the maven-install-plugin Robert On Mon, 12 Mar 2018 17:35:16 +0100, Karl Heinz Marbaise wrote: Hi, On 12/03/18 14:51, Zos Rothko wrote: Hi http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 fr.swisslife.archiev3 maven 1.0.0 If I take a look at your pom file...just remove the whole configuration for maven-install-plugin... and just try to do: mvn clean install If you are artifacts installed fine if not ...there is something else wrong.. Please at best a link to a project github/bitbucket etc... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven EAR Version 3.0.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven EAR Plugin Version 3.0.0 This plugin generates Java EE Enterprise Archive (EAR) file. It can also generate the deployment descriptor file (e.g. application.xml). https://maven.apache.org/plugins/maven-ear-plugin/ Important Note since 3.0.0: * Maven 3.X only * JDK 7 minimum requirement You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ear-plugin 3.0.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-ear-plugin/download.cgi Release Notes Maven EAR Plugin 3.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422&version=12330696 Bugs: * [MEAR-171] - Full customization of FileNameMapping is needed * [MEAR-217] - Snapshot dependencies are not deleted from skinny WARs * [MEAR-243] - Skinny WARs - JAR not removed from WAR if scope in EAR is set to provided * [MEAR-244] - Remove link to non-existing Codehaus wiki * [MEAR-246] - Upgrade the EAR lifecycle to use the maven-resources-plugin 3.0.2. * [MEAR-250] - IT skinny-wars-javaee5 fails while running with JDK 9 New Features: * [MEAR-247] - resource-ref in generated application.xml * [MEAR-248] - Support lookup-name in env-entry section Improvements: * [MEAR-198] - Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin * [MEAR-223] - Link to wiki on documentation page is pointing to shutdown codehaus * [MEAR-226] - bundleFileName functionality for the acr plugin * [MEAR-228] - Remove manifestFile parameter * [MEAR-229] - Change default value for version parameter * [MEAR-232] - Remove param properties that doesn't make sense for CLI usage * [MEAR-234] - Upgrade maven-shared-components parent to version 30 * [MEAR-241] - Change package to o.a.m.plugins * [MEAR-242] - Update lifecycle mapping plugin version * [MEAR-254] - Support JavaEE version 8 * [MEAR-258] - Upgrade site skin to 1.7 * [MEAR-260] - Remove finalName as a parameter * [MEAR-261] - In cases where fileNameMapping is used fail the build * [MEAR-262] - Missing since for outputFileNameMapping parameter * [MEAR-263] - Wrong docs in examples/customize-file-name-mapping.html Tasks: * [MEAR-207] - Remove the JavaModule/Ejb3Module which are marked deprecated * [MEAR-208] - Upgrade to Maven 3.0 compatiblity + JDK 6 * [MEAR-209] - Change and use a internal unique id instead of artifactId only * [MEAR-259] - Fix formatting date issues in apt files Dependency upgrades: * [MEAR-224] - Upgrade plexus-archiver from 2.10.3 to 3.0.1 * [MEAR-233] - Upgrade plexus-archiver from 3.0.3 to 3.1.1 * [MEAR-235] - Upgrade maven-archiver to 3.1.0 * [MEAR-236] - Upgrade maven-filtering to 3.1.1 * [MEAR-237] - Upgrade plexus-archiver to 3.3 * [MEAR-238] - Upgrade of plexus-archiver to 3.4. * [MEAR-240] - Upgrade of maven-archiver to 3.1.1. * [MEAR-245] - Upgrade of plexus-interpolation to 1.24. * [MEAR-251] - Upgrade maven-archiver to 3.2.0 * [MEAR-252] - Upgrade plexus-archiver to 3.5. * [MEAR-253] - Upgrade plexus-utils to version 3.1.0 * [MEAR-255] - Upgrade parent to 31 * [MEAR-256] - Upgrade maven-verifier component * [MEAR-257] - Upgrade JUnit to 4.12 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-install-plugin: Why it does not install the artifacts
Hi Le 12/03/2018 à 17:35, Karl Heinz Marbaise a écrit : Hi, On 12/03/18 14:51, Zos Rothko wrote: Hi http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 fr.swisslife.archiev3 maven 1.0.0 If I take a look at your pom file...just remove the whole configuration for maven-install-plugin... and just try to do: I do not understand your advise: How a "mvn clean install" command can install the file/artifact if the configurations specifying those file/artifacts are removed??? mvn clean install If you are artifacts installed fine if not ...there is something else wrong.. Please at best a link to a project github/bitbucket etc... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: maven-install-plugin: Why it does not install the artifacts
Hello, if you start with a empty POM of type JAR the Default LifeCycle bindings (which include intall plugin) apply. See here: http://maven.apache.org/ref/3.2.2/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging -- http://bernd.eckenfels.net Von: Zos Rothko Gesendet: Dienstag, 13. März 2018 06:58 An: i...@soebes.de; Maven Users List Betreff: Re: maven-install-plugin: Why it does not install the artifacts Hi Le 12/03/2018 à 17:35, Karl Heinz Marbaise a écrit : > Hi, > > On 12/03/18 14:51, Zos Rothko wrote: >> Hi >> >> >> http://maven.apache.org/POM/4.0.0"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/xsd/maven-4.0.0.xsd";> >> 4.0.0 >> fr.swisslife.archiev3 >> maven >> 1.0.0 >> >> >> >> >> > > If I take a look at your pom file...just remove the whole > configuration for maven-install-plugin... > and just try to do: I do not understand your advise: How a "mvn clean install" command can install the file/artifact if the configurations specifying those file/artifacts are removed??? > > mvn clean install > > > If you are artifacts installed fine if not ...there is something else > wrong.. > > Please at best a link to a project github/bitbucket etc... > > Kind regards > Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
