[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-20068:
---
Fix Version/s: (was: 1.5.0)
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.3.3, 1.4.4, 2.0.1, 1.2.7
>
> Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Resolution: Fixed
Fix Version/s: 2.0.1
1.4.4
1.3.3
1.2.7
1.5.0
2.1.0
3.0.0
Status: Resolved (was: Patch Available)
thanks for the reviews!
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.4, 2.0.1
>
> Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Status: Patch Available (was: In Progress)
-v1
- accounts for HBASE-15466 landing with another direct invocation of {{MAVEN}}
- disable shellcheck warnings present, since that's what yetus does when it
uses the executor function internally.
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Attachment: HBASE-20068.1.patch
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Status: In Progress (was: Patch Available)
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Attachments: HBASE-20068.0.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Status: Patch Available (was: In Progress)
-v0
- switch all uses of {{${MAVEN}}} with {{maven_executor}}
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Attachments: HBASE-20068.0.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Attachment: HBASE-20068.0.patch
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Attachments: HBASE-20068.0.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20068:
Component/s: community
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Priority: Major
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
