[
https://issues.apache.org/jira/browse/SLIDER-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335299#comment-14335299
]
Billie Rinaldi commented on SLIDER-791:
---------------------------------------
Yes, I see that hbase for example is using hbase-${pkg.version} in its
appConfig and metainfo; this is a mistake, because it must always be
hbase-${hbase.version}, so if you ever set pkg.version to something other than
hbase.version, there will be an error. The pkg.version is an arbitrary label
-- we can set it to whatever we want, but it can't be used internally in the
app packages except in the zip's name.
> Minimize the multiple different versions that appear in app-packages
> --------------------------------------------------------------------
>
> Key: SLIDER-791
> URL: https://issues.apache.org/jira/browse/SLIDER-791
> Project: Slider
> Issue Type: Bug
> Components: app-package
> Affects Versions: Slider 0.61
> Reporter: Gour Saha
>
> Currently the app-package file names and the references of package tarballs
> in metainfo are associated with multiple different version related properties
> -
> - pkg.version
> - project.version
> - accumulo.version/hbase.version/storm.version
> This causes a lot of confusion and inconsistency of the actual tarball
> filename and its reference in metainfo and also the final app package file
> name (property app.package.name).
> This needs to be cleaned up and simplified. Versions should be dropped from
> wherever it makes sense. No of version properties should be minimized
> wherever possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
