Re: Skipping install phase for a particular artifact in a project
Hi, Gupta, Nishant. wrote: > Hi, > > I was wondering if there is a way by which we can skip the install phase > for a particular artifact. My use case is that I am using > maven-assembly-plugin with two assembly descriptors in it. The output of > first assembly descriptor is being used as input of the second assembly > descriptor. After package phase, I deleted the first assembly descriptor > artifact (in the target folder) using maven-clean-plugin but in the > install phase, it throws and error saying that it couldn't find the first > assembly descriptor artifact. > > Any help will be appreciated. Why do you clean something inbetween at all? This is not Ant. In a typical Maven project you keep everything that has been built in the target folder - even the intermediate results. The final artifacts will be installed (and copied to the remote repo) later. You should rather have a look at the configuration of the assembly plugin. There you can define wether a resulting artifact is automatically attached to the project (default behavior) or not. Only the attached ones are "final results" and therefore installed later. Cheers, Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping install phase for a particular artifact in a project
Also, to me, this sounds as it should be two Maven projects in a multi-module project. Maven rule: one project produces one artifact. You could comapre this with how it works when you create an ear, which contains a jar. It's two separate Maven projects. /Anders On Fri, Nov 4, 2016 at 8:28 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Hi, > > Gupta, Nishant. wrote: > > > Hi, > > > > I was wondering if there is a way by which we can skip the install phase > > for a particular artifact. My use case is that I am using > > maven-assembly-plugin with two assembly descriptors in it. The output of > > first assembly descriptor is being used as input of the second assembly > > descriptor. After package phase, I deleted the first assembly descriptor > > artifact (in the target folder) using maven-clean-plugin but in the > > install phase, it throws and error saying that it couldn't find the first > > assembly descriptor artifact. > > > > Any help will be appreciated. > > > Why do you clean something inbetween at all? This is not Ant. In a typical > Maven project you keep everything that has been built in the target folder > - > even the intermediate results. The final artifacts will be installed (and > copied to the remote repo) later. > > You should rather have a look at the configuration of the assembly plugin. > There you can define wether a resulting artifact is automatically attached > to the project (default behavior) or not. Only the attached ones are "final > results" and therefore installed later. > > Cheers, > Jörg > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Maven-Site-Plugin: Generated content?
Hello everyone, :-)
I'm trying to create some content for the Maven site during the Maven
build process.
I recognized that the maven-site-plugin has a
configuration property which allows defining a directory which holds
such generated content.
Normally it's the target/generated-site folder.
So I placed an APT as well as a HTML file there.
But nothing happened.
So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:
${project.build.directory}/generated-site
But also that didn't change anything.
After the Maven build there is still no file in the target/site folder.
Neither the rendered APT file nor the HTML file.
Where is my mistake? :-(
Regards
Gerrit
Re: Maven-Site-Plugin: Generated content?
Hi Gerrit,
I am also heavily using the site-plugin to generate the site of the flex
project.
I didn’t have to provide the generatedSiteDirectory config option at all ...
As soon as I run:
mvn site
It generates the „target/site“ directory with all of the site content.
Eventually you could have a look at the maven-site branch of the flex-site repo:
https://git-wip-us.apache.org/repos/asf?p=flex-site.git;a=tree;h=refs/heads/maven-site;hb=refs/heads/maven-site
If you want to generate the site for an apache project, eventually this could
help (I wrote down everything needed):
http://flex.apache.org/ng/doc-website.html
Chris
Am 04.11.16, 09:20 schrieb "Hohl, Gerrit" :
Hello everyone, :-)
I'm trying to create some content for the Maven site during the Maven
build process.
I recognized that the maven-site-plugin has a
configuration property which allows defining a directory which holds
such generated content.
Normally it's the target/generated-site folder.
So I placed an APT as well as a HTML file there.
But nothing happened.
So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:
${project.build.directory}/generated-site
But also that didn't change anything.
After the Maven build there is still no file in the target/site folder.
Neither the rendered APT file nor the HTML file.
Where is my mistake? :-(
Regards
Gerrit
AW: Maven-Site-Plugin: Generated content?
Hello Chris,
thanks for the fast reply. :-)
I had a peak at your project, but I'm not sure if I explained my problem very
well.
All of the src/main/site content is rendered perfectly and can be found in the
target/site folder.
But I also want to create some content during the Maven build which is not
stored in the src/main/site folder, but in a different folder in the target
folder (I don't want it to be part of the source code management).
It seems that for such generated content the target/generated-site folder is
the place to be.
But the maven-site-plugin seems to totally ignore any content in that folder.
Regards
Gerrit
-Ursprüngliche Nachricht-
Von: Christofer Dutz [mailto:christofer.d...@c-ware.de]
Gesendet: Freitag, 4. November 2016 10:08
An: Maven Users List
Betreff: Re: Maven-Site-Plugin: Generated content?
Hi Gerrit,
I am also heavily using the site-plugin to generate the site of the flex
project.
I didn’t have to provide the generatedSiteDirectory config option at all ...
As soon as I run:
mvn site
It generates the „target/site“ directory with all of the site content.
Eventually you could have a look at the maven-site branch of the flex-site repo:
https://git-wip-us.apache.org/repos/asf?p=flex-site.git;a=tree;h=refs/heads/maven-site;hb=refs/heads/maven-site
If you want to generate the site for an apache project, eventually this could
help (I wrote down everything needed):
http://flex.apache.org/ng/doc-website.html
Chris
Am 04.11.16, 09:20 schrieb "Hohl, Gerrit" :
Hello everyone, :-)
I'm trying to create some content for the Maven site during the Maven
build process.
I recognized that the maven-site-plugin has a
configuration property which allows defining a directory which holds
such generated content.
Normally it's the target/generated-site folder.
So I placed an APT as well as a HTML file there.
But nothing happened.
So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:
${project.build.directory}/generated-site
But also that didn't change anything.
After the Maven build there is still no file in the target/site folder.
Neither the rendered APT file nor the HTML file.
Where is my mistake? :-(
Regards
Gerrit
---
ssi,-i e-...@v.aer
rdtn mn,-i e-lmeac.g
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Layered BOMs and overriding dependency management
> So you'd say that your patched 3.4.0-SNAPSHOT (model version 4.0.0) is > behaving the way you'd expect Maven to behave out of the box? If you mean "as I'd like it to behave," yes. At least with this feature (dependency exclusions in BOM declarations). -- View this message in context: http://maven.40175.n5.nabble.com/Layered-BOMs-and-overriding-dependency-management-tp5884866p5884919.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Skipping install phase for a particular artifact in a project
Thank you all for the valuable suggestions. Attach parameter in maven-assembly-plugin along solved my use-case. I was wrong in cleaning the artifact though I have rectified that error. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, November 04, 2016 1:36 PM To: Maven Users List Subject: Re: Skipping install phase for a particular artifact in a project Also, to me, this sounds as it should be two Maven projects in a multi-module project. Maven rule: one project produces one artifact. You could comapre this with how it works when you create an ear, which contains a jar. It's two separate Maven projects. /Anders On Fri, Nov 4, 2016 at 8:28 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Hi, > > Gupta, Nishant. wrote: > > > Hi, > > > > I was wondering if there is a way by which we can skip the install > > phase for a particular artifact. My use case is that I am using > > maven-assembly-plugin with two assembly descriptors in it. The > > output of first assembly descriptor is being used as input of the > > second assembly descriptor. After package phase, I deleted the first > > assembly descriptor artifact (in the target folder) using > > maven-clean-plugin but in the install phase, it throws and error > > saying that it couldn't find the first assembly descriptor artifact. > > > > Any help will be appreciated. > > > Why do you clean something inbetween at all? This is not Ant. In a > typical Maven project you keep everything that has been built in the > target folder > - > even the intermediate results. The final artifacts will be installed > (and copied to the remote repo) later. > > You should rather have a look at the configuration of the assembly plugin. > There you can define wether a resulting artifact is automatically > attached to the project (default behavior) or not. Only the attached > ones are "final results" and therefore installed later. > > Cheers, > Jörg > > > - > 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 Shared Component: Maven Artifact Transfer Version 0.9.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Artifact Transfer Version 0.9.0. https://maven.apache.org/shared/maven-artifact-transfer/ An API to install, deploy and resolving artifacts with Maven3 You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-artifact-transfer 0.9.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-artifact-transfer/download.cgi Release Notes Maven Artifact Transfer 0.9.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12334238 Bugs: * [MSHARED-580] - Doclint errors in maven-artifact-transfer * [MSHARED-594] - NullPointerException is thrown when trying to install a project without POM file * [MSHARED-595] - In DefaultProjectInstaller, the path to the local repository should be retrieved from the RepositoryManager Improvements: * [MSHARED-469] - Upgrade maven common artifact filters to 3.0.0 * [MSHARED-523] - Upgrade maven-shared-components parent to version 30 * [MSHARED-550] - Removed hard code version for animal-sniffer-maven-plugin * [MSHARED-573] - Upgrade plexus-component-annotations to 1.7 to go in line with plexus-component-metadata plugin * [MSHARED-591] - Add interface to deploy a Maven Project * [MSHARED-593] - Add interface to install a Maven Project * [MSHARED-596] - Support for getting local metadata for RepositoryManager * [MSHARED-598] - Simplify ProjectInstaller by not requiring an ArtifactRepository Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
