[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656070#comment-15656070
]
Kenneth Knowles commented on BEAM-688:
--
I don't believe it has to be repeated. It causes flakes on Travis CI very
frequently. Example:
https://travis-ci.org/apache/incubator-beam/builds/174930789
> 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: Scott Wegner
>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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15598380#comment-15598380
]
Neelesh Srinivas Salian commented on BEAM-688:
--
Seeing this as well.
`mvn clean install` helps avoid it.
> 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: Scott Wegner
>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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572415#comment-15572415
]
Venkata Bijjam commented on BEAM-688:
-
I am seeing this on the initial build itself. I downloaded the code from master
branch today 10/13/2016.
mvn clean install -DskipTests -Dcheckstyle.skip=true -DskipIT
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.4:integration-test
(default-integration-test) on project beam-sdks-java-maven-archetype
s-starter:
[ERROR] Archetype IT 'basic' failed: Cannot run additions goals.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :beam-sdks-java-maven-archetypes-starter
> 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: Scott Wegner
>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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530210#comment-15530210
]
Scott Wegner commented on BEAM-688:
---
Yes, [~dhalp...@google.com] and [~jbonofre] you both seem to be correct. Here's
what I see from playing around a bit:
{noformat}
mvn clean install -DskipTests # install dependencies
cd sdks/java/maven-archetypes/starter
mvn clean # start with clean project
mvn dependency:analyze -DignoreNonCompile=false # 1. clean => warning
mvn dependency:analyze -DignoreNonCompile=true # 2. clean => no warning
mvn install # build project
mvn dependency:analyze -DignoreNonCompile=false # 3. prebuilt => warning
mvn dependency:analyze -DignoreNonCompile=true # 4. prebuilt => warning
{noformat}
The difference between ignoreNonCompile true/false is expected, but the
difference between clean/prebuilt (#2 vs #4) seems like a bug.
> 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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530113#comment-15530113
]
Jean-Baptiste Onofré commented on BEAM-688:
---
I think it's more the dependency-plugin which check the pom.xml from the target
folder (the second time, whereas it doesn't exist the first time).
> 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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530100#comment-15530100
]
Daniel Halperin commented on BEAM-688:
--
Something related to the {{ignoreNonCompile}} setting being lost the second
time around?
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html#ignoreNonCompile
> 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)
[jira] [Commented] (BEAM-688) Repeated 'mvn install' fails on beam-sdks-java-maven-archetypes-starter with undeclared dependency error
[
https://issues.apache.org/jira/browse/BEAM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530082#comment-15530082
]
Scott Wegner commented on BEAM-688:
---
I began seeing symptoms of this when upgrading the maven-compiler-plugin
version in [PR-1020|https://github.com/apache/incubator-beam/pull/1020] for
[BEAM-687|https://issues.apache.org/jira/browse/BEAM-687].
> 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)
