My own preference is to have the person who is going to provide the
personal guarantee to the rest of the team that module B is ready for
release to do the release.
This may take a few minutes but the peace of mind that it gives me is
worth that few minutes.
If Maven does the release, who is responsible? The person doing the
release on A might have no knowledge of the state of B.
We have over 70 modules that are required to build our LMS portal and we
manually release even with a very small team.
We have made the decision that not all modules in a project will have
the same release number. It is possible to release 1.19 of the portal
with a dependency of 1.10 on the messaging utilities if they have not
changed.
The system is very modular and uses web services and a bit of an SOA so
that releases tend to affect a subset of the modules available.
The core is always affected since that contains the database access.
Once the system reached a reasonable level of functionality, very few
releases affect more than half of the projects.
We have a simple spreadsheet that is used to document the plan of which
versions will be used of each module that makes up each application release.
Once we start developing a release, we discuss any change in this plan
so that we all know why we had an unexpected change to a module.
Ron
On 26/09/2011 8:08 AM, Abid Hussain wrote:
It's simply to save time. Let's say you have a project containing of several
components. Instead of releasing every component separate, you perform the
release only for the main component and in a transitive way maven performs
automatically releases of all dependent SNAPSHOT components. Naturally this
process includes compiling and running tests.
But maybe it is better to use a multi module project (in which SNAPSHOT
dependencies between submodules are resolved by maven) for this kind of project
structure.
Regards,
Abid
-------- Original-Nachricht --------
Datum: Fri, 23 Sep 2011 12:23:21 -0400
Von: Ron Wheeler<[email protected]>
An: Maven Users List<[email protected]>
Betreff: Re: release transitive SNAPSHOT dependency
I hope not!
Sounds like a really bad thing to do.
How does maven know that B is release quality?
Ron
On 23/09/2011 11:58 AM, Abid Hussain wrote:
Hello,
e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to
another non-released project B (e.g. 2.3-SNAPSHOT).
AFAIK performing a release which has SNAPSHOT versions is not possible.
Is there a way to tell maven that when a release of project A should be
performed to automatically
- perform a release of B (e.g. 2.3)
- update the dependency from A to B (so that A is dependent to B 2.3)
- and then actually perform the release of A (resulting in A 1.0)?
Regards,
Abid
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
