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
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
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,
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
contain
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
cont
, 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,
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&
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
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&#x
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
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 p
es
> 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?
> > >
> > > Wit
y 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
ng
> 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-plugi
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
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
ady 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
>
gards,
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 de
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
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 ->
fa
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
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
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
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
> 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 t
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
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/
o 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/e
Maven (core), we use a
> dedicated assembly descriptor instead of the generic one [1]
>
thank you very much
very clear
Enrico
> HTH
>
> Hervé
>
> [1]
> https://github.com/apache/maven/blob/master/apache-maven/src/assembly/maven/component.xml
>
> Le lundi 14 j
if you need to have consistent executable flags, you need to avoid getting it
from filesystem, because it is dependent on OS and user configuration
that's why for example, on such requirements in Maven (core), we use a
dedicated assembly descriptor instead of the generic one [1]
HTH
Herv
Hello,
It looks like following this guide in order to create a good "source
bundle" for an ASF Project (in this case Apache Pulsar) leads to a
strange behaviour.
https://maven.apache.org/apache-resource-bundles/
Basically some files miss the 'executable' flag, this way when the
user unpacks the re
> With all due respect, this is horrible. It is not just a scripted build
I respectfully shared a pragmatic and to paraphrase myself "easily made
into a windows- specific powershell or cmd file" approach after having
written off shade and assembly plugins. whatever your personal vi
perfect.
Still hoping for a more generic way to produce a DRP also for other
plugins such as Assembly. But we are making progress. :)
--
Alexander Kriegisch
https://scrum-master.de
Alexander Kriegisch schrieb am 25.04.2021 15:29 (GMT +07:00):
> Last time I checked, Maven Shade did *not* att
ments. You can later chain it
> into assembly plugin to produce an archive that contains your launch
> scripts, dependencies, configurations, and perhaps even the JDK itself. If
> youre against having launchscripts, you can write classpath into manifest
> via archive plugin.
>
> I do
With all due respect, this is horrible. It is not just a scripted build
and like Ant through the back door, but also shell- and
platform-specific (unless you happen to have Git Bash or so installe on
Windows).
Furthermore, it does not even relate to my question.
--
Alexander Kriegisch
https://sc
For executable JARs I do this as well.
Sometimes for simpler projects, I'll add:
true
lib/
to the JAR plugin. I use the assembly plugin to place everything in its
proper place.
That way I can just ship a tar.gz or zip file with all of the bits.
Unzip /
I second this approach. It's much more simple, maintainble and you retain
the ability to monkeypatch production deployments. You can later chain it
into assembly plugin to produce an archive that contains your launch
scripts, dependencies, configurations, and perhaps even the JDK itself. If
there's nothing that really painlessly replaced the first
maven fatjar since it became outmoded.
that said, i use dependency plugin to dump a lib/ dir even for reactor
builds, and then a shell script that uses that classpath syntax to load a
directory at a time.
this happens with maven exec anywa
Last time I checked, Maven Shade did *not* attach the dependency-reduced
POM, but that was a while ago and the project I am contributing to uses
Maven Assembly. I am certainly going to try again later today or
tomorrow when I back at my desk and have access to my computer. I shall
report back here
obably quite common:
>>
>> ** I build an uber JAR containing some module dependencies, possibly
>> also transitive ones. This could be done using Maven Shade or Maven
>> Assembly, maybe even something with nested JARs like One-JAR.
>> ** The built ub
e case which IMO is probably quite common:
>
> ** I build an uber JAR containing some module dependencies, possibly
> also transitive ones. This could be done using Maven Shade or Maven
> Assembly, maybe even something with nested JARs like One-JAR.
> ** The built uber JAR repla
be obious
> to others, but for a long time I have wondered why I do not find any
> examples for the following use case which IMO is probably quite common:
>
> ** I build an uber JAR containing some module dependencies, possibly
> also transitive ones. This could be done using
transitive ones. This could be done using Maven Shade or Maven
Assembly, maybe even something with nested JARs like One-JAR.
** The built uber JAR replaces the module's original artifact when
installed and/or deployed.
** By default, the original POM gets attached to the build. Th
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.
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/XML
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
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 'ar
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 gener
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
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
t;get-infos
>
> copy-dependencies
>
>compile
>
> com.acme
> yaml
> info
>
> ${project.build.directory}/infos
>
>
>
>
>
>
-assembly-plugin
3.3.0
build-infos
single
prepare-package
assemblies/infos-yaml.xml
...
and for the assembly:
http://maven.apache.org/ASSEMBLY
I've added further notes into issue
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-940
along with a reference to a sandpit project which shows the issue more clearly
(and quickly!)
-
To unsubscribe, e-mail
ross the entire
assembly. This would look like a bug to me?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
I took a debug log earlier -- as I found my overall assembly was taking 10
minutes to build
For that last example which has a handful of dependencies, what I actually see
the assembly plugin reporting is:
17:11:33,629 [DEBUG] Dependencies for project:
org.odpi.egeria:open-metadata
On 2020/07/17 15:33:26, Nigel Jones wrote:
> I have a large multimodule project (https://github.com/odpi/egeria) which has
> over 300 modules, mostly java (->jar).
Here's the full assembly definition (with the first attempt at including
dependencies) ->
https://gist.gi
I have a large multimodule project (https://github.com/odpi/egeria) which has
over 300 modules, mostly java (->jar).
One of our submodules is responsible for creating the composite assembly.
Previously we were doing it 'the wrong way' (IMO) with lots of relative paths
(../../..
s 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 er
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
gt; no, you can't, and this is for a reason: in the repository, every attached
> > sub-artifact is expected to have the same artifactId, then have a filename
> > starting with the artifactId. This is key to our convention, sorry.
> >
> > Looking at Zookeeper distribution
hanging the artifactid
> no, you can't, and this is for a reason: in the repository, every attached
> sub-artifact is expected to have the same artifactId, then have a filename
> starting with the artifactId. This is key to our convention, sorry.
>
> Looking at Zookeeper distrib
eason: in the repository, every attached
sub-artifact is expected to have the same artifactId, then have a filename
starting with the artifactId. This is key to our convention, sorry.
Looking at Zookeeper distribution [1], what about renaming zookeeper-assembly
module to apache-zookeeper and publish
MNG-5001 [1]), then you'll get soon the expected failure
>
> Either you should rename parent artifact to zookeeper, then you'll have to
> rename the current zookeeper to zookeeper-server for example.
> Either you're stuck with your specific assembly.
>
> In Maven
zookeeper-server for example.
Either you're stuck with your specific assembly.
In Maven itself, we have 2 cases:
- Maven core, that has a specific assembly in apache-maven module where source-
release is published [2] with a specific src+bin and zip+tar.gz output
- every other multi-module pr
Self answer, I have cloned the execution but I have reused the common
assembly descriptor. It is a trade off but it works
https://github.com/apache/zookeeper/commit/9053f7c431bb17ed79c2be129b6ba4ba18d15ab1
Enrico
Il giorno ven 17 gen 2020 alle ore 08:50 Enrico Olivelli <
eolive...@gmail.com&
Hi,
In Apache ZooKeeper community we want to switch to using the "source
package" generated by the apache parent pom with the execution of
"source-release-assembly".
https://github.com/apache/maven-apache-parent/blob/master/pom.xml#L381
What is the *best* way to achieve
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
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 wi
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
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
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
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
So I have hibernate-core 3.6.10.Final and it depends on jta1.1
and the assembly picks up jta1.1 correctly but the MANIFEST.MF file constructs
a class path with jta1.0.1b
Is it unreasonable to expect that the classpath in MANIFEST.MF be inline with
what assembles that package the zip see?
ie
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 directo
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 t
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
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,
The Apache Maven team is pleased to announce the release of the
Apache Maven EJB Plugin Version 3.0.1
This plugin generates J2EE Enterprise Javabean (EJB) file as well as the
associated client jar.
https://maven.apache.org/plugins/maven-ejb-plugin/
Important Note since 3.0.1:
* Maven 3.X onl
he 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
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
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.
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
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 Plugi
, December 15, 2017 at 12:27 PM
To: Maven Users List
Subject: Re: Maven Assembly Plugin renaming jar
From the small snippet of log, it's bit confusing, because it looks like the
artifact you are assembling is named the same as the dependency you are pulling
in. Because you have this setting in the
>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-a
> Reply-To: Maven Users List
> Date: Friday, November 24, 2017 at 11:12 AM
> To: "users@maven.apache.org"
> Subject: Re: Maven Assembly Plugin renaming jar
>
> Oh, I should mention that I've tried this with maven-assembly-plugin 2.4
> and 3.1.0.
>
&
Sorry to bump and old thread, but I’d appreciate it if someone had any insight.
Sam
From: Sam Wilson
Reply-To: Maven Users List
Date: Friday, November 24, 2017 at 11:12 AM
To: "users@maven.apache.org"
Subject: Re: Maven Assembly Plugin renaming jar
Oh, I should mention that I
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
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
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
The Apache Maven team is pleased to announce the release of the
Apache Maven EJB Plugin Version 3.0.0
This plugin generates J2EE Enterprise Javabean (EJB) file as well as the
associated client jar.
https://maven.apache.org/plugins/maven-ejb-plugin/
Important Note since 3.0.0:
* Maven 3.X onl
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
Hi Curtis,
Why not stick with the old version of maven-assembly-plugin until you have
> to refactor your build more thoroughly?
>
I thought to that, but it collides another (philosophical) concept: to use
always the last version of plugins ! ^^
More seriously and to explain, the "
Hi Alix,
Why not stick with the old version of maven-assembly-plugin until you have
to refactor your build more thoroughly?
Regards,
Curtis
--
Curtis Rueden
LOCI software architect - https://loci.wisc.edu/software
ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
On Tue, Mar 14
Alix Lourme :
> Hi Karl Heinz,
>
> Thanks for your answer (and sorry for mine late).
>
> the best thing to create a separate module in your build with packaging
>> pom and only put the maven-assembly-plugin in it and bind it to the life
>> cycle
>> This is
Hi Karl Heinz,
Thanks for your answer (and sorry for mine late).
the best thing to create a separate module in your build with packaging pom
> and only put the maven-assembly-plugin in it and bind it to the life cycle
> This is simply a good way of following single responsibility pri
Hi,
If you like to produce a package (zip/tar/whatever kind of
archive/bundle) which contains some modules/artifacts etc. from your
multi module build it is the best thing to create a separate module in
your build with packaging pom and only put the maven-assembly-plugin in
it and bind it to
Hello,
Since maven-assembly-plugin v3.3.0, the *attached* goal has been removed (
MASSEMBLY-704 <https://issues.apache.org/jira/browse/MASSEMBLY-704>).
This *attached* goal was an aggregator (v2.6 source
<https://svn.apache.org/repos/asf/maven/plugins/tags/maven-assembly-plugin-2.6/src/
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
ckage 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
T
1 - 100 of 2777 matches
Mail list logo
