I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead of N
places, where N is the avg # of reverse
On Mon, Feb 28, 2011 at 9:49 AM, Phillip Hellewell ssh...@gmail.com wrote:
The problem I see with using a snapshot for the parent is it doesn't
allow you to make changes in a safe way. I could update the version #
of a lower component, and then a much higher component could build
against that
Our move to aggregation jars was our solution of this problem.
We wanted central control over versions without a lot places to manage
version numbers.
For each application release, we decide what third versions of third
party libraries will be used.
If any of the libraries need changing we
Our move to aggregation jars was our solution of this problem.
We wanted central control over versions without a lot places to manage
version numbers.
For each application release, we decide what third versions of third
party libraries will be used.
If any of the libraries need changing we
Interesting ideas, thanks. By aggregation jars I assume you mean
like intermediate components with no actual code but that serve to
manage versions. I think that is a neat idea.
Phillip
On Mon, Feb 28, 2011 at 10:23 AM, Ron Wheeler
rwhee...@artifact-software.com wrote:
Our move to aggregation
On 28/02/2011 2:39 PM, Phillip Hellewell wrote:
Interesting ideas, thanks. By aggregation jars I assume you mean
like intermediate components with no actual code but that serve to
manage versions. I think that is a neat idea.
As much I Iove being associated with a neat idea, I have to point
Hi Phillip,
Phillip Hellewell wrote:
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead of N
