Great, thanks Rex.
Mark
On 13 September 2010 18:45, Rex Hoffman wrote:
> Hey Mark,
>
> A little later than I promised but here it is:
>
> http://jira.codehaus.org/browse/MENFORCER-107
>
> Rex
>
>
> On Wed, Sep 8, 2010 at 1:16 PM, Mark Hobson wrote:
>> Great, no real rush thanks, I just wondered
Hey Mark,
A little later than I promised but here it is:
http://jira.codehaus.org/browse/MENFORCER-107
Rex
On Wed, Sep 8, 2010 at 1:16 PM, Mark Hobson wrote:
> Great, no real rush thanks, I just wondered if anything was happening.
> If you could post the issues to this thread when they're ra
Great, no real rush thanks, I just wondered if anything was happening.
If you could post the issues to this thread when they're raised then
I'll track it from there.
Thanks and happy time off!
Mark
On 8 September 2010 18:41, Rex Hoffman wrote:
> I haven't opened it yet as I still have to separ
I haven't opened it yet as I still have to separate out functionality,
and write up some info for the site report. Already have the
integration test done.
I just quit my job and have two weeks off until I start my next, last
day, yay! So really good news for you!
I expect to have this split out
Were any issues raised to track the progress of these new rules? I'm
particularly interested in this one:
> 2) Maven should have the option of forcing developers to ensure
> dependencies converge rather than relying on the "closest to the top"
> rule it uses by default. In large projects this ca
On Thu, Aug 26, 2010 at 12:39 PM, Rex Hoffman wrote:
> Baptiste:
>
> I work in a large organization, where there are differing degrees of
> familiarity with maven.
> Most devs shy away from the release plugin for several reasons. One
> is the use of hudson and nexus.
>
I actually wrote those rul
Baptiste:
I work in a large organization, where there are differing degrees of
familiarity with maven.
Most devs shy away from the release plugin for several reasons. One
is the use of hudson and nexus.
Developers are not allowed to cut releases on their machines. Simply
checking in updated ver
2010/8/25 Rex Hoffman
> So I felt there are few gaps in the maven release process (and
> enforcing a project or a reactor project is releasable).
>
> Perceived gaps:
>
> 1) Maven should fail a build if it is building a release version
> number and any of it's dependencies (including transitive de
Yes, these are useful rules, although we have some that sound the
same, but maybe there's a subtle difference?
http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
http://maven.apache.org/enforcer/enforcer-rules/requireReleaseVersion.html
On Wed, Aug 25, 2010 at 6:26 PM, Rex Ho
Just want to make sure before I do this that there is desire for these
kinds of enforcer rules in the community.
Don't want to engage in the extra effort if others dont feel the need
for rules like these.
Wont be hard to split the functionality, will just result in a shared
library or (some) duplic
IMHO, if you can separate the rules by function and file enhancement JIRAs
with the appropriate patches attached to each, that would probably be the
best way
-Stephen
On 25 August 2010 20:00, Rex Hoffman wrote:
> So I felt there are few gaps in the maven release process (and
> enforcing a proje
11 matches
Mail list logo
