Bug 1106598

Summary: If ${project.build.directory} is not set to "target" then .mfiles-javadoc is not generated
Product: [Fedora] Fedora Reporter: Mat Booth <mat.booth>
Component: xmvnAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: java-sig-commits, mizdebsk, msimacek, msrb
Target Milestone: ---Keywords: FutureFeature, Upstream, VerifiedUpstream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 09:08:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Simple test case spec file none

Description Mat Booth 2014-06-09 16:13:36 UTC
Created attachment 904790 [details]
Simple test case spec file

Description of problem:
If the maven project's build directory is set to something other than the default value of "target" then the .mfiles-javadoc file does not get generated and the javadoc subpackage fails to build 

Version-Release number of selected component (if applicable):
[mbooth@rawhide ~]$ rpm -q maven-local xmvn
maven-local-4.0.0-4.fc21.noarch
xmvn-2.0.1-1.fc21.noarch

Steps to Reproduce:
1. Build the attached rpm spec file -- fails
2. Change <directory>not-target</directory> to <directory>target</directory>
3. Re-build the spec file -- succeeds

Actual results:
Build failure when the project's build directory is not the default value "target"

Expected results:
It should detect where the javadoc is built to, no matter what the build directory is set to.

Comment 1 Mikolaj Izdebski 2014-07-15 08:44:12 UTC
Implemented upstream.

http://github.com/mizdebsk/xmvn/commit/4509590
http://github.com/mizdebsk/javapackages/commit/5a942fd

Now XMvn will listen to executions of "aggregate" goal of Maven Javadoc Plugin, capture Javadoc report output location and save it as a symlink in .xmvn/apidocs.  This symlink will be checked by %mvn_install macro when installing javadocs.

Comment 2 Mikolaj Izdebski 2014-07-15 08:57:55 UTC
Verified upstream:

$ rpm -qp /var/lib/xmock/maven/result/MrTest-javadoc-1-1.fc22.x86_64.rpm -l
/usr/share/javadoc/MrTest
/usr/share/javadoc/MrTest/MrTest.html
/usr/share/javadoc/MrTest/allclasses-frame.html
/usr/share/javadoc/MrTest/allclasses-noframe.html
/usr/share/javadoc/MrTest/class-use
/usr/share/javadoc/MrTest/class-use/MrTest.html
/usr/share/javadoc/MrTest/constant-values.html
/usr/share/javadoc/MrTest/deprecated-list.html
/usr/share/javadoc/MrTest/help-doc.html
/usr/share/javadoc/MrTest/index-all.html
/usr/share/javadoc/MrTest/index.html
/usr/share/javadoc/MrTest/overview-tree.html
/usr/share/javadoc/MrTest/package-frame.html
/usr/share/javadoc/MrTest/package-list
/usr/share/javadoc/MrTest/package-summary.html
/usr/share/javadoc/MrTest/package-tree.html
/usr/share/javadoc/MrTest/package-use.html
/usr/share/javadoc/MrTest/script.js
/usr/share/javadoc/MrTest/stylesheet.css

Comment 3 Mikolaj Izdebski 2014-09-24 09:08:41 UTC
Fixed in rawhide.