The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.6.0
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some
of the dependencies.
https
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.5.3
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some
of the dependencies.
https
t Shade find that one.
> --
> Alexander Kriegisch
> https://scrum-master.de
>
>
> Toshiya Kobayashi schrieb am 28.03.2024 06:22 (GMT +01:00):
>
> > Hello,
> >
> > I use maven-shade-plugin to create an uber jar and its source jar with
> > .
aggregate
sources JAR and then let Shade find that one.
--
Alexander Kriegisch
https://scrum-master.de
Toshiya Kobayashi schrieb am 28.03.2024 06:22 (GMT +01:00):
> Hello,
>
> I use maven-shade-plugin to create an uber jar and its source jar with
> .
>
> https://github.com/t
Hello,
I use maven-shade-plugin to create an uber jar and its source jar with
.
https://github.com/tkobayas/shade-test/blob/main/pom.xml
```
org.apache.maven.plugins
maven-shade-plugin
3.5.2
source-jar
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.5.2
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some
of the dependencies.
https
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 3.5.1
https://maven.apache.org/plugins/maven-shade-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-shade-plugin
3.5.1
You can
The Apache Maven team is pleased to announce the release of the
Maven Shade Plugin 3.5.0
https://maven.apache.org/plugins/maven-shade-plugin/
Release Notes - Maven Shade Plugin - Version 3.5.0
** Bug
* [MSHADE-443] - Fix problems with shadeSourcesContent
** New Feature
* [MSHADE-400
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin Version 3.4.1
https://maven.apache.org/plugins/maven-shade-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-shade-plugin
3.4.1
You
implements MavenResourcesFiltering
and so you do not need the plugin plexus-component-metadata
HTH
Olivier
[1]
https://github.com/apache/maven-shade-plugin/tree/master/src/main/java/org/apache/maven/plugins/shade/resource
[2]
https://maven.apache.org/plugins/maven-resources-plugin/examples/custom-resource-filters.ht
Hi everyone,
I have another question about maven-shade-plugin. I'm wondering if there is an
equivalent of ServicesResourceTransformer that can be used on resource files
that appear outside META-INF/services dir.
My use case involves avro-compiler.jar. It has Velocity templates that are used
Thanks Delany. That was exactly what I was looking for.
On Sunday 4 September 2022 at 18:44:18 IST, Delany
wrote:
hi PJ. You can do like this:
true
org.apache.avro:avro
Kind regards,
Delany
On Sun, 4 Sept 2022 at 19:05, PJ Fanning
wrote:
> Hi everyone,
> Apologies
hi PJ. You can do like this:
true
org.apache.avro:avro
Kind regards,
Delany
On Sun, 4 Sept 2022 at 19:05, PJ Fanning
wrote:
> Hi everyone,
> Apologies if this has been answered before but I searched around and
> couldn't find an answer.
> For Apache Hadoop, I'm looking to shade
Hi everyone,
Apologies if this has been answered before but I searched around and couldn't
find an answer.
For Apache Hadoop, I'm looking to shade Apache Avro jar, relocating the avro
classes to a new package name.
This new jar would be published to Maven Central and used by Hadoop.
The aim is
On Sun, Jun 26, 2022 at 9:49 AM Alexander Kriegisch <
alexan...@kriegisch.name> wrote:
>
> Firstly, you are not crerating a test JAR but a regular JAR with
> application classes, so of course test-scoped dependencies like JUnit
> are not going to be contained in the uber JAR.
>
Oh, right.
> I get a build success, but when I inspect the generated jar, I don’t
> see the junit classes
Firstly, you are not crerating a test JAR but a regular JAR with
application classes, so of course test-scoped dependencies like JUnit
are not going to be contained in the uber JAR.
Secondly, you are
I am trying to use maven-shade-plugin for the first time to create an uber-jar
and I can’t even get the simplest example to work.
For example, I created a simple pom based on the example at the top of this
page:
https://maven.apache.org/plugins/maven-shade-plugin/examples/includes
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 3.3.0
https://maven.apache.org/plugins/maven-shade-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-shade-plugin
3.3.0
You can
This isn't actually what we do. The ASF release is NOT a Git tag, but the
source release ZIP file. Please retain the tag as-is.
> Gesendet: Freitag, 27. August 2021 um 10:02 Uhr
> Von: "Robert Scholte"
> An: "Maven Users List"
> Betreff: Re: New release of Maven
Aan: users@maven.apache.org
Verzonden: 27-8-2021 09:40:47
Onderwerp: Re: New release of Maven Shade Plugin
Hi
Sorry for digging up this old mail thread.
I'm also interesseted in a new maven-shade-plugin.
I noticed the 3.3.0 git tag
(https://github.com/apache/maven-shade-plugin/releases/tag/maven-shade-pl
Hi
Sorry for digging up this old mail thread.
I'm also interesseted in a new maven-shade-plugin.
I noticed the 3.3.0 git tag
(https://github.com/apache/maven-shade-plugin/releases/tag/maven-shade-plugin-3.3.0),
but this version doesn't seems to be published on maven central
(https
merge https://github.com/apache/maven-shade-plugin/pull/104 as-is. then
> you do not have to wait for me to finish the self-shading feature, which
> IMO is out of scope for MSHADE-366 anyway.
I created MSHADE-400 on top of it and PR
https://github.com/apache/maven-shade-plugin/pull/110, whi
MSHADE-366: Romain and I are still talking and working on a possible
basic implementation of self-shading. (I have started hacking around,
but it is not easy.) But in order to get rid of the warning, you could
merge https://github.com/apache/maven-shade-plugin/pull/104 as-is. then
you do not have
Can we cut a new release of m-shade-p?
Is there any pending bug fix or improvement that you want to include in the
release?
Cheers
Tibor
[4]. Start
> simple and step by step, then increase the level of difficulty. Don't
> try to use 7 options at one, see what each of them does.
>
> [1] https://stackoverflow.com/help/mcve
> [2] https://maven.apache.org/plugins/maven-shade-plugin/
> [3]
> https://maven.apache.org/
at one, see what each of them does.
[1] https://stackoverflow.com/help/mcve
[2] https://maven.apache.org/plugins/maven-shade-plugin/
[3]
https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html
[4]
https://maven.apache.org/plugins/maven-shade-plugin/examples/class
I have a single module Maven build where one of the dependences has well
over 200 transitive dependencies. These transitive dependencies are
incompatible with the rest of my application.
I would like to use the maven-shade-plugin to create a shaded jar uber jar
that contains all
Dear list members,
I am having a problem with deploying jar files created by the
maven-shade-plugin. It used to work, but it has stopped working. From my
research the problem seems to be that the install step is overwriting the
shaded jar.
Please cc me when replying, because I haven't
The Maven team is pleased to announce the release of the Apache Maven Shade
Plugin, version 3.2.4
This plugin repackages the project classes together with their dependencies
into a single uber-jar, optionally renaming classes or removing unused classes.
https://maven.apache.org/plugins/maven
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.2.3
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
https
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.2.2
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
https
n has one. You can set it in the XML configuration, but
> there's also a user property for it. As a result, your dev-local profile
> could look like this:
>
>
> dev-local
>
> true
>
>
>
> But you could even skip the profile completely and invoke Maven
look like this:
dev-local
true
But you could even skip the profile completely and invoke Maven with
-Dspring-boot.repackage.skip=true.
The Maven Shade Plugin [3] has no such property documented, so that
could be a reason for using the Spring Boot Maven Plugin over
I am cross-posting from stackoverflow
<https://stackoverflow.com/questions/59393863/skipping-maven-shade-plugin-in-a-spring-boot-project-based-on-maven-profile>
as I did not get any reply there.
I want to skip the execution of maven-shade-plugin when a certain maven
profile is act
Hi,
My default JAVA_HOME points to java 1.6 and I am trying use
maven-shade-plugin version 3.2.1 which requires java 1.7+
So I looking for a way to configure my maven-shade-plugin to execute using
required java version and not my default JAVA_HOME version.
E.g. I had similar issue with maven
dependency set of the shaded module as seen from within the multi-module
project.
However, I think it might be best for Maven to (re-)allow the set of
dependencies listed to reduce after build due to plugins like
maven-shade-plugin. While needing to shade in general is not ideal,
needing to build
Hi Nikki,
Regarding your question, I'm not sure of what is a "reactor of reactor"...
by 2 separate "projects" I mean 2 different build. Hence 2 different
"reactor".
As I understand it, the reactor is the sum of all Maven modules
participating in the build. Usually in the case of a multi-modules
work-around ?
Would that satisfy the separate-projects rule ?
Or no ?
Thanks,
Nick
From: Francois MAROT
Sent: Sunday, March 17, 2019 10:38 PM
To: users@maven.apache.org
Subject: Re: Usage of dependency-reduced-pom.xml from maven-shade-plugin in a
multi-module
Hello Kyle,
to my knowledge your analysis is good, you are correct.
Sorry but I did not take the time to read your pom excerpt but I have been
using the shade plugin for quite some time now and concluded that shaded
artifacts must be leafs in the Maven modules tree. By "leaf" I mean no
artifact
ers@maven.apache.org
Subject: Usage of dependency-reduced-pom.xml from maven-shade-plugin in a
multi-module/reactor project
I am having a dependency conflict issue in a project I am working on.
Specifically, a dependency of a dependency of a dependency depends on Jersey
1.9 for internal client
Jersey 1.9 is basically being used invisibly and behind
the scenes inside of my dependency, I am attempting to use
maven-shade-plugin to include the dependency and Jersey 1.9 and relocate
Jersey to another package while I use Jersey 2.28 up front in its
original package.
maven-shade-plugin creates
nks for your reply! So it sounds like since
> maven-shade-plugin still has not been updated to use the new API, the
> problem should still be there. But did you check my test project? I thought
> it would capture the problem, if it was still there and I understood it
> correctly, but I gu
Hi Hervé, and thanks for your reply! So it sounds like since
maven-shade-plugin still has not been updated to use the new API, the
problem should still be there. But did you check my test project? I thought
it would capture the problem, if it was still there and I understood it
correctly, but I
-plugin/pull/30
I just had a look at maven-shade-plugin source and found "project.setFile(
dependencyReducedPomLocation );": this call has not been replaced by
setPomFile() API.
That means that the limitation on the chosen directory should still be here
Hope this helps...
Regards,
what you want. This is considered an open
issue with this plugin."
https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation
I created a small test project which performs a shade in the package
phase (with the dependencyReducedPomLo
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 3.2.1
Repackages the project classes together with their dependencies into a
single uber-jar, optionally renaming classes or removing unused classes.
https://maven.apache.org/plugins/maven-shade
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 3.2.0
https://maven.apache.org/plugins/maven-shade-plugin/
Important Note since 3.2.0:
* Maven 3.X only
* If you like to use minimizeJar you have to use JDK8+
otherwise you can keep running
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 3.1.1
https://maven.apache.org/plugins/maven-shade-plugin/
Important Note since 3.1.1:
* Maven 3.X only
You should specify the version in your project's plugin configuration
Hi all,
Has anyone tried using the MojoHaus flatten plugin in conjunction with
Maven shade plugin? The trick is to get the flatten plugin to flatten
the DRP after shading, instead of the original pom.
My goal is for the uber-jar to include a standalone POM that does not
reference any parent
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 3.1.0
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies.
https
Hi,
Quick help - This is the first time i am using the shade plugin. I saw the
shading documentation here - but could not figure out which transformer
should I use -
https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html
My requirement is this - I am using
Hi,
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 3.0.0
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of
some of the dependencies.
https
gom...@hotmail.com>
wrote:
Hi there,
I’m having some trouble while working with maven-shade-plugin, profiles
and classifiers.
I need my classified jar to be an input to the shade plugin. Currently
only the main artifact is an input.
If i change the execution id of maven-jar-plugin to “d
Hi there,
I’m having some trouble while working with maven-shade-plugin, profiles and
classifiers.
I need my classified jar to be an input to the shade plugin. Currently only the
main artifact is an input.
If i change the execution id of maven-jar-plugin to “default-jar”, the
following error
http://blog.artifact-software.com/tech/?p=121 and other Maven posts
might give you some ideas about handling large numbers of third party
jars in a large project.
We use Eclipse/STS and Maven.
Ron
On 30/06/2016 11:10 AM, Eddie Galvez wrote:
What is the way to use the maven-shade-plugin
Hi!
I think nothing should depend on shaded names. Everything should use
original names, which is then fixed by the shade plugin during packaging.
Regards,
Aliaksei
On Thu, Jun 30, 2016 at 5:10 PM, Eddie Galvez <egal...@tibco.com> wrote:
> What is the way to use the maven-sha
What is the way to use the maven-shade-plugin but, what I think is the
obvious usage then of such a shaded project, to have it in eclipse as a
source project?
In other words - because maven-shade-plugin only does its thing on
package... while you are in Eclipse (your IDE), other projects
Hi,
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 2.4.3
The release contains 4 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
https://maven.apache.org
Hi,
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 2.4.3
The release contains 4 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
https://maven.apache.org
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 2.4.2.
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
https
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 2.4.1
http://maven.apache.org/plugins/maven-shade-plugin/
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename
Hi,
just simply use
finalNameclient-api-all/finalName
..
Kind regards
Karl Heinz Marbaise
On 7/13/15 1:02 AM, Zheng, Kai wrote:
Hi experts,
With the following, it generates a uber-jar, but the generated jar file name
isn't expected, being client-api-all.jar.pom. Note the content is correct,
[mailto:khmarba...@gmx.de]
Sent: Monday, July 13, 2015 2:04 PM
To: Maven Users List
Subject: Re: Maven shade plugin generates uber-jar but in a file name like *.pom
Hi,
just simply use
finalNameclient-api-all/finalName
..
Kind regards
Karl Heinz Marbaise
On 7/13/15 1:02 AM, Zheng, Kai wrote:
Hi experts
Hi experts,
With the following, it generates a uber-jar, but the generated jar file name
isn't expected, being client-api-all.jar.pom. Note the content is correct,
containing classes files, not any POM stuff.
Would anyone help? Thanks a lot.
plugin
/maven-shade-plugin/
Release Notes - Apache Maven Shade - Version 2.4
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921version=12331393
Bugs:
* [MSHADE-155] - dependency-reduced-pom should use shadedArtifactId
* [MSHADE-169] - Typos in warning message
* [MSHADE-172
What am I supposed to do with dependency-reduced-pom.xml? Add it to
revision control or ignore it?
Not entirely clear why I need it, but it's added by default so assume it's
important.
Also, the documentation for it is incorrect. The file is by default written
to the base dir and not the same
On 14 January 2015 at 10:12, James Green james.mk.gr...@gmail.com wrote:
What am I supposed to do with dependency-reduced-pom.xml? Add it to
revision control or ignore it?
I say ignore it.
For technical reasons a dependency reduced pom needs to land in the same
directory as the pom it is
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 2.3.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies.
http
.nabble.com/Maven-shade-plugin-Class-Overlap-tp5787056p5787741.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
the place to start.
For fine-grained control of which classes from the selected
dependencies are included, artifact filters can be used:
https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html
Wayne
://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html
Wayne
Well, I can find out which are and aren't but they change every release, and
there will be many eventually. Which the filter using include/excludes would
be unmanageable when it gets as large as I imagine
Well, I can find out which are and aren't but they change every release, and
there will be many eventually. Which the filter using include/excludes would
be unmanageable when it gets as large as I imagine it will be
Try this experiment for me.
Make 3 jar file with content as follows:
1.jar
overlaying. I want to know if it's possible to either chose the order the
jars are added or to tell it to skip any classes that overlap.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-shade-plugin-Class-Overlap-tp5787056.html
Sent from the Maven - Users mailing list
I'm trying to use maven shade to overlay all of my changes to a jar on top of
another in a manner similar to a jar overlay. However there are some classes
that overlap in my source files with the jar I wish to overlap. After I
build, the ones that overlap are replaced by what is in the jar's
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 2.2
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies.
http
For now, as a work around, I wrote a shell script that after the shading
process rewrites the timestamps of clojure files to sometime in the past. I
am using maven-exec-plugin to run that shell script.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-shade-plugin
.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-shade-plugin-Retaining-origin-file-timestamps-tp5773664p5773855.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe
We could remove clj files from the jar altogether. However, the problem is we
don't know if all the clojure dependencies are AOT compiled. So, some of the
clojure files should be compiled on the fly. The problem is when dynamically
compiling clojure files whose class files already exist in the
Hello,
I am currently using maven shade plugin to package a project jar that would
contain some java libraries as well as some clojure libraries. After some
investigation into load time performance issue, I found that maven shade
plugin default behaviour is to re-write or create the files, which
compile it on the fly. For example, if a.clj and a corresponding a.class is
present with equal timestamps then clojure would think that a.clj is newer
and would compile it. This is causing all the clojure files to be compiled
again and thus causing jar load time to increase.
Perhaps just
Hi all,
I would like to know if this behavior is normal while using the
maven-shade-plugin.
Take this sample pom as input:
project
modelVersion4.0.0/modelVersion
groupIdsample/groupId
artifactIdshade-effect/artifactId
packagingjar
Am 2013-08-30 17:47, schrieb David Gay:
[...]
Why are all the transitive dependencies of the test artifacts being excluded
It surprise me a lot (and made some of my jobs fails in specific situations,
for example when using Sonar, but that's another story/problem)
Please suffer with me:
Hello,
The org.apache.maven.plugins.shade.resource.AppendingTransformer in the
maven shade plugin (v 2.0) only supports exact resource name matches for
appending resources for the uber jar. Do you guys see any problems if this
this supports patterns that might be able to do it for a bunch
Hello,
The org.apache.maven.plugins.shade.resource.AppendingTransformer in the
maven shade plugin (v 2.0) only supports exact resource name matches for
appending resources for the uber jar. Do you guys see any problems if this
this supports patterns that might be able to do it for a bunch
The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 2.1
Repackages the project classes together with their dependencies into a
single uber-jar, optionally
renaming classes or removing unused classes.
http://maven.apache.org/plugins/maven-shade-plugin/
You should
, Germany
Phone +49 7681 202-3214
mailto:jan.eng...@sick.de
http://www.sick.com
Von:Jörg Schaible joerg.schai...@scalaris.com
An: users@maven.apache.org
Datum: 01.03.2013 08:27
Betreff:Re: Antwort: Re: Maven Shade Plugin
Hi Tim,
Tim Kettler wrote:
Am 28.02.2013 19:47, schrieb
Am 01.03.2013 08:26, schrieb Jörg Schaible:
Hi Tim,
Tim Kettler wrote:
Am 28.02.2013 19:47, schrieb Joachim Durchholz:
Am 28.02.2013 16:24, schrieb Jan Engler:
At first: in fact this is only one artifact. The full jar contains all
classes of the dependecies, the api a reduced set (using
An: Maven Users List users@maven.apache.org
Datum: 01.03.2013 09:49
Betreff:Re: Antwort: Re: Maven Shade Plugin
Am 01.03.2013 08:26, schrieb Jörg Schaible:
Hi Tim,
Tim Kettler wrote:
Am 28.02.2013 19:47, schrieb Joachim Durchholz:
Am 28.02.2013 16:24, schrieb Jan Engler:
At first
Am 01.03.2013 07:17, schrieb Tim Kettler:
That's not correct. The classifier is part of the artifact coordinates
just like group, artifact(name) and version.
I knew. I just didn't want to contradict Stephen right away. Plus,
classifiers are usually assumed to identify auxiliary artifacts for
working with a split-up build project seems to work. The only problem that
I face in the moment is that there is not only my 2 shaded jars (api and
api-sources) but also a file called original-api.jar. The content of
this jar is only the meta-inf folder and I don't want this file to be
placed
Waldkirch, Germany
Phone +49 7681 202-3214
mailto:jan.eng...@sick.de
http://www.sick.com
Von:Wayne Fay wayne...@gmail.com
An: Maven Users List users@maven.apache.org
Datum: 01.03.2013 14:00
Betreff:Re: Re: Antwort: Re: Maven Shade Plugin
working with a split-up build project
On 1 March 2013 12:08, Joachim Durchholz j...@durchholz.org wrote:
Am 01.03.2013 07:17, schrieb Tim Kettler:
That's not correct. The classifier is part of the artifact coordinates
just like group, artifact(name) and version.
I knew. I just didn't want to contradict Stephen right away.
Am 01.03.2013 14:59, schrieb Stephen Connolly:
On 1 March 2013 12:08, Joachim Durchholz j...@durchholz.org wrote:
Am 01.03.2013 07:17, schrieb Tim Kettler:
That's not correct. The classifier is part of the artifact coordinates
just like group, artifact(name) and version.
I knew. I just
On 1 March 2013 15:03, Joachim Durchholz j...@durchholz.org wrote:
Am 01.03.2013 14:59, schrieb Stephen Connolly:
On 1 March 2013 12:08, Joachim Durchholz j...@durchholz.org wrote:
Am 01.03.2013 07:17, schrieb Tim Kettler:
That's not correct. The classifier is part of the artifact
the shaded artifact
should be attached as classifier to the original artifact. If false,
the shaded jar will be the main artifact of the project
http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#shadedArtifactAttached
Wayne
Joachim Durchholz j...@durchholz.org wrote on 03/01/2013 07:08:52 AM:
The complete coordinates of an artifact are GAVTC: group,
artifact(name), version, type (default is jar), classifier (default is
empty).
Hm. Can I specify the type in a dependency as well?
Just curious, I certainly
Hi everybody,
Currently I am trying to build up an assembly for our project. I needed a
filtered output so I came to the shade plugin.
This is what I am doing:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-shade-plugin/artifactId
version2.0/version
There is a golden principle of maven, one artifact per module...
You seem to be trying to get 4 artifacts out of 1 module... Not on the
maven way are you!
On Thursday, 28 February 2013, Jan Engler wrote:
Hi everybody,
Currently I am trying to build up an assembly for our project. I needed a
Am 28.02.2013 14:50, schrieb Jan Engler:
As you might have seen, I want to have 4 artifacts: api.jar,
api-sources.jar, full.jar, full-sources.jar.
Which of these are supposed to be used as dependencies in other projects?
Each project can supply exactly 1 artifact for dependent Maven builds.
...@durchholz.org
An: users@maven.apache.org
Datum: 28.02.2013 15:38
Betreff:Re: Maven Shade Plugin
Am 28.02.2013 14:50, schrieb Jan Engler:
As you might have seen, I want to have 4 artifacts: api.jar,
api-sources.jar, full.jar, full-sources.jar.
Which of these are supposed to be used
1 - 100 of 169 matches
Mail list logo
