Re: maven-assembly-plugin, bin example is giving me trouble
On 11.11.23 04:54, Alexander Kriegisch wrote: Tried making my top-level module dependent on all the others Don't! That does not make any logical sense. Checked in on xalan-java branch xalan-java-mvn-refactored Please always provide a link. I have no idea where to find your project. To you, that might be obvious. to others, it is not. Don't do that because the parent runs first ... if you need some dependency order define the appropriate dependencies in your modules which automatically orders the build reactor accordingly. If you have other issue please show a real example what exactly the problem is... 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-assembly-plugin, bin example is giving me trouble
Duh. Just noticed that the FAQ explicitly mentions creating a child module just to achieve this sequencing in multi-module projects. Mea culpa, mea maxima culpa... I'd have hoped something could be done with phase and target, but if not, not. On 11/11/2023 11:44 AM, Joseph Kessselman wrote: Sorry: https://github.com/apache/xalan-java/tree/xalan-java-mvn-refactored (which currently has the binary assembly commented out). Dependency order... Well, I'm currently running the assembly at the top level, which would presumably mean it has to run after packaging of the contained modules. I suppose I could try moving it down to the module at the farthest end of the current dependency chain, or even into a new module which exists just to depend on everything else, but that feels like I'm solving the wrong problem; "give me an assembly for the whole project" is conceptually a top-level operation and I'd expect to invoke it from the root module. On 11/10/2023 10:54 PM, Alexander Kriegisch wrote: Tried making my top-level module dependent on all the others Don't! That does not make any logical sense. Checked in on xalan-java branch xalan-java-mvn-refactored Please always provide a link. I have no idea where to find your project. To you, that might be obvious. to others, it is not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin, bin example is giving me trouble
Sorry: https://github.com/apache/xalan-java/tree/xalan-java-mvn-refactored (which currently has the binary assembly commented out). Dependency order... Well, I'm currently running the assembly at the top level, which would presumably mean it has to run after packaging of the contained modules. I suppose I could try moving it down to the module at the farthest end of the current dependency chain, or even into a new module which exists just to depend on everything else, but that feels like I'm solving the wrong problem; "give me an assembly for the whole project" is conceptually a top-level operation and I'd expect to invoke it from the root module. On 11/10/2023 10:54 PM, Alexander Kriegisch wrote: Tried making my top-level module dependent on all the others Don't! That does not make any logical sense. Checked in on xalan-java branch xalan-java-mvn-refactored Please always provide a link. I have no idea where to find your project. To you, that might be obvious. to others, it is not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin, bin example is giving me trouble
> Tried making my top-level module dependent on all the others Don't! That does not make any logical sense. > Checked in on xalan-java branch xalan-java-mvn-refactored Please always provide a link. I have no idea where to find your project. To you, that might be obvious. to others, it is not. -- Alexander Kriegisch Joseph Kessselman schrieb am 11.11.2023 09:51 (GMT +07:00): > Tried making my top-level module dependent on all the others so the > assembly invoked there would run last. Unfortunately, it seems the > dependencies are inherited to all the children, and Maven complains > about dependencies upon self. > > I presume there's an obvious idiom that I just haven't yet beaten into > my head. > > Checked in on xalan-java branch xalan-java-mvn-refactored with bin > assembly commented out, if anyone wants to see it in context. > > > On 11/10/2023 9:37 PM, Joseph Kessselman wrote: >> Oh. I probably forgot to set dependencies. Checking. >> >> >> On 11/10/2023 9:35 PM, Joseph Kessselman wrote: >>> I'm trying to adapt the examples given at >>> https://maven.apache.org/plugins/maven-assembly-plugin to work with my >>> multi-module project. >>> >>> Source was mostly easy -- I copied the into a file, >>> tweaked its excludes (still wish it picked up the .gitinclude >>> automagically), and it worked. I'd still like to change which >>> directory the resulting archive files were written to, but that's a >>> nitpick; maybe I can copy 'em to the "ant simulation" build/ directory >>> afterward. >>> >>> >>> But binary is giving me a bit more trouble. This is working for >>> others, so I presume it's another case of my just not understanding >>> the idiom well enough. >>> >>> >>> All I did was add one more to reference >>> src/assembly/bin.xml, and dropped there a copy of the >>> taken from the page, modified to output to tar.gz and zip. I changed the >>> s to reference my artifacts, and ran mvn package again. >>> >>> Maven objects to my first child module: >>> >>> > [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single >>> (make-assembly) on project xalan-project: Failed to create assembly: >>> Artifact: xalan:serializer:jar:2.7.3 (included by module) does not >>> have an artifact with a file. Please ensure the package phase is run >>> before the assembly is generated. -> [Help 1] >>> >>> >>> This confuses me. There is indeed a file there, >>> serializer/target/serializer-2.7.3.jar, which xalan:xalan seems to >>> successfully use as the artifact for further compilation. Why isn't >>> maven-assembly-plugin finding and using it? >>> >>> If I take out the section entirely (trying to rely on >>> defaults), I get the same error message. >>> >>> Does a assembly need to be put on a later phase? Or a >>> different execution? >>> >>> >>> Any advice would bemore than welcome...! >>> >>> >>> In my pom.xml, last plugin before : >>> ... >>> >>> maven-assembly-plugin >>> 3.6.0 >>> false >>> >>> >>> src/assembly/src.xml >>> src/assembly/bin.xml >>> >>> >>> >>> >>> make-assembly >>> package >>> >>> single >>> >>> >>> >>> >>> ... >>> >>> And my bin.xml: >>> >>> >>> >>> http://maven.apache.org/ASSEMBLY/2.2.0"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> >>> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.2.0 >>> http://maven.apache.org/xsd/assembly-2.2.0.xsd";> >>> bin >>> >>> tar.gz >>> zip >>> >>> true >>> >>> >>> >>> true >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> modules/maven-assembly-plugin >>> false >>> >>> >>> >>> > > - > 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
Re: maven-assembly-plugin, bin example is giving me trouble
Tried making my top-level module dependent on all the others so the assembly invoked there would run last. Unfortunately, it seems the dependencies are inherited to all the children, and Maven complains about dependencies upon self. I presume there's an obvious idiom that I just haven't yet beaten into my head. Checked in on xalan-java branch xalan-java-mvn-refactored with bin assembly commented out, if anyone wants to see it in context. On 11/10/2023 9:37 PM, Joseph Kessselman wrote: Oh. I probably forgot to set dependencies. Checking. On 11/10/2023 9:35 PM, Joseph Kessselman wrote: I'm trying to adapt the examples given at https://maven.apache.org/plugins/maven-assembly-plugin to work with my multi-module project. Source was mostly easy -- I copied the into a file, tweaked its excludes (still wish it picked up the .gitinclude automagically), and it worked. I'd still like to change which directory the resulting archive files were written to, but that's a nitpick; maybe I can copy 'em to the "ant simulation" build/ directory afterward. But binary is giving me a bit more trouble. This is working for others, so I presume it's another case of my just not understanding the idiom well enough. All I did was add one more to reference src/assembly/bin.xml, and dropped there a copy of the taken from the page, modified to output to tar.gz and zip. I changed the s to reference my artifacts, and ran mvn package again. Maven objects to my first child module: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (make-assembly) on project xalan-project: Failed to create assembly: Artifact: xalan:serializer:jar:2.7.3 (included by module) does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. -> [Help 1] This confuses me. There is indeed a file there, serializer/target/serializer-2.7.3.jar, which xalan:xalan seems to successfully use as the artifact for further compilation. Why isn't maven-assembly-plugin finding and using it? If I take out the section entirely (trying to rely on defaults), I get the same error message. Does a assembly need to be put on a later phase? Or a different execution? Any advice would bemore than welcome...! In my pom.xml, last plugin before : ... maven-assembly-plugin 3.6.0 false src/assembly/src.xml src/assembly/bin.xml make-assembly package single ... And my bin.xml: http://maven.apache.org/ASSEMBLY/2.2.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.2.0 http://maven.apache.org/xsd/assembly-2.2.0.xsd";> bin tar.gz zip true true modules/maven-assembly-plugin false - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin, bin example is giving me trouble
Oh. I probably forgot to set dependencies. Checking. On 11/10/2023 9:35 PM, Joseph Kessselman wrote: I'm trying to adapt the examples given at https://maven.apache.org/plugins/maven-assembly-plugin to work with my multi-module project. Source was mostly easy -- I copied the into a file, tweaked its excludes (still wish it picked up the .gitinclude automagically), and it worked. I'd still like to change which directory the resulting archive files were written to, but that's a nitpick; maybe I can copy 'em to the "ant simulation" build/ directory afterward. But binary is giving me a bit more trouble. This is working for others, so I presume it's another case of my just not understanding the idiom well enough. All I did was add one more to reference src/assembly/bin.xml, and dropped there a copy of the taken from the page, modified to output to tar.gz and zip. I changed the s to reference my artifacts, and ran mvn package again. Maven objects to my first child module: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (make-assembly) on project xalan-project: Failed to create assembly: Artifact: xalan:serializer:jar:2.7.3 (included by module) does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. -> [Help 1] This confuses me. There is indeed a file there, serializer/target/serializer-2.7.3.jar, which xalan:xalan seems to successfully use as the artifact for further compilation. Why isn't maven-assembly-plugin finding and using it? If I take out the section entirely (trying to rely on defaults), I get the same error message. Does a assembly need to be put on a later phase? Or a different execution? Any advice would bemore than welcome...! In my pom.xml, last plugin before : ... maven-assembly-plugin 3.6.0 false src/assembly/src.xml src/assembly/bin.xml make-assembly package single ... And my bin.xml: http://maven.apache.org/ASSEMBLY/2.2.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.2.0 http://maven.apache.org/xsd/assembly-2.2.0.xsd";> bin tar.gz zip true true modules/maven-assembly-plugin false - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven assembly plugin - Proxies not working with mirrors
Sorry not familiar with proxies. Make sure there isn't a bug at https://issues.apache.org/jira/projects/MNG/issues/MNG-7642?filter=allopenissues Delany On Thu, 22 Dec 2022 at 15:34, Abhinav Sharma wrote: > I have tried with maven 3.8.6 as well. Same error comes. > > On Thu, 22 Dec, 2022, 19:00 Delany, wrote: > > > Use Maven v3.8.6 if you can Abhinav > > Delany > > > > > > On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma > > wrote: > > > > > Hi, > > > I am using maven 3.8.2 with java 11 in my system, with remotes > configured > > > for jfrog artifactory. > > > > > > With both mirror and proxy added, mvn is ignoring the proxies and > failing > > > to resolve any dependency. How do I set proxies for maven mirrors as > > well? > > > > > > Without a mirror, the maven assembly plugin is not looking in the > > > configured jfrog repositories for the dependencies. It starts looking > at > > > some random repo. > > > > > > [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project > > --- > > > Downloading from jvnet-nexus-staging: > > > http://maven.java.net/content/repositories/staging/ > > > < > > > > > > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > >com/example/sample-project/0.0.1-SNAPSHOT > > > < > > > > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > >/maven-metadata.xml > > > < > > > > > > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > > > Downloading from releases.java.net: > > > http://maven.java.net/content/repositories/releases/ > > > < > > > > > > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > >com/example/sample-project/0.0.1-SNAPSHOT > > > < > > > > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > >/maven-metadata.xml > > > < > > > > > > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > > > Downloading from shapshots.java.net: > > > > > > > > > http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml > > > < > > > > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > > > > > > > > > I am expecting to access jfrog maven virtual repo with mirror enabled > > > behind the company proxy, or force assembly plugin to look into the > > > repositories defined in settings.xml. > > > > > > I am using settings.xml file similar to this: > > > > > > > > > http://maven.apache.org/SETTINGS/1.2.0 > > > http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns=" > > > http://maven.apache.org/SETTINGS/1.2.0"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > username > > > password > > > central > > > > > > > > > username > > > password > > > snapshots > > > > > > > > > > > > > > > * > > > project-repo > > > https://company.jfrog.io/artifactory/project-repo > > > project-repo > > > > > > > > > > > > > > > > > > > > > > > > false > > > > > > central > > > project-repo > > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > > > > > snapshots > > > project-repo > > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > > > > > > > > > > > false > > > > > > central > > > project-repo > > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > > > > > snapshots > > > project-repo > > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > > artifactory > > > > > > > > > > > > artifactory > > > > > > > > > > > > jfrog-proxy > > > true > > > https > > > proxyhost > > > proxyport > > > > > > > > > > > > > > >
Re: Maven assembly plugin - Proxies not working with mirrors
I have tried with maven 3.8.6 as well. Same error comes. On Thu, 22 Dec, 2022, 19:00 Delany, wrote: > Use Maven v3.8.6 if you can Abhinav > Delany > > > On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma > wrote: > > > Hi, > > I am using maven 3.8.2 with java 11 in my system, with remotes configured > > for jfrog artifactory. > > > > With both mirror and proxy added, mvn is ignoring the proxies and failing > > to resolve any dependency. How do I set proxies for maven mirrors as > well? > > > > Without a mirror, the maven assembly plugin is not looking in the > > configured jfrog repositories for the dependencies. It starts looking at > > some random repo. > > > > [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project > --- > > Downloading from jvnet-nexus-staging: > > http://maven.java.net/content/repositories/staging/ > > < > > > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > >com/example/sample-project/0.0.1-SNAPSHOT > > < > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > >/maven-metadata.xml > > < > > > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > Downloading from releases.java.net: > > http://maven.java.net/content/repositories/releases/ > > < > > > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > >com/example/sample-project/0.0.1-SNAPSHOT > > < > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > >/maven-metadata.xml > > < > > > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > Downloading from shapshots.java.net: > > > > > http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml > > < > > > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > > > > > I am expecting to access jfrog maven virtual repo with mirror enabled > > behind the company proxy, or force assembly plugin to look into the > > repositories defined in settings.xml. > > > > I am using settings.xml file similar to this: > > > > > > http://maven.apache.org/SETTINGS/1.2.0 > > http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns=" > > http://maven.apache.org/SETTINGS/1.2.0"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > username > > password > > central > > > > > > username > > password > > snapshots > > > > > > > > > > * > > project-repo > > https://company.jfrog.io/artifactory/project-repo > > project-repo > > > > > > > > > > > > > > > > false > > > > central > > project-repo > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > snapshots > > project-repo > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > > > > > false > > > > central > > project-repo > > https://company.jfrog.io/artifactory/project-repo > > > > > > > > snapshots > > project-repo > > https://company.jfrog.io/artifactory/project-repo > > > > > > artifactory > > > > > > > > artifactory > > > > > > > > jfrog-proxy > > true > > https > > proxyhost > > proxyport > > > > > > > > >
Re: Maven assembly plugin - Proxies not working with mirrors
Use Maven v3.8.6 if you can Abhinav Delany On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma wrote: > Hi, > I am using maven 3.8.2 with java 11 in my system, with remotes configured > for jfrog artifactory. > > With both mirror and proxy added, mvn is ignoring the proxies and failing > to resolve any dependency. How do I set proxies for maven mirrors as well? > > Without a mirror, the maven assembly plugin is not looking in the > configured jfrog repositories for the dependencies. It starts looking at > some random repo. > > [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project --- > Downloading from jvnet-nexus-staging: > http://maven.java.net/content/repositories/staging/ > < > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > >com/example/sample-project/0.0.1-SNAPSHOT > < > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > >/maven-metadata.xml > < > http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > Downloading from releases.java.net: > http://maven.java.net/content/repositories/releases/ > < > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > >com/example/sample-project/0.0.1-SNAPSHOT > < > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > >/maven-metadata.xml > < > http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > Downloading from shapshots.java.net: > > http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml > < > http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml > > > > > I am expecting to access jfrog maven virtual repo with mirror enabled > behind the company proxy, or force assembly plugin to look into the > repositories defined in settings.xml. > > I am using settings.xml file similar to this: > > > http://maven.apache.org/SETTINGS/1.2.0 > http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns=" > http://maven.apache.org/SETTINGS/1.2.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > username > password > central > > > username > password > snapshots > > > > > * > project-repo > https://company.jfrog.io/artifactory/project-repo > project-repo > > > > > > > > false > > central > project-repo > https://company.jfrog.io/artifactory/project-repo > > > > snapshots > project-repo > https://company.jfrog.io/artifactory/project-repo > > > > > > false > > central > project-repo > https://company.jfrog.io/artifactory/project-repo > > > > snapshots > project-repo > https://company.jfrog.io/artifactory/project-repo > > > artifactory > > > > artifactory > > > > jfrog-proxy > true > https > proxyhost > proxyport > > > >
Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
Howdy,
yes, maven-common-artifact-filters vote/release is ongoing, next will be
m-asembly-p 3.4.2
filters is out tomorrow (3 day vote), and then m-asembly-p release (another
3 day vote).
HTH
T
On Tue, Jul 19, 2022 at 12:56 PM Jean Pierre URKENS
wrote:
> Looks like the issue is already reported:
>
> https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969?filter=allopenissues
> and solved by
> https://github.com/apache/maven-common-artifact-filters/pull/29.
>
> Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0 ->
> fails
> Maven-Assembly-Plugin v3.3.0 uses maven-common-artifact-filters v3.1.0 ->
> works
>
> I will need maven-common-artifact-filters v3.3.1 released on 16/07/2022.
>
>
>
> -Original Message-
> From: Karl Heinz Marbaise
> Sent: dinsdag 19 juli 2022 12:39
> To: Maven Users List
> Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly
> descriptors?
>
> Hi,
>
>
> can you make an example project on github or alike...
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 19.07.22 12:07, Jean Pierre URKENS wrote:
> > I am trying to re-zip some deliverables into one packaging using the
> > maven-assembly-plugin.
> >
> > My plugin configuration looks like:
> >
> >
> >
> > org.apache.maven.plugins
> >
> >
> > *maven-assembly-plugin*
> >
> > 3.4.1
> >
> >
> >
> >
> >
> > dvtm.base
> >
> > Assembly
> >
> >
> > ${dvtm.base.assembly.version} > version>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > unziprezip
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I.e. the descriptor unziprezip is located in the artifact
> > dvtm.base.Assembly and contains a dependencySet as follows:
> >
> >
> >
> >
> >
> > provided
> >
> > /
> >
> > false
> >
> > true
> >
> >
> >
> >**
> >
> > dvtm*:*:zip:deliverables
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Now if I try to execute ‘mvn assembly:single’ I get the error: Error
> > creating assembly archive deliverables: archive cannot be empty ->
> > [Help 1]
> >
> >
> >
> > Looking at the maven log file I see that:
> >
> > 0.The plugin configuration looks like:
> >
> > [DEBUG] Configuring mojo
> > 'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with
> > basic configurator -->
> >
> > [DEBUG] (s) appendAssemblyId = true
> >
> > [DEBUG] (f) attach = true
> >
> > [DEBUG] (s) basedir =
> > f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent
> >
> > [DEBUG] (s) descriptorRefs = [unziprezip]
> >
> > [DEBUG] (f) dryRun = false
> >
> > [DEBUG] (f) encoding = UTF-8
> >
> > [DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT
> >
> > [DEBUG] (f) ignoreDirFormatExtensions = true
> >
> > [DEBUG] (f) ignoreMissingDescriptor = false
> >
> > [DEBUG] (f) ignorePermissions = false
> >
> > [DEBUG] (f) includeProjectBuildFilters = true
> >
> > [DEBUG] (s) localRepository = id: local
> >
> > [DEBUG] (f) mavenSession =
> > org.apache.maven.execution.MavenSession@586cc15d
> >
> > [DEBUG] (s) outputDirectory =
> > f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target
> >
> > [DEBUG] (f) project = MavenProject:
> > dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
> > f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
> >
> > [DEBUG] (s) reactorProjects = [MavenProject:
> > dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
> > f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
> > ]
> >
> > [DEBUG] (f) recompressZippedFiles = true
> >
> > [DEBUG] (f) remoteRepositories = […]
> &g
RE: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
Unfortunately,
I already tried it but v3.3.1 of the maven-common-artifact-filters is for
the moment in no maven repository available, so dependency resolution fails.
I don't know where to download the artifact otherwise (github page doesn't
include references to builds).
Kind Regards,
J.P.
-Original Message-
From: Karl Heinz Marbaise
Sent: dinsdag 19 juli 2022 13:42
To: Maven Users List
Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly
descriptors?
Hi,
You can verify that if you simply add the maven-common-artifact-filters
version in the dependencies part of the plugin configuration where you
defined the
dvtm.base
Assembly
Kind regards
Karl Heinz Marbaise
On 19.07.22 12:55, Jean Pierre URKENS wrote:
> Looks like the issue is already reported:
> https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969
> ?filter=allopenissues
> and solved by
> https://github.com/apache/maven-common-artifact-filters/pull/29.
>
> Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0
> -> fails Maven-Assembly-Plugin v3.3.0 uses
> maven-common-artifact-filters v3.1.0 -> works
>
> I will need maven-common-artifact-filters v3.3.1 released on 16/07/2022.
>
>
>
> -Original Message-
> From: Karl Heinz Marbaise
> Sent: dinsdag 19 juli 2022 12:39
> To: Maven Users List
> Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing
> assembly descriptors?
>
> Hi,
>
>
> can you make an example project on github or alike...
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 19.07.22 12:07, Jean Pierre URKENS wrote:
>> I am trying to re-zip some deliverables into one packaging using the
>> maven-assembly-plugin.
>>
>> My plugin configuration looks like:
>>
>>
>>
>>org.apache.maven.plugins
>>
>>
>> *maven-assembly-plugin*
>>
>> 3.4.1
>>
>>
>>
>>
>>
>>dvtm.base
>>
>> Assembly
>>
>>
>> ${dvtm.base.assembly.version}> version>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> unziprezip
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> I.e. the descriptor unziprezip is located in the artifact
>> dvtm.base.Assembly and contains a dependencySet as follows:
>>
>>
>>
>>
>>
>> provided
>>
>> /
>>
>> false
>>
>> true
>>
>>
>>
>> **
>>
>> dvtm*:*:zip:deliverables
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Now if I try to execute ‘mvn assembly:single’ I get the error: Error
>> creating assembly archive deliverables: archive cannot be empty ->
>> [Help 1]
>>
>>
>>
>> Looking at the maven log file I see that:
>>
>> 0.The plugin configuration looks like:
>>
>> [DEBUG] Configuring mojo
>> 'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with
>> basic configurator -->
>>
>> [DEBUG] (s) appendAssemblyId = true
>>
>> [DEBUG] (f) attach = true
>>
>> [DEBUG] (s) basedir =
>> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent
>>
>> [DEBUG] (s) descriptorRefs = [unziprezip]
>>
>> [DEBUG] (f) dryRun = false
>>
>> [DEBUG] (f) encoding = UTF-8
>>
>> [DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT
>>
>> [DEBUG] (f) ignoreDirFormatExtensions = true
>>
>> [DEBUG] (f) ignoreMissingDescriptor = false
>>
>> [DEBUG] (f) ignorePermissions = false
>>
>> [DEBUG] (f) includeProjectBuildFilters = true
>>
>> [DEBUG] (s) localRepository = id: local
>>
>> [DEBUG] (f) mavenSession =
>> org.apache.maven.execution.MavenSession@586cc15d
>>
>> [DEBUG] (s) outputDirectory =
>> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target
>>
>> [DEBUG] (f) project = MavenProject:
>> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
>> f:\Documents\Workspaces\AEO-Gitlab\a
Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
Hi,
You can verify that if you simply add the maven-common-artifact-filters
version in the dependencies part of the plugin configuration where you
defined the
dvtm.base
Assembly
Kind regards
Karl Heinz Marbaise
On 19.07.22 12:55, Jean Pierre URKENS wrote:
Looks like the issue is already reported:
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969?filter=allopenissues
and solved by
https://github.com/apache/maven-common-artifact-filters/pull/29.
Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0 ->
fails
Maven-Assembly-Plugin v3.3.0 uses maven-common-artifact-filters v3.1.0 ->
works
I will need maven-common-artifact-filters v3.3.1 released on 16/07/2022.
-Original Message-
From: Karl Heinz Marbaise
Sent: dinsdag 19 juli 2022 12:39
To: Maven Users List
Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly
descriptors?
Hi,
can you make an example project on github or alike...
Kind regards
Karl Heinz Marbaise
On 19.07.22 12:07, Jean Pierre URKENS wrote:
I am trying to re-zip some deliverables into one packaging using the
maven-assembly-plugin.
My plugin configuration looks like:
org.apache.maven.plugins
*maven-assembly-plugin*
3.4.1
dvtm.base
Assembly
${dvtm.base.assembly.version}
unziprezip
I.e. the descriptor unziprezip is located in the artifact
dvtm.base.Assembly and contains a dependencySet as follows:
provided
/
false
true
**
dvtm*:*:zip:deliverables
Now if I try to execute ‘mvn assembly:single’ I get the error: Error
creating assembly archive deliverables: archive cannot be empty ->
[Help 1]
Looking at the maven log file I see that:
0.The plugin configuration looks like:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with
basic configurator -->
[DEBUG] (s) appendAssemblyId = true
[DEBUG] (f) attach = true
[DEBUG] (s) basedir =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent
[DEBUG] (s) descriptorRefs = [unziprezip]
[DEBUG] (f) dryRun = false
[DEBUG] (f) encoding = UTF-8
[DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT
[DEBUG] (f) ignoreDirFormatExtensions = true
[DEBUG] (f) ignoreMissingDescriptor = false
[DEBUG] (f) ignorePermissions = false
[DEBUG] (f) includeProjectBuildFilters = true
[DEBUG] (s) localRepository = id: local
[DEBUG] (f) mavenSession =
org.apache.maven.execution.MavenSession@586cc15d
[DEBUG] (s) outputDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target
[DEBUG] (f) project = MavenProject:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
[DEBUG] (s) reactorProjects = [MavenProject:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
]
[DEBUG] (f) recompressZippedFiles = true
[DEBUG] (f) remoteRepositories = […]
[DEBUG] (f) runOnlyAtExecutionRoot = false
[DEBUG] (s) siteDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
site
[DEBUG] (f) skipAssembly = false
[DEBUG] (s) tarLongFileMode = warn
[DEBUG] (s) tempRoot =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
archive-tmp
[DEBUG] (f) updateOnly = false
[DEBUG] (f) useJvmChmod = false
[DEBUG] (s) workDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
assembly\work
[DEBUG] -- end configuration --
1.My project dependencies are included (and they do exist):
[DEBUG] Dependencies for project:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:jar:6.0.0-SNAPSHOT are:
dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0:provided
dvtm.aeo.kmop:AEO-KMO-Portefeuille-EAWS-webservice:zip:deliverables:2.
0.2:provided
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Emittent:zip:deliverables:4.0.0:pro
vided
…
2.All my dependencies are filtered out when processing the dependencySet:
[DEBUG] Processing DependencySet (output=/)
[DEBUG] Filtering dependency artifacts WITHOUT transitive dependency
path information.
[DEBUG] dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0 *was
removed by one or more filters*.
…
3.In the end nothing is included in my assembly hence the final error
‘archive cannot be empty’
My project d
RE: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
Looks like the issue is already reported:
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969?filter=allopenissues
and solved by
https://github.com/apache/maven-common-artifact-filters/pull/29.
Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0 ->
fails
Maven-Assembly-Plugin v3.3.0 uses maven-common-artifact-filters v3.1.0 ->
works
I will need maven-common-artifact-filters v3.3.1 released on 16/07/2022.
-Original Message-
From: Karl Heinz Marbaise
Sent: dinsdag 19 juli 2022 12:39
To: Maven Users List
Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly
descriptors?
Hi,
can you make an example project on github or alike...
Kind regards
Karl Heinz Marbaise
On 19.07.22 12:07, Jean Pierre URKENS wrote:
> I am trying to re-zip some deliverables into one packaging using the
> maven-assembly-plugin.
>
> My plugin configuration looks like:
>
>
>
> org.apache.maven.plugins
>
>
> *maven-assembly-plugin*
>
> 3.4.1
>
>
>
>
>
> dvtm.base
>
> Assembly
>
>
> ${dvtm.base.assembly.version} version>
>
>
>
>
>
>
>
>
>
>
> unziprezip
>
>
>
>
>
>
>
>
>
> I.e. the descriptor unziprezip is located in the artifact
> dvtm.base.Assembly and contains a dependencySet as follows:
>
>
>
>
>
> provided
>
> /
>
> false
>
> true
>
>
>
>**
>
> dvtm*:*:zip:deliverables
>
>
>
>
>
>
>
>
>
> Now if I try to execute ‘mvn assembly:single’ I get the error: Error
> creating assembly archive deliverables: archive cannot be empty ->
> [Help 1]
>
>
>
> Looking at the maven log file I see that:
>
> 0.The plugin configuration looks like:
>
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with
> basic configurator -->
>
> [DEBUG] (s) appendAssemblyId = true
>
> [DEBUG] (f) attach = true
>
> [DEBUG] (s) basedir =
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent
>
> [DEBUG] (s) descriptorRefs = [unziprezip]
>
> [DEBUG] (f) dryRun = false
>
> [DEBUG] (f) encoding = UTF-8
>
> [DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT
>
> [DEBUG] (f) ignoreDirFormatExtensions = true
>
> [DEBUG] (f) ignoreMissingDescriptor = false
>
> [DEBUG] (f) ignorePermissions = false
>
> [DEBUG] (f) includeProjectBuildFilters = true
>
> [DEBUG] (s) localRepository = id: local
>
> [DEBUG] (f) mavenSession =
> org.apache.maven.execution.MavenSession@586cc15d
>
> [DEBUG] (s) outputDirectory =
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target
>
> [DEBUG] (f) project = MavenProject:
> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
>
> [DEBUG] (s) reactorProjects = [MavenProject:
> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
> ]
>
> [DEBUG] (f) recompressZippedFiles = true
>
> [DEBUG] (f) remoteRepositories = […]
>
> [DEBUG] (f) runOnlyAtExecutionRoot = false
>
> [DEBUG] (s) siteDirectory =
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
> site
>
> [DEBUG] (f) skipAssembly = false
>
> [DEBUG] (s) tarLongFileMode = warn
>
> [DEBUG] (s) tempRoot =
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
> archive-tmp
>
> [DEBUG] (f) updateOnly = false
>
> [DEBUG] (f) useJvmChmod = false
>
> [DEBUG] (s) workDirectory =
> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\
> assembly\work
>
> [DEBUG] -- end configuration --
>
> 1.My project dependencies are included (and they do exist):
>
> [DEBUG] Dependencies for project:
> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:jar:6.0.0-SNAPSHOT are:
>
> dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0:provided
>
> dvtm.aeo.kmop:AEO-KMO-Portefeuille-EAWS-webservice:zip:deliverables:2.
> 0.2:provided
>
> dvtm.aeo.kmop:AEO-KMO-Portefeu
Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
Hi,
can you make an example project on github or alike...
Kind regards
Karl Heinz Marbaise
On 19.07.22 12:07, Jean Pierre URKENS wrote:
I am trying to re-zip some deliverables into one packaging using the
maven-assembly-plugin.
My plugin configuration looks like:
org.apache.maven.plugins
*maven-assembly-plugin*
3.4.1
dvtm.base
Assembly
${dvtm.base.assembly.version}
unziprezip
I.e. the descriptor unziprezip is located in the artifact
dvtm.base.Assembly and contains a dependencySet as follows:
provided
/
false
true
**
dvtm*:*:zip:deliverables
Now if I try to execute ‘mvn assembly:single’ I get the error: Error
creating assembly archive deliverables: archive cannot be empty -> [Help 1]
Looking at the maven log file I see that:
0.The plugin configuration looks like:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with basic
configurator -->
[DEBUG] (s) appendAssemblyId = true
[DEBUG] (f) attach = true
[DEBUG] (s) basedir =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent
[DEBUG] (s) descriptorRefs = [unziprezip]
[DEBUG] (f) dryRun = false
[DEBUG] (f) encoding = UTF-8
[DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT
[DEBUG] (f) ignoreDirFormatExtensions = true
[DEBUG] (f) ignoreMissingDescriptor = false
[DEBUG] (f) ignorePermissions = false
[DEBUG] (f) includeProjectBuildFilters = true
[DEBUG] (s) localRepository = id: local
[DEBUG] (f) mavenSession =
org.apache.maven.execution.MavenSession@586cc15d
[DEBUG] (s) outputDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target
[DEBUG] (f) project = MavenProject:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml
[DEBUG] (s) reactorProjects = [MavenProject:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xml]
[DEBUG] (f) recompressZippedFiles = true
[DEBUG] (f) remoteRepositories = […]
[DEBUG] (f) runOnlyAtExecutionRoot = false
[DEBUG] (s) siteDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\site
[DEBUG] (f) skipAssembly = false
[DEBUG] (s) tarLongFileMode = warn
[DEBUG] (s) tempRoot =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\archive-tmp
[DEBUG] (f) updateOnly = false
[DEBUG] (f) useJvmChmod = false
[DEBUG] (s) workDirectory =
f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target\assembly\work
[DEBUG] -- end configuration --
1.My project dependencies are included (and they do exist):
[DEBUG] Dependencies for project:
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:jar:6.0.0-SNAPSHOT are:
dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0:provided
dvtm.aeo.kmop:AEO-KMO-Portefeuille-EAWS-webservice:zip:deliverables:2.0.2:provided
dvtm.aeo.kmop:AEO-KMO-Portefeuille-Emittent:zip:deliverables:4.0.0:provided
…
2.All my dependencies are filtered out when processing the dependencySet:
[DEBUG] Processing DependencySet (output=/)
[DEBUG] Filtering dependency artifacts WITHOUT transitive dependency path
information.
[DEBUG] dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0 *was
removed by one or more filters*.
…
3.In the end nothing is included in my assembly hence the final error
‘archive cannot be empty’
My project dependencies (see point 1) do match with the -filter of
my dependencySet.
Referring to
https://maven.apache.org/plugins/maven-assembly-plugin/advanced-descriptor-topics.html
, I do not understand why my dependencies are are filtered out?
Is there a reference manual describing the exact configuration of the maven
element ?
*NOTE:* with maven-assembly-plugin set to version 3.3.0 the archive is
correctly assembled.
Regards,
J.P.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
Thanks, exactly what I was looking for.
-Original Message-
From: Thomas Broyer
Sent: donderdag 18 februari 2021 11:44
To: jean-pierre.urk...@devoteam.com.invalid
Cc: Maven Users List
Subject: Re: maven-assembly-plugin v3.3.0 - how to modify generated
MANIFEST.MF
Use the 'archive' property of the assembly plugin itself (not in the
assembly descriptor):
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#archive
Le jeu. 18 févr. 2021 à 11:23, Jean-Pierre Urkens
a écrit :
> Hi all,
>
>
>
> I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’
> in the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
> generating its own (plexus archiver) MANIFEST file with contents:
>
>Manifest-Version: 1.0
>
> Created-By: Plexus Archiver 4.2.1
>
>
>
> My idea was to include via a my own MANIFEST.MF file
> specifying the Main-Class and ‘append’ this to the generated MANIFEST
> using the ‘file-aggregator’ containerDescriptorHandler in my descriptor
> file:
>
>
>
>
>
>
>
> file-aggregator
>
>
>
> .*/MANIFEST.MF
>
> META-INF/MANIFEST.MF
>
>
>
>
>
>
>
>
>
> This didn’t work so I was wondering whether it found my manifest file.
> So I adjusted the above configuration to write to ‘test/
> META-INF/MANIFEST.MF’.
>
> My own manifest file resides under ‘db/MANIFEST.MF’ and should be
> picked up
> by:
>
>
>
>
>
>
>
>
> ${project.build.directory}/classes
>
>
>
> false
>
>
>
> db/**
>
>
>
>
>
>
>
>
>
> Now it does generate an ‘test/META-INF/MANIFEST.MF’ but with following
> contents:
>
># Aggregated on Thu Feb 18 11:18:39 CET 2021 from:
>
>
>
> So it looks that the content of my ‘db/MANIFEST.MF’ isn’t included.
> What am I missing? How can I add my own content to the generated
> manifest file of this plugin?
>
>
>
> Tanks for any hints,
>
>
>
> J.P.
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
Use the 'archive' property of the assembly plugin itself (not in the
assembly descriptor):
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#archive
Le jeu. 18 févr. 2021 à 11:23, Jean-Pierre Urkens
a écrit :
> Hi all,
>
>
>
> I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’ in
> the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
> generating its own (plexus archiver) MANIFEST file with contents:
>
>Manifest-Version: 1.0
>
> Created-By: Plexus Archiver 4.2.1
>
>
>
> My idea was to include via a my own MANIFEST.MF file specifying
> the Main-Class and ‘append’ this to the generated MANIFEST using the
> ‘file-aggregator’ containerDescriptorHandler in my descriptor file:
>
>
>
>
>
>
>
> file-aggregator
>
>
>
> .*/MANIFEST.MF
>
> META-INF/MANIFEST.MF
>
>
>
>
>
>
>
>
>
> This didn’t work so I was wondering whether it found my manifest file. So I
> adjusted the above configuration to write to ‘test/
> META-INF/MANIFEST.MF’.
>
> My own manifest file resides under ‘db/MANIFEST.MF’ and should be picked up
> by:
>
>
>
>
>
>
>
> ${project.build.directory}/classes
>
>
>
> false
>
>
>
> db/**
>
>
>
>
>
>
>
>
>
> Now it does generate an ‘test/META-INF/MANIFEST.MF’ but with following
> contents:
>
># Aggregated on Thu Feb 18 11:18:39 CET 2021 from:
>
>
>
> So it looks that the content of my ‘db/MANIFEST.MF’ isn’t included. What am
> I missing? How can I add my own content to the generated manifest file of
> this plugin?
>
>
>
> Tanks for any hints,
>
>
>
> J.P.
>
Re: maven-assembly-plugin after plexus-archiver 4.2.0 is released; implement user/group override for archives
I'm working on that, to do (binary) Reproducible Builds with Maven: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74682318 There is a plexus-archiver GitHub issue https://github.com/codehaus-plexus/plexus-archiver/pull/124 Currently, on maven-assembly-plugin, this API will be used to set GID/UID to 0 = root when doing Reproducible Builds. I didn't work on opening these values as plugin parameter. Regards, Hervé Le samedi 28 septembre 2019, 20:42:06 CEST Karl Heinz Marbaise a écrit : > Hi, > > On 28.09.19 19:49, Václav Haisman wrote: > > Hi. > > > > I have noticed that Plexus Archiver 4.2.0 in SNAPSHOT version has grown > > methods like `org.codehaus.plexus.archiver.Archiver#setOverrideUid`. It > > seems that after it is released it should be possible implement Maven > > Assembly Plugin extension that would allow to use these methods to set, > > e.g., TAR archive owner/group entries to some reasonable value even on > > Windows. > > > > Is anyone already working on this? > > Does exist an JIRA issue for that? > > If not why not creating one? > > 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
Re: maven-assembly-plugin after plexus-archiver 4.2.0 is released; implement user/group override for archives
Hi, On 28.09.19 19:49, Václav Haisman wrote: Hi. I have noticed that Plexus Archiver 4.2.0 in SNAPSHOT version has grown methods like `org.codehaus.plexus.archiver.Archiver#setOverrideUid`. It seems that after it is released it should be possible implement Maven Assembly Plugin extension that would allow to use these methods to set, e.g., TAR archive owner/group entries to some reasonable value even on Windows. Is anyone already working on this? Does exist an JIRA issue for that? If not why not creating one? 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 assembly Plugin - ignore pom packaging
You should NOT have a plugin execution defined in a pom packaging project if it works as an aggregator. Instead just define it in pluginManagement and add it where you want the exection to be happening. Manfred Rahamim, Ben wrote on 2018-05-23 02:03: > Hi all, > > TL;DR – why isn’t a flag in the Maven assembly Plugin allowing to skip POMs > with packaging “pom” ? > > I have a question about using the Maven assembly Plugin. > > We have a parent POM, called “super-parent”, which is being used as a > parent to all of our projects. It includes all of the dependencies & the maven > assembly plugin, set to create a tar.gz. > > One of its children the “runtime-super-parent”, which all of the other > projects use as a parent, and it has “pom” as packaging type, as required. > Now, even though we don’t need it, the assembly plugin creates a tar.gz to > this POM as well, taking a lot of space in our repositories. > > The logical thing to me was to have a flag allowing us to exclude the pom > packaged projects from the plugin, hence the name “pom” packaging. > > Is there any way to achieve this? I haven’t found one. > > Thanks in advance, > Ben > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Assembly Plugin renaming jar
As you didn't post a complete log or pom.xml (i.e. no properties, or or
artifact metadata (group, artifactId, version, etc). We don't know what phase
or goal you're executing, etc. With what you provided it's difficult to discern
what's going on.
Maven Assembly Plugin assembles new artifacts... it's going to copy from your
.m2 to a representative location specified in your assembly descriptor. It
won't rename unless you explicity tell it to. You're doing some renaming, but
that's inside the artifact you're creating. I can only assume what's going on
without seeing the rest of your POM, assembly descriptor, and log.
You have things like this in your descriptor...
target/${artifactId}-${version}.${packaging}
/
${artifactId}.${packaging}
Note artifactID, version, packaging are going to be inherited from the POM,
they going to resolve from your descriptor. This all can have some strange side
effects because it looks like you're trying to include yourself but then rename
yourself to something different inside an artifact you're creating. To a
certain extent this looks a bit bizzare.
Without any other information on hand, the only think I can suggest is try
changing the setting for appendAssemblyId from false to true; then rerun and
inspect the log... what does the log say it's "renaming" it to? My suspicion
is that you'll see:
[DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
assembly location: lib/MyArtifact-bin-8.0.0.jar.
[DEBUG] Adding file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
archive location: Project/lib/MyArtifact-bin-8.0.0.jar
Before anyone can really help you futher, I'd say you need to provide more
complete information; redacted where appropriate, but it really needs to be
complete.
- JK
On 12/15/17, 10:18 AM, "Wilson, Sam" wrote:
Hey James,
The way you interpreted the version range is indeed what I intended (we use
semantic versioning.)
It is definitely renaming the jar. I checked the shasums of
MyArtifact-8.0.2.jar and the file included in the archive, and they match, even
though the file is named MyArtifact-8.0.0.jar.
The MANIFEST contains “lib/MyArtifact-8.0.2.jar” as an entry.
Why would it be named MyArtifact-bin-8.0.0.jar ever?
I can try to create a minimal repro, but it’ll be hard because this is a
big project with lots of parts.
Sam
From: James Klo
Reply-To: Maven Users List
Date: Friday, December 15, 2017 at 12:27 PM
To: Maven Users List
Subject: Re: Maven Assembly Plugin renaming jar
From the small snippet of log, it's bit confusing, because it looks like
the artifact you are assembling is named the same as the dependency you are
pulling in. Because you have this setting in the maven-assembly-plugin:
false
The generated Artifact is being named:
MyArtifact-8.0.0.jar
Instead of being named:
MyArtifact-bin-8.0.0.jar
Additionally, look at version range declaration for MyArtifact...
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
Per this enforcer docs:
https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html
I would read your requirement as
8.0.0-SNAPSHOT >= X < 9.0.0-SNAPSHOT
So it's not renaming your jar, it is fetching the most current version of
the dependent artifact defined for that range and adding it into your current
project assembly which just so happens to now have the same name AND a similar
version number.
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
On 12/15/17, 8:51 AM, "Wilson, Sam"
mailto:sawil...@akamai.com>> wrote:
Sorry to bump and old thread, but I’d appreciate it if someone had any
insight.
Sam
From: Sam Wilson mailto:sawil...@akamai.com>>
Reply-To: Maven Users List
mailto:users@maven.apache.org>>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org<mailto:users@maven.apache.org>"
mailto:users@maven.apache.org>>
Subject: Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
and 3.1.0.
Sam
On 11/24/2
Re: Maven Assembly Plugin renaming jar
Hey James,
The way you interpreted the version range is indeed what I intended (we use
semantic versioning.)
It is definitely renaming the jar. I checked the shasums of
MyArtifact-8.0.2.jar and the file included in the archive, and they match, even
though the file is named MyArtifact-8.0.0.jar.
The MANIFEST contains “lib/MyArtifact-8.0.2.jar” as an entry.
Why would it be named MyArtifact-bin-8.0.0.jar ever?
I can try to create a minimal repro, but it’ll be hard because this is a big
project with lots of parts.
Sam
From: James Klo
Reply-To: Maven Users List
Date: Friday, December 15, 2017 at 12:27 PM
To: Maven Users List
Subject: Re: Maven Assembly Plugin renaming jar
From the small snippet of log, it's bit confusing, because it looks like the
artifact you are assembling is named the same as the dependency you are pulling
in. Because you have this setting in the maven-assembly-plugin:
false
The generated Artifact is being named:
MyArtifact-8.0.0.jar
Instead of being named:
MyArtifact-bin-8.0.0.jar
Additionally, look at version range declaration for MyArtifact...
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
Per this enforcer docs:
https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html
I would read your requirement as
8.0.0-SNAPSHOT >= X < 9.0.0-SNAPSHOT
So it's not renaming your jar, it is fetching the most current version of the
dependent artifact defined for that range and adding it into your current
project assembly which just so happens to now have the same name AND a similar
version number.
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
On 12/15/17, 8:51 AM, "Wilson, Sam"
mailto:sawil...@akamai.com>> wrote:
Sorry to bump and old thread, but I’d appreciate it if someone had any
insight.
Sam
From: Sam Wilson mailto:sawil...@akamai.com>>
Reply-To: Maven Users List
mailto:users@maven.apache.org>>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org<mailto:users@maven.apache.org>"
mailto:users@maven.apache.org>>
Subject: Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
and 3.1.0.
Sam
On 11/24/2017 11:07 AM, Wilson, Sam wrote:
Hey!
Hopefully you can help me out. Maven assembly plugin seems to be renaming a
jar file without being told to, and it’s messing up my MANIFEST.MF classpath.
You notice in the snippet of mvn -X below the assembly plugin seems to be
getting version 8.0.2, but it renames it to 8.0.0.
Thanks,
Sam
---
mvn -X package
--
[…]
[DEBUG] Adding dependency artifact com.example:MyArtifact:jar:8.0.0.
[DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
assembly location: lib/MyArtifact-8.0.0.jar.
[DEBUG] Adding file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
archive location: Project/lib/MyArtifact-8.0.0.jar
[…]
---
Project/pom.xml
---
com.example
MyArtifact
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
org.apache.maven.plugins
maven-jar-plugin
2.4
true
lib/
com.example.MainClass
org.apache.maven.plugins
maven-assembly-plugin
2.2
package
single
${project.artifactId}
false
src/assembly/bin.xml
false
---
Project/src/assembly/bin.xml
---
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.
Re: Maven Assembly Plugin renaming jar
>From the small snippet of log, it's bit confusing, because it looks like the
>artifact you are assembling is named the same as the dependency you are
>pulling in. Because you have this setting in the maven-assembly-plugin:
false
The generated Artifact is being named:
MyArtifact-8.0.0.jar
Instead of being named:
MyArtifact-bin-8.0.0.jar
Additionally, look at version range declaration for MyArtifact...
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
Per this enforcer docs:
https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html
I would read your requirement as
8.0.0-SNAPSHOT >= X < 9.0.0-SNAPSHOT
So it's not renaming your jar, it is fetching the most current version of the
dependent artifact defined for that range and adding it into your current
project assembly which just so happens to now have the same name AND a similar
version number.
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
On 12/15/17, 8:51 AM, "Wilson, Sam" wrote:
Sorry to bump and old thread, but I’d appreciate it if someone had any
insight.
Sam
From: Sam Wilson
Reply-To: Maven Users List
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org"
Subject: Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
and 3.1.0.
Sam
On 11/24/2017 11:07 AM, Wilson, Sam wrote:
Hey!
Hopefully you can help me out. Maven assembly plugin seems to be renaming a
jar file without being told to, and it’s messing up my MANIFEST.MF classpath.
You notice in the snippet of mvn -X below the assembly plugin seems to be
getting version 8.0.2, but it renames it to 8.0.0.
Thanks,
Sam
---
mvn -X package
--
[…]
[DEBUG] Adding dependency artifact com.example:MyArtifact:jar:8.0.0.
[DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
assembly location: lib/MyArtifact-8.0.0.jar.
[DEBUG] Adding file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
archive location: Project/lib/MyArtifact-8.0.0.jar
[…]
---
Project/pom.xml
---
com.example
MyArtifact
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
org.apache.maven.plugins
maven-jar-plugin
2.4
true
lib/
com.example.MainClass
org.apache.maven.plugins
maven-assembly-plugin
2.2
package
single
${project.artifactId}
false
src/assembly/bin.xml
false
---
Project/src/assembly/bin.xml
---
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd";<http://maven.apache.org/xsd/assembly-1.1.0.xsd%22>>
bin
${artifactId}
tar.gz
dir
false
false
runtime
lib
target/${artifactId}-${version}.${packaging}
/
${artifactId}.${packaging}
Re: Maven Assembly Plugin renaming jar
Sam,
I am not an expert but dod you try not using 8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
but a defined version ?
Enrico
Il ven 15 dic 2017, 17:51 Wilson, Sam ha scritto:
> Sorry to bump and old thread, but I’d appreciate it if someone had any
> insight.
>
> Sam
>
> From: Sam Wilson
> Reply-To: Maven Users List
> Date: Friday, November 24, 2017 at 11:12 AM
> To: "users@maven.apache.org"
> Subject: Re: Maven Assembly Plugin renaming jar
>
> Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
> and 3.1.0.
>
> Sam
>
> On 11/24/2017 11:07 AM, Wilson, Sam wrote:
> Hey!
> Hopefully you can help me out. Maven assembly plugin seems to be renaming
> a jar file without being told to, and it’s messing up my MANIFEST.MF
> classpath.
> You notice in the snippet of mvn -X below the assembly plugin seems to be
> getting version 8.0.2, but it renames it to 8.0.0.
> Thanks,
> Sam
> ---
> mvn -X package
> --
> […]
> [DEBUG] Adding dependency artifact com.example:MyArtifact:jar:8.0.0.
> [DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
> /Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar
> to assembly location: lib/MyArtifact-8.0.0.jar.
> [DEBUG] Adding file:
> /Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar
> to archive location: Project/lib/MyArtifact-8.0.0.jar
> […]
> ---
> Project/pom.xml
> ---
>
>
>
>
>
> com.example
> MyArtifact
> [8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
>
>
>
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.4
>
>
>
> true
> lib/
> com.example.MainClass
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 2.2
>
>
> package
>
> single
>
>
>
> ${project.artifactId}
>
>
> false
>
>
>
> src/assembly/bin.xml
>
> false
>
>
>
>
>
> ---
> Project/src/assembly/bin.xml
> ---
> xmlns="
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";<
> http://maven.apache.org/xsd/assembly-1.1.0.xsd%22>>
> bin
> ${artifactId}
>
> tar.gz
> dir
>
>
>
> false
> false
> runtime
> lib
>
>
>
>
>
> target/${artifactId}-${version}.${packaging}
> /
> ${artifactId}.${packaging}
>
>
>
> src/main/resources/ProjectConfiguration.properties
> ${artifactId}.properties
> /
>
>
> log4j2.xml
> /
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org users-unsubscr...@maven.apache.org>
> For additional commands, e-mail: users-h...@maven.apache.org users-h...@maven.apache.org>
>
>
> --
-- Enrico Olivelli
Re: Maven Assembly Plugin renaming jar
Sorry to bump and old thread, but I’d appreciate it if someone had any insight.
Sam
From: Sam Wilson
Reply-To: Maven Users List
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org"
Subject: Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
and 3.1.0.
Sam
On 11/24/2017 11:07 AM, Wilson, Sam wrote:
Hey!
Hopefully you can help me out. Maven assembly plugin seems to be renaming a jar
file without being told to, and it’s messing up my MANIFEST.MF classpath.
You notice in the snippet of mvn -X below the assembly plugin seems to be
getting version 8.0.2, but it renames it to 8.0.0.
Thanks,
Sam
---
mvn -X package
--
[…]
[DEBUG] Adding dependency artifact com.example:MyArtifact:jar:8.0.0.
[DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
assembly location: lib/MyArtifact-8.0.0.jar.
[DEBUG] Adding file:
/Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
archive location: Project/lib/MyArtifact-8.0.0.jar
[…]
---
Project/pom.xml
---
com.example
MyArtifact
[8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
org.apache.maven.plugins
maven-jar-plugin
2.4
true
lib/
com.example.MainClass
org.apache.maven.plugins
maven-assembly-plugin
2.2
package
single
${project.artifactId}
false
src/assembly/bin.xml
false
---
Project/src/assembly/bin.xml
---
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd";<http://maven.apache.org/xsd/assembly-1.1.0.xsd%22>>
bin
${artifactId}
tar.gz
dir
false
false
runtime
lib
target/${artifactId}-${version}.${packaging}
/
${artifactId}.${packaging}
src/main/resources/ProjectConfiguration.properties
${artifactId}.properties
/
log4j2.xml
/
-
To unsubscribe, e-mail:
users-unsubscr...@maven.apache.org<mailto:users-unsubscr...@maven.apache.org>
For additional commands, e-mail:
users-h...@maven.apache.org<mailto:users-h...@maven.apache.org>
Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
and 3.1.0.
Sam
On 11/24/2017 11:07 AM, Wilson, Sam wrote:
> Hey!
>
> Hopefully you can help me out. Maven assembly plugin seems to be renaming a
> jar file without being told to, and it’s messing up my MANIFEST.MF classpath.
>
> You notice in the snippet of mvn -X below the assembly plugin seems to be
> getting version 8.0.2, but it renames it to 8.0.0.
>
> Thanks,
> Sam
>
> ---
> mvn -X package
> --
>
> […]
> [DEBUG] Adding dependency artifact com.example:MyArtifact:jar:8.0.0.
> [DEBUG] Adding artifact: com.example:MyArtifact:jar:8.0.0 with file:
> /Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
> assembly location: lib/MyArtifact-8.0.0.jar.
> [DEBUG] Adding file:
> /Users/me/.m2/repository/com/example/MyArtifact/8.0.2/MyArtifact-8.0.2.jar to
> archive location: Project/lib/MyArtifact-8.0.0.jar
> […]
>
> ---
> Project/pom.xml
> ---
>
>
>
>
>
>
> com.example
> MyArtifact
> [8.0.0-SNAPSHOT,9.0.0-SNAPSHOT)
>
>
>
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.4
>
>
>
> true
> lib/
> com.example.MainClass
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 2.2
>
>
> package
>
> single
>
>
>
> ${project.artifactId}
>
>
> false
>
>
> src/assembly/bin.xml
>
> false
>
>
>
>
>
>
> ---
> Project/src/assembly/bin.xml
> ---
>
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
> bin
> ${artifactId}
>
> tar.gz
> dir
>
>
>
> false
> false
> runtime
> lib
>
>
>
>
>
> target/${artifactId}-${version}.${packaging}
> /
> ${artifactId}.${packaging}
>
>
>
> src/main/resources/ProjectConfiguration.properties
> ${artifactId}.properties
> /
>
>
> log4j2.xml
> /
>
>
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin not recognizing
Thanks, I have it working with custom names when I don't mention the
for plugin. is there any side effect of not mentioning the
version ?
bikram
On Wed, Mar 8, 2017 at 10:32 AM, Paul Munsey
wrote:
> finalName has limited use. It works for me at the build level, as seen
> here:
>
> my-name-1.2.3
>
> ...
>
> But even then, Maven won't install (mvn install) that name. As Anders
> mentioned, if you want multiple assembled artifacts with different names,
> use true and your package file's id
> will be included in the filename.
>
> Paul
>
> -Original Message-
> From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
> Behalf Of Anders Hammar
> Sent: Tuesday, March 07, 2017 10:44 PM
> To: Maven Users List
> Subject: Re: maven assembly plugin not recognizing
>
> There is no finalName config parameter for the single goal, see [1]. I
> suggest that you use appendAssemblyId, which is the intended usage.
>
> [1] http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html
>
> /Anders
>
> On Tue, Mar 7, 2017 at 11:48 PM, Bikramjit Singh
> wrote:
>
> > I have following Question
> >
> > How do I use tag to give different name to two jars ? it
> > is not picking up the for 2nd ("client" )
> >
> > Am I doing it wrong ?
> >
> > I have following.
> >
> >
> >
> >
> > org.apache.maven.plugins
> > maven-assembly-plugin
> >
> >
> >
> > core-assembly
> > package
> >
> > single
> >
> >
> >
> >
> >
> > ${project.version}
> >
> >
> >
> >
> > src/main/core-descriptor.xml
> >
> > false
> >
> > ${project.basedir}/target/dist/framework/lib/server/<
> > /
> > outputDirectory>
> > core
> >
> >
> >
> > client-assembly
> > package
> >
> > single
> >
> >
> >
> >
> >
> > ${project.version}
> >
> >
> >
> >
> > src/main/client-descriptor.xml
> >
> > false
> >
> > ${project.basedir}/target/dist/framework/lib/client/<
> > /
> > outputDirectory>
> > client
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > *Thanks*
> >
> >
> > *Bikramjit Singh*
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
*Thanks*
*Bikramjit Singh*
RE: maven assembly plugin not recognizing
finalName has limited use. It works for me at the build level, as seen here:
my-name-1.2.3
...
But even then, Maven won't install (mvn install) that name. As Anders
mentioned, if you want multiple assembled artifacts with different names, use
true and your package file's id will be
included in the filename.
Paul
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Tuesday, March 07, 2017 10:44 PM
To: Maven Users List
Subject: Re: maven assembly plugin not recognizing
There is no finalName config parameter for the single goal, see [1]. I suggest
that you use appendAssemblyId, which is the intended usage.
[1] http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html
/Anders
On Tue, Mar 7, 2017 at 11:48 PM, Bikramjit Singh
wrote:
> I have following Question
>
> How do I use tag to give different name to two jars ? it
> is not picking up the for 2nd ("client" )
>
> Am I doing it wrong ?
>
> I have following.
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
>
>
>
> core-assembly
> package
>
> single
>
>
>
>
>
> ${project.version}
>
>
>
>
> src/main/core-descriptor.xml
>
> false
>
> ${project.basedir}/target/dist/framework/lib/server/<
> /
> outputDirectory>
> core
>
>
>
> client-assembly
> package
>
> single
>
>
>
>
>
> ${project.version}
>
>
>
>
> src/main/client-descriptor.xml
>
> false
>
> ${project.basedir}/target/dist/framework/lib/client/<
> /
> outputDirectory>
> client
>
>
>
>
>
>
>
>
> --
> *Thanks*
>
>
> *Bikramjit Singh*
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin not recognizing
There is no finalName config parameter for the single goal, see [1]. I
suggest that you use appendAssemblyId, which is the intended usage.
[1] http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html
/Anders
On Tue, Mar 7, 2017 at 11:48 PM, Bikramjit Singh
wrote:
> I have following Question
>
> How do I use tag to give different name to two jars ? it is not
> picking up the for 2nd ("client" )
>
> Am I doing it wrong ?
>
> I have following.
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
>
>
>
> core-assembly
> package
>
> single
>
>
>
>
>
> ${project.version}
>
>
>
>
> src/main/core-descriptor.xml
>
> false
>
> ${project.basedir}/target/dist/framework/lib/server/ outputDirectory>
> core
>
>
>
> client-assembly
> package
>
> single
>
>
>
>
>
> ${project.version}
>
>
>
>
> src/main/client-descriptor.xml
>
> false
>
> ${project.basedir}/target/dist/framework/lib/client/ outputDirectory>
> client
>
>
>
>
>
>
>
>
> --
> *Thanks*
>
>
> *Bikramjit Singh*
>
Re: maven-assembly-plugin:2.5 ignores lineEnding=unix if file is not filtered
Yeah, extensive changes related to everything filtering-related. I might add that the 2.4.1 code in this area was intensely duplicated. I probably selected the wrong code when removing the duplication. 2.5.1 is due today but I'll keep on pushing 2.5.X until we have a reasonably bug-free version. There's about 30 more bugs in jira that should be fixed :) Kristian 2014-11-07 8:37 GMT+01:00 Tony Jewell : > Yep, > > Run with 2.4.1 and it sets the line ending to Unix for both files. Filtered > and unfiltered. > > I have used this extensively in past projects to enforce line endings on > released assemblies for run scripts and the like. > > I guess the change was something to do with preserving file times? > > ATB > TonyJ > On 7 Nov 2014 07:27, "Kristian Rosenvold" > wrote: > >> Yeah; i've sen that in the code and been puzzled by that line; I think >> I even wrote a TODO about it since it was "obviously" incorrect. Did >> this actually work without filtering enabled at some point ? >> >> Kristian >> >> >> 2014-11-06 22:41 GMT+01:00 Tony Jewell : >> > Hi, >> > >> > Have raised JIRA: http://jira.codehaus.org/browse/MASSEMBLY-729 >> > >> > Example project attached to JIRA. >> > >> > Thanks, >> > Tony Jewell >> > Cregganna Computer Consultants Ltd. >> >> - >> 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
Re: maven-assembly-plugin:2.5 ignores lineEnding=unix if file is not filtered
Yep, Run with 2.4.1 and it sets the line ending to Unix for both files. Filtered and unfiltered. I have used this extensively in past projects to enforce line endings on released assemblies for run scripts and the like. I guess the change was something to do with preserving file times? ATB TonyJ On 7 Nov 2014 07:27, "Kristian Rosenvold" wrote: > Yeah; i've sen that in the code and been puzzled by that line; I think > I even wrote a TODO about it since it was "obviously" incorrect. Did > this actually work without filtering enabled at some point ? > > Kristian > > > 2014-11-06 22:41 GMT+01:00 Tony Jewell : > > Hi, > > > > Have raised JIRA: http://jira.codehaus.org/browse/MASSEMBLY-729 > > > > Example project attached to JIRA. > > > > Thanks, > > Tony Jewell > > Cregganna Computer Consultants Ltd. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-assembly-plugin:2.5 ignores lineEnding=unix if file is not filtered
Yeah; i've sen that in the code and been puzzled by that line; I think I even wrote a TODO about it since it was "obviously" incorrect. Did this actually work without filtering enabled at some point ? Kristian 2014-11-06 22:41 GMT+01:00 Tony Jewell : > Hi, > > Have raised JIRA: http://jira.codehaus.org/browse/MASSEMBLY-729 > > Example project attached to JIRA. > > Thanks, > Tony Jewell > Cregganna Computer Consultants Ltd. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 13/02/2014 4:23 PM, Barrie Treloar wrote:
On 13 February 2014 23:25, Ron Wheeler wrote:
Good point.
After I fixed the spelling, it works fine.
Is was a great help to have a second set of eyes to find my stupid mistakes.
It would have been nice to have a better error message.
[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o 'com.artifact-software.taw:taw-localized-iumessage-ws:war'
o 'com.artifact-software.taw:taw-dataccess-ws:war'
A "file not found" would have been more helpful.
I tested to see if the file was not found by adding a deliberate spelling
mistake but I drew the wrong conclusion when I got the same error message.
You're welcome to make a patch :)
You probably don't want me writing patches!
I could probably drive your car but you would not be very happy if I
tried to help you by reprogramming your engine control unit to get more
horsepower.
I person who is using Maven to build tar files and webapps is not
necessarily the best person to start mucking with internals.
I dont think it is working with files at the point it is doing all the
checking, especially if the filter has a * in it.
The message could be clearer about what it was complaining about: "Found
Include in a Dependency Set that is not declared as a dependency"
If the message is triggered by other events, perhaps it might need to be
a bit more general.
"The following patterns were never triggered in this artifact inclusion filter"
makes one think that the problem has something to do with the flow
control ("triggered") rather than the artifact itself.
It looks like the message has more to do with the way the plug-in is
structured internally than the way the configuration is specified.
Ron
I guess you could use
http://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringUtils.html#getLevenshteinDistance%28java.lang.CharSequence,%20java.lang.CharSequence%29
And if they are close include a "Did you mean this instead?"
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 13 February 2014 23:25, Ron Wheeler wrote: > Good point. > After I fixed the spelling, it works fine. > > Is was a great help to have a second set of eyes to find my stupid mistakes. > > It would have been nice to have a better error message. > > > [WARNING] The following patterns were never triggered in this artifact > inclusion filter: > o 'com.artifact-software.taw:taw-localized-iumessage-ws:war' > o 'com.artifact-software.taw:taw-dataccess-ws:war' > > A "file not found" would have been more helpful. > I tested to see if the file was not found by adding a deliberate spelling > mistake but I drew the wrong conclusion when I got the same error message. You're welcome to make a patch :) I dont think it is working with files at the point it is doing all the checking, especially if the filter has a * in it. I guess you could use http://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringUtils.html#getLevenshteinDistance%28java.lang.CharSequence,%20java.lang.CharSequence%29 And if they are close include a "Did you mean this instead?" - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
Good point. After I fixed the spelling, it works fine. Is was a great help to have a second set of eyes to find my stupid mistakes. It would have been nice to have a better error message. [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'com.artifact-software.taw:taw-localized-iumessage-ws:war' o 'com.artifact-software.taw:taw-dataccess-ws:war' A "file not found" would have been more helpful. I tested to see if the file was not found by adding a deliberate spelling mistake but I drew the wrong conclusion when I got the same error message. Ron On 12/02/2014 6:11 PM, Barrie Treloar wrote: On 13 February 2014 02:24, Ron Wheeler wrote: I did a debug run and I think that the log shows where the includes get webapps tar false /target false false runtime com.artifact-software.taw:taw-localized-iumessage-ws:war com.artifact-software.taw:taw-dataccess-ws:war [del] [DEBUG] com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2 was removed by one or more filters. [DEBUG] com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2 was removed by one or more filters. [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'com.artifact-software.taw:taw-localized-iumessage-ws:war' o 'com.artifact-software.taw:taw-dataccess-ws:war' [del] http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html defines the spec for "dependency conflict id" and it does not include version. It is either * short form = groupId:artifactId * long form = groupId:artifactId:type:classifier I'm guiding you blind since I've not done this before. The output is telling us that the pattern 'com.artifact-software.taw:taw-localized-iumessage-ws:war' does not match the artifact com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2 And there is your problem. You have an _ in your groupid for the artifact, but not your include filter. I've been looking at maven-common-artifact-filters-1.4 PatternIncludesArtifactFilter.matchAgainst(). since I thought that may you needed a trailing : on the long id. But it does the "right thing" with as much of the pattern you provide - and wildcards the rest. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 13 February 2014 02:24, Ron Wheeler wrote: > I did a debug run and I think that the log shows where the includes get > webapps > > tar > >false > > > /target > false > false > runtime > > > com.artifact-software.taw:taw-localized-iumessage-ws:war > com.artifact-software.taw:taw-dataccess-ws:war > > > [del] > [DEBUG] com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2 was > removed by one or more filters. > [DEBUG] com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2 was removed by > one or more filters. > > [WARNING] The following patterns were never triggered in this artifact > inclusion filter: > o 'com.artifact-software.taw:taw-localized-iumessage-ws:war' > o 'com.artifact-software.taw:taw-dataccess-ws:war' [del] >> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html >> defines the spec for "dependency conflict id" and it does not include >> version. >> >> It is either >> * short form = groupId:artifactId >> * long form = groupId:artifactId:type:classifier I'm guiding you blind since I've not done this before. The output is telling us that the pattern 'com.artifact-software.taw:taw-localized-iumessage-ws:war' does not match the artifact com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2 And there is your problem. You have an _ in your groupid for the artifact, but not your include filter. I've been looking at maven-common-artifact-filters-1.4 PatternIncludesArtifactFilter.matchAgainst(). since I thought that may you needed a trailing : on the long id. But it does the "right thing" with as much of the pattern you provide - and wildcards the rest. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
Thanks for the help.
Here are more details from the pom and assembly.
I did a debug run and I think that the log shows where the includes get
excluded
[DEBUG] com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2
was removed by one or more filters.
[DEBUG] com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2 was
removed by one or more filters.
You can see this in context below.
They make it through the scope filter but are getting rejected in
another filter that does not get applied when "includes" are not specified.
BTW:
1) If I comment out the includes, I get all the dependencies from the
pom packed into a giant tar.
It appears that when the includes are added,the plug-in recognizes the
includes and thinks that I might want them to be used so it warns me
2) If I add "xxx" in the middle of the name
(com.artifact-software.taw:taw-localized-iumessagexxx-ws:war) in the
include, I get the same "not triggered" message so it appears that the
plug-in suspects that I want to do an include but I have missed a
required directive and it doesn't get to the point of referencing the
pom to find the dependencies since it never sees the bogus artifact name
as a problem.
We use the assembly plug-in a lot so I would like to stick with it for
consistency but I way try shade or a simple ANT script
com.artifact_software.taw
taw-localized-uimessage-ws
${project.version}
war
runtime
com.artifact_software.taw
taw-dataaccess-ws
${project.version}
war
runtime
webapps
tar
false
/target
false
false
runtime
com.artifact-software.taw:taw-localized-iumessage-ws:war
com.artifact-software.taw:taw-dataccess-ws:war
maven-assembly-plugin
src/assembly/webapps-tar.xml
true
true
Log
lots of stuff then
[DEBUG] Resolving project dependencies transitively.
[DEBUG] com.artifact_software.taw:taw-webapps-assembler:jar:1.0.2
(selected for null)
[DEBUG] Using mirror nexus
(http://repo.artifact-software.com:8081/nexus/content/groups/public) for
central (http://repo1.maven.org/maven2).
[DEBUG]
com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2:runtime
(selected for runtime)
[DEBUG] Using mirror nexus
(http://repo.artifact-software.com:8081/nexus/content/groups/public) for
central (http://repo1.maven.org/maven2).
[DEBUG] com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2:runtime
(selected for runtime)
[DEBUG] While resolving dependencies of
com.artifact_software.taw:taw-webapps-assembler:jar:1.0.2:
[DEBUG] Statistics for Scope filter [null-scope=true, compile=true,
runtime=true, test=false, provided=false, system=false]
... many lines that look ok
... cannot find something that it would like to have
[DEBUG] Cannot find ArtifactResolver with hint: project-cache-aware
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
java.util.NoSuchElementException
role: org.apache.maven.artifact.resolver.ArtifactResolver
roleHint: project-cache-aware
... stack dump
* THIS LOOKS LIKE THE POINT WHERE THE INCLUDES
GET DROPPED
[DEBUG] Processing DependencySet (output=/target)
[DEBUG] Filtering dependency artifacts WITHOUT transitive dependency
path information.
[DEBUG] com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2
was removed by one or more filters.
[DEBUG] com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2 was
removed by one or more filters.
... restof dependencies also removed
[DEBUG] Statistics for Includes filter:
o 'com.artifact-software.taw:taw-localized-iumessage-ws:war'
o 'com.artifact-software.taw:taw-dataccess-ws:war'
[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o 'com.artifact-software.taw:taw-localized-iumessage-ws:war'
o 'com.artifact-software.taw:taw-dataccess-ws:war'
[DEBUG] The following artifacts were removed by this artifact inclusion
filter:
com.artifact_software.taw:taw-localized-uimessage-ws:war:1.0.2
com.artifact_software.taw:taw-dataaccess-ws:war:1.0.2
.
. list of other dependencies that I will add once I get this to wok
.
com.artifact_software.taw:taw-profile-edit:war:1.0.2
[DEBUG] Adding 0 dependency artifacts.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.154s
[INFO] Finished at: Wed Feb 12 10:40:22 EST 2014
[INFO] Final Memory: 12M/209M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on
project taw-webapps-assembler:
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
>> >From >> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html >> I think the shortened form assumes a "jar" classifier. >> I'm guessing from your assembly name "webapps-tar.xml" that these might be >> wars? >> Have you tried using the long form of the dependency conflict id? > > I am not sure what you mean by this. > The dependency specification in the pom has the right type. > I tried adding the version and type in the assembly file and just got an > error message with a more specific file name. http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html defines the spec for "dependency conflict id" and it does not include version. It is either * short form = groupId:artifactId * long form = groupId:artifactId:type:classifier Can you paste in your pom values for the dependency, as well as the snippet from your assembly file. I'm suggesting that you may not be able to use com.artifact-software.taw:taw-localized-iumessage-ws but instead need com.artifact-software.taw:taw-localized-iumessage-ws:war: > I have not specified a specific phase but I assume that the plug-in is being > triggered since the error comes from the plug-in. > > I did read the docs but there is no example showing including of specific > dependencies. http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html Has the example you want to look at. It has the assembly descriptior, the pom that describes the plugin management, and the actual pom that defines the dependencies and invokes the assembly plugin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 11/02/2014 9:06 PM, Barrie Treloar wrote: On 12 February 2014 11:43, Ron Wheeler wrote: I am trying to build a timesaving module that will build tar files to be installed on a server I have defined a bunch of dependencies in the pom and want to build 2 tar files by invoking 2 instances of the plug-in. In each one I want to specify a list of dependencies to be included from the repository. in the assembly descriptor I have dependencySets dependencySet includes include com.artifact-software.taw:taw-localized-iumessage-ws include com.artifact-software.taw:taw-dataccess-ws: I would like it to take just these 2 modules for this tar file. There are a lot more dependencies that will go in the second invocation of the assembly plug-in. This gets the following message [INFO] --- maven-assembly-plugin:2.4:single (default) @ taw-webapps-assembler --- [INFO] Reading assembly descriptor: src/assembly/webapps-tar.xml [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'com.artifact-software.taw:taw-localized-iumessage-ws' o 'com.artifact-software.taw:taw-dataccess-ws:' [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 9.658s [INFO] Finished at: Tue Feb 11 19:54:13 EST 2014 [INFO] Final Memory: 10M/148M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project taw-webapps-assembler: Failed to create assembly: Error creating assembly archive webapps: You must set at least one file. -> [Help 1] What have I misunderstood about the assembly. I'm assuming you've read the docs. >From http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html I think the shortened form assumes a "jar" classifier. I'm guessing from your assembly name "webapps-tar.xml" that these might be wars? Have you tried using the long form of the dependency conflict id? I am not sure what you mean by this. The dependency specification in the pom has the right type. I tried adding the version and type in the assembly file and just got an error message with a more specific file name. I have not specified a specific phase but I assume that the plug-in is being triggered since the error comes from the plug-in. I did read the docs but there is no example showing including of specific dependencies. Ron >From http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html What phase to did you attach the plugin to? It may be possible you haven't bound it to a phase that has resolved the dependencies and so there are none for it to find. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 12 February 2014 11:43, Ron Wheeler wrote: > I am trying to build a timesaving module that will build tar files to be > installed on a server > I have defined a bunch of dependencies in the pom and want to build 2 tar > files by invoking 2 instances of the plug-in. > In each one I want to specify a list of dependencies to be included from the > repository. > in the assembly descriptor I have > dependencySets > dependencySet > includes > include com.artifact-software.taw:taw-localized-iumessage-ws > include com.artifact-software.taw:taw-dataccess-ws: > > I would like it to take just these 2 modules for this tar file. > There are a lot more dependencies that will go in the second invocation of > the assembly plug-in. > > > This gets the following message > > [INFO] --- maven-assembly-plugin:2.4:single (default) @ > taw-webapps-assembler --- > [INFO] Reading assembly descriptor: src/assembly/webapps-tar.xml > [WARNING] The following patterns were never triggered in this artifact > inclusion filter: > o 'com.artifact-software.taw:taw-localized-iumessage-ws' > o 'com.artifact-software.taw:taw-dataccess-ws:' > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 9.658s > [INFO] Finished at: Tue Feb 11 19:54:13 EST 2014 > [INFO] Final Memory: 10M/148M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on > project taw-webapps-assembler: Failed to create > assembly: Error creating assembly archive webapps: You must set at least one > file. -> [Help 1] > > What have I misunderstood about the assembly. I'm assuming you've read the docs. >From >http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html I think the shortened form assumes a "jar" classifier. I'm guessing from your assembly name "webapps-tar.xml" that these might be wars? Have you tried using the long form of the dependency conflict id? >From >http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html What phase to did you attach the plugin to? It may be possible you haven't bound it to a phase that has resolved the dependencies and so there are none for it to find. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin not retaining timestamps of files
Am 2013-10-29 20:38, schrieb Steve Cohen: When building a .tar.gz archive with the maven assembly plugin, should it not be keeping the timestamps of the files it is adding to the archive? This is how tar behaves. I find it NOT to be the case with the assembly plugin. The files are dated with the time they were added to the archive. This is not how tar behaves. Steve, this does not seem to be possible with the currect discriptor [1]. Please search in JIRA for such a ticket or file one. Mike [1] http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin set permissions on base directory
It does not. I hadn't tried using '/' as the output directory spec
(i.e. the base-directory) but it doesn't help. The basic problem is this:
The archiver does not create an entry in the archive for the
base-directory. This is because no matter where you put the
it applies to directories WITHIN that , not to
the root of the fileset itself. If a directory entry is not created
in the archive, then the -p switch of tar will have nothing to
"preserve" and just use the default permission for the directory.
Really, I think to make this work, one would have to be somehow be able
to put a on itself. But this would be
a change to the plugin.
On 10/09/2013 05:03 PM, Martin Gainty wrote:
Add a fileset pointing to ${basedir} to your configuration
${basedir}
/
*.properties
...
does this not work for you?
Martin
Date: Wed, 9 Oct 2013 14:41:35 -0500
From: sco...@javactivity.org
To: users@maven.apache.org
Subject: Re: maven assembly plugin set permissions on base directory
Martin, yes, I'm well aware of that functionality.
However, I cannot figure out how to apply it to the base directory.
Let's say I've set all my filesets which are packaged underneath the
base directory to
775
664
The plugin handles this beautifully.
But let's suppose I want the basedir of the archive to also be
775
That does not seem possible. At least I have not figured out how to do it.
Steve
On 10/09/2013 02:21 PM, Martin Gainty wrote:
Stephen
or or or or or
allow you to assemble a package based on Octal setting of the File/Directory Permissions ..
fileMode
String
Similar to a UNIX permission, sets the file mode of the files included. THIS IS
AN OCTAL VALUE. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the value 0644 translates to
User read-write, Group and Other read-only. (more on unix-style permissions)
directoryMode
String
Similar to a UNIX permission, sets the directory mode of the directories
included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each
component is a sum of Read = 4, Write = 2, and Execute = 1. For example, the
value 0755 translates to User read-write, Group and Other read-only. (more on
unix-style permissions)
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
Does this answer your question?
Martin
Date: Wed, 9 Oct 2013 14:05:49 -0500
From: sco...@javactivity.org
To: users@maven.apache.org
Subject: Re: maven assembly plugin set permissions on base directory
On 10/09/2013 11:43 AM, Baptiste Mathus wrote:
What are you trying to do? The 'why' may also help.
Is there a way to do this?
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.org
For additional commands, e-mail: users-h...@maven.apache.org
I'm working in a very specialized legacy environment in which it would
be nice to have an archive (.tar.gz) that had all the permissions as I
want from the start. Granted it's not all that hard to do after
unpackaging with chmod running under find, but it would be nice if the
base-directory itself had a as do the that
get packaged under it. Bottom-line: the plugin doesn't give me the same
level of control as the OS does.
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: maven assembly plugin set permissions on base directory
Add a fileset pointing to ${basedir} to your configuration
${basedir}
/
*.properties
...
does this not work for you?
Martin
> Date: Wed, 9 Oct 2013 14:41:35 -0500
> From: sco...@javactivity.org
> To: users@maven.apache.org
> Subject: Re: maven assembly plugin set permissions on base directory
>
> Martin, yes, I'm well aware of that functionality.
> However, I cannot figure out how to apply it to the base directory.
>
> Let's say I've set all my filesets which are packaged underneath the
> base directory to
> 775
> 664
>
> The plugin handles this beautifully.
>
> But let's suppose I want the basedir of the archive to also be
> 775
>
> That does not seem possible. At least I have not figured out how to do it.
>
> Steve
>
>
>
> On 10/09/2013 02:21 PM, Martin Gainty wrote:
> > Stephen
> >
> >
> >
> >
> >
> > or or or or or
> > allow you to assemble a package based on Octal setting of the
> > File/Directory Permissions ..
> >
> >
> >
> >
> >
> >
> > fileMode
> > String
> > Similar to a UNIX permission, sets the file mode of the files included.
> > THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each component
> > is a sum of Read = 4, Write = 2, and Execute = 1. For example, the value
> > 0644 translates to User read-write, Group and Other read-only. (more on
> > unix-style permissions)
> >
> > directoryMode
> > String
> > Similar to a UNIX permission, sets the directory mode of the directories
> > included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each
> > component is a sum of Read = 4, Write = 2, and Execute = 1. For example,
> > the value 0755 translates to User read-write, Group and Other read-only.
> > (more on unix-style permissions)
> >
> >
> >
> > http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
> >
> >
> >
> > Does this answer your question?
> >
> > Martin
> >
> >
> >
> >
> >
> >
> >> Date: Wed, 9 Oct 2013 14:05:49 -0500
> >> From: sco...@javactivity.org
> >> To: users@maven.apache.org
> >> Subject: Re: maven assembly plugin set permissions on base directory
> >>
> >> On 10/09/2013 11:43 AM, Baptiste Mathus wrote:
> >>> What are you trying to do? The 'why' may also help.
> >>> Is there a way to do this?
> >>>
> >>> --**--**-
> >>> To unsubscribe, e-mail:
> >>> users-unsubscribe@maven.**apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >> I'm working in a very specialized legacy environment in which it would
> >> be nice to have an archive (.tar.gz) that had all the permissions as I
> >> want from the start. Granted it's not all that hard to do after
> >> unpackaging with chmod running under find, but it would be nice if the
> >> base-directory itself had a as do the that
> >> get packaged under it. Bottom-line: the plugin doesn't give me the same
> >> level of control as the OS does.
> >>
> >> -
> >> 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
>
Re: maven assembly plugin set permissions on base directory
Martin, yes, I'm well aware of that functionality. However, I cannot figure out how to apply it to the base directory. Let's say I've set all my filesets which are packaged underneath the base directory to 775 664 The plugin handles this beautifully. But let's suppose I want the basedir of the archive to also be 775 That does not seem possible. At least I have not figured out how to do it. Steve On 10/09/2013 02:21 PM, Martin Gainty wrote: Stephen or or or or or allow you to assemble a package based on Octal setting of the File/Directory Permissions .. fileMode String Similar to a UNIX permission, sets the file mode of the files included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each component is a sum of Read = 4, Write = 2, and Execute = 1. For example, the value 0644 translates to User read-write, Group and Other read-only. (more on unix-style permissions) directoryMode String Similar to a UNIX permission, sets the directory mode of the directories included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each component is a sum of Read = 4, Write = 2, and Execute = 1. For example, the value 0755 translates to User read-write, Group and Other read-only. (more on unix-style permissions) http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html Does this answer your question? Martin Date: Wed, 9 Oct 2013 14:05:49 -0500 From: sco...@javactivity.org To: users@maven.apache.org Subject: Re: maven assembly plugin set permissions on base directory On 10/09/2013 11:43 AM, Baptiste Mathus wrote: What are you trying to do? The 'why' may also help. Is there a way to do this? --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org For additional commands, e-mail: users-h...@maven.apache.org I'm working in a very specialized legacy environment in which it would be nice to have an archive (.tar.gz) that had all the permissions as I want from the start. Granted it's not all that hard to do after unpackaging with chmod running under find, but it would be nice if the base-directory itself had a as do the that get packaged under it. Bottom-line: the plugin doesn't give me the same level of control as the OS does. - 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
RE: maven assembly plugin set permissions on base directory
Stephen or or or or or allow you to assemble a package based on Octal setting of the File/Directory Permissions .. fileMode String Similar to a UNIX permission, sets the file mode of the files included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each component is a sum of Read = 4, Write = 2, and Execute = 1. For example, the value 0644 translates to User read-write, Group and Other read-only. (more on unix-style permissions) directoryMode String Similar to a UNIX permission, sets the directory mode of the directories included. THIS IS AN OCTAL VALUE. Format: (User)(Group)(Other) where each component is a sum of Read = 4, Write = 2, and Execute = 1. For example, the value 0755 translates to User read-write, Group and Other read-only. (more on unix-style permissions) http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html Does this answer your question? Martin > Date: Wed, 9 Oct 2013 14:05:49 -0500 > From: sco...@javactivity.org > To: users@maven.apache.org > Subject: Re: maven assembly plugin set permissions on base directory > > On 10/09/2013 11:43 AM, Baptiste Mathus wrote: > > What are you trying to do? The 'why' may also help. > > Is there a way to do this? > > > > --**--**- > > To unsubscribe, e-mail: > > users-unsubscribe@maven.**apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > I'm working in a very specialized legacy environment in which it would > be nice to have an archive (.tar.gz) that had all the permissions as I > want from the start. Granted it's not all that hard to do after > unpackaging with chmod running under find, but it would be nice if the > base-directory itself had a as do the that > get packaged under it. Bottom-line: the plugin doesn't give me the same > level of control as the OS does. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: maven assembly plugin set permissions on base directory
On 10/09/2013 11:43 AM, Baptiste Mathus wrote: What are you trying to do? The 'why' may also help. Is there a way to do this? --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org For additional commands, e-mail: users-h...@maven.apache.org I'm working in a very specialized legacy environment in which it would be nice to have an archive (.tar.gz) that had all the permissions as I want from the start. Granted it's not all that hard to do after unpackaging with chmod running under find, but it would be nice if the base-directory itself had a as do the that get packaged under it. Bottom-line: the plugin doesn't give me the same level of control as the OS does. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin set permissions on base directory
What are you trying to do? The 'why' may also help. Is there a way to do this? --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven Assembly plugin is not working when install
Looks like your bind works well. The assembly was called when the package phase was arrived. Br, Tim -Original Message- From: Baptiste Mathus [mailto:bmat...@gmail.com] Sent: Monday, September 02, 2013 2:47 PM To: Maven Users List Subject: Re: Maven Assembly plugin is not working when install What is actually "wrong"? Could you provide some details? Le 2 sept. 2013 06:50, "禹航" a écrit : > hi there, >i try to user maven-assembly plugin to generate a tar.gz.my pom is > like > this: > * > > > org.apache.maven.plugins > maven-assembly-plugin > > tauras-master > > > src/main/assembly/assembly-offline.xml > > > > > make-assembly > package > > single > > > > > > * > > when i use assembly:single, it works well. > but when i use install or package, the result is wrong the output of > the console: > > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ > tauras-master > --- > [INFO] Deleting E:\svn\taurus\tauras-master\target > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ > tauras-master --- [debug] execute contextualize [INFO] Using 'UTF-8' > encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ > tauras-master --- [INFO] Compiling 5 source files to > E:\svn\taurus\tauras-master\target\classes > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources > (default-testResources) @ tauras-master --- [debug] execute > contextualize [INFO] Using 'UTF-8' encoding to copy filtered > resources. > [INFO] skip non existing resourceDirectory > E:\svn\taurus\tauras-master\src\test\resources > [INFO] > [INFO] --- maven-compiler-plugin:2.5.1:testCompile > (default-testCompile) @ tauras-master --- [INFO] Not compiling test > sources [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test > (default-test) @ tauras-master > --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ tauras-master --- > [INFO] Building jar: > E:\svn\taurus\tauras-master\target\tauras-master.jar > *missing > [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ > **tauras-master --- [INFO] Reading assembly descriptor: > src/main/assembly/assembly-offline.xml > missing* > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > tauras-master --- > > Any comments for this? >
Re: Maven Assembly plugin is not working when install
What is actually "wrong"? Could you provide some details? Le 2 sept. 2013 06:50, "禹航" a écrit : > hi there, >i try to user maven-assembly plugin to generate a tar.gz.my pom is like > this: > * > > > org.apache.maven.plugins > maven-assembly-plugin > > tauras-master > > > src/main/assembly/assembly-offline.xml > > > > > make-assembly > package > > single > > > > > > * > > when i use assembly:single, it works well. > but when i use install or package, the result is wrong > the output of the console: > > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ tauras-master > --- > [INFO] Deleting E:\svn\taurus\tauras-master\target > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ > tauras-master --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ > tauras-master --- > [INFO] Compiling 5 source files to > E:\svn\taurus\tauras-master\target\classes > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) > @ tauras-master --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > E:\svn\taurus\tauras-master\src\test\resources > [INFO] > [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ > tauras-master --- > [INFO] Not compiling test sources > [INFO] > [INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @ tauras-master > --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ tauras-master --- > [INFO] Building jar: E:\svn\taurus\tauras-master\target\tauras-master.jar > *missing > [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ > **tauras-master --- > [INFO] Reading assembly descriptor: src/main/assembly/assembly-offline.xml > missing* > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > tauras-master --- > > Any comments for this? >
Re: maven-assembly-plugin StackOverflowError
I had a similar problem and fixed it by setting the stack size -Xss10M. The output was even more than the max screen buffer, I couldn't even see the exception message. I found this post by searching "at org.codehaus.plexus.archiver.AbstractArchiver". Thanks for the solution, it saved my time. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p5769114.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: Maven Assembly Plugin - Changing File Name Case Using FileSets
> org.apache.maven.plugins > maven-assembly-plugin What version of the plugin (and Maven, and your JDK) is this? And which OS? Can you create a sample project (zip) and post somewhere online so it can be downloaded and executed locally to duplicate the results you're seeing? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Assembly Plugin: Is there a way to specify the assembly location in the assembly descriptor?
On Nov 21, 2012, at 3:16 PM, Javier Ortiz wrote: > Is there a way to specify the location of the assembly? Sure. https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#outputDirectory > > Can I specify the file's full name instead of the default appending the id > to the project file name? Yep. First, disable appending id (https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#appendAssemblyId). Second, specify https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#finalName - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Assembly Plugin: Is there a way to specify the assembly location in the assembly descriptor?
> Is there a way to specify the location of the assembly? > Not that I know of. What you should keep in mind is that Maven is intended to deploy to a repository, and a Maven repo has a pre-defined structure. You cannot alter that. > Can I specify the file's full name instead of the default appending the id > to the project file name? > There might be some hacky solutions to do something like this for the created assembly file in the target folder. BUT, as I pointed out above, the intended way to use Maven is to deploy to a repo. And in the repo an artifact (your assembly for example) has coordinates (groupId, artifactId, version, classifier and type). You shouldn't think of it as "file name". /Anders
Re: maven-assembly-plugin 2.3 and parent pom
That's it…thanks for getting me to think about what I'm doing! The / section and the section are very different things. - Simon On 17 Sep 2012, at 17:03, Ron Wheeler wrote: > I believe that this is the correct behaviour. > The Parent pom has a dependencyManagement section where you can put the > versions of libraries that you want to use but this does not push > dependencies into child POMs. > This is a good thing since we have about 60 POMs that share a parent and do > not want all the dependencies in every jar or war that we make. > We do want the version of any artifact to be the same in all projects. > > Ron > > On 17/09/2012 11:15 AM, Simon Temple wrote: >> Hi >> >> I'm trying to use the assembly plugin to build a product distribution. I >> include a parent POM declaration in my POM. The parent POM has many >> dependencies (mixed scope: compile, provided and test) >> >> When I execute make-assembly the resulting distribution does not contain the >> dependent artifacts defined in my parent POM. >> >> Looking at the 'effective POM' I can see the parent POM dependencies, yet >> the assembly plugin does not include them in the distribution. >> >> Is this a bug in the assembly-plugin or am I doing something wrong? >> >> assembly.xml: >> >> > >> distro >> >> dir >> >> false >> >> >> src/main/resources >> / >> >> >> >> >> >> /lib >> >> >> >> >> pom.xml: >> >> >> >> >> my-parent.pom >> com.name.product >> 5.0.0-SNAPSHOT >> >> >> >> >> If I explicitly add dependencies to my POM then the assembly plugin >> correctly adds them to the lib folder of my distribution. >> >> >> TIA >> >> >> >> Simon Temple >> >> >> >> >> >> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: maven-assembly-plugin 2.3 and parent pom
I believe that this is the correct behaviour. The Parent pom has a dependencyManagement section where you can put the versions of libraries that you want to use but this does not push dependencies into child POMs. This is a good thing since we have about 60 POMs that share a parent and do not want all the dependencies in every jar or war that we make. We do want the version of any artifact to be the same in all projects. Ron On 17/09/2012 11:15 AM, Simon Temple wrote: Hi I'm trying to use the assembly plugin to build a product distribution. I include a parent POM declaration in my POM. The parent POM has many dependencies (mixed scope: compile, provided and test) When I execute make-assembly the resulting distribution does not contain the dependent artifacts defined in my parent POM. Looking at the 'effective POM' I can see the parent POM dependencies, yet the assembly plugin does not include them in the distribution. Is this a bug in the assembly-plugin or am I doing something wrong? assembly.xml: distro dir false src/main/resources / /lib pom.xml: my-parent.pom com.name.product 5.0.0-SNAPSHOT If I explicitly add dependencies to my POM then the assembly plugin correctly adds them to the lib folder of my distribution. TIA Simon Temple -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin and dependencySet includes format
On Thu, Aug 2, 2012 at 1:35 PM, Anders Hammar wrote: > Please file a JIRA ticket [1] for the plugin's documentation to be fixed! > Done: http://jira.codehaus.org/browse/MASSEMBLY-620 Best, Laird -- http://about.me/lairdnelson
Re: maven-assembly-plugin and dependencySet includes format
Please file a JIRA ticket [1] for the plugin's documentation to be fixed! For the Sonatype book, the source is in GitHub [2] so you can clone and fix it yourself. And then send a pull request. /Anders [1] http://jira.codehaus.org/browse/MASSEMBLY [2] https://github.com/sonatype/maven-reference-en On Thu, Aug 2, 2012 at 10:20 PM, Laird Nelson wrote: > On Thu, Aug 2, 2012 at 12:49 PM, Laird Nelson wrote: > >> Which is it? >> > > The format that works is none of these (!). In fact in version 2.3 of the > maven-assembly-plugin it needs to be: > > groupId:artifactId:type:classifier[:version] > > > So, for example: > > org.liquibase:liquibase-core:zip:bin:2.0.1 > > > Best, > Laird > > -- > http://about.me/lairdnelson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin and dependencySet includes format
On Thu, Aug 2, 2012 at 12:49 PM, Laird Nelson wrote: > Which is it? > The format that works is none of these (!). In fact in version 2.3 of the maven-assembly-plugin it needs to be: groupId:artifactId:type:classifier[:version] So, for example: org.liquibase:liquibase-core:zip:bin:2.0.1 Best, Laird -- http://about.me/lairdnelson
RE: Maven Assembly plugin -Multi module project- source and javadoc not getting added to zip file
I used dependecySet to solve this problem and as walsmatt mentioned correctly, we can use wildcard to add all binaries. http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd";> bin false zip groupA:*:*:* This will add all binary artifacts of project. Posting here in case if anybody runs into similar kind of issue, this might help. Thanks walshmatt. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Assembly-plugin-Multi-module-project-source-and-javadoc-not-getting-added-to-zip-file-tp5708932p5709447.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: Maven Assembly plugin -Multi module project- source and javadoc not getting added to zip file
Yeah. You need to read the documentation. The format is "groupId:artifactId:type:version[:classifier]". "Artifact coordinatess may be given in simple groupId:artifactId form, or they may be fully qualified in the form groupId:artifactId:type:version[:classifier]. Additionally, wildcards can be used, as in *:maven-*." So maybe groupA:A:jar:*:* ? > -Original Message- > From: Pankaj [mailto:pankaji...@rediffmail.com] > Sent: Thursday, May 17, 2012 1:31 PM > To: users@maven.apache.org > Subject: RE: Maven Assembly plugin -Multi module project- source and > javadoc not getting added to zip file > > Thanks for your reply. > > I'm still getting the same problem. Getting below warning > > > [WARNING] The following patterns were never triggered in this artifact > inclusion > filter: > o 'groupA:A:jar:javadoc' > o 'groupA:A:jar:source' > where as artifact which has all classes is getting added. > > Thanks > Pankaj > > > -- > View this message in context: http://maven.40175.n5.nabble.com/Maven- > Assembly-plugin-Multi-module-project-source-and-javadoc-not-getting- > added-to-zip-file-tp5708932p5708936.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 __ This message, including any attachments, is confidential and contains information intended only for the person(s) named above. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply email and permanently delete the original transmission from all of your systems and hard drives, including any attachments, without making a copy. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven Assembly plugin -Multi module project- source and javadoc not getting added to zip file
Thanks for your reply. I'm still getting the same problem. Getting below warning [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'groupA:A:jar:javadoc' o 'groupA:A:jar:source' where as artifact which has all classes is getting added. Thanks Pankaj -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Assembly-plugin-Multi-module-project-source-and-javadoc-not-getting-added-to-zip-file-tp5708932p5708936.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: Maven Assembly plugin -Multi module project- source and javadoc not getting added to zip file
Pankaj, The problem is in your includes. "javadoc" and "source" are classifiers, not types. Try groupA:A:jar:sources groupB:A:jar:javadoc and so on. Matt > -Original Message- > From: Pankaj [mailto:pankaji...@rediffmail.com] > Sent: Thursday, May 17, 2012 12:11 PM > To: users@maven.apache.org > Subject: Maven Assembly plugin -Multi module project- source and > javadoc not getting added to zip file > > I've multi module project and using maven's assembly plugin to zip the > project's artifact. > > Proj > +Module A >pom.xml > +Module B >pom.xml > pom.xml > > When i build main module, it will produce following things > > Proj > +Module A >target\A.jar >target\A-source.jar >target\A-javadoc.jar > +Module B >target\B.jar >target\B-source.jar >target\B-javadoc.jar > > 1) I've added assembly plugin under ModuleB pom file and I'm using > ModuleSet > in assembly discriptor file > > > > true > > groupA:A:jar > groupA:A:javadoc > groupA:A:source > > > moduleA > false > > > > > true > > groupB:B:jar > groupB:B:javadoc > groupB:B:source > > > moduleB > false > > > > > But i'm getting only A.jar and B.Jar under zip file. I'm not getting > javadoc > and source in zip file. Is it downloading it from m2 repo, i'm > suspecting > if it does so, because sources and java doc wouldn't be there in maven > repo. > How can i add all three artifact in a zip file ? > > 2) I want to add assembly plugin in my parent pom rather than in > ModuleB's > pom but if i do so, i get an exception "Please ensure the package phase > is > run before the assembly is generated". After googling, i found few > suggetion > to add assembly as module. Is there any other way to handle this ? > > > -- > View this message in context: http://maven.40175.n5.nabble.com/Maven- > Assembly-plugin-Multi-module-project-source-and-javadoc-not-getting- > added-to-zip-file-tp5708932.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 __ This message, including any attachments, is confidential and contains information intended only for the person(s) named above. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply email and permanently delete the original transmission from all of your systems and hard drives, including any attachments, without making a copy. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin causing modules in multi-module project being build twice
> So what would cause the maven-assembly-plugin to build my multi-module > project again? Note that a few of the sub-modules of the root / parent pom > are also dependencies of the module with the maven-assembly-plugin and used > in of the assembly.xml file. What do your pom.xml and assembly.xml configuration files look like? Post them at Gist and send us a link. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin causing modules in multi-module project being build twice
I have confirmed that my weird problem of building the multi-module project a second time is happening due to the maven-assembly-plugin. If I configure the pom for last (problem) modules to not bind maven-assembly-plugin to any goal then the build happens once and all is well. So what would cause the maven-assembly-plugin to build my multi-module project again? Note that a few of the sub-modules of the root / parent pom are also dependencies of the module with the maven-assembly-plugin and used in of the assembly.xml file. On 05/08/2012 09:21 AM, Farrukh Najmi wrote: Hi Guys, I have a multi-module project to which I recently added a new module as the last module. When I build the project it builds all modules but the last module fine and then fails to build the last module and gives the stack trace below. [ERROR] Failed to execute goal org.codehaus.mojo:jaxws-maven-plugin:1.9:wsimport (default) on project : org.apache.xerces.parsers.XML 11Configuration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:jaxws-maven-plugin:1.9:wsimport (default) on projec t regrep-bindings: org.apache.xerces.parsers.XML11Configuration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration 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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) 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:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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: org.apache.xerces.parsers.XML11Configuration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration at org.codehaus.mojo.jaxws.WsImportMojo.execute(WsImportMojo.java:204) at org.codehaus.mojo.jaxws.MainWsImportMojo.execute(MainWsImportMojo.java:15) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 23 more Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XML11Configuration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.(Unknown Source) at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source) at com.sun.org.apache.xml.internal.resolver.readers.SAXCatalogReader.readCatalog(SAXCatalogReader.java:238) at com.sun.org.apache.xml.internal.resolver.Catalog.parseCatalog(Catalog.java:680) at com.sun.xml.ws.util.xml.XmlUtil.createEntityResolver(XmlUtil.java:270) at com.sun.tools.ws.wscompile.WsimportOptions.parseArguments(WsimportOptions.java:207) at com.sun.tools.ws.wscompile.WsimportOptions.parseArguments(WsimportOptions.java:149) at
Re: maven-assembly-plugin StackOverflowError
I ended up getting this resolved some time ago but I figure I post the best solution. The stackoverflow isnt a product of infinite recursion it's just a matter of recursion that is simply too deep because of how far down the file directory tree goes. Simply increasing the stack size with -Xss. We increased it to 2m and the assembler plugin was able to handle the recursive stack size. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p5039058.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: Maven assembly plugin outputDirectory cannot contain an extension
Hi, have you tried to add a supplemental slash in outputDirectory ? Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/Maven-assembly-plugin-outputDirectory-cannot-contain-an-extension-tp5017443p5017462.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: maven-assembly-plugin for test?
If you want to have a jar with reusable test-classes, you have to create a separate project for it. http://rfscholte.wordpress.com/2010/09/05/how-to-create-a-jar-containing-reusableabstract-testclasses-with-maven/ -Robert > Date: Tue, 16 Aug 2011 12:54:54 -0700 > Subject: maven-assembly-plugin for test? > From: tedd...@gmail.com > To: users@maven.apache.org > > I could use jar:test-jar to generate a jar for my test cases, > > but it lacks the dependencies > > is there a way to let maven-assembly-plugin generate a > jar-with-dependencies for test classes? > > I looked into > http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html > nothing seems related to this > > Thanks > Yang > > - > 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
Re: maven-assembly-plugin StackOverflowError
The best I could do was to exclude the dependency itself (this works for me because I needed a subset of the code that was not effected by the exclusion) org.apache.poi poi-ooxml-schemas Not sure if this would help you. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p4528687.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: maven-assembly-plugin StackOverflowError
Hello, did you ever resolve this issue? I ran into the same problem using poi 3.7 and maven-assembly-plugin 2.2.1. Cheers, Manuel-- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p4358228.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: maven-assembly-plugin StackOverflowError
A quick update. Despite having other poi dependencies, this is the only one which causes the StackOverFlow. It occurs when the plugin imports the xsb's into the jar. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p3321427.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: [maven-assembly-plugin] Using binaries from submodule instead of executing assembly again
I'm not saying you should move it, I'm only saying you have to if you don't want to build it. The short answer my put the assembly in it's own module is that it's best practice. If your aggregating project also is the parent you may run into issues otherwise (as the parent needs to build first, but you want the assembling to happen last). There was a thread about this some days ago. Please search a mail archive (like nabble for example). /Anders On Sun, Sep 12, 2010 at 19:15, M. Richey wrote: > > Hi Anders, > > when moving C outside A how to assemble B and C using the assembly plugin > and without installing the artifact before? > And why not binding the assembly plugin in project A (which is also an > aggregating project)? > > Thanks for your help! > > Regards, > > Maik > > > Original-Nachricht > > Datum: Sun, 12 Sep 2010 18:40:40 +0200 > > Von: Anders Hammar > > An: Maven Users List > > Betreff: Re: [maven-assembly-plugin] Using binaries from submodule > instead of executing assembly again > > > If you execute "mvn package" on the aggregating project, all the modules > > will be built. That's how it works. If you don't want that, you need to > > move > > C outside of the aggregating project. > > You shouldn't bind the m-assembly-p in the A projects, but rather put it > > in > > a module of its own instead. That's best-practice and it will keep you > > away > > from some issues. > > > > /Anders > > > > On Sun, Sep 12, 2010 at 18:02, M. Richey wrote: > > > > > Hi all, > > > > > > I've got a question regarding the assembly plugin. Assume we have three > > > projetcs called A, B, C. Project B and C are modules of A. C is a multi > > > module project itself. Both A and C uses the assembly plugin bind to > the > > > package phase. My problem is that each time executing mvn package on A > > to > > > assemble B and C together, module C is rebuild. Instead of rebuilding C > > each > > > time I would like to use the artifact attached to C (assuming that mvn > > > package has been executed on C before). Do anyone know how that can be > > done? > > > How to avoid rebuilding C again and again? Any ideas? > > > > > > Thanks in advance! > > > > > > Kind regards, > > > > > > Maik > > > > > > > > > -- > > > Achtung Sicherheitswarnung: GMX warnt vor Phishing-Attacken! > > > http://portal.gmx.net/de/go/sicherheitspaket > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > GRATIS: Spider-Man 1-3 sowie 300 weitere Videos! > Jetzt freischalten! http://portal.gmx.net/de/go/maxdome > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: [maven-assembly-plugin] Using binaries from submodule instead of executing assembly again
Hi Anders, when moving C outside A how to assemble B and C using the assembly plugin and without installing the artifact before? And why not binding the assembly plugin in project A (which is also an aggregating project)? Thanks for your help! Regards, Maik Original-Nachricht > Datum: Sun, 12 Sep 2010 18:40:40 +0200 > Von: Anders Hammar > An: Maven Users List > Betreff: Re: [maven-assembly-plugin] Using binaries from submodule instead of > executing assembly again > If you execute "mvn package" on the aggregating project, all the modules > will be built. That's how it works. If you don't want that, you need to > move > C outside of the aggregating project. > You shouldn't bind the m-assembly-p in the A projects, but rather put it > in > a module of its own instead. That's best-practice and it will keep you > away > from some issues. > > /Anders > > On Sun, Sep 12, 2010 at 18:02, M. Richey wrote: > > > Hi all, > > > > I've got a question regarding the assembly plugin. Assume we have three > > projetcs called A, B, C. Project B and C are modules of A. C is a multi > > module project itself. Both A and C uses the assembly plugin bind to the > > package phase. My problem is that each time executing mvn package on A > to > > assemble B and C together, module C is rebuild. Instead of rebuilding C > each > > time I would like to use the artifact attached to C (assuming that mvn > > package has been executed on C before). Do anyone know how that can be > done? > > How to avoid rebuilding C again and again? Any ideas? > > > > Thanks in advance! > > > > Kind regards, > > > > Maik > > > > > > -- > > Achtung Sicherheitswarnung: GMX warnt vor Phishing-Attacken! > > http://portal.gmx.net/de/go/sicherheitspaket > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > -- GRATIS: Spider-Man 1-3 sowie 300 weitere Videos! Jetzt freischalten! http://portal.gmx.net/de/go/maxdome - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-assembly-plugin] Using binaries from submodule instead of executing assembly again
If you execute "mvn package" on the aggregating project, all the modules will be built. That's how it works. If you don't want that, you need to move C outside of the aggregating project. You shouldn't bind the m-assembly-p in the A projects, but rather put it in a module of its own instead. That's best-practice and it will keep you away from some issues. /Anders On Sun, Sep 12, 2010 at 18:02, M. Richey wrote: > Hi all, > > I've got a question regarding the assembly plugin. Assume we have three > projetcs called A, B, C. Project B and C are modules of A. C is a multi > module project itself. Both A and C uses the assembly plugin bind to the > package phase. My problem is that each time executing mvn package on A to > assemble B and C together, module C is rebuild. Instead of rebuilding C each > time I would like to use the artifact attached to C (assuming that mvn > package has been executed on C before). Do anyone know how that can be done? > How to avoid rebuilding C again and again? Any ideas? > > Thanks in advance! > > Kind regards, > > Maik > > > -- > Achtung Sicherheitswarnung: GMX warnt vor Phishing-Attacken! > http://portal.gmx.net/de/go/sicherheitspaket > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven-assembly-plugin: How to make the assembly the primary artifact
I'm with Tamás here. Having something that works, is not always the correct
solution...
/Anders
2010/7/1 Tamás Cservenák
> While Kalle's solution will do the work, I can't emphasize how this
> approach
> is wrong, at least I think it is.
>
> For situations like this, a custom plugin (or better, custom packaging)
> would be the best, since this solution will produce inconsistent data:
>
> Deployed POM will have packaging "pom", and that packaging has nothing to
> do
> with ZIP as primary artifact. But it's only me ;)
>
>
> Thanks,
> ~t~
>
> On Thu, Jul 1, 2010 at 8:09 PM, Kalle Korhonen
> wrote:
>
> > The pom artifact is always produced regardless. Make your module type
> > pom and attach the assembly zip as an artifact with the help of
> > buildhelper plugin:
> > http://mojo.codehaus.org/build-helper-maven-plugin/usage.html.
> >
> > Kalle
> >
> >
> > On Thu, Jul 1, 2010 at 9:56 AM, Andreas Sewe
> > wrote:
> > > Hi all,
> > >
> > > I have a project which should produce a ZIP, with all contents of
> > > ${project.build.outputDirect} put into a base directory within the ZIP.
> > So
> > > far, the maven-assembly-plugin with fits the
> bill
> > > perfectly.
> > >
> > > There is one issue, however, which I haven't been able to solve: I
> can't
> > get
> > > the plugin to make the produced assembly the *primary* artifact. (There
> > is
> > > only a single assembly per project produced this way.)
> > >
> > > Is this possible? Or is there another plugin which I can resort to?
> (The
> > > org.apache.maven.plugins:maven-zip-plugin does almost what I want, but
> > > seems to be not longer supported in favour of the
> maven-assembly-plugin.)
> > > Any suggestions?
> > >
> > > Best wishes,
> > >
> > > Andreas
> > >
> > > -
> > > 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
> >
> >
>
Re: Maven-assembly-plugin: How to make the assembly the primary artifact
While Kalle's solution will do the work, I can't emphasize how this approach
is wrong, at least I think it is.
For situations like this, a custom plugin (or better, custom packaging)
would be the best, since this solution will produce inconsistent data:
Deployed POM will have packaging "pom", and that packaging has nothing to do
with ZIP as primary artifact. But it's only me ;)
Thanks,
~t~
On Thu, Jul 1, 2010 at 8:09 PM, Kalle Korhonen
wrote:
> The pom artifact is always produced regardless. Make your module type
> pom and attach the assembly zip as an artifact with the help of
> buildhelper plugin:
> http://mojo.codehaus.org/build-helper-maven-plugin/usage.html.
>
> Kalle
>
>
> On Thu, Jul 1, 2010 at 9:56 AM, Andreas Sewe
> wrote:
> > Hi all,
> >
> > I have a project which should produce a ZIP, with all contents of
> > ${project.build.outputDirect} put into a base directory within the ZIP.
> So
> > far, the maven-assembly-plugin with fits the bill
> > perfectly.
> >
> > There is one issue, however, which I haven't been able to solve: I can't
> get
> > the plugin to make the produced assembly the *primary* artifact. (There
> is
> > only a single assembly per project produced this way.)
> >
> > Is this possible? Or is there another plugin which I can resort to? (The
> > org.apache.maven.plugins:maven-zip-plugin does almost what I want, but
> > seems to be not longer supported in favour of the maven-assembly-plugin.)
> > Any suggestions?
> >
> > Best wishes,
> >
> > Andreas
> >
> > -
> > 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
>
>
Re: Maven-assembly-plugin: How to make the assembly the primary artifact
The pom artifact is always produced regardless. Make your module type
pom and attach the assembly zip as an artifact with the help of
buildhelper plugin:
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html.
Kalle
On Thu, Jul 1, 2010 at 9:56 AM, Andreas Sewe
wrote:
> Hi all,
>
> I have a project which should produce a ZIP, with all contents of
> ${project.build.outputDirect} put into a base directory within the ZIP. So
> far, the maven-assembly-plugin with fits the bill
> perfectly.
>
> There is one issue, however, which I haven't been able to solve: I can't get
> the plugin to make the produced assembly the *primary* artifact. (There is
> only a single assembly per project produced this way.)
>
> Is this possible? Or is there another plugin which I can resort to? (The
> org.apache.maven.plugins:maven-zip-plugin does almost what I want, but
> seems to be not longer supported in favour of the maven-assembly-plugin.)
> Any suggestions?
>
> Best wishes,
>
> Andreas
>
> -
> 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
Re: Maven-assembly-plugin: outputFileNameMapping and ${artifact.*}
Hi all,
here's a report of my "progress" on this issue, in case others find it
useful:
The maven-assembly-plugin uses an ObjectBasedValueSource to evaluate
${artifact.*} expressions with respect to the artifact's MavenProject
(among other things). You can thus access the artifact's properties by
${artifact.model.properties}. This, however, gives you a map and the
reflection-based ObjectBasedValueSource is stuck; there is no
zero-arguments getter to use.
At the moment, I don't see a way to accomplish what I am trying to do,
even although the documentation hints that this is possible:
3. Match against the project instance associated with the
dependency’s Artifact (resolves: mainly POM properties)
Are there any chances of extending the capabilities of the
maven-assembly-plugin in this respect? Or of at least fixing the
documentation -- although this does not solve my problem. :-(
Best wishes,
Andreas Sewe
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin not producing a Main-Class in the Manifest
Solved As you may have guessed, I forgot to run the assembly step. This added a lot of things to the jar that I had overlooked as missing after the build. Sorry for the silly question. On 09/06/2010 1:17 PM, Ron Wheeler wrote: I expected the following plug-in to produce a line in the Jar manifest Main-Class: com.artifact_software.carshistorycollector.CarsHistoryCollectorMain maven-assembly-plugin 2.2-beta-5 com.artifact_software.carshistorycollector.CarsHistoryCollectorMain jar-with-dependencies As you may have guessed, it did not. Got the jar with a nice manifest but no Main-Class line. Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: rwheeler Build-Jdk: 1.5.0_15 No error messages and the rest of the Jar looks good. Any suggestions? - 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
Re: Maven-Assembly-Plugin throwing (InvalidArtifactRTException).
Hello everybody, I solve my problem, but for that I had to changed the plugin
version of maven-assembly-plugin again, this time I decide to 2.2-beta-2, so
on follows my plugin config at pom.xml file.
maven-assembly-plugin
2.2-beta-2
jar-with-dependencies
${project.build.finalName}-bin
false
Anyway would be good if someone could help me to understand why the
exception is threw ... anyone?
--
View this message in context:
http://n2.nabble.com/Maven-Assembly-Plugin-throwing-InvalidArtifactRTException-tp4466929p4471619.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: maven assembly plugin - the artefact size is multiplied by 2
On Mon, Dec 14, 2009 at 7:43 PM, le squere, vincent wrote: > I've tried to use winzip, 7-zip, and to extract with the jar command. > It's always the same message, this archive is not a valid archive. > > So I can't see its contents. > > Just a precision, my assembly work fine on windows, the problem is just on > debian. > The JDK I use is 1.6.0_16-b01 Do you mean that on Windows, your assembly size isn't doubled ? Or that it is also doubled but can be opened properly by Winzip ? can you try: * from the module that fails mvn clean install file target/path_to_your_assembled_file unzip -l target/path_to_your_assembled_file and look at the output contents. Feel free to send it here if you don't make any progress. * try again building from scratch from the root of your multi-module project >> But, when the size of my ear is more than 20Mo, the size is multiplied by >> 2 in the destination folder. >> I thought that it just makes a copy. double size sounds like it included the EAR + all the dependencies of the EAR. How are you using the maven assembly plugin exactly ? J - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin - the artefact size is multiplied by 2
I've tried to use winzip, 7-zip, and to extract with the jar command. It's always the same message, this archive is not a valid archive. So I can't see its contents. Just a precision, my assembly work fine on windows, the problem is just on debian. The JDK I use is 1.6.0_16-b01 >But, when the size of my ear is more than 20Mo, the size is multiplied by > 2 in the destination folder. >I thought that it just makes a copy. Use Winzip or similar to unpack the Ear and look at the contents. You can probably figure out what's going on with a little more information, but just saying "its twice the size" without knowing anything more about it makes it tough to say why its happening. Wayne This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: maven assembly plugin - the artefact size is multiplied by 2
> But, when the size of my ear is more than 20Mo, the size is multiplied by > 2 in the destination folder. > I thought that it just makes a copy. Use Winzip or similar to unpack the Ear and look at the contents. You can probably figure out what's going on with a little more information, but just saying "its twice the size" without knowing anything more about it makes it tough to say why its happening. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin et dependencySet
Rémy wrote: > Hi, > > I've got a problem with the maven-assembly-plugin:2.2-beta-4 plugin. In the > POM, I set a reference to a descriptor.xml's file and some dependencies. > In the descriptor.xml file I defined to spread dependencies > in folders. I noticed that by using the element transitive > dependencies are not include. > > > > /yy/lib > > fr.:ww > > false > runtime > > > I can't find the dependencies of fr.:ww in the folder /yy/lib. I recently fell into the trap that I used the dependencySet but never actually had a dependency declared on that artifact in my POM. Maybe that's your case, too? Watch the build log, if you specify invalid dependencies, the assembly plugin will complain. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven Assembly Plugin] Deploy assembly
Yes, read the docs. My earlier link points at info about the deprecated goal (attached). There is a new one. My apologizes. /Anders On Fri, Nov 13, 2009 at 10:55, Stevo Slavić wrote: > http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html > > Regards, > Stevo. > > On Fri, Nov 13, 2009 at 10:51 AM, rgubler2 wrote: > > > > > > > > > Anders Hammar wrote: > > > > > > A quick Internet search gives the answer: > > > > > > http://old.nabble.com/Maven-assembly-plug-in-and-deploy-not-happening--td18161292.html > > > > > > /Anders > > > > > > > > > > Hmm, > > > > I changed > > > > > > make-assembly > > package > > > >assembly > > > > > > > > to > > > > > > make-assembly > > package > > > > attach > > > > > > > > > > and get now the following error: > > > > 'attach' was specified in an execution, but not found in the plugin > > > > > > What's wrong? > > > > > > Yours Rüdiger > > > > -- > > View this message in context: > > > http://old.nabble.com/-Maven-Assembly-Plugin--Deploy-assembly-tp26333720p26333970.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: [Maven Assembly Plugin] Deploy assembly
http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html Regards, Stevo. On Fri, Nov 13, 2009 at 10:51 AM, rgubler2 wrote: > > > > Anders Hammar wrote: > > > > A quick Internet search gives the answer: > > > http://old.nabble.com/Maven-assembly-plug-in-and-deploy-not-happening--td18161292.html > > > > /Anders > > > > > > Hmm, > > I changed > > > make-assembly > package > >assembly > > > > to > > > make-assembly > package > > attach > > > > > and get now the following error: > > 'attach' was specified in an execution, but not found in the plugin > > > What's wrong? > > > Yours Rüdiger > > -- > View this message in context: > http://old.nabble.com/-Maven-Assembly-Plugin--Deploy-assembly-tp26333720p26333970.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: [Maven Assembly Plugin] Deploy assembly
Anders Hammar wrote: > > A quick Internet search gives the answer: > http://old.nabble.com/Maven-assembly-plug-in-and-deploy-not-happening--td18161292.html > > /Anders > > Hmm, I changed make-assembly package assembly to make-assembly package attach and get now the following error: 'attach' was specified in an execution, but not found in the plugin What's wrong? Yours Rüdiger -- View this message in context: http://old.nabble.com/-Maven-Assembly-Plugin--Deploy-assembly-tp26333720p26333970.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: [Maven Assembly Plugin] Deploy assembly
A quick Internet search gives the answer: http://old.nabble.com/Maven-assembly-plug-in-and-deploy-not-happening--td18161292.html /Anders On Fri, Nov 13, 2009 at 10:35, rgubler2 wrote: > > Hello, > > we have the following pom: > > 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/maven-v4_0_0.xsd";> > 4.0.0 > gisdistribution > gisdistribution > gisdistribution > 0.0.2 > distribution archive of the mirgis > pom > > >mirgis >mirgis >1.11 > > > > > >maven-assembly-plugin > > > src/main/assembly/distribution.xml > > > > > > make-assembly > package > >assembly > > > > > > > > > > > giskernel > giskernel > 0.0.4 > > > > > > > > > > And the following distribution.xml: > > > assembly > >zip > > > > > lib > true > > > > > > > Maven now creates the "gisdistribution-0.0.2-assembly.zip" but it doesn't > deploy it. > We tried to use packaging "jar" but only empty jars are deployed. > > In which way can we deploy the assembly? > > > Yours Rüdiger > > > > -- > View this message in context: > http://old.nabble.com/-Maven-Assembly-Plugin--Deploy-assembly-tp26333720p26333720.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: Maven Assembly PlugIn...Multiple Artifacts with different configurations
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-components.html
Regards,
Stevo.
On Tue, Oct 20, 2009 at 8:39 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> i have the following question:
>
> I have to deliver a package with different configurations for different
> environments, to make things simple let us talk about a database connection
> for test, development and production.
>
> So the result of the build will be:
>
> package-1.0-dev.tar.gz
> package-1.0-test.tar.gz
> package-1.0-prod.tar.gz
>
> so i have discovered the following solutions for this:
>
> Solution 1:
>
> I can use a profiles.xml with different profiles which set a property
> which will be used for the package phase.
> This will result in the following calls of maven:
>
> mvn -Pdev package
> mvn -Ptest package
> mvn -Pprod package
>
> The disadvantage of this is that every time we call the package all other
> things like unit test etc. will run...and of course i have to call mvn three
> time (manually)...
>
>
> Solution 2:
>
> I can configure the Maven Assembly Plugin like the following:
>
>
>org.apache.maven.plugins
>maven-assembly-plugin
>2.2-beta-3
>
>
>db-config-1
>package
>
>single
>
>
>
>
> ${basedir}/src/main/assembly/dbconfig.xml
>
>
>
> ${basedir}/src/main/assembly/filterdb.properties
>
>${anemone.db.config.name}-test
>
>
>
> ...
>
>
> So for every environment which i need i can repeat the execution block with
> different names or property file etc.
>
> The result of such a configuration is that with a simple:
>
> mvn package
>
> as many packages will be produced as many execution parts are configured,
> but if i need for example more than three different packages it blow up my
> pom file with many repetitions...
>
> So my question is: Does exist a better or more elegant solution for this
> problem ?
>
> Many thanks in advance
>
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen http://www.soebes.de
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Maven Assembly Plugin
Try adding a . under fileset like below ... . ... On windows you can use '/' but this won't work on *nix boxes, where you have to use '.' -- View this message in context: http://www.nabble.com/Maven-Assembly-Plugin-tp16351103p25783885.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: [Solved] Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
I'm just having the same issue on MacOS after upgrading the assembly plugin from 2.1 to 2.2-beta-4 I think we could consider that it is a regression ? In my case the build hangs and I have to do a CTRL+C to have the error. Googling it I found this thread. Even if it took for me only few minutes to find, it can be very annoying for our users. What could we do ? Arnaud 2009/3/12 Raphaël Piéroni > Hi I solved my problem: > I should have not specified / in the descriptor. > I should have removed that line. > > Sorry for the noise. > > Thanks > > Raphaël > > 2009/3/12 Raphaël Piéroni : > > Thanks, Santos > > > > Right the command seems OK with adding double-quotes. > > > > But : > > 1. The error comes from Plexus. > > Caused by: java.io.IOException: Failed to retrieve numeric file > > attributes using: '/bin/sh -c ls -1nlaR /' > > at > org.codehaus.plexus.components.io.attributes.PlexusIoResourceAttributeUtils.executeLs(PlexusIoResourceAttributeUtils.java:238) > > > > 2. Plexus is used by the assembly plugin > > > > 3. The same plugin using plexus worked fine just in the precedent > > module of my multi-module build. > > > > Should i raise Jira against the assembly plugin ? > > > > Regards, > > > > Raphaël > > > > > > 2009/3/12 Santos Patel : > >> hi, > >> > >> i think the problem is with the command... > >> > >> /bin/sh -c ls -1nlaR as you have shown only results in the > result > >> given by /bin/sh -c ls > >> > >> It doesn't seem to take the ls options in to consideration. > >> the options > >> a --> show all files including ones starting with "." > >> R --> follow sub directories recursively. > >> > >> /bin/sh -c "ls -1nlaR" works fine and shows the results with the > file > >> attributes as required. > >> > >> Santosh > >> =-=-= > >> Notice: The information contained in this e-mail > >> message and/or attachments to it may contain > >> confidential or privileged information. If you are > >> not the intended recipient, any dissemination, use, > >> review, distribution, printing or copying of the > >> information contained in this e-mail message > >> and/or attachments to it are strictly prohibited. If > >> you have received this communication in error, > >> please notify us by reply e-mail or telephone and > >> immediately and permanently delete the message > >> and any attachments. Thank you > >> > >> > >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-assembly-plugin fileset excludes
I just struggled with this very thing yesterday... Adding a trailing
slash to the directory name did the trick for me.
Example: **/somedir/
On 7/27/09, Jason Chaffee wrote:
> I am not able to exclude directories for some reason. I have several
> directories that are identified with .temp and I have particular directory
> config that I would like to exclude them as follows:
>
>
> ${project.build.directory}/ux
> ./
>
> **/*.template
> **/config
>
>
>
> Having these are still being included in the archive. I was not able to
> find any examples on the plugin site. I am not sure if this is a bug or my
> excludes are simply wrong. Does anyone have any insight?
>
> thanks.
>
> Jason
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Sent from my mobile device
�...@n
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly plugin problem.
Thanks. It's work :)!
Mohan KR schrieb:
Did you try the outputFileNameMapping in the dependencySet descriptor for
assembly?
${artifact.artifactId}-${artifact.baseVersion}${dashC
lassifier?}.${artifact.extension}
Notice the version it is ${artifact.baseVersion} and *not*
${artifact.version}
Thanks,
mohan kr
-Original Message-
From: Alexander Vaysberg [mailto:w...@vaisberg.de]
Sent: Wednesday, July 01, 2009 2:42 AM
To: Maven Users List
Subject: maven assembly plugin problem.
Hi,
I have a problem with assembly plugin. I have a standalone application
and I make for this app a jar with manifest. In manifest set I a
Main-Class and all dependencies for this app with jar plugin. That work
fine. Than, I create with assembly the zip and get the all dependencies
in lib. But I have a problem with SNAPSHOT jars. I have 5 SNAPSHOT jars.
3-Jars copy the assembly as so:- db-1.0.0-SNAPSHOT.jar, but for 2 -jars
so same as: - firm-db-data-0.0.122-20090623.122812-2.jar. That is a date
and time. For Deploying use I the Archiva.
The jar plugin write in Manifest firm-db-data-0.0.122-SNAPSHOT. But the
assembly put the dependency as firm-db-data-0.0.122-20090623.122812-2. I
need the solution for this problem.
Alexander Vaysberg
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: maven assembly plugin problem.
Did you try the outputFileNameMapping in the dependencySet descriptor for
assembly?
${artifact.artifactId}-${artifact.baseVersion}${dashC
lassifier?}.${artifact.extension}
Notice the version it is ${artifact.baseVersion} and *not*
${artifact.version}
Thanks,
mohan kr
-Original Message-
From: Alexander Vaysberg [mailto:w...@vaisberg.de]
Sent: Wednesday, July 01, 2009 2:42 AM
To: Maven Users List
Subject: maven assembly plugin problem.
Hi,
I have a problem with assembly plugin. I have a standalone application
and I make for this app a jar with manifest. In manifest set I a
Main-Class and all dependencies for this app with jar plugin. That work
fine. Than, I create with assembly the zip and get the all dependencies
in lib. But I have a problem with SNAPSHOT jars. I have 5 SNAPSHOT jars.
3-Jars copy the assembly as so:- db-1.0.0-SNAPSHOT.jar, but for 2 -jars
so same as: - firm-db-data-0.0.122-20090623.122812-2.jar. That is a date
and time. For Deploying use I the Archiva.
The jar plugin write in Manifest firm-db-data-0.0.122-SNAPSHOT. But the
assembly put the dependency as firm-db-data-0.0.122-20090623.122812-2. I
need the solution for this problem.
Alexander Vaysberg
-
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
RE: maven assembly plugin
Hi there,
The assembly plugin has an outputFileNameMapping capability. So you would add
something like this:
${artifact.artifactId}.${artifact.extension}
You can find additional info here:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
I think that will get you what you want.
-Jim
-Original Message-
From: huser [mailto:mpinj...@atxg.com]
Sent: Thursday, June 04, 2009 9:49 AM
To: users@maven.apache.org
Subject: maven assembly plugin
Hi,
I am using the maven assembly plugin to create a zip file containing certain
jars. The zip file contains the version info of the jars as well.
Example:
abc.zip has activation-1.1.jar, commons-7.2.jar
How can I remove the version info from getting attached to the jar file and
consequently getting zipped ?
TIA,
--
View this message in context:
http://www.nabble.com/maven-assembly-plugin-tp23871508p23871508.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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-assembly-plugin][jar-with-dependencies] How to include only one dependency in the final jar ?
Hi everybody, you can find my solution http://www.developpez.net/forums/d751119/java/edi-outils-java/maven/maven-assembly-plugin-inclure-seule-dependence-jar/#post4348039 here it's my french thread Have a nice day Tchû -- View this message in context: http://www.nabble.com/-maven-assembly-plugin--jar-with-dependencies--How-to-include-only-one-dependency-in-the-final-jar---tp23737766p23758875.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
[Solved] Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
Hi I solved my problem: I should have not specified / in the descriptor. I should have removed that line. Sorry for the noise. Thanks Raphaël 2009/3/12 Raphaël Piéroni : > Thanks, Santos > > Right the command seems OK with adding double-quotes. > > But : > 1. The error comes from Plexus. > Caused by: java.io.IOException: Failed to retrieve numeric file > attributes using: '/bin/sh -c ls -1nlaR /' > at > org.codehaus.plexus.components.io.attributes.PlexusIoResourceAttributeUtils.executeLs(PlexusIoResourceAttributeUtils.java:238) > > 2. Plexus is used by the assembly plugin > > 3. The same plugin using plexus worked fine just in the precedent > module of my multi-module build. > > Should i raise Jira against the assembly plugin ? > > Regards, > > Raphaël > > > 2009/3/12 Santos Patel : >> hi, >> >> i think the problem is with the command... >> >> /bin/sh -c ls -1nlaR as you have shown only results in the result >> given by /bin/sh -c ls >> >> It doesn't seem to take the ls options in to consideration. >> the options >> a --> show all files including ones starting with "." >> R --> follow sub directories recursively. >> >> /bin/sh -c "ls -1nlaR" works fine and shows the results with the file >> attributes as required. >> >> Santosh >> =-=-= >> Notice: The information contained in this e-mail >> message and/or attachments to it may contain >> confidential or privileged information. If you are >> not the intended recipient, any dissemination, use, >> review, distribution, printing or copying of the >> information contained in this e-mail message >> and/or attachments to it are strictly prohibited. If >> you have received this communication in error, >> please notify us by reply e-mail or telephone and >> immediately and permanently delete the message >> and any attachments. Thank you >> >> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
Thanks, Santos Right the command seems OK with adding double-quotes. But : 1. The error comes from Plexus. Caused by: java.io.IOException: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.codehaus.plexus.components.io.attributes.PlexusIoResourceAttributeUtils.executeLs(PlexusIoResourceAttributeUtils.java:238) 2. Plexus is used by the assembly plugin 3. The same plugin using plexus worked fine just in the precedent module of my multi-module build. Should i raise Jira against the assembly plugin ? Regards, Raphaël 2009/3/12 Santos Patel : > hi, > > i think the problem is with the command... > > /bin/sh -c ls -1nlaR as you have shown only results in the result > given by /bin/sh -c ls > > It doesn't seem to take the ls options in to consideration. > the options > a --> show all files including ones starting with "." > R --> follow sub directories recursively. > > /bin/sh -c "ls -1nlaR" works fine and shows the results with the file > attributes as required. > > Santosh > =-=-= > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
hi, i think the problem is with the command... /bin/sh -c ls -1nlaR as you have shown only results in the result given by /bin/sh -c ls It doesn't seem to take the ls options in to consideration. the options a --> show all files including ones starting with "." R --> follow sub directories recursively. /bin/sh -c "ls -1nlaR" works fine and shows the results with the file attributes as required. Santosh =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
OK my project is some thing like this : root/ pom.xml (pom + dependency management) client/ pom.xml (pom) client-lib/ pom.xml (jar + an assembly + generated client from wsdl) client-app/ pom.xml (grails application + an assembly) stub/ pom.xml (pom) stub-lib/ pom.xml (jar + generated server from wsdl) stub-app/ pom.xml (war) integration/ pom.xml (jar + only tests that launc cargo to deploy both the stub-app and the client-app) My assembly are called in the client-lib and the client-app in a profile to deliver the sources. My client has to compile on its own computer using ant only. Hence the assembly of sources. Raphaël 2009/3/12 Santos Patel : > Hi, > > Can you please elaborate on the area where that command is used in your > code. > > Santosh > =-=-= > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
Exactly the same result as if i used ls directly but ls has the coloring. [u...@dev1 trunk]$ /bin/sh -c ls -1nlaR / client stub integration pom.xml pom.xml.releaseBackup release.properties [u...@dev1 trunk]$ ls client stub integration pom.xml pom.xml.releaseBackup release.properties Raphaël 2009/3/12 Nick Stolwijk : > What happens if you put "/bin/sh -c ls -1nlaR / " in a command window? > > With regards, > > Nick Stolwijk > ~Java Developer~ > > Iprofs BV. > Claus Sluterweg 125 > 2012 WS Haarlem > www.iprofs.nl > > > > On Thu, Mar 12, 2009 at 10:18 AM, Raphaël Piéroni > wrote: >> Please any help on this, >> I am stuck on the matter and >> also in a kind of a hurry. >> >> Regards, >> >> Raphaêl >> >> 2009/3/11 Raphaël Piéroni : >>> Hi folks, >>> >>> I have a strange error using the assembly plugin on CentOs4.7. >>> Obvioulsy the same checkout on windows works like a charm. >>> >>> For information my build is multi-module an two modules have an assembly. >>> The first succeed and the second fails. It even fails when i call it >>> in a mono module. >>> >>> I attached the offending assembly descriptor. >>> >>> Thanks in advance for any help. >>> >>> Regards, >>> >>> Raphaël >>> >>> Here the error i have: >>> [INFO] Failed to create assembly: Error creating assembly archive >>> source-distribution: Failed to retrieve numeric file attributes using: >>> '/bin/sh -c ls -1nlaR /' >>> >>> [INFO] >>> >>> [INFO] Trace >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>> create assembly: Error creating assembly archive source-distribution: >>> Failed to retrieve numeric file attributes using: '/bin/sh -c ls >>> -1nlaR /' >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) >>> 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:585) >>> at >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>> at >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to >>> create assembly: Error creating assembly archive source-distribution: >>> Failed to retrieve numeric file attributes using: '/bin/sh -c ls >>> -1nlaR /' >>> at >>> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:405) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) >>> ... 16 more >>> Caused by: >>> org.apache.maven.plugin.assembly.archive.ArchiveCreationException: >>> Error creating assembly archive source-distribution: Failed to >>> retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' >>> at >>> org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:194) >>> at >>> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:354) >>> ... 18 more >>> Caused by: org.codehaus.plexus.archiver.ArchiverException: Failed to >>> retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' >>> at >>> org.codehaus.plexus.archiver.AbstractArchiver$1.hasNext(AbstractArchiver.java:366) >>> at >>> org.apache.maven.plugin.assembly.filter.ComponentsXmlArchiverFileFilter.finalizeArchiveCreation(ComponentsXmlArchiverFileFilter.java:166) >>> at >>> org.codehaus.plexus.archiver.AbstractArchiver.runArchiveFinalizers(AbstractArchiver.java:760) >>> at >>> org.
Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
Hi, Can you please elaborate on the area where that command is used in your code. Santosh =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
