[
https://issues.apache.org/jira/browse/HCATALOG-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475198#comment-13475198
]
Travis Crawford commented on HCATALOG-528:
------------------------------------------
Hey Raji - this looks like a useful option to put in place. I just looked at
the ant docs and when reading properties files variable expansion is supported.
Instead of putting this in
[ivysettings.xml|https://svn.apache.org/repos/asf/incubator/hcatalog/trunk/ivy/ivysettings.xml],
what do you think about moving the property definition to
[build.properties|https://svn.apache.org/repos/asf/incubator/hcatalog/trunk/build.properties]?
The reason for requesting this is that we've been working towards consolidating
the different knobs one can turn into a single place, so its easier for users
to see what's configurable. For example, if it were already setup this way you
could just {{ant -Dmvn.local.repo=/my/path}} and it would just work. You would
have known where to look for this option because they're all specified in the
same place. Of course, we don't have all knobs defined in build.properties yet
but I'm hoping we can put new ones there.
>From http://ant.apache.org/manual/Tasks/property.html we see:
{code}
In-file property expansion is very cool. Learn to use it.
Example:
build.compiler=jikes
deploy.server=lucky
deploy.port=8080
deploy.url=http://${deploy.server}:${deploy.port}/
{code}
> ivysettings.xml does not let you override .m2/repository
> --------------------------------------------------------
>
> Key: HCATALOG-528
> URL: https://issues.apache.org/jira/browse/HCATALOG-528
> Project: HCatalog
> Issue Type: Bug
> Components: build
> Affects Versions: 0.4
> Reporter: Raja Aluri
> Assignee: Raja Aluri
> Fix For: 0.4.1
>
> Attachments: HCATALOG-528.branch-0.4.patch, HCATALOG-528.trunk.patch
>
>
> ivysettings.xml does not let you override .m2/repository. This will be useful
> for people who wants to use a localrepository, thats outside of
> ~/.m2/repository
--
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
