Hi,
To prevent any problems, I have now split up the build into two builds
(api-build and full-jar). I think I will introduce now a third project
(with pom packaging) that will build up all modules and collect the
artifacts that are needed. I hope that is a correct strategy to solve the
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
Ok,
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
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
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?
Jan
Mit freundlichen Grüßen / Best regards
Jan Engler
Central Research Development
SICK AG
Erwin-Sick-Str. 1
79183
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
Well I guess, I will eventually whip up such a plugin myself, cause I really
need to cleanup quite a code-generation mess.
Eventually based upon the GraniteDS libs, as does the Flexmojos plugin.
Chris
-Ursprüngliche Nachricht-
Von: bmat...@gmail.com [mailto:bmat...@gmail.com] Im
Chef or puppet?
On Friday, 1 March 2013, Eric Kolotyluk wrote:
A while back we had some interesting discussions on using Maven, or
maven-like technology for deploying production software. I was wondering if
anything new has been happening since then.
Basically what I am hoping to see is a
On 01/03/2013 4:26 PM, Eric Kolotyluk wrote:
A while back we had some interesting discussions on using Maven, or
maven-like technology for deploying production software. I was wondering if
anything new has been happening since then.
Basically what I am hoping to see is a generic installer
Thanks for the pointers Stephen,...
http://wiki.opscode.com/display/chef/Chef+Basics
https://puppetlabs.com/puppet/what-is-puppet/
Ron,...
Yes, I remember that deployment was outside the scope of Maven, but one
of the things I like about Maven is the repository concept. I was
advocating
My feeling is that this would be a major addition to Maven and would
still be missing a lot of stuff.
It looks more like a CMS with some rules and some processes that
construct a zip or an installer.
You need a lot of flexibility in defining how assets are assembled into
the required artifact.
I was not thinking of adding to Maven, rather I was soliciting insight
from the Maven community because I value their inventiveness.
I am half way toying with the idea of building something myself, but
first I want to make sure I am not reinventing the wheel.
I have been toying with the idea
I was not thinking of adding to Maven, rather I was soliciting insight
from the Maven community because I value their inventiveness.
I am half way toying with the idea of building something myself, but
first I want to make sure I am not reinventing the wheel.
Sounds like you have some good
Literally *just* stumbled across Bintray: https://bintray.com/beta
Best,
Laird
On Fri, Mar 1, 2013 at 9:33 PM, Wayne Fay wayne...@gmail.com wrote:
I was not thinking of adding to Maven, rather I was soliciting insight
from the Maven community because I value their inventiveness.
I am
19 matches
Mail list logo
