accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1521) If poms need to be sorted, they just get sorted
Date Tue, 18 Jun 2013 17:42:20 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687001#comment-13687001
] 

John Vines commented on ACCUMULO-1521:
--------------------------------------

The cleanup will not create a backup file if it's already sorted, so the issue of it creating
a backup file in the tarball is moot since things will be compiled before committing anyway.
If things are being edited in the pom for the release, then there's something wrong with the
release process.

I can see the check being part of the release process, but using them for just doing a build
seems excessive.
                
> If poms need to be sorted, they just get sorted
> -----------------------------------------------
>
>                 Key: ACCUMULO-1521
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1521
>             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: http://www.atlassian.com/software/jira

Mime
View raw message