[
https://issues.apache.org/jira/browse/HBASE-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003860#comment-15003860
]
Duo Zhang commented on HBASE-14806:
-----------------------------------
I tried locally with command
{noformat}
mvn clean install -DskipTests -DHBasePatchProcess -Dhadoop-two.version=2.4.0
{noformat}
passed.
Let me try again to see if jenkins fail at the same place...
> 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
> Assignee: 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)
