[
https://issues.apache.org/jira/browse/BEAM-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378656#comment-15378656
]
Kenneth Knowles commented on BEAM-445:
--------------------------------------
The build breakage itself is fixed - users are still required to include the
{{os-maven-plugin}} in their build.
Three avenues, off the top of my head:
- Get upstream upgraded to a version with an uber-jar..
- Try a same-major-version override to get a working uber-jar (I understand
that upstream is not using semantic versions, so this is a wildcard)
- Produce classifiers ourselves; it doesn't absolve the user of including the
plugin, but makes it less of a spooky issue.
> Beam-examples-java build failed through local "mvn install"
> -----------------------------------------------------------
>
> Key: BEAM-445
> URL: https://issues.apache.org/jira/browse/BEAM-445
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Environment: linux
> Reporter: Mark Liu
> Assignee: Daniel Halperin
> Priority: Critical
>
> Build project under beam/examples/java with command "mvn clean install
> -DskipTests" failed with following error:
> [ERROR] Failed to execute goal on project beam-examples-java: Could not
> resolve dependencies for project
> org.apache.beam:beam-examples-java:jar:0.2.0-incubating-SNAPSHOT: Could not
> transfer artifact
> io.netty:netty-tcnative-boringssl-static:jar:${os.detected.classifier}:1.1.33.Fork13
> from/to central (http://repo.maven.apache.org/maven2): Illegal character in
> path at index 138:
> http://repo.maven.apache.org/maven2/io/netty/netty-tcnative-boringssl-static/1.1.33.Fork13/netty-tcnative-boringssl-static-1.1.33.Fork13-${os.detected.classifier}.jar
> Reason: can't resolve ${os.detected.classifier} in
> beam/sdks/java/io/google-cloud-platform/pom file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
