[ANN] Apache Maven Assembly Plugin 3.7.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.7.1 The Assembly Plugin for Maven enables developers to combine project output into a single distributable archive that also contains dependencies, modules, site documentation, and other files. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.7.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.7.1 ** Bug * [MASSEMBLY-1020] - Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null * [MASSEMBLY-1021] - Nullpointer in assembly:single when upgrading to 3.7.0 * [MASSEMBLY-1022] - Unresolved artifacts should be not processed ** Dependency upgrade * [MASSEMBLY-1023] - Bump org.apache.maven.shared:maven-filtering from 3.3.1 to 3.3.2 * [MASSEMBLY-1024] - Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 * [MASSEMBLY-1025] - Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 Enjoy, -The Apache Maven team
[ANN] Apache Maven Assembly Plugin 3.7.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.7.0 The Assembly Plugin for Maven enables developers to combine project output into a single distributable archive that also contains dependencies, modules, site documentation, and other files. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.7.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.7.0 ** Bug * [MASSEMBLY-967] - maven-assembly-plugin doesn't add target/class artifacts in generated jarfat but META-INF/MANIFEST.MF seems to be correct * [MASSEMBLY-994] - Items from unpacked dependency are not refreshed * [MASSEMBLY-998] - Transitive dependencies are not properly excluded as of 3.1.1 * [MASSEMBLY-1008] - Assembly plugin handles scopes wrongly * [MASSEMBLY-1018] - Fix examples about useStrictFiltering ** New Feature * [MASSEMBLY-992] - Facility to define assembly descriptor in body of POM ** Improvement * [MASSEMBLY-1007] - Upgrade maven-plugin parent to 41 * [MASSEMBLY-1016] - clarify and fix plugin system requirements history * [MASSEMBLY-1017] - Don't use deprecated methods in code ** Task * [MASSEMBLY-991] - XSDs for 2.2.0 missing from Maven Project Web Site * [MASSEMBLY-1000] - ITs - cleanups, refresh plugins versions * [MASSEMBLY-1003] - Remove unused remoteRepositories * [MASSEMBLY-1004] - Remove ignored and deprecated parameter - useJvmChmod * [MASSEMBLY-1010] - Use IOUtils from commons-io instead of plexus * [MASSEMBLY-1013] - Code cleanups ** Dependency upgrade * [MASSEMBLY-995] - Bump org.codehaus.plexus:plexus-archiver from 4.7.1 to 4.9.1 * [MASSEMBLY-996] - Bump zstd-jni from 1.5.5-4 to 1.5.5-11 * [MASSEMBLY-997] - Bump commons-io from 2.11.0 to 2.13.0 * [MASSEMBLY-999] - Upgrade Parent to 40 * [MASSEMBLY-1009] - Bump commons-io from 2.13.0 to 2.15.1 * [MASSEMBLY-1011] - Bump maven-archiver from 3.6.0 to 3.6.1 * [MASSEMBLY-1012] - Bump org.apache.commons:commons-compress from 1.23.0 to 1.25.0 * [MASSEMBLY-1014] - Bump org.codehaus.plexus:plexus-interpolation from 1.26 to 1.27 * [MASSEMBLY-1015] - Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 * [MASSEMBLY-1019] - Maven 3.6.3 as minimum requirements Enjoy, -The Apache Maven team
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
maven-assembly-plugin, bin example is giving me trouble
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
[ANN] Apache Maven Assembly Plugin 3.6.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.6.0 The Assembly Plugin for Maven enables developers to combine project output into a single distributable archive that also contains dependencies, modules, site documentation, and other files. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.6.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.6.0 ** Bug * [MASSEMBLY-843] - finalName as readonly parameter makes common usecases very complicated * [MASSEMBLY-965] - Symbolic links get copied with absolute path * [MASSEMBLY-977] - Warning if using Maven 3.9.1 * [MASSEMBLY-986] - Minimal default Manifest configuration of jar archiver should be respected ** New Feature * [MASSEMBLY-973] - Support Zstandard compression format ** Improvement * [MASSEMBLY-989] - in RB mode, apply 022 umask to ignore environment group write umask * [MASSEMBLY-990] - add system requirements history ** Task * [MASSEMBLY-974] - Drop deprecated repository element * [MASSEMBLY-983] - Support running build on Java 20 * [MASSEMBLY-984] - Refresh download page * [MASSEMBLY-985] - Cleanup declared dependencies * [MASSEMBLY-988] - Avoid using deprecated methods of plexus-archiver ** Dependency upgrade * [MASSEMBLY-972] - Upgrade maven-plugin parent to 39 * [MASSEMBLY-978] - Upgrade plexus-utils to 3.5.1 * [MASSEMBLY-979] - Bump maven-common-artifact-filters from 3.3.1 to 3.3.2 * [MASSEMBLY-981] - Bump log4j from 1.x to 2.x in integration tests * [MASSEMBLY-982] - drop dependency to maven-compat * [MASSEMBLY-987] - Bump plexus-archiver from 4.6.0 to 4.7.1 Enjoy, -The Apache Maven team
[ANN] Apache Maven Assembly Plugin 3.5.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.5.0 This plugin builds an assembly (distribution) of sources and/or binaries. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.5.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.5.0 ** Bug * [MASSEMBLY-941] - file permissions removed during assembly:single since 3.2.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 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 > > > >
Maven assembly plugin - Proxies not working with mirrors
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
[ANN] Maven Assembly Plugin 3.4.2 released
The Apache Maven team is pleased to announce the release of the Maven Assembly Plugin version 3.4.2. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.4.2 Release Notes - Maven Assembly Plugin - Version 3.4.2 ** Bug * [MASSEMBLY-969] - Excludes filtering in 3.4.0 and 3.4.1 differs from 3.3.0 ** Task * [MASSEMBLY-949] - Examples should refer to https instead of http Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-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\aeo-kmo-portefeuille-
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 dependencie
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-Portefeuille-Emitt
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
Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?
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.
[ANN] Apache Maven Assembly Plugin 3.4.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.4.1 https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.4.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.4.1 ** Bug * [MASSEMBLY-964] - Error build with shared assemblies Enjoy, -The Apache Maven team
[ANN] Maven Assembly Plugin 3.4.0 released
The Apache Maven team is pleased to announce the release of the Maven Assembly Plugin, version 3.4.0 https://maven.apache.org/plugins/maven-assembly-plugin/ Release Notes - Maven Assembly Plugin - Version 3.4.0 ** Bug * [MASSEMBLY-955] - dependencySet includes filter with classifier breaks include of artifacts without classifier ** Task * [MASSEMBLY-945] - Speed improvements * [MASSEMBLY-954] - Update plugin (requires Maven 3.2.5+) * [MASSEMBLY-956] - assembly plugin resolves too much, even plugins used to build dependencies * [MASSEMBLY-957] - Deprecate the repository element in assembly descriptor * [MASSEMBLY-959] - Upgrade to Java 8, drop unused dependencies ** Dependency upgrade * [MASSEMBLY-960] - Upgrade Maven Filtering to 3.3.0 * [MASSEMBLY-961] - Upgrade maven-archiver to 3.6.0 * [MASSEMBLY-962] - Upgrade maven-common-artifact-filters to 3.3.0 Have fun - The Apache Maven Team
Re: Splitting a dependency tree with the assembly plugin
> On 2022-05-07T20:42:51 +0200 > Thomas Broyer wrote: > > How about first building a distribution for each module separately (each in > its own Maven module) and then assemble them into a single distribution? I eventually went with this model. One application produces a distribution zip, and the distribution model unpacks the distribution and re-packs it with the contents of the other application. I've had to introduce profiles in order to avoid breaking the build if assemblies are skipped. -- Mark Raynsford | https://www.io7m.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Splitting a dependency tree with the assembly plugin
On 2022-05-07T20:42:51 +0200 Thomas Broyer wrote: > How about first building a distribution for each module separately (each in > its own Maven module) and then assemble them into a single distribution? Hello! That might be an option, although I'm not sure how the modules and dependencies would need to be arranged. -- Mark Raynsford | https://www.io7m.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Splitting a dependency tree with the assembly plugin
How about first building a distribution for each module separately (each in its own Maven module) and then assemble them into a single distribution? Le sam. 7 mai 2022 à 18:49, Mark Raynsford a écrit : > Hello! > > I'm running into a problem when trying to produce an application > distribution. > > This is the pom.xml file: > > > https://github.com/io7m/eigion/blob/develop/com.io7m.eigion.distribution.example/pom.xml > > The module essentially represents two isolated applications that have > been combined into one Maven module for the purposes of producing a > distribution zip file. The first application is represented by the > com.io7m.eigion.launcher.main dependency, and the other is represented > by the com.io7m.eigion.gui dependency. > > I have the following assembly descriptor: > > > https://github.com/io7m/eigion/blob/develop/com.io7m.eigion.distribution.example/src/main/assembly/distribution.xml > > What I'm trying to do is: > > * Put com.io7m.eigion.gui and all dependencies of com.io7m.eigion.gui > into "workbench/modules" in the assembly. > * Put all dependencies of com.io7m.eigion.launcher.main into > "launcher/modules" in the assembly. > > This is _mostly_ working, except that it seems that at least one > transitive dependency of com.io7m.eigion.launcher.main is being left > out. Specifically, for example, it seems that com.io7m.junreachable.core > is being left out of "launcher/modules". I _think_ what's happening is > that because com.io7m.junreachable.core is also transitive dependency > of com.io7m.eigion.gui, it's being excluded. > > Is there perhaps a more intelligent way to achieve what I'm trying to > achieve? > > -- > Mark Raynsford | https://www.io7m.com > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Splitting a dependency tree with the assembly plugin
Hello! I'm running into a problem when trying to produce an application distribution. This is the pom.xml file: https://github.com/io7m/eigion/blob/develop/com.io7m.eigion.distribution.example/pom.xml The module essentially represents two isolated applications that have been combined into one Maven module for the purposes of producing a distribution zip file. The first application is represented by the com.io7m.eigion.launcher.main dependency, and the other is represented by the com.io7m.eigion.gui dependency. I have the following assembly descriptor: https://github.com/io7m/eigion/blob/develop/com.io7m.eigion.distribution.example/src/main/assembly/distribution.xml What I'm trying to do is: * Put com.io7m.eigion.gui and all dependencies of com.io7m.eigion.gui into "workbench/modules" in the assembly. * Put all dependencies of com.io7m.eigion.launcher.main into "launcher/modules" in the assembly. This is _mostly_ working, except that it seems that at least one transitive dependency of com.io7m.eigion.launcher.main is being left out. Specifically, for example, it seems that com.io7m.junreachable.core is being left out of "launcher/modules". I _think_ what's happening is that because com.io7m.junreachable.core is also transitive dependency of com.io7m.eigion.gui, it's being excluded. Is there perhaps a more intelligent way to achieve what I'm trying to achieve? -- Mark Raynsford | https://www.io7m.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Regarding component usage in maven-assembly-plugin
That file does not define top level element called component, hence the original question. On Mon, Feb 22, 2021 at 4:24 PM Jean-Pierre Urkens wrote: > > Have a look at http://maven.apache.org/xsd/assembly-2.1.0.xsd > Look in the example assembly files that come packaged with the plugin. In > the xml assembly file you'll see a reference to: > > http://maven.apache.org/ASSEMBLY/2.1.0; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0 > http://maven.apache.org/xsd/assembly-2.1.0.xsd;> > > > -Original Message- > From: Mantas Gridinas > Sent: maandag 22 februari 2021 15:20 > To: users@maven.apache.org > Subject: Regarding component usage in maven-assembly-plugin > > Yo! > > I've recently started using the assembly plugin and noticed that the > documentation does not specify the XSD files for component descriptor files. > Is there a particular reason for this? > > Cheers! > > - > 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: Regarding component usage in maven-assembly-plugin
Have a look at http://maven.apache.org/xsd/assembly-2.1.0.xsd Look in the example assembly files that come packaged with the plugin. In the xml assembly file you'll see a reference to: http://maven.apache.org/ASSEMBLY/2.1.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0 http://maven.apache.org/xsd/assembly-2.1.0.xsd;> -Original Message- From: Mantas Gridinas Sent: maandag 22 februari 2021 15:20 To: users@maven.apache.org Subject: Regarding component usage in maven-assembly-plugin Yo! I've recently started using the assembly plugin and noticed that the documentation does not specify the XSD files for component descriptor files. Is there a particular reason for this? Cheers! - 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
Regarding component usage in maven-assembly-plugin
Yo! I've recently started using the assembly plugin and noticed that the documentation does not specify the XSD files for component descriptor files. Is there a particular reason for this? Cheers! - 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.
>
maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
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.
maven-assembly-plugin Windows vs Linux
https://stackoverflow.com/questions/64364051/maven-assembly-plugin-windows-vs-linux
.. sorry to post in two places, but hoping to get someones attention :-[ ...
I have a project that uses the maven-assembly-plugin and I see a
difference in behavior when building on Linux vs Windows. Exactly the
same pom.xml and assembly.xml are used on each platform.
Windows:
mvn logging looks like this:
|[INFO] --- maven-jar-plugin:3.1.0:jar (default-jar) @ foo --- [INFO]
Building jar: C:\foo\target\foo.jar [INFO] [INFO] ---
maven-assembly-plugin:3.1.0:single (default) @ foo --- [INFO] Reading
assembly descriptor: assembly.xml [INFO] Copying files to
C:\foo\target\foo [WARNING] Assembly file: C:\foo\target\foo is not a
regular file (it may be a directory). It cannot be attached to the
project build for installation or deployment. |
And in the target directory I observe a directory C:\foo\target\foo
which contains all the project's dependent jars.
Linux:
mvn logging looks like this:
|[INFO] --- maven-jar-plugin:3.1.0:jar (default-jar) @ foo --- [INFO]
Building jar: /home//foo/target/foo.jar [INFO] [INFO] ---
maven-assembly-plugin:3.1.0:single (default) @ foo --- [INFO] Reading
assembly descriptor: assembly.xml [INFO] Copying files to
/home//foo/target/foo-1.0.0001 [WARNING] Assembly file:
/home//foo/target/foo-1.0.0001 is not a regular file (it may be a
directory). It cannot be attached to the project build for installation
or deployment. |
But in the target directory there is no directory target/foo (nor
target/foo-1.0.001)
I should note that a downstream project is expecting the target/foo
directory to exist which is why I'm investigating the difference in
behavior between Windows and Linux.
This is plugin definition in my pom:
| maven-assembly-plugin
package single
false
assembly.xml
|
and this is the assembly descriptor:
|xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/3.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/3.1.0
http://maven.apache.org/xsd/assembly-3.1.0.xsd;> tar
dir
false
${project.build.directory}/${project.artifactId}.jar
./
false
${artifact}
|
I have tried tinkering with finalName in both the and
sections to no avail and have also tried more recent versions of
the plugin.
*The urgent question is why does a build on Windows give me the
target\foo directory with the dependencies in, whilst after a build on
Linux I don't see the equivalent ?*
Thanks very much for getting this far :-)
[maven-assembly-plugin] tries to find tools.jar which does not exist in adoptopenjdk-11
Hello, I am wondering if someone could give me a hint regarding the following error when building a maven project (Maven 3.6.1, adoptopenjdk 11.0.6) "Could not find artifact com.sun:tools:jar:2.0.5 at specified path /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/../lib/tools.jar" It seems to arise from the "single"-goal of the maven-assembly-plugin. I know that there is no tools.jar in Java 11 JDKs in general any more. I tried versions 3.0.0, 3.2.0 and 3.3.0 of maven-assembly-plugin, which yield the above error. I also tried Version 2.6 which does not yield the above error. Thank you very much in advance, kind regards, Heinz -- Heinz KnocheConsultantDevelopmentPublic Authorities Web & Application Securitysecunet Security Networks AG +49 201 5454-3933+49 1512 4169541heinz.kno...@secunet.com Konrad-Zuse-Platz 281829 Munich, Germanywww.secunet.com Sitz: Kurfürstenstraße 58, 45138 Essen, DeutschlandAmtsgericht Essen HRB 13615Vorstand: Dr. Rainer Baumgart (Vors.), Thomas PleinesAufsichtsratsvorsitzender: Ralf Wintergerst signature.asc Description: This is a digitally signed message part
[ANN] Apache Maven Assembly Plugin 3.3.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.3.0 The Assembly Plugin for Maven enables developers to combine project output into a single distributable archive that also contains dependencies, modules, site documentation, and other files. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.3.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.3.0 ** Bug * [MASSEMBLY-879] - useDefaultExcludes has no effect in dependencySet/unpack * [MASSEMBLY-920] - ContainerDescriptorHandler for MetaInf-Services breaks folder structure * [MASSEMBLY-932] - resource filtering skipped for resources in the current project ** New Feature * [MASSEMBLY-922] - allow to override UID/GID and user name and group name for files stored in TAR (and other formats that store UID/GID) * [MASSEMBLY-927] - Support for properties mapping on executions of maven-assembly-plugin * [MASSEMBLY-934] - Support concatenation of files ** Improvement * [MASSEMBLY-765] - add property groupIdPath * [MASSEMBLY-849] - Add nonFilteredFileExtensions to avoid filtering of binary files * [MASSEMBLY-933] - make build Reproducible ** Dependency upgrade * [MASSEMBLY-924] - Upgrade commons-compress to 1.19 Enjoy, -The Apache Maven team
[ANN] Apache Maven Assembly Plugin 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.2.0 This plugin is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.2.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.2.0 ** Bug * [MASSEMBLY-871] - Descriptor ref "bin" causes error messages in the build log on Windows ** New Feature * [MASSEMBLY-921] - Reproducible Builds: make entries in output archive reproducible (order + timestamp) ** Improvement * [MASSEMBLY-914] - Add GitHub Informations ** Task * [MASSEMBLY-915] - Remove integration-test-archetype Read https://maven.apache.org/guides/mini/guide-reproducible-builds.html for more information on Reproducible Builds with Maven. Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-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
maven-assembly-plugin after plexus-archiver 4.2.0 is released; implement user/group override for archives
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? -- VH signature.asc Description: OpenPGP digital signature
Where in the Maven source code "default excludes" of the Maven Assembly plugin are defined?
I grep'd over the main Maven repo as well as the Assembly plugin's repo and couldn't find anything helpful. --- Best regards, Behrang Saeedzadeh blog.behrang.org
[ANN] Apache Maven Assembly Plugin 3.1.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.1.1 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.1.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.1.1 ** Bug * [MASSEMBLY-675] - Maven Assembly packaging wildcard-excluded dependencies * [MASSEMBLY-762] - Assembly plugin doesn't exclude transitive dependencies when excluded by wildcards in dependencies section * [MASSEMBLY-799] - Exclusion on wildcard, then the assembly would still package to include the excluded libraries * [MASSEMBLY-861] - exclusion * also packaged * [MASSEMBLY-873] - Maven-Assembly-Plugin freezes when building jar-with-dependencies of project depending on org.bouncycastle:bcprov-jdk15on:1.58 * [MASSEMBLY-893] - Typo in FAQ ** Task * [MASSEMBLY-885] - remove unused unpack code * [MASSEMBLY-898] - upgrade to plexus-io 3.1.1 * [MASSEMBLY-899] - Make deprecated and non used of parameter useJvmChmod parameter (plugin is now 1.7) * [MASSEMBLY-901] - Fix trivial javadocs HTML errors * [MASSEMBLY-902] - Some Integration tests fails if launched with an very large UID ** Dependency upgrade * [MASSEMBLY-876] - Upgrade parent to 31 * [MASSEMBLY-882] - Upgrade mave-surefire/failsafe-plugin 2.21.0 * [MASSEMBLY-884] - Upgrade plexus-archiver to 3.6.0 * [MASSEMBLY-890] - Upgrade plexus-interpolation to 1.25 * [MASSEMBLY-892] - Upgrade maven-plugins parent to version 33 * [MASSEMBLY-900] - Upgrade plexus-archiver to 4.0.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven assembly Plugin - Shared Assembly Descriptor interpolation ?
Hello,
Can I use variables in a assembly xml that is inside a shared descriptor
project?
inside my assembly file I have put this:
${my.cacheDirectory}/plugins
bundles
But I'm getting a failure on the build goal because the directory is not
found.
Am I missing something?
thanks,
Cristiano
-
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
Maven assembly Plugin - ignore pom packaging
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
How maven assembly plugin auto-resolves classpath conflicts (example case)
Hello. I have found this to be an issue while migrating a project from Maven to SBT. SBT is only here for reference since it reports what I think should be reported. To describe the problem I have created an example project with dependencies that I found to behave differently, depending on the build tool. https://github.com/atais/mvn-sbt-assembly The only dependencies are (sbt style) "com.netflix.astyanax" % "astyanax-cassandra" % "3.9.0", "org.apache.cassandra" % "cassandra-all" % "3.4", and what I do not understand is, why mvn package creates the fat jar successfully, while sbt assembly gives conflicts: [error] 39 errors were encountered during merge [error] java.lang.RuntimeException: deduplicate: different file contents found in the following: [error] /home/siatkowskim/.ivy2/cache/org.slf4j/jcl-over-slf4j/jars/jcl-over-slf4j-1.7.7.jar:org/apache/commons/logging/ [error] /home/siatkowskim/.ivy2/cache/commons-logging/commons-logging/jars/commons-logging-1.1.1.jar:org/apache/commons/logging/ ... [error] /home/siatkowskim/.ivy2/cache/com.github.stephenc.high-scale-lib/high-scale-lib/jars/high-scale-lib-1.1.2.jar:org/cliffc/high_scale_lib/ [error] /home/siatkowskim/.ivy2/cache/com.boundary/high-scale-lib/jars/high-scale-lib-1.0.6.jar:org/cliffc/high_scale_lib/ ... How come Maven knows which class to take? How can it be sure, that it is the correct choice? There is a question on SO, if you would like to earn some points: https://stackoverflow.com/questions/50249818/why-maven-assembly-works-when-sbt-assembly-find-conflicts I have been directed here, from https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-887
Re: Dependency is missed while using maven-assembly-plugin
Hello, Thorsten Thank you very much for the help! Yes, this is the reason of my problem. I tested it on next releases of batik and found that the dependency structure changed in next versions and there's no batik-js in dependency tree. Unfortunately, I couldn't upgrade version because in real project these batik 1.7 libraries are used in some third-party plugin used by our GUI developers. For my case it was convenient to use exclusions for batik-script and batik-bridge. And use these excluded dependencies external. Like this. internal-module-groupId internal-module-artifactId org.apache.xmlgraphics batik-bridge org.apache.xmlgraphics batik-script org.apache.xmlgraphics batik-script 1.7 org.apache.xmlgraphics batik-bridge 1.7 Anyway, thank you for your responses! Have a nice day! -- Regards, Sergey Vaysman On 03.04.2018 14:05, Thorsten Heit wrote: Hi Sergey, I updated to the latest maven version 3.5.3 and configured the project to use the latest maven-assembly-plugin version 3.1.0. You seem to be hit by https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-782. In short: You have circular dependencies in Batik 1.7: batik-bridge -> batik-script -> batik-bridge... Can you use a newer version of batik-transcoder such as 1.8, 1.9 or 1.9.1 (all available on Maven Central)? Regards Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re: Dependency is missed while using maven-assembly-plugin
Hi Sergey, > I updated to the latest maven version 3.5.3 and configured the project > to use > the latest maven-assembly-plugin version 3.1.0. You seem to be hit by https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-782. In short: You have circular dependencies in Batik 1.7: batik-bridge -> batik-script -> batik-bridge... Can you use a newer version of batik-transcoder such as 1.8, 1.9 or 1.9.1 (all available on Maven Central)? Regards Thorsten
Re: Re: Dependency is missed while using maven-assembly-plugin
Hi, > The first thing I need to mention that I gave you a wrong version of > maven-assembly-plugin. > Maven-assembly-plugin version: 2.2-beta-5 > Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; > 2014-12-14T20:29:23+03:00) > Maven home: C:\soft\apache-maven-3.2.5 > Java version: 1.8.0_131, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.8.0_131\jre > Default locale: ru_RU, platform encoding: Cp1251 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" Can you try with with m-assembly-p 3.1.0 and see whether this behaves different? Could you switch to a newer version of Maven, i.e. 3.5.3 (the newest? Regards Thorsten
Re: Dependency is missed while using maven-assembly-plugin
ran mvn package against pom.xml from supplied project.zip with no missing
dependencies:
[DEBUG] Goal:
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (default)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${appendAssemblyId}
${attach}
${classifier}
${descriptor}
${descriptorId}
src/main/assembly/assembly-descriptor.xml
${assembly.dryRun}
${ignoreMissingDescriptor}
${includeSite}
${session}
${runOnlyAtExecutionRoot}
${skipAssembly}
${tarLongFileMode}
[DEBUG] ===
[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1972051,
ConflictMarker.markTime=738132, ConflictMarker.nodeCount=84,
ConflictIdSorter.graphTime=1371731, ConflictIdSorter.topsortTime=935252,
ConflictIdSorter.conflictIdCount=24, ConflictIdSorter.conflictIdCycleCount=3,
ConflictResolver.totalTime=8674975, ConflictResolver.conflictItemCount=82,
DefaultDependencyCollector.collectTime=137005478,
DefaultDependencyCollector.transformTime=16792725}
[DEBUG] ru.spi2.test:sbercap-dependencies:jar:1.0-SNAPSHOT
[DEBUG]org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:fop:jar:0.94:compile
[DEBUG] org.apache.xmlgraphics:xmlgraphics-commons:jar:1.2:compile
[DEBUG] commons-logging:commons-logging:jar:1.0.4:compile
[DEBUG] commons-io:commons-io:jar:1.1:compile
[DEBUG]
org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
[DEBUG]
org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1:compile
[DEBUG] org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-css:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-script:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-js:jar:1.7:compile
I am baffled why your dependency manager is skipping batik-js:1.7?
with same pom.xml can you
mvn dependency:tree >output
and send us output
?
Martin
__
From: Сергей Вайсман <vaysman.spi.w...@gmail.com>
Sent: Monday, April 2, 2018 10:24 AM
To: users@maven.apache.org
Subject: Dependency is missed while using maven-assembly-plugin
Hello.
I have a problem using maven-assembly-plugin.
I want to get during package phase a directory with all project dependencies.
But I have a transitive dependency with compile scope which is missed from
assembly output directory.
The missed jar is batik-js-1.7.jar. Here is a dependency tree for this jar
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
sbercap-dependencies ---
[INFO] ru.spi2.test:sbercap-dependencies:jar:1.0-SNAPSHOT
[INFO] \- org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
...
[INFO]+- org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-css:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-script:jar:1.7:compile
[INFO]| | \- org.apache.xmlgraphics:batik-js:jar:1.7:compile
...
When assembly plugin is finished, others dependencies (batik-anim-1.7.jar,
batik-css-1.7.jar) are added to output directory successfully. The
batik-js-1.7.jar
is missed (screenshot no-batik-js-in-assembly-output.png attached).
On the other side, if I try to copy all dependencies using
maven-dependency-plugin,
the batik-js-1.7.jar is successfully added to the folder (screenshot
batik-js-in-dependencies attached).
Here is my dependencies and build blocks from pom.xml
org.apache.xmlgraphics
batik-transcoder
1.7
org.apache.maven.plugins
maven-dependency-plugin
copy
package
copy-dependencies
${project.build.directory}/dependency-libs
org.apache.maven.plugins
maven-assembly-plugin
package
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" <sawil...@akamai.com> 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 <jim@sri.com>
Reply-To: Maven Users List <users@maven.apache.org>
Date: Friday, December 15, 2017 at 12:27 PM
To: Maven Users List <users@maven.apache.org>
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"
<sawil...@akamai.com<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 <sawil...@akamai.com<mailto:sawil...@akamai.com>>
Reply-To: Maven Users List
<users@maven.apache.org<mailto:users@maven.apache.org>>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org<mailto:users@maven.apache.org>"
<users@maven.apache.org<mailto:users@maven.apache.org>>
Subject: Re: Maven Assembly Plugin renaming jar
Oh,
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 <jim@sri.com>
Reply-To: Maven Users List <users@maven.apache.org>
Date: Friday, December 15, 2017 at 12:27 PM
To: Maven Users List <users@maven.apache.org>
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"
<sawil...@akamai.com<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 <sawil...@akamai.com<mailto:sawil...@akamai.com>>
Reply-To: Maven Users List
<users@maven.apache.org<mailto:users@maven.apache.org>>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org<mailto:users@maven.apache.org>"
<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
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" <sawil...@akamai.com> wrote:
Sorry to bump and old thread, but I’d appreciate it if someone had any
insight.
Sam
From: Sam Wilson <sawil...@akamai.com>
Reply-To: Maven Users List <users@maven.apache.org>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org" <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}
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 <sawil...@akamai.com> ha scritto:
> Sorry to bump and old thread, but I’d appreciate it if someone had any
> insight.
>
> Sam
>
> From: Sam Wilson <sawil...@akamai.com>
> Reply-To: Maven Users List <users@maven.apache.org>
> Date: Friday, November 24, 2017 at 11:12 AM
> To: "users@maven.apache.org" <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 <sawil...@akamai.com>
Reply-To: Maven Users List <users@maven.apache.org>
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org" <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
Maven Assembly Plugin renaming jar
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;>
bin
${artifactId}
tar.gz
dir
false
false
runtime
lib
target/${artifactId}-${version}.${packaging}
/
${artifactId}.${packaging}
src/main/resources/ProjectConfiguration.properties
${artifactId}.properties
/
log4j2.xml
/
Assembly plugin not packaging all dependencies as expected
I define a dependencySet entry in my assembly descriptor where I explicitly include one or more artifacts, like this: false myBaseDir 0755 0755 true true mygroup:myartifact1 mygroup:myartifact2 The resulting assembly includes "artifact1" and "artifact2" and a lot of their dependencies, but it does not include ALL of their dependencies. When i run mvn with the -X option, I can see a message like this: "[DEBUG] The following artifacts were removed by this artifact inclusion filter: " followed by a list of artifacts that were not included in the assembly (for whatever reason). Unfortunately, some of the artifacts that I actually need to be included in the assembly are in this list. Can someone please explain why artifacts that are in the dependency hierarchy of "artifact1" and/or "artifact2" are somehow being excluded? I've resorted to explicitly including the missing dependencies but that's not really an optimal solution :) Thanks in advance for any help -- Phil Adams
[ANN] Apache Maven Assembly Plugin Version 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin Version 3.1.0 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. https://maven.apache.org/plugins/maven-assembly-plugin/ Important Note since 3.1.0: * Maven 3.X only * JDK 7 minimum requirement You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.1.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes Maven Assembly Plugin 3.1.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12338667 Bugs: * [MASSEMBLY-643] - descriptorSourceDirectory: parameter isn't used * [MASSEMBLY-841] - Maven Assembly Plugin throws IllegalStateException when looking for project modules * [MASSEMBLY-842] - Incorrect entries created in MANIFEST/maven * [MASSEMBLY-855] - Remote repositories ignored in a multi-module project Dependency upgrades: * [MASSEMBLY-854] - Upgrade to Plexus Archiver 3.5 * [MASSEMBLY-859] - Upgrade to Plexus IO 3.0.0 * [MASSEMBLY-867] - Upgrade maven-archiver to 3.2.0 * [MASSEMBLY-868] - Upgrade plexus-utils to version 3.1.0 Improvements: * [MASSEMBLY-711] - Add support for generating XZ compressed tarballs (.tar.xz) * [MASSEMBLY-858] - don't read assembly descriptor from thread classloader but plugin classloader * [MASSEMBLY-860] - Upgrade to Java 7 Thanks to the volunteer(s) who helped to check this release. o Grzegorz Grzybek Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven 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 <paul.mun...@verifone.com>
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 <bs.sandh...@gmail.com>
> 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 <bs.sandh...@gmail.com>
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 <bs.sandh...@gmail.com>
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*
>
maven assembly plugin not recognizing
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/
core
client-assembly
package
single
${project.version}
src/main/client-descriptor.xml
false
${project.basedir}/target/dist/framework/lib/client/
client
--
*Thanks*
*Bikramjit Singh*
[ANN] Apache Maven Assembly Plugin 3.0.0 Released
Hi, The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.0.0 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. https://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 3.0.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 3.0.0 ** Bug * [MASSEMBLY-756] - escapeString doesn't work correctly for the 2nd filtering * [MASSEMBLY-773] - MetaInfServicesHandler catalog is not cleared between invocations in multimodule projects * [MASSEMBLY-777] - The assembly plugin refuses to copy a file named lexicon.filtered or lexicon.formatted * [MASSEMBLY-789] - assembly:single with repacking tar.gz results in UndeclaredThrowableException * [MASSEMBLY-802] - Dependencies version conflict leads to run-time exception when creating archive * [MASSEMBLY-824] - Use of appendAssemblyId and finalName can cause problems * [MASSEMBLY-829] - fileMode on a dependencySet with unpack does not work * [MASSEMBLY-834] - Maven assembly plugin fails with Java 9 * [MASSEMBLY-836] - Remove link to non-existing Codehaus wiki ** Improvement * [MASSEMBLY-704] - Remove all goals which are marked deprecated * [MASSEMBLY-770] - List of XSD's on the main site is cluttered. * [MASSEMBLY-790] - Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 * [MASSEMBLY-792] - Expose merge manifest mode from the plexus archiver * [MASSEMBLY-793] - Remove cluttering System.out.println statements * [MASSEMBLY-795] - Upgrade file-management to 3.0.0 * [MASSEMBLY-796] - Upgrade maven-shared-io to 3.0.0 * [MASSEMBLY-797] - Upgrade plexus-archiver from 3.0.1 to 3.0.3 * [MASSEMBLY-801] - Upgrade plexus-archiver from 3.0.3 to 3.1 * [MASSEMBLY-807] - Upgrade maven-plugins to version 30 * [MASSEMBLY-808] - Upgrade of 'plexus-archiver' to version 3.3. * [MASSEMBLY-810] - Upgrade com.google.code.findbugs:jsr305 to 3.0.0 * [MASSEMBLY-813] - Upgrade maven-archiver to 3.1.0 * [MASSEMBLY-814] - Upgrade maven-filtering to 3.1.1 * [MASSEMBLY-817] - Make finalName readonly parameter * [MASSEMBLY-818] - Remove deprecated parameters for the single goal * [MASSEMBLY-819] - Update to release version if Maven Artifact Transfer Component released? * [MASSEMBLY-823] - Documentation refers to deprecated goals ** New Feature * [MASSEMBLY-780] - Snappy supported ** Task * [MASSEMBLY-744] - Use the same namespace pattern for assembly/component format as the rest of Maven * [MASSEMBLY-745] - Give the component format schema file a better name * [MASSEMBLY-794] - Update and revise documentation for 3.0.0 release * [MASSEMBLY-804] - Dependency updates. * [MASSEMBLY-806] - Use new Modello home in MDO files * [MASSEMBLY-816] - Fix problem with building Maven site * [MASSEMBLY-820] - Upgrade of plexus-archiver to 3.4. * [MASSEMBLY-821] - Upgrade of maven-archiver to 3.1.1. * [MASSEMBLY-837] - Revise features page on site Enjoy, -The Apache Maven team
maven-assembly-plugin mysterious error
Hi,
I’m doing some refactoring of some existing projects - mostly we are moving
from SVN to GIT and making a larger project more modular. One piece I’m
working on packages our native code into an assembly to be posted into our
Artifactory so other projects can depend upon those native bits without having
to build them.
So at this point… all I’ve done is taken the existing code and shuffled
directories around, making them shallower, and then fixed up various scripts
and paths to reference the new paths. This all seems to work, however - when I
go to build these assemblies, I receive a NullPointerError referencing the
TarArchiver.cleanup() line 494, and no other aid as to indicate what might be
wrong.
Can anyone provide any insight as to what might be going wrong, how I might
better debug, etc?
The full execution log + error is below my sig.
Thanks,
- JK
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
pom.xml
===
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
xmlns="http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
4.0.0
com.sri
xsb
0.0.8349-SNAPSHOT
pom
${project.basedir}/../../build
maven-assembly-plugin
2.5.3
cocoa-x64.xml
true
make-assembly
package
single
Descriptor for cocoa-x64.xml
==
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd;>
cocoa-x64
tar.bz2
false
${project.properties.artifact.basedir}/trunk.osx/flserver-build/ext/XSB
${file.separator}XSB
Log
===
xsb jklo$ mvn -e -X package
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T08:41:47-08:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds
How to set filesetManifestConfig from maven-assembly-plugin
Hi, is there a way to set the value filesetManifestConfig in src/main/java/org/codehaus/plexus/archiver/jar/JarArchiver.java (plexus-archiver) from the maven-assembly-plugin? It would be great if I could set this value from the maven-assembly plugin to merge or mergewithoutmain. What do you think about enhancing src/main/java/org/apache/maven/archiver/MavenArchiveConfigura tion.java (maven-archiver) with above option? with kind regards thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly plugin: use unpacked existing manifest
Hi, When I unpack a dependency in the assembly plugin can I somehow use the already existing manifest file from this unpacked jar? And I want to change the Main-Class header in this manifest file! Is this possible? The archives plugin seems to always override an already existing manifest file from an unpacked dependency. With kind regards Thomas With kind regards Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Assembly Plugin 2.6 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.6 This plugin builds directories and archives of files, usually for releases. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin You can download the appropriate sources etc. from the download page: http://maven.apache.org/plugins/maven-2.6-plugin/download.cgi Release Notes - Maven Assembly Plugin - Version 2.6 Improvements: MASSEMBLY-780 Snappy supported 06/Oct/15 NOTE: This version requires Java 1.6. Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
So if you have type=jar then dependencies of that artifact are transitive. What I suspect was intended was to introduce a new packaging type (i.e. jarjar) that was added to the classpath but does not pull in dependencies to indicate a jar with its dependencies included... At least that is what my gut tells me might have been the reason... no clue if it actually is the reason however! On 8 September 2015 at 16:29, Timo <mailant...@gmx.de> wrote: > Anyone? If nobody knows what the comment is for, I vote to remove it, > if I may. I'm sure I'm not the only one being confused about it. > > 2015-09-03 12:59 GMT+02:00 Timo <mailant...@gmx.de>: > > Thanks for the insight! I guess we'll have to hope for more info from > > Brett. Since the TODO is obviously over 10 years old, maybe it should > > be removed so as not to confuse users. > > > > Timo > > > > > > 2015-09-02 0:44 GMT+02:00 Wayne Fay <wayne...@gmail.com>: > >> SVN says Brett posted that file (over 10 yrs ago), so maybe he can tell > us more: > >> > >> "Added Mon Apr 18 07:07:58 2005 UTC (10 years, 4 months ago) by brett" > >> > http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.5/src/main/resources/assemblies/jar-with-dependencies.xml?view=log > >> > >> I scanned quickly and found some files in the JarJar project you > >> linked to that date back to Aug 2004, so I suspect that is what he is > >> talking about, but can't really be certain... > >> > >> Wayne > >> > >> On Tue, Sep 1, 2015 at 1:25 PM, Timo <mailant...@gmx.de> wrote: > >>> Hello everyone, > >>> > >>> a question on Stack Overflow made me curious about the following line > >>> in the jar-with-dependencies example descriptor file > >>> ( > http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies > ): > >>> > >>> > >>> > >>> What does this mean? Is it refering to jarjar > >>> (https://code.google.com/p/jarjar/) or to something like what the > >>> Spring Boot Maven plugin does? > >>> > >>> Thanks for any insight! > >>> Timo > >>> > >>> - > >>> 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: What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
Anyone? If nobody knows what the comment is for, I vote to remove it, if I may. I'm sure I'm not the only one being confused about it. 2015-09-03 12:59 GMT+02:00 Timo <mailant...@gmx.de>: > Thanks for the insight! I guess we'll have to hope for more info from > Brett. Since the TODO is obviously over 10 years old, maybe it should > be removed so as not to confuse users. > > Timo > > > 2015-09-02 0:44 GMT+02:00 Wayne Fay <wayne...@gmail.com>: >> SVN says Brett posted that file (over 10 yrs ago), so maybe he can tell us >> more: >> >> "Added Mon Apr 18 07:07:58 2005 UTC (10 years, 4 months ago) by brett" >> http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.5/src/main/resources/assemblies/jar-with-dependencies.xml?view=log >> >> I scanned quickly and found some files in the JarJar project you >> linked to that date back to Aug 2004, so I suspect that is what he is >> talking about, but can't really be certain... >> >> Wayne >> >> On Tue, Sep 1, 2015 at 1:25 PM, Timo <mailant...@gmx.de> wrote: >>> Hello everyone, >>> >>> a question on Stack Overflow made me curious about the following line >>> in the jar-with-dependencies example descriptor file >>> (http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies): >>> >>> >>> >>> What does this mean? Is it refering to jarjar >>> (https://code.google.com/p/jarjar/) or to something like what the >>> Spring Boot Maven plugin does? >>> >>> Thanks for any insight! >>> Timo >>> >>> - >>> 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: What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
Thanks for the insight! I guess we'll have to hope for more info from Brett. Since the TODO is obviously over 10 years old, maybe it should be removed so as not to confuse users. Timo 2015-09-02 0:44 GMT+02:00 Wayne Fay <wayne...@gmail.com>: > SVN says Brett posted that file (over 10 yrs ago), so maybe he can tell us > more: > > "Added Mon Apr 18 07:07:58 2005 UTC (10 years, 4 months ago) by brett" > http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.5/src/main/resources/assemblies/jar-with-dependencies.xml?view=log > > I scanned quickly and found some files in the JarJar project you > linked to that date back to Aug 2004, so I suspect that is what he is > talking about, but can't really be certain... > > Wayne > > On Tue, Sep 1, 2015 at 1:25 PM, Timo <mailant...@gmx.de> wrote: >> Hello everyone, >> >> a question on Stack Overflow made me curious about the following line >> in the jar-with-dependencies example descriptor file >> (http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies): >> >> >> >> What does this mean? Is it refering to jarjar >> (https://code.google.com/p/jarjar/) or to something like what the >> Spring Boot Maven plugin does? >> >> Thanks for any insight! >> Timo >> >> - >> 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
What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
Hello everyone, a question on Stack Overflow made me curious about the following line in the jar-with-dependencies example descriptor file (http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies): What does this mean? Is it refering to jarjar (https://code.google.com/p/jarjar/) or to something like what the Spring Boot Maven plugin does? Thanks for any insight! Timo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
SVN says Brett posted that file (over 10 yrs ago), so maybe he can tell us more: "Added Mon Apr 18 07:07:58 2005 UTC (10 years, 4 months ago) by brett" http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.5/src/main/resources/assemblies/jar-with-dependencies.xml?view=log I scanned quickly and found some files in the JarJar project you linked to that date back to Aug 2004, so I suspect that is what he is talking about, but can't really be certain... Wayne On Tue, Sep 1, 2015 at 1:25 PM, Timo <mailant...@gmx.de> wrote: > Hello everyone, > > a question on Stack Overflow made me curious about the following line > in the jar-with-dependencies example descriptor file > (http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies): > > > > What does this mean? Is it refering to jarjar > (https://code.google.com/p/jarjar/) or to something like what the > Spring Boot Maven plugin does? > > Thanks for any insight! > Timo > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Assembly Plugin 2.5.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.5 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release fixes a serious problem with 2.5.5 when creating jar files, MASSEMBLY-768. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5.5/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5.5 ** Bug * [MASSEMBLY-767] - Schema missing from the web site * [MASSEMBLY-768] - JarInputStream unable to find manifest created by version 2.5.4 * [MASSEMBLY-769] - ZIP fileMode permissions not properly set with dependencySet and unpackOptions Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Cannot compile bundle with maven-assembly-plugin version 2.5.4
Ref
http://stackoverflow.com/questions/30140331/cannot-compile-bundle-with-maven-assembly-plugin-version-2-5-4
I can't compile properly bundle with maven-assembly-plugin version 2.5.4
?xml version=1.0 encoding=UTF-8?
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdBundle_Loader/groupId
artifactIdSystem_Install/artifactId
nameSystem_Install/name
packagingbundle/packaging
version1.0/version
dependencies
dependency
groupIdorg.osgi/groupId
artifactIdorg.osgi.core/artifactId
version5.0.0/version
typejar/type
/dependency
dependency
groupIdorg.apache.felix/groupId
artifactIdorg.apache.felix.framework/artifactId
version5.0.0/version
typejar/type
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
version2.5.4/version
extensionstrue/extensions
configuration
instructions
Import-Package
org.osgi.framework,
javax.xml.bind,
javafx.collections
/Import-Package
Bundle-SymbolicName${project.artifactId}/Bundle-SymbolicName
Bundle-Activatororg.osgi.system.activator.Activator/Bundle-Activator
/instructions
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.6/version
configuration
archive
manifest
addClasspathtrue/addClasspath
classpathPrefixlib//classpathPrefix
mainClassorg.osgi.system.main.Main/mainClass
/manifest
/archive
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version3.3/version
configuration
source1.8/source
target1.8/target
encoding${project.build.sourceEncoding}/encoding
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.5.4/version
configuration
archive
manifest
mainClassorg.osgi.system.main.Main/mainClass
addClasspathtrue/addClasspath
classpathPrefixlib//classpathPrefix
/manifest
/archive
descriptorRefs
descriptorRefjar-with-dependencies/descriptorRef
/descriptorRefs
/configuration
executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.7/version
executions
execution
idcopy-resources01/id
phaseprocess-classes/phase
goals
goalcopy-resources/goal
/goals
configuration
outputDirectory${basedir}/target/classes/outputDirectory
encodingUTF-8/encoding
resources
resource
directory${basedir}/src/directory
includes
include**/*.properties/include
/includes
/resource
/resources
/configuration
/execution
execution
idcopy-resources02/id
phaseverify/phase
goals
[ANN] Apache Maven Assembly Plugin 2.5.4 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5.4/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5.4 ** Bug * [MASSEMBLY-742] - Unclosed ZipFile warnings when ZIP archives are included * [MASSEMBLY-746] - Warnings about platform dependent paths inconsistent. * [MASSEMBLY-747] - StackOverflowError when building assembly * [MASSEMBLY-748] - problem to extract zip files including file names with umlauts * [MASSEMBLY-750] - descriptor in dir format changes symbolic links in non symlink files * [MASSEMBLY-753] - LineEnding CR to LF conversion output is wrong : All EOL are removed * [MASSEMBLY-754] - Non existing folder produces NPE * [MASSEMBLY-755] - missing whitespace in log message ** Improvement * [MASSEMBLY-764] - Upgrade to plexus-archiver 2.10 and io 2.5 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven Assembly Plugin 2.5.4 Released
Am 2015-04-27 um 20:39 schrieb Kristian Rosenvold: The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files. This works by default and requires no further config? How does the logic decide that divide and conquer will gain a speedup? Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven Assembly Plugin 2.5.4 Released
I divides the zip into N streams where N=number of cpu cores. Subsequently files are submitted round-robin to each stream (it's actually fork-join with work-stealing on java7). Each stream is written to memory with an offload to disk if it grows too large. When all streams are done they are merged back into a single well formed zip file. This is totally zero-config and cannot be disabled :) Any users of plexus-archiver can get this feature by simply upgrading to version 2.10 (and plexus-io 2.5). This includes war and jar plugin too. Kristian 2015-04-27 20:45 GMT+02:00 Michael Osipov micha...@apache.org: Am 2015-04-27 um 20:39 schrieb Kristian Rosenvold: The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files. This works by default and requires no further config? How does the logic decide that divide and conquer will gain a speedup? Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [ANN] Apache Maven Assembly Plugin 2.5.4 Released
Is the same change going to be made to the plexus-archiver 3.x branch? Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On Behalf Of Kristian Rosenvold Sent: Monday, April 27, 2015 2:00 PM To: Maven Users List Subject: Re: [ANN] Apache Maven Assembly Plugin 2.5.4 Released I divides the zip into N streams where N=number of cpu cores. Subsequently files are submitted round-robin to each stream (it's actually fork-join with work-stealing on java7). Each stream is written to memory with an offload to disk if it grows too large. When all streams are done they are merged back into a single well formed zip file. This is totally zero-config and cannot be disabled :) Any users of plexus-archiver can get this feature by simply upgrading to version 2.10 (and plexus-io 2.5). This includes war and jar plugin too. Kristian 2015-04-27 20:45 GMT+02:00 Michael Osipov micha...@apache.org: Am 2015-04-27 um 20:39 schrieb Kristian Rosenvold: The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files. This works by default and requires no further config? How does the logic decide that divide and conquer will gain a speedup? Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [ANN] Apache Maven Assembly Plugin 2.5.4 Released
Yep. Real soon. This was the last planned jdk5 release of assembly. Kristian 27. apr. 2015 21.09 skrev cody.a.fy...@wellsfargo.com: Is the same change going to be made to the plexus-archiver 3.x branch? Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On Behalf Of Kristian Rosenvold Sent: Monday, April 27, 2015 2:00 PM To: Maven Users List Subject: Re: [ANN] Apache Maven Assembly Plugin 2.5.4 Released I divides the zip into N streams where N=number of cpu cores. Subsequently files are submitted round-robin to each stream (it's actually fork-join with work-stealing on java7). Each stream is written to memory with an offload to disk if it grows too large. When all streams are done they are merged back into a single well formed zip file. This is totally zero-config and cannot be disabled :) Any users of plexus-archiver can get this feature by simply upgrading to version 2.10 (and plexus-io 2.5). This includes war and jar plugin too. Kristian 2015-04-27 20:45 GMT+02:00 Michael Osipov micha...@apache.org: Am 2015-04-27 um 20:39 schrieb Kristian Rosenvold: The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files. This works by default and requires no further config? How does the logic decide that divide and conquer will gain a speedup? Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
assembly plugin dependencySet not factoring in exclusions in my dependencies.
I have some issues with dependency conflicts in my dependencies section in
my pom.
I need to have a way to compute a directory of .jar files for use with
creating debian packages
I’ve been using the assembly package do this this via:
dependencySets
dependencySet
outputDirectorylib/outputDirectory
useProjectArtifacttrue/useProjectArtifact
scoperuntime/scope
/dependencySet
/dependencySets
… this build a directory of .jar files I can use.
The problem is that one of my dependencies pulled in an optional .jar which
has conflicting dependencies on OLD version of a library we use.
So I have this:
dependency
groupIdorg.apache.activemq/groupId
artifactIdactivemq-leveldb-store/artifactId
version${activemq.version}/version
exclusions
exclusion
groupIdorg.mortbay.jetty/groupId
artifactId*/artifactId
/exclusion
/exclusions
/dependency
… which specifies an inclusion to not fetch this older dependency.
and if I do a dependency:tree it shows that it’s properly excluded.
BUT , once I try to run the assembly, that’s ignored and all the transitive
dependencies are pulled in.
This breaks my class path and my app now breaks because it tries to load
old versions of classes.
Any advice here? Maybe there’s a better way to build the .jar directory
instead of the assembly plugin?
--
Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
https://plus.google.com/102718274791889610666/posts
http://spinn3r.com
Assembly plugin: excluding dependencies
Hi all, I have a pom.xml with assembly descriptor. My problem that assembly is fetching dependencies, which are not defined in pom.xml As a result - huge *.zip file with distribution. I've tried the following example: excludes exclude*spring*:jar:*/exclude /excludes but it does not help - *.jar files remain in *.zip archive. What should I check to find a solution? Thanks in advance! -- View this message in context: http://maven.40175.n5.nabble.com/Assembly-plugin-excluding-dependencies-tp5826295.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: Assembly plugin: excluding dependencies
There is also a useTransitiveDependencies/ tag in assembly descriptor format. And a useTransitiveFiltering with default value to false which I'm not totally sure what it does but could explain why your syntax does'nt work. see http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html On Tue, Feb 10, 2015 at 11:06 AM, Anders Hammar and...@hammar.net wrote: Well, you're probably getting transitive dependencies. Typically they are required as well. Are they not? You could try excluding them in standard Maven way (dependencies/dependency/exclusions). /Anders On Tue, Feb 10, 2015 at 10:59 AM, Zmicer Kashlach dzmitrykashl...@gmail.com wrote: Hi all, I have a pom.xml with assembly descriptor. My problem that assembly is fetching dependencies, which are not defined in pom.xml As a result - huge *.zip file with distribution. I've tried the following example: excludes exclude*spring*:jar:*/exclude /excludes but it does not help - *.jar files remain in *.zip archive. What should I check to find a solution? Thanks in advance! -- View this message in context: http://maven.40175.n5.nabble.com/Assembly-plugin-excluding-dependencies-tp5826295.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 -- Adrien Rivard
Re: Assembly plugin: excluding dependencies
Well, you're probably getting transitive dependencies. Typically they are required as well. Are they not? You could try excluding them in standard Maven way (dependencies/dependency/exclusions). /Anders On Tue, Feb 10, 2015 at 10:59 AM, Zmicer Kashlach dzmitrykashl...@gmail.com wrote: Hi all, I have a pom.xml with assembly descriptor. My problem that assembly is fetching dependencies, which are not defined in pom.xml As a result - huge *.zip file with distribution. I've tried the following example: excludes exclude*spring*:jar:*/exclude /excludes but it does not help - *.jar files remain in *.zip archive. What should I check to find a solution? Thanks in advance! -- View this message in context: http://maven.40175.n5.nabble.com/Assembly-plugin-excluding-dependencies-tp5826295.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: Assembly plugin: excluding dependencies
Thank you! You're right, it was problem with transitive dependencies. Setting scopeprovided/scope solved the issue. -- View this message in context: http://maven.40175.n5.nabble.com/Assembly-plugin-excluding-dependencies-tp5826295p5826308.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
[ANN] Apache Maven Assembly Plugin 2.5.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.3. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. This release is a bugfix release. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5.3/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5.3 ** Bug * [MASSEMBLY-648] - lineEnding in fileSet corrupts jar files * [MASSEMBLY-665] - OS dependent behaviour while packaging * [MASSEMBLY-735] - NullPointerException at org.apache.commons.compress.archivers.zip.FallbackZipEncoding.encode(FallbackZipEncoding.java:80) * [MASSEMBLY-739] - directory permissions are not 755 but 000 in zip * [MASSEMBLY-741] - wrong paths in file-modes tests * [MASSEMBLY-742] - Unclosed ZipFile warnings when ZIP archives are included * [MASSEMBLY-743] - includeBaseDirectory not correct ** Improvement * [MASSEMBLY-720] - Fixed Checkstyle reported errors / warnings * [MASSEMBLY-738] - Upgrade to plexus-archiver from 2.8.4 to 2.9.1 and plexus-io from 2.3.5 to 2.4.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Assembly Plugin 2.5.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.2. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. Most notable for this release are: Rewritten duplicate handling strategy, revised documentation. Please note that previously documented strategy was mostly wishful thinking, the currently documented strategy is hard reality :) See http://maven.apache.org/plugins/maven-assembly-plugin/advanced-descriptor-topics.html http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5.2/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5.2 ** Bug * [MASSEMBLY-478] - allow overwriting newer files with older files contained within fileset * [MASSEMBLY-558] - Assembly does not include runtime-dependency if test-dependency with shorter path exists * [MASSEMBLY-565] - jar-with-dependencies: class from the source in project does NOT override the class in jar dependency * [MASSEMBLY-569] - The numbering of the items in the FAQ on the site is messed up * [MASSEMBLY-580] - dependencySet ignores directoryMode descriptor * [MASSEMBLY-583] - DependencySet elements appear not to be able to target the same outputDirectory * [MASSEMBLY-597] - Duplicate files added to archive when present in both dependencyset and fileset of the same assembly * [MASSEMBLY-601] - http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html seems to have the components of a filter element in the wrong order * [MASSEMBLY-609] - Misbehavior on multi-module projects, outputDirectory not being interpolated properly * [MASSEMBLY-655] - Archive file resolution does not work as documented * [MASSEMBLY-671] - Cryptic debug warning message needs improvement and/or documentation * [MASSEMBLY-725] - Fix phase ordering * [MASSEMBLY-726] - Fix artifact inclusion/exclusion filtering * [MASSEMBLY-728] - Assembly plugin = 2.5 thinks my group ID is too big * [MASSEMBLY-729] - lineEnding ignored when file is not filtered * [MASSEMBLY-730] - jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE * [MASSEMBLY-731] - Assembly plugin bundles symlinks as emtpy folders when directoryMode is set on fileset * [MASSEMBLY-732] - baseDirectory is ignored with files entries * [MASSEMBLY-733] - Plugin no longer prepends final name when packaging files specified using 'files/file' elements. ** Improvement * [MASSEMBLY-702] - Add default values for directoryMode / fileMode * [MASSEMBLY-708] - predefined descriptors lack of permission definition for unix (directoryMode/fileMode) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
assembly plugin
Hi all, I am trying to use the artifact version within the java code of my project, by reading the contents of META-INF/maven/plugin-id/artifact-id/pom.properties file that is generated by the jar plugin. I am creating a package of my project using the assembly plugin with the jar-with-dependencies prefabricated assembly descriptor. I noticed in the generated jar file that all the pom.properties files are correctly included for all my dependencies, but the one corresponding to my project. Is there any special parameter I need to provide to the assembly plugin to include this file? Thanks in advance, Carlos Alegria
[ANN] Apache Maven Assembly Plugin 2.5.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.1. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. http://maven.apache.org/plugins/maven-assembly-plugin/ (Note; there are some problems with clustering/replication on the apache web servers and pressing refresh may sometimes give you an old version of the site) You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5.1/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5.1 ** Bug * [MASSEMBLY-357] - transitive dependencies erroneously excluded from dependencySet in some cases * [MASSEMBLY-395] - Module dependencies not included * [MASSEMBLY-474] - Assembly is duplicating dependecies in the output * [MASSEMBLY-533] - Outputidrectory appended by dependencyset include name on filtered=true * [MASSEMBLY-554] - DependencySet unpackOptions 'filtered' causes unpack not to work * [MASSEMBLY-559] - useTransitiveDependencies leaks from one dependency set to another * [MASSEMBLY-571] - moduleSet dependencies processed incorrectly * [MASSEMBLY-577] - dependencySet inside moduleSet/binaries picks up dependencies of other dependencySets * [MASSEMBLY-579] - Dependency-filename appended as subdirectory of outputDirectory of dependencySet when unpackOptions/filtered = true * [MASSEMBLY-582] - Plugin omits transitive runtime dependencies where artifact is present with test-scope in current project * [MASSEMBLY-619] - Configurations of different dependencySets influence each other * [MASSEMBLY-640] - Artifact data added to path when lineEnding tag set in dependencySet * [MASSEMBLY-672] - unpack adds the name of the artifact in case of filtered unpack * [MASSEMBLY-691] - dependencySet with filtered option has differents behaviors * [MASSEMBLY-701] - class AddDependencySetsTask doesn't re-unpack contents of unpacked SNAPSHOT artifacts * [MASSEMBLY-722] - Assembly with filters fails on Version 2.5 with NoSuchElementException and then IOException (This archives contains unclosed entries) on clean up * [MASSEMBLY-727] - Implied dependencysets have incorrect outputfilemapping Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-assembly-plugin:2.5 ignores lineEnding=unix if file is not filtered
Hi, Have raised JIRA: http://jira.codehaus.org/browse/MASSEMBLY-729 Example project attached to JIRA. Thanks, Tony Jewell Cregganna Computer Consultants Ltd.
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 tony.jew...@cregganna.com: 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
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 kristian.rosenv...@gmail.com 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 tony.jew...@cregganna.com: 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, 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 tony.jew...@cregganna.com: 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 kristian.rosenv...@gmail.com 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 tony.jew...@cregganna.com: 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: [ANN] Apache Maven Assembly Plugin 2.5 Released
AS can be seen from http://jira.codehaus.org/browse/MASSEMBLY-722, this can be fixed for 2.5 by adding the following to your pom (these component updates are available in central): plugin artifactIdmaven-assembly-plugin/artifactId ... dependencies dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId version2.8.2/version /dependency dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-io/artifactId version2.3.3/version /dependency /dependencies /plugin Or alteranately you could give 2.6-SNAPSHOT (will be 2.5.1) a spin. I will await some feedback on this fix before I stage 2.5.1 for relase. Kristian 2014-10-28 22:03 GMT+01:00 Kristian Rosenvold krosenv...@apache.org: Unfortunately filtering into tar/zip is broken (http://jira.codehaus.org/browse/MASSEMBLY-722), and users of filtering/line endings must use a previous version or wait for 2.5.1, which will be released fairly soon. Kristian 2014-10-27 5:50 GMT+01:00 Kristian Rosenvold kristian.rosenv...@zenior.no: The Apache Maven team is pleased to announce the release of the long-awaited Apache Maven Assembly Plugin, version 2.5. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. Notable in this release is improved file attribute support and full symlink support for java7+ users. Users of filtering/line ending selection should also notice a nice performance improvement. A large number of bugs have also been fixed. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5 ** Bug * [MASSEMBLY-75] - Unpacked TAR dependencies do not preserve file mode nor uid/gid * [MASSEMBLY-458] - Directory name resolution ignores $ and beyond * [MASSEMBLY-495] - Assembly changes timestamps when extracting dependency sets * [MASSEMBLY-523] - Filtering causes a loss of original unix file permissions * [MASSEMBLY-543] - japanese filenames cannot be correctly assembled by maven-assembly-plugin * [MASSEMBLY-557] - Corrupted zip created by assembly: extracting the zip forgets certain folders (or throws permission denied errors) possibly because zip index is corrupted * [MASSEMBLY-563] - JAR entry not found when including jar dependencies with # in classname * [MASSEMBLY-576] - addClasspath broken in new single goal * [MASSEMBLY-605] - Filtering does not work on files which are symlinks * [MASSEMBLY-615] - assembly:single fails with odd resource file name * [MASSEMBLY-622] - Unable to create TAR artifacts * [MASSEMBLY-641] - Assembly fails on resource name with a percent character * [MASSEMBLY-661] - Assembly plugin looses permissions when using fileSets * [MASSEMBLY-670] - Specifying lineEnding option of fileSet causes timestamps not to be preserved * [MASSEMBLY-684] - Parallel Execution w Custom Assembly Descriptor Fails * [MASSEMBLY-692] - Assembly ID is global * [MASSEMBLY-709] - When assembling a zip on windows duplicate files are added to the assembly * [MASSEMBLY-721] - Failing ITs for Maven 2.2.1 ** Improvement * [MASSEMBLY-479] - Add option to generate Posix tar files. * [MASSEMBLY-530] - Allow configuration of encoding * [MASSEMBLY-638] - [PATCH] Support tgz and tbz2 formats in assemblies * [MASSEMBLY-673] - Add support for delimiters and useDefaultDelimiters like the maven-resources-plugin 2.4 has * [MASSEMBLY-688] - Use maven-invoker-plugin 1.9 * [MASSEMBLY-705] - Removed compatibility with Maven 2.0.X * [MASSEMBLY-706] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MASSEMBLY-707] - Remove unnecessary excludes / Cleaning up console output * [MASSEMBLY-710] - Fix RAT Report * [MASSEMBLY-712] - Update version of plexus-archiver to 2.5 * [MASSEMBLY-714] - Update version of plexus-archiver to 2.7.1 * [MASSEMBLY-716] - Update plexus-io from 2.0.9 to 2.3.2 * [MASSEMBLY-719] - Ugrade to plexus-interpolation 1.21 ** New Feature * [MASSEMBLY-717] - Add an option to turn off project filters ** Wish * [MASSEMBLY-343] - add symbolic links managment (java7+ only supported) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [ANN] Apache Maven Assembly Plugin 2.5 Released
This fixes the issue for me. Thanks Kristian! Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Kristian Rosenvold [mailto:krosenv...@apache.org] Sent: Wednesday, October 29, 2014 2:21 AM To: Maven Users List Cc: Maven Developers List Subject: Re: [ANN] Apache Maven Assembly Plugin 2.5 Released AS can be seen from http://jira.codehaus.org/browse/MASSEMBLY-722, this can be fixed for 2.5 by adding the following to your pom (these component updates are available in central): plugin artifactIdmaven-assembly-plugin/artifactId ... dependencies dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId version2.8.2/version /dependency dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-io/artifactId version2.3.3/version /dependency /dependencies /plugin Or alteranately you could give 2.6-SNAPSHOT (will be 2.5.1) a spin. I will await some feedback on this fix before I stage 2.5.1 for relase. Kristian 2014-10-28 22:03 GMT+01:00 Kristian Rosenvold krosenv...@apache.org: Unfortunately filtering into tar/zip is broken (http://jira.codehaus.org/browse/MASSEMBLY-722), and users of filtering/line endings must use a previous version or wait for 2.5.1, which will be released fairly soon. Kristian 2014-10-27 5:50 GMT+01:00 Kristian Rosenvold kristian.rosenv...@zenior.no: The Apache Maven team is pleased to announce the release of the long-awaited Apache Maven Assembly Plugin, version 2.5. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. Notable in this release is improved file attribute support and full symlink support for java7+ users. Users of filtering/line ending selection should also notice a nice performance improvement. A large number of bugs have also been fixed. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5 ** Bug * [MASSEMBLY-75] - Unpacked TAR dependencies do not preserve file mode nor uid/gid * [MASSEMBLY-458] - Directory name resolution ignores $ and beyond * [MASSEMBLY-495] - Assembly changes timestamps when extracting dependency sets * [MASSEMBLY-523] - Filtering causes a loss of original unix file permissions * [MASSEMBLY-543] - japanese filenames cannot be correctly assembled by maven-assembly-plugin * [MASSEMBLY-557] - Corrupted zip created by assembly: extracting the zip forgets certain folders (or throws permission denied errors) possibly because zip index is corrupted * [MASSEMBLY-563] - JAR entry not found when including jar dependencies with # in classname * [MASSEMBLY-576] - addClasspath broken in new single goal * [MASSEMBLY-605] - Filtering does not work on files which are symlinks * [MASSEMBLY-615] - assembly:single fails with odd resource file name * [MASSEMBLY-622] - Unable to create TAR artifacts * [MASSEMBLY-641] - Assembly fails on resource name with a percent character * [MASSEMBLY-661] - Assembly plugin looses permissions when using fileSets * [MASSEMBLY-670] - Specifying lineEnding option of fileSet causes timestamps not to be preserved * [MASSEMBLY-684] - Parallel Execution w Custom Assembly Descriptor Fails * [MASSEMBLY-692] - Assembly ID is global * [MASSEMBLY-709] - When assembling a zip on windows duplicate files are added to the assembly * [MASSEMBLY-721] - Failing ITs for Maven 2.2.1 ** Improvement * [MASSEMBLY-479] - Add option to generate Posix tar files. * [MASSEMBLY-530] - Allow configuration of encoding * [MASSEMBLY-638] - [PATCH] Support tgz and tbz2 formats in assemblies * [MASSEMBLY-673] - Add support for delimiters and useDefaultDelimiters like the maven-resources-plugin 2.4 has * [MASSEMBLY-688] - Use maven-invoker-plugin 1.9 * [MASSEMBLY-705] - Removed compatibility with Maven 2.0.X * [MASSEMBLY-706] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MASSEMBLY-707] - Remove unnecessary excludes / Cleaning up console output * [MASSEMBLY-710] - Fix RAT Report * [MASSEMBLY-712] - Update version of plexus-archiver to 2.5 * [MASSEMBLY-714] - Update version of plexus-archiver to 2.7.1 * [MASSEMBLY-716] - Update plexus-io from 2.0.9 to 2.3.2 * [MASSEMBLY-719] - Ugrade to plexus-interpolation 1.21 ** New Feature * [MASSEMBLY-717] - Add an option to turn off project filters ** Wish * [MASSEMBLY-343] - add symbolic links managment (java7+ only supported) Enjoy, -The Apache Maven team
Re: [ANN] Apache Maven Assembly Plugin 2.5 Released
Unfortunately filtering into tar/zip is broken (http://jira.codehaus.org/browse/MASSEMBLY-722), and users of filtering/line endings must use a previous version or wait for 2.5.1, which will be released fairly soon. Kristian 2014-10-27 5:50 GMT+01:00 Kristian Rosenvold kristian.rosenv...@zenior.no: The Apache Maven team is pleased to announce the release of the long-awaited Apache Maven Assembly Plugin, version 2.5. The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. Notable in this release is improved file attribute support and full symlink support for java7+ users. Users of filtering/line ending selection should also notice a nice performance improvement. A large number of bugs have also been fixed. http://maven.apache.org/plugins/maven-assembly-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.5/version /plugin Release Notes - Maven Assembly Plugin - Version 2.5 ** Bug * [MASSEMBLY-75] - Unpacked TAR dependencies do not preserve file mode nor uid/gid * [MASSEMBLY-458] - Directory name resolution ignores $ and beyond * [MASSEMBLY-495] - Assembly changes timestamps when extracting dependency sets * [MASSEMBLY-523] - Filtering causes a loss of original unix file permissions * [MASSEMBLY-543] - japanese filenames cannot be correctly assembled by maven-assembly-plugin * [MASSEMBLY-557] - Corrupted zip created by assembly: extracting the zip forgets certain folders (or throws permission denied errors) possibly because zip index is corrupted * [MASSEMBLY-563] - JAR entry not found when including jar dependencies with # in classname * [MASSEMBLY-576] - addClasspath broken in new single goal * [MASSEMBLY-605] - Filtering does not work on files which are symlinks * [MASSEMBLY-615] - assembly:single fails with odd resource file name * [MASSEMBLY-622] - Unable to create TAR artifacts * [MASSEMBLY-641] - Assembly fails on resource name with a percent character * [MASSEMBLY-661] - Assembly plugin looses permissions when using fileSets * [MASSEMBLY-670] - Specifying lineEnding option of fileSet causes timestamps not to be preserved * [MASSEMBLY-684] - Parallel Execution w Custom Assembly Descriptor Fails * [MASSEMBLY-692] - Assembly ID is global * [MASSEMBLY-709] - When assembling a zip on windows duplicate files are added to the assembly * [MASSEMBLY-721] - Failing ITs for Maven 2.2.1 ** Improvement * [MASSEMBLY-479] - Add option to generate Posix tar files. * [MASSEMBLY-530] - Allow configuration of encoding * [MASSEMBLY-638] - [PATCH] Support tgz and tbz2 formats in assemblies * [MASSEMBLY-673] - Add support for delimiters and useDefaultDelimiters like the maven-resources-plugin 2.4 has * [MASSEMBLY-688] - Use maven-invoker-plugin 1.9 * [MASSEMBLY-705] - Removed compatibility with Maven 2.0.X * [MASSEMBLY-706] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MASSEMBLY-707] - Remove unnecessary excludes / Cleaning up console output * [MASSEMBLY-710] - Fix RAT Report * [MASSEMBLY-712] - Update version of plexus-archiver to 2.5 * [MASSEMBLY-714] - Update version of plexus-archiver to 2.7.1 * [MASSEMBLY-716] - Update plexus-io from 2.0.9 to 2.3.2 * [MASSEMBLY-719] - Ugrade to plexus-interpolation 1.21 ** New Feature * [MASSEMBLY-717] - Add an option to turn off project filters ** Wish * [MASSEMBLY-343] - add symbolic links managment (java7+ only supported) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [ANN] Apache Maven Assembly Plugin 2.5 Released
This version breaks my build. The error I receive is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2. 5:single (flex-flexA-single) on project flexA: Failed to create assembly: Error creating assembly archive flexA: This archives contains unclosed entries. - [He lp 1] My installation details: C:\Users\fylerca\workspace\FlexFrameworkPackaging\branches\R4.14mvn -v Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T15:58:1 0-05:00) Maven home: C:\bin\apache-maven-3.2.3 Java version: 1.8.0_20-ea, vendor: Oracle Corporation Java home: C:\Java\jdk1.8.0_20\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: amd64, family: dos Here is the packaging file that works under previous versions: ?xml version=1.0 encoding=UTF-8? assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1 http://maven.apache.org/xsd/assembly-1.1.1.xsd; idflexA/id formats formatdir/format formattar.gz/format /formats includeBaseDirectoryfalse/includeBaseDirectory dependencySets !-- jars we add to /flexshare/flex(A-Z)/commonLib -- dependencySet excludes excludexpp3:xpp3_min/exclude excludecom.wellsfargo.lendinggrid:MQ/exclude exclude*:pom/exclude /excludes includes includecom.wellsfargo.lendinggrid.framework:CommonLibDependencies:pom/include includejavax.servlet:jstl/include includecom.ibm.as400:jt400/include includeojdbc:ojdbc/include includecom.oracle:ojdbc6/include includecom.teradata.jdbc:tdgssconfig/include includecom.teradata.jdbc:terajdbc4/include includenet.sourceforge.jtds:jtds/include includecom.ibm.db2:db2jcc/include includecom.thoughtworks.xstream:xstream/include /includes outputDirectory/flexshare/flexA/commonLib/outputDirectory useTransitiveFilteringtrue/useTransitiveFiltering /dependencySet !-- jars we add to /flexshare/flex(A-Z)/flexwebLib -- dependencySet excludes excludecom.wellsfargo.lendinggrid.frameworkFlexFrameworkPackaging:pom:*/exclude /excludes includes includeorg.apache.rampart:rampart/include includeorg.apache.rampart:rampart-core/include includeorg.apache.rampart:rampart-policy/include includeorg.apache.rampart:rampart-trust/include includeorg.apache.axis2:addressing:jar/include includeorg.opensaml:opensaml/include includeorg.apache.ws.security:wss4j/include includeorg.apache.santuario:xmlsec/include includeorg.opensaml:xmltooling/include includecom.wellsfargo.pps.core.handlers:PasswordCallback/include includecom.wellsfargo.lending.mortgagepricing:vbjorb/include includecom.wellsfargo.lendinggrid.framework:framework-common/include includecom.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector:com.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector/include includecom.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator:com.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator/include includeorg.apache.axis2:axis2-transport-jms:jar:patch/include includecom.wellsfargo:ExperianATBxmltypes/include includeorg.jdom:jdom2/include /includes outputDirectory/flexshare/flexA/flexwebLib/outputDirectory /dependencySet !-- Flex Framework bundled service archives -- dependencySet includes includecom.wellsfargo.lending.services:HelloWorld/include includecom.wellsfargo.lendinggrid.framework:version/include /includes !--outputDirectory/flexshare/flexA/webapps/flexweb/WEB-INF/services/outputDirectory-- outputDirectory/flexshare/flexA/services/outputDirectory /dependencySet /dependencySets fileSets !-- copy dir structure -- fileSet directorytarget/directory outputDirectory/flexshare/flexA/flexwebLib/outputDirectory excludes exclude**/*/exclude exclude*/exclude /excludes /fileSet fileSet directorytarget/directory outputDirectory/flexshare/flexA/webapps/outputDirectory excludes exclude**/*/exclude exclude*/exclude /excludes lineEndingunix/lineEnding /fileSet fileSet directorytarget/directory outputDirectory/flexshare/flexA/config/outputDirectory excludes exclude**/*/exclude exclude*/exclude /excludes lineEndingunix/lineEnding /fileSet fileSet directoryC:\\Users\\fylerca\\workspace\\FlexFrameworkPackaging\\branches\\R4.14/domainconfig2/src/main/resources/tokenized/context/directory outputDirectory/flexshare/flexA/context/outputDirectory
Re: [ANN] Apache Maven Assembly Plugin 2.5 Released
Do you have the stacktrace for this ? (run with mvn -e) You'll probably need to file an issue for this at http://jira.codehaus.org/browse/MASSEMBLY, preferably with a small sample project enclosed. A stacktrace is probably the most important starting point to find the problem though. Kristian 2014-10-27 15:11 GMT+01:00 cody.a.fy...@wellsfargo.com: This version breaks my build. The error I receive is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2. 5:single (flex-flexA-single) on project flexA: Failed to create assembly: Error creating assembly archive flexA: This archives contains unclosed entries. - [He lp 1] My installation details: C:\Users\fylerca\workspace\FlexFrameworkPackaging\branches\R4.14mvn -v Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T15:58:1 0-05:00) Maven home: C:\bin\apache-maven-3.2.3 Java version: 1.8.0_20-ea, vendor: Oracle Corporation Java home: C:\Java\jdk1.8.0_20\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: amd64, family: dos Here is the packaging file that works under previous versions: ?xml version=1.0 encoding=UTF-8? assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1 http://maven.apache.org/xsd/assembly-1.1.1.xsd; idflexA/id formats formatdir/format formattar.gz/format /formats includeBaseDirectoryfalse/includeBaseDirectory dependencySets !-- jars we add to /flexshare/flex(A-Z)/commonLib -- dependencySet excludes excludexpp3:xpp3_min/exclude excludecom.wellsfargo.lendinggrid:MQ/exclude exclude*:pom/exclude /excludes includes includecom.wellsfargo.lendinggrid.framework:CommonLibDependencies:pom/include includejavax.servlet:jstl/include includecom.ibm.as400:jt400/include includeojdbc:ojdbc/include includecom.oracle:ojdbc6/include includecom.teradata.jdbc:tdgssconfig/include includecom.teradata.jdbc:terajdbc4/include includenet.sourceforge.jtds:jtds/include includecom.ibm.db2:db2jcc/include includecom.thoughtworks.xstream:xstream/include /includes outputDirectory/flexshare/flexA/commonLib/outputDirectory useTransitiveFilteringtrue/useTransitiveFiltering /dependencySet !-- jars we add to /flexshare/flex(A-Z)/flexwebLib -- dependencySet excludes excludecom.wellsfargo.lendinggrid.frameworkFlexFrameworkPackaging:pom:*/exclude /excludes includes includeorg.apache.rampart:rampart/include includeorg.apache.rampart:rampart-core/include includeorg.apache.rampart:rampart-policy/include includeorg.apache.rampart:rampart-trust/include includeorg.apache.axis2:addressing:jar/include includeorg.opensaml:opensaml/include includeorg.apache.ws.security:wss4j/include includeorg.apache.santuario:xmlsec/include includeorg.opensaml:xmltooling/include includecom.wellsfargo.pps.core.handlers:PasswordCallback/include includecom.wellsfargo.lending.mortgagepricing:vbjorb/include includecom.wellsfargo.lendinggrid.framework:framework-common/include includecom.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector:com.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector/include includecom.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator:com.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator/include includeorg.apache.axis2:axis2-transport-jms:jar:patch/include includecom.wellsfargo:ExperianATBxmltypes/include includeorg.jdom:jdom2/include /includes outputDirectory/flexshare/flexA/flexwebLib/outputDirectory /dependencySet !-- Flex Framework bundled service archives -- dependencySet includes includecom.wellsfargo.lending.services:HelloWorld/include includecom.wellsfargo.lendinggrid.framework:version/include /includes !--outputDirectory/flexshare/flexA/webapps/flexweb/WEB-INF/services/outputDirectory-- outputDirectory/flexshare/flexA/services/outputDirectory /dependencySet /dependencySets fileSets !-- copy dir structure -- fileSet directorytarget/directory outputDirectory/flexshare/flexA/flexwebLib/outputDirectory excludes exclude**/*/exclude exclude*/exclude /excludes /fileSet fileSet directorytarget/directory outputDirectory/flexshare/flexA/webapps/outputDirectory excludes exclude**/*/exclude exclude*/exclude /excludes lineEndingunix/lineEnding
Re: [ANN] Apache Maven Assembly Plugin 2.5 Released
Hi, I too got this problem when upgrading to 2.5 on my project. I have raised a JIRA: http://jira.codehaus.org/browse/MASSEMBLY-722 Assembly with filters fails on Version 2.5 with NoSuchElementException and then IOException (This archives contains unclosed entries) on clean up that includes an attached simple project zip with build.log included - result of mvn -X clean install. I tried to track it down but got lost in project dependency issues in the assembly project - there appears to be a lot of dependency overrides around the plexus projects. I'll have another look if I can but am travelling this week. BTW - apologies for creating a duplicate of the JIRA MASSEMBLY-723 by mistake - I have closed it as duplicate. ATB, Tony Jewell On 27 October 2014 17:08, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Do you have the stacktrace for this ? (run with mvn -e) You'll probably need to file an issue for this at http://jira.codehaus.org/browse/MASSEMBLY, preferably with a small sample project enclosed. A stacktrace is probably the most important starting point to find the problem though. Kristian 2014-10-27 15:11 GMT+01:00 cody.a.fy...@wellsfargo.com: This version breaks my build. The error I receive is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2. 5:single (flex-flexA-single) on project flexA: Failed to create assembly: Error creating assembly archive flexA: This archives contains unclosed entries. - [He lp 1] My installation details: C:\Users\fylerca\workspace\FlexFrameworkPackaging\branches\R4.14mvn -v Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T15:58:1 0-05:00) Maven home: C:\bin\apache-maven-3.2.3 Java version: 1.8.0_20-ea, vendor: Oracle Corporation Java home: C:\Java\jdk1.8.0_20\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: amd64, family: dos Here is the packaging file that works under previous versions: ?xml version=1.0 encoding=UTF-8? assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.1 http://maven.apache.org/xsd/assembly-1.1.1.xsd; idflexA/id formats formatdir/format formattar.gz/format /formats includeBaseDirectoryfalse/includeBaseDirectory dependencySets !-- jars we add to /flexshare/flex(A-Z)/commonLib -- dependencySet excludes excludexpp3:xpp3_min/exclude excludecom.wellsfargo.lendinggrid:MQ/exclude exclude*:pom/exclude /excludes includes includecom.wellsfargo.lendinggrid.framework:CommonLibDependencies:pom/include includejavax.servlet:jstl/include includecom.ibm.as400:jt400/include includeojdbc:ojdbc/include includecom.oracle:ojdbc6/include includecom.teradata.jdbc:tdgssconfig/include includecom.teradata.jdbc:terajdbc4/include includenet.sourceforge.jtds:jtds/include includecom.ibm.db2:db2jcc/include includecom.thoughtworks.xstream:xstream/include /includes outputDirectory/flexshare/flexA/commonLib/outputDirectory useTransitiveFilteringtrue/useTransitiveFiltering /dependencySet !-- jars we add to /flexshare/flex(A-Z)/flexwebLib -- dependencySet excludes excludecom.wellsfargo.lendinggrid.frameworkFlexFrameworkPackaging:pom:*/exclude /excludes includes includeorg.apache.rampart:rampart/include includeorg.apache.rampart:rampart-core/include includeorg.apache.rampart:rampart-policy/include includeorg.apache.rampart:rampart-trust/include includeorg.apache.axis2:addressing:jar/include includeorg.opensaml:opensaml/include includeorg.apache.ws.security:wss4j/include includeorg.apache.santuario:xmlsec/include includeorg.opensaml:xmltooling/include includecom.wellsfargo.pps.core.handlers:PasswordCallback/include includecom.wellsfargo.lending.mortgagepricing:vbjorb/include includecom.wellsfargo.lendinggrid.framework:framework-common/include includecom.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector:com.wellsfargo.service.provider.hcfg.creditrisk.riskenginedirector/include includecom.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator:com.wellsfargo.service.provider.hcfg.creditRisk.decisionCoordinator/include includeorg.apache.axis2:axis2-transport-jms:jar:patch/include includecom.wellsfargo:ExperianATBxmltypes/include includeorg.jdom:jdom2/include /includes outputDirectory/flexshare/flexA/flexwebLib/outputDirectory /dependencySet !-- Flex Framework bundled service
