You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Chang chen (JIRA)" <ji...@apache.org> on 2016/06/08 07:00:29 UTC
[jira] [Updated] (EAGLE-332) Build failed to due to [EAGLE-325]
[ https://issues.apache.org/jira/browse/EAGLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chang chen updated EAGLE-332:
-----------------------------
Description:
When building codes on develop branch after [EAGLE-329] [Dependency incompatibility bug among jersey, asm and extcos under Java 8], I get the following errors:
[ERROR] Failed to execute goal on project alert-assembly: Could not resolve dependencies for project org.apache.eagle:alert-assembly:jar:0.5.0-incubating-SNAPSHOT: The following artifacts could n
alert-coordinator:war:0.5.0-incubating-SNAPSHOT, org.apache.eagle:alert-metadata-service:war:0.5.0-incubating-SNAPSHOT: Failure to find org.apache.eagle:alert-coordinator:war:0.5.0-incubating-SNA
com/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of hdp has elapsed or updates are forced -> [Help 1]
it was introduced by EAGLE-325, which changed packaging type of alert-coordinator and alert-metadata-service from war to jar, but forget to update dependency in alert-assembly
was:
When building codes on develop branch after [EAGLE-329] Dependency incompatibility bug among jersey, asm and extcos under Java 8, I get the following errors:
[ERROR] Failed to execute goal on project alert-assembly: Could not resolve dependencies for project org.apache.eagle:alert-assembly:jar:0.5.0-incubating-SNAPSHOT: The following artifacts could n
alert-coordinator:war:0.5.0-incubating-SNAPSHOT, org.apache.eagle:alert-metadata-service:war:0.5.0-incubating-SNAPSHOT: Failure to find org.apache.eagle:alert-coordinator:war:0.5.0-incubating-SNA
com/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of hdp has elapsed or updates are forced -> [Help 1]
it was introduced by EAGLE-325, which changed packaging type of alert-coordinator and alert-metadata-service from war to jar, but forget to update dependency in alert-assembly
> Build failed to due to [EAGLE-325]
> ----------------------------------
>
> Key: EAGLE-332
> URL: https://issues.apache.org/jira/browse/EAGLE-332
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Chang chen
> Labels: build
> Fix For: v0.5.0
>
>
> When building codes on develop branch after [EAGLE-329] [Dependency incompatibility bug among jersey, asm and extcos under Java 8], I get the following errors:
> [ERROR] Failed to execute goal on project alert-assembly: Could not resolve dependencies for project org.apache.eagle:alert-assembly:jar:0.5.0-incubating-SNAPSHOT: The following artifacts could n
> alert-coordinator:war:0.5.0-incubating-SNAPSHOT, org.apache.eagle:alert-metadata-service:war:0.5.0-incubating-SNAPSHOT: Failure to find org.apache.eagle:alert-coordinator:war:0.5.0-incubating-SNA
> com/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of hdp has elapsed or updates are forced -> [Help 1]
> it was introduced by EAGLE-325, which changed packaging type of alert-coordinator and alert-metadata-service from war to jar, but forget to update dependency in alert-assembly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)