[
https://issues.apache.org/jira/browse/SLIDER-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221044#comment-14221044
]
Steve Loughran commented on SLIDER-627:
---------------------------------------
cause is those POMs are trying to set their versions from a build property.
This is fundamentally wrong.
We need to split out the packages into their own artifacts & versions
> Storm and HBase app packages installing bad pom names
> -----------------------------------------------------
>
> Key: SLIDER-627
> URL: https://issues.apache.org/jira/browse/SLIDER-627
> Project: Slider
> Issue Type: Bug
> Reporter: Billie Rinaldi
> Assignee: Sumit Mohanty
> Fix For: Slider 2.0.0
>
>
> When doing a mvn install I noticed the following bad pom names deployed to my
> local repo. If we want to deploy maven artifacts, this seems like it would
> be an issue (even if we're not planning to deploy app packages).
> {noformat}
> [INFO] Installing /home/hrt_qa/incubator-slider/app-packages/storm/pom.xml to
> /home/hrt_qa/.m2/repository/org/apache/slider/slider-storm-app-package/${pkg.version}/slider-storm-app-package-${pkg.version}.pom
> [INFO] Installing /home/hrt_qa/incubator-slider/app-packages/hbase/pom.xml to
> /home/hrt_qa/.m2/repository/org/apache/slider/slider-hbase-app-package/${pkg.version}/slider-hbase-app-package-${pkg.version}.pom
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
