[
https://issues.apache.org/jira/browse/HTRACE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877410#comment-14877410
]
stack commented on HTRACE-259:
------------------------------
Yeah, I think rename of the htrace-core module to htrace-core4 is way to go. In
submodules we refer to the htrace-core4 'dependency' from htrace-hbase for
instance already. Only place we don't do this is in top-level pom itself.
Messing with substitution in the assembly, it only works if variable names:
i.e. ${htrace-core}. Having a module be a variable name is kinda weird.
> Rename htrace-core module as htrace-core4 to match the artifactId
> -----------------------------------------------------------------
>
> Key: HTRACE-259
> URL: https://issues.apache.org/jira/browse/HTRACE-259
> Project: HTrace
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 259.patch
>
>
> When we build an assembly, it contains htrace-core4 rather than htrace-core.
> Same for when we deploy to maven repository; the repository has htrace-core4
> .. jar rather than htrace-core.
> We should rename the module in git to match else build from source fails with
> following:
> {code}
> kalashnikov:htrace-4.0.1-incubating stack$ mvn install
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project org.apache.htrace:htrace:4.0.1-incubating
> (/Users/stack/Downloads/htrace-4.0.1-incubating/pom.xml) has 1 error
> [ERROR] Child module
> /Users/stack/Downloads/htrace-4.0.1-incubating/htrace-core of
> /Users/stack/Downloads/htrace-4.0.1-incubating/pom.xml does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
