[
http://jira.codehaus.org/browse/MNG-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3371:
------------------------------
Fix Version/s: 2.0.x
seems like a matter of using getCanonical* more consistently
> Use Consistent Path Case for $basedir
> -------------------------------------
>
> Key: MNG-3371
> URL: http://jira.codehaus.org/browse/MNG-3371
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.0.8
> Reporter: Geoffrey Wiseman
> Fix For: 2.0.x
>
>
> We're using the Maven liquibase plugin, and we're using a project-local path
> to define the changelog's filename (e.g.
> ${basedir}/some/path/to/filename.xml).
> We're doing so in a multiproject build, and when we run the subproject build,
> basedir is defined as "c:/dev/work/...". In the multiproject build, it's
> defined as "C:/dev/work/...". This results in two paths that are, in
> Windows, not case sensitive. Liquibase, which supports operating systems
> that are case sensitive, uses a case-sensitive comparison to determine if the
> changelogs are the same and accordingly decides that they aren't the same
> (although they do, in fact, in this case, refer to the same file).
> While I'm sure there are ways to improve this within the liquibase codebase,
> it'd also be nice if Maven used a consistent case for paths such that this
> problem wouldn't exist.
> See also:
> http://www.nabble.com/Maven-Plugin-and-Multi-Project-Build-to15001965.html
--
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
