You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2015/11/13 11:16:10 UTC

[jira] [Updated] (HBASE-14806) Missing sources.jar for several modules when building HBase

     [ https://issues.apache.org/jira/browse/HBASE-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang updated HBASE-14806:
------------------------------
    Attachment: HBASE-14806.patch

Seems only hbase-common and hbase-external-blockcache missing sources.jar.

I modified the pom.xml. But I'm not sure whether the output sources.jar contains correct LICENSE files.

[~busbey] Could you please help verifying the sources.jar generated with this patch?

Thanks.

> Missing sources.jar for several modules when building HBase
> -----------------------------------------------------------
>
>                 Key: HBASE-14806
>                 URL: https://issues.apache.org/jira/browse/HBASE-14806
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>         Attachments: HBASE-14806.patch
>
>
> Introduced by HBASE-14085. The problem is, for example, in hbase-common/pom.xml, we have
> {code:title=pom.xml}
> <plugin>
>           <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-source-plugin</artifactId>
>           <configuration>
>             <excludeResources>true</excludeResources>
>             <includes>
>               <include>src/main/java</include>
>               <include>${project.build.outputDirectory}/META-INF</include>
>             </includes>
>           </configuration>
>         </plugin>
> {code}
> But in fact, the path inside {{<include>}} tag is relative to source directories, not the project directory. So the maven-source-plugin always end with
> {noformat}
> No sources in project. Archive not created.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)