[
https://issues.apache.org/jira/browse/HTRACE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735592#comment-14735592
]
Colin Patrick McCabe commented on HTRACE-236:
---------------------------------------------
So, I have noticed that setting {{promoteTransitiveDependencies}} to {{true}}
avoids this bug on Maven 3.3.3. It seems like for us, this might be a valid
solution.
The documentation for this option says:
bq. When true, transitive deps of removed dependencies are promoted to direct
dependencies. This should allow the drop in replacement of the removed deps
with the new shaded jar and everything should still work
Changing the generated {{dependency-reduced-pom.xml}} seems potentially OK,
since we don't have other projects pulling in {{htrace-hbase}}. The intended
use for htrace-hbase is dropping it onto the CLASSPATH of a project that wants
to use the htrace-hbase span receiver. I guess I'll have to see if setting
this option adds anything to the jar that we don't want?
> Support building release artifacts with Maven versions other than 3.0.4
> -----------------------------------------------------------------------
>
> Key: HTRACE-236
> URL: https://issues.apache.org/jira/browse/HTRACE-236
> Project: HTrace
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: Colin Patrick McCabe
>
> Because of HTRACE-234, we have had to limit the Maven version we use to
> create releases to Maven 3.0.4. We should figure out how to make things work
> correctly with later Maven releases as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
