We're updating the issue view to help you get more done. 

Introducing javadocs for etl packages breaks the release build

Description

None

Release Notes

None

Activity

Show:
John Jackson
June 8, 2015, 9:27 PM

I sync'd up to e75b1c5307d13f34ec8cb07c4424f6a415bfff1c and was able to build the SDK successfully. It's after this that Sree made and merged his changes.
(That change was a merge to fix the version of parent pom used by the cdap-ui pom.xml.)

I did see some Javadoc builds in the log with 1700 warnings...

I successfully built both the SDK and the package command:

John Jackson
June 8, 2015, 11:59 PM

By making a branch, and running this again. I was able to get test fail.

works, suggesting that "release" is what is causing the problem. It looks like it is trying to run Javadocs on each directory, which is unnecessary for most cases.

John Jackson
June 9, 2015, 6:25 PM

The solution we have arrived at is to move the Javadoc creation out of the release profile and into the sites.

That way, when an aggregate is run, it will do the correct thing, and not interfere with the general javadoc creation.

Terence Yim
June 9, 2015, 9:29 PM
Fixed

Assignee

Terence Yim

Reporter

Sreevatsan Raman

Labels

None

Docs Impact

None

UX Impact

None

Fix versions

Priority

Blocker
Configure