On Wed, Oct 20, 2010 at 8:12 AM, Michael McCallum
mich...@redengine.co.nz wrote:
You could try something like...
mvn -s special-settings-file.xml verify install
haha. Hudson has a horrible bug involving -s that the maintainers keep
claiming to fix and failing to fix. Perhaps some day.
set
On 18 October 2010 23:15, Zac Thompson z...@zac.ca wrote:
On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I just set up a big fat aggrigator for each of the test everything
together projects that I want to run CI over. I use svn:externals to
check
If you are using 'downstream', how do you avoid the need to publish to
at least a common local repo?
I've been facing the following variation on this:
I do not want to publish snapshots to nexus, since they mess up people
who download stale ones into their development process.
I do want to
because downstream is the trigger, the build checks everything out and
uses an uber-aggregator build so that all the artifacts will be in the
reactor which is how mvn verify can work (no need for clean because
I do a clean checkout for every build)
On 19 October 2010 12:25, Benson Margulies
On Tue, Oct 19, 2010 at 7:28 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
because downstream is the trigger, the build checks everything out and
uses an uber-aggregator build so that all the artifacts will be in the
reactor which is how mvn verify can work (no need for clean
On 19 October 2010 12:42, Benson Margulies bimargul...@gmail.com wrote:
On Tue, Oct 19, 2010 at 7:28 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
because downstream is the trigger, the build checks everything out and
uses an uber-aggregator build so that all the artifacts will
Attached is a sample of how I configure the builders (using
update-properties as my inter-module deps are via properties for this
uber-integration-project) the principle remains the same
On 19 October 2010 12:50, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 19 October 2010 12:42,
Attached is a sample of how I configure the builders (using
update-properties as my inter-module deps are via properties for this
uber-integration-project) the principle remains the same
Either you failed to attach anything, or it got stripped.
Wayne
stripped
On 19 October 2010 16:50, Wayne Fay wayne...@gmail.com wrote:
Attached is a sample of how I configure the builders (using
update-properties as my inter-module deps are via properties for this
uber-integration-project) the principle remains the same
Either you failed to attach
On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I just set up a big fat aggrigator for each of the test everything
together projects that I want to run CI over. I use svn:externals to
check everything out and then two maven builders, first to update the
Hello,
following situation:
I have like 20 projects which are libs of different level. They are
all built as jars. They are partially dependent on each other (not
circularly).
For example project A provides very basic utils. Project B is more
specialized and depends on A. Project C depends on A,
On 15 October 2010 07:28, Leon Rosenberg rosenberg.l...@gmail.com wrote:
Hello,
following situation:
I have like 20 projects which are libs of different level. They are
all built as jars. They are partially dependent on each other (not
circularly).
For example project A provides very basic
On Fri, Oct 15, 2010 at 10:31 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 15 October 2010 07:28, Leon Rosenberg rosenberg.l...@gmail.com wrote:
Hello,
following situation:
I have like 20 projects which are libs of different level. They are
all built as jars. They are
On 15 October 2010 12:57, Leon Rosenberg rosenberg.l...@gmail.com wrote:
On Fri, Oct 15, 2010 at 10:31 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 15 October 2010 07:28, Leon Rosenberg rosenberg.l...@gmail.com wrote:
Hello,
following situation:
I have like 20 projects
14 matches
Mail list logo
