On 18-Jul-08, at 10:30 AM, Ralph Goers wrote:
Jason van Zyl wrote:
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you
do there is no need to rewrite anything it just works...
My builds never use versi
Jason van Zyl wrote:
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you do
there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceab
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you
do there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceable at any time in th
Thursday, July 17, 2008 10:02 AM
>> To: Maven Developers List
>> Subject: Re: How do I go about contributing a plugin to mojo?
>>
>> Anyway, my question is how do I go about contributing this?
>>
>> On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly
>> <[EM
Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you do
there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceable at any time in the future. Version ranges d
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you do there is
no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceable at any time in the future. Version ranges don't guarantee
that.
; -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 17, 2008 10:02 AM
> To: Maven Developers List
> Subject: Re: How do I go about contributing a plugin to mojo?
>
> Anyway, my question is how do I go about contributing this?
>
You would attach it to a jira at the mojo.codehaus.org project and then
try to get some mojo committer to pick it up.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2008 10:02 AM
To: Maven Developers List
Subject: Re: How do I go about
Anyway, my question is how do I go about contributing this?
On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly
<[EMAIL PROTECTED]> wrote:
> one use case for this is when you have a suite of components and you
> want to force _all_ of them to the same version.
>
> Perhaps you have several suites of
one use case for this is when you have a suite of components and you
want to force _all_ of them to the same version.
Perhaps you have several suites of components and you want to force
all the components in each suite to the same versions across the
suite.
On Thu, Jul 17, 2008 at 2:56 PM, Stephe
And then when you want to roll a release?
Anyway, if that was the case why is it that most of the maven plugins
themselves use this pattern?
e.g. ${maven.version}
Also you may want to force all one set of components to the same suite
release... so blah-core may be only available at 1.3.5 while
b
why not just specify the dependencies with version ranges, if you do there is
no need to rewrite anything it just works...
On Fri, 18 Jul 2008 00:35:17 Stephen Connolly wrote:
>
> Oh... and if you want to prevent jumping too high in versions or too
> low, it supports adding a version specificatio
Oh and -Dproperties=blah.version,foo.version will only do the update
check for ${blah.version} and ${foo.version}
On Thu, Jul 17, 2008 at 1:35 PM, Stephen Connolly
<[EMAIL PROTECTED]> wrote:
> I have developed a plugin that makes keeping versions of related but
> not quite tightly coupled in sync
I have developed a plugin that makes keeping versions of related but
not quite tightly coupled in sync a lot easier.
How do I go about contributing this to mojo?
-Stephen
FYI here's how it works...
In your pom you probably have a property used to define the version in
one place, for example:
14 matches
Mail list logo
