beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
Date Wed, 28 Sep 2016 16:18:21 GMT

    [ https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530111#comment-15530111
] 

Jean-Baptiste Onofré commented on BEAM-688:
-------------------------------------------

I can reproduce the issue. A simple workaround is to use {{mvn clean install}} instead of
just {{mvn install}}.

It sounds like the first execution populated the {{target}} folder, and the existing {{pom.xml}}
is used. This {{target/test-classes/projects/basic/project/basic/pom.xml}} doesn't contain
the expected dependencies and is checked by the maven-dependency-plugin. So, I would ignore
the generated pom.xml from the target folder, or I would change the execution phase of the
dependency plugin.

> Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared
dependency error
> --------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-688
>                 URL: https://issues.apache.org/jira/browse/BEAM-688
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system, sdk-java-extensions
>            Reporter: Scott Wegner
>            Assignee: James Malone
>            Priority: Minor
>
> When building repeatedly using {{mvn install}}, the second build will fail on target
beam-sdks-java-maven-archetypes-starter with error:
> {noformat}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (default) @ beam-sdks-java-maven-archetypes-starter
---
> [WARNING] Used undeclared dependencies found:
> [WARNING]    org.slf4j:slf4j-api:jar:1.7.14:runtime
> {noformat}
> For some reason this only happens on the second build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message