Thanks, I guess it really could work either way.
I've normally used to having some type of automated build which
eventually gets released as you move it forward (ie: v2.0.1.xyz, the xyz
build of 2.0.1 is what ships), but what you are saying is just get
things tested/integrated/refined by way of the snapshot artifacts from
CI and then perform the release what that is all good.
I still need to read-up on the standard way of doing maven releases.
Haven't gotten that far yet..
-jr
Todd Thiessen wrote:
CI I believe would use SNAPSHOTS. CI and SNAPSHOTs are a great match. It
would be somewhat more complicated to use releases. And you would deploy
to your maven repository so anyone else could then download to their
local.
---
Todd Thiessen
-----Original Message-----
From: James Russo [mailto:[email protected]]
Sent: Thursday, September 10, 2009 4:20 PM
To: Maven Users List
Subject: question re: CI builds and maven.
Hello,
This is likely more of a software engineering related
maven question. With the concept of snapshots and versioned
artifacts where would a continuous build system come into
place? How do others use it? I guess you really have two
options, the CI system can produce snapshots or it can
produce version'd releases. I would imagine that you would
want to have the CI server publish these artifacts back to
your local internal repository..
So, how do others use continuous integration servers like
hudson in their maven environment?
thanks!
-jr
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
