accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-1521) If poms need to be sorted, they just get sorted
Date Tue, 18 Jun 2013 18:34:19 GMT


John Vines resolved ACCUMULO-1521.

    Resolution: Won't Fix

It just seems strange to me. I'm making modifications of both pom and code, and I wanted to
do a test build. And it failed because I didn't sort it first. So I just sorted it and did
the operation again. I just can't imagine a case where a developer will make changes, attempt
to package, and NOT follow it up with just doing the sorting.

But I guess it is the better way to go. Having the build fail when it happens will notify
the perpetrator that they messed up. Otherwise you could have a perpetually bad pom in svn.
There is the option of having jenkins using a different profile to provide the different feedback,
but it's not worth the effort IMO.
> If poms need to be sorted, they just get sorted
> -----------------------------------------------
>                 Key: ACCUMULO-1521
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>            Reporter: John Vines
>             Fix For: 1.6.0
> If the pom is not sorted and you run mvn clean package, it will immediately fail stating
the poms aren't sorted. Rather than making me run mvn clean -Psort, it should just always
run the sort profile.
> Or sorted poms should not be required to package

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message