[jira] Commented: (MNG-4492) Integration test MNG1830 fails with GIT based forks

["Kristian Rosenvold (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202424#action_202424 ] 

Kristian Rosenvold commented on MNG-4492:
-----------------------------------------

This patch is not good, will be back shortly with reworked version

> Integration test MNG1830 fails with GIT based forks
> ---------------------------------------------------
>
>                 Key: MNG-4492
>                 URL: http://jira.codehaus.org/browse/MNG-4492
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: IT Failures
>    Affects Versions: 3.0-alpha-5
>         Environment: linux
>            Reporter: Kristian Rosenvold
>         Attachments: mng1830GitCheck.patch, mng1830GitVersionNumber.patch
>
>
> Git is rapidly becoming the tool of choice for working with forks/patches of svn projects. MavenITmng1830ShowVersionTest fails if no svn repo is present.
> The enclosed patches need to be applied in maven3 trunk (mng1830GitVersionNumber.patch), and adds a profile that activates a different buildnumber plugin setting 
> when no ".svn" folder is present.
> I have made no attempts at being overly clever with the version number, which is basically "rGIT; <date>".
> The second patch is for MavenITmng1830ShowVersionTest to accept this format in addition to the two others. 
> Since this fix is mostly in the test, there is no additional testcase.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira