You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Artem Ervits (JIRA)" <ji...@apache.org> on 2018/05/24 13:59:00 UTC
[jira] [Comment Edited] (OOZIE-3178) ./bin/mkdistro.sh
-Papache-release fails due to javadoc errors
[ https://issues.apache.org/jira/browse/OOZIE-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489035#comment-16489035 ]
Artem Ervits edited comment on OOZIE-3178 at 5/24/18 1:59 PM:
--------------------------------------------------------------
[~andras.piros] happy to do so, not sure which report pre hook is executed against as on my environment, I have to run mvn javadoc:javadoc goal then followed by mvn site and I'm getting
{code:java}
[INFO] --------------------< org.apache.oozie:oozie-tools >--------------------
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was encountered while building the effective model
[FATAL] Non-readable POM /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. Also, I think it's time to address mvn site plugin, the one we have is way old and uses a hacked version of Doxia. I once looked at it but this is over my head.
also, addressing a minor issue in OOZIE-2363
was (Author: dbist13):
[~andras.piros] happy to do so, not sure which report pre hook is executed against as on my environment, I have to run mvn javadoc:javadoc goal then followed by mvn site and I'm getting
{code:java}
[INFO] --------------------< org.apache.oozie:oozie-tools >--------------------
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was encountered while building the effective model
[FATAL] Non-readable POM /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. Also, I think it's time to address mvn site plugin, the one we have is way old and uses a hacked version of Doxia. I once looked at it but this is over my head.
> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --------------------------------------------------------------
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
> Issue Type: Bug
> Components: build
> Affects Versions: 5.0.0
> Reporter: Peter Cseh
> Assignee: Artem Ervits
> Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from happening in the future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)