Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual upload
procedure with some version number (nice if it relates to the version
that the authors gave them) and reference them as dependencies.
That's 13 jars to be built from their sources,
On 24/01/2013 3:34 AM, Joachim Durchholz wrote:
Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual upload
procedure with some version number (nice if it relates to the version
that the authors gave them) and reference them as dependencies.
On Thursday, 24 January 2013, Joachim Durchholz wrote:
Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual upload
procedure with some version number (nice if it relates to the version
that the authors gave them) and reference them as
Am 24.01.2013 16:35, schrieb Stephen Connolly:
What you want to do is create a series of shim projects for each of these
external libs,
If you mean a just-pass-it-through-unchanged-already project with shim
project, then yes that's what I want to do.
and then just have your CI server roll
Am 24.01.2013 15:00, schrieb Ron Wheeler:
On 24/01/2013 3:34 AM, Joachim Durchholz wrote:
Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual upload
procedure with some version number (nice if it relates to the version
that the authors gave
On 24/01/2013 11:54 AM, Joachim Durchholz wrote:
Am 24.01.2013 15:00, schrieb Ron Wheeler:
On 24/01/2013 3:34 AM, Joachim Durchholz wrote:
Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual upload
procedure with some version number (nice
Am 24.01.2013 18:53, schrieb Ron Wheeler:
On 24/01/2013 11:54 AM, Joachim Durchholz wrote:
Am 24.01.2013 15:00, schrieb Ron Wheeler:
On 24/01/2013 3:34 AM, Joachim Durchholz wrote:
Am 24.01.2013 05:39, schrieb Ron Wheeler:
You manually put the jars in your Maven repo through its manual
Seems a pity not to just set it up right at the start and then your life
with maven would be harmonious.
What I suggested is a way to use maven in a way that everyone here could
help you and your builds would be very simple.
Stephen seems to be giving you a solution that fits with what you
Am 24.01.2013 19:53, schrieb Ron Wheeler:
Seems a pity not to just set it up right at the start and then your
life with maven would be harmonious. What I suggested is a way to
use maven in a way that everyone here could help you and your builds
would be very simple.
Sorry, I must have been
If you are either replacing the (empty) jar with your real jar in the
package phase of your 13 projects without source,
And with the disclaimer that we don't like this way and prefer the MRM +
simple shell script to do the mvn deploy:deploy-file, but understand your
needs, you should be ok
Note
Am 24.01.2013 21:23, schrieb Stephen Connolly:
If you are either replacing the (empty) jar with your real jar in the
package phase of your 13 projects without source,
Ah, good to know. I had intended to put that into an earlier phase, but
of course the compiler will recreate the jar.
Hi all,
I have a bunch of projects that need to extract files from an SVN
repository as part of their build process.
I need to make sure that all of them use the same SVN revision. It's
initially determined as whatever the current HEAD is, but since HEAD
might change anytime, I need a way to
Hi
I am going on a hunch here what your are trying to do, in my opinion
this is poorly supported by maven currently (I however guess you could
use the maven-release-plugin and create a tag but I am not entirely sure
that this is something that maven should solve ?) in my experience it's
Am 23.01.2013 13:44, schrieb Manfred Nilsson:
Hi
I am going on a hunch here what your are trying to do, in my opinion
this is poorly supported by maven currently (I however guess you could
use the maven-release-plugin and create a tag
Creating an SVN tag?
No, that's not the point at all. I
You are probably over-automating things at this point.
I would suggest getting your maven builds running, go through a full
release cycle and then look for ways to improve.
A good thing to remember is:
Thousands of products have been built with Maven; it is unlikely that
you want to do
Am 23.01.2013 21:08, schrieb Ron Wheeler:
You are probably over-automating things at this point.
I would suggest getting your maven builds running, go through a full
release cycle and then look for ways to improve.
A good thing to remember is:
Thousands of products have been built with Maven;
On 23/01/2013 4:48 PM, Toolforger wrote:
Am 23.01.2013 21:08, schrieb Ron Wheeler:
You are probably over-automating things at this point.
I would suggest getting your maven builds running, go through a full
release cycle and then look for ways to improve.
A good thing to remember is:
Thousands
17 matches
Mail list logo
