, 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
Hmmm, I don't understand this. I will have an more or less empty jar in my
nexus then, which is useless and there for no reason? For what reason does
that file exists then?
Most like you are missing a configuration of the shade plugin:
shadedArtifactAttached boolean - Defines whether the
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
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 filtern in the
shade plugin).
Is there a (conceivable) Maven build that uses api.jar as a dependency?
Then it must be the
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 filtern in the
shade plugin).
Is there a (conceivable) Maven build that uses
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 filtern in the
shade plugin).
Is there a
14 matches
Mail list logo
