Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selenium dependency boundaries not working with Maven #718

Closed
Hi-Fi opened this issue Sep 3, 2017 · 7 comments
Closed

Selenium dependency boundaries not working with Maven #718

Hi-Fi opened this issue Sep 3, 2017 · 7 comments
Assignees
Labels

Comments

@Hi-Fi
Copy link

Hi-Fi commented Sep 3, 2017

Description

While trying to create jar with dependencies with Selenium2library-java (https://github.com/Hi-Fi/robotframework-selenium2library-java/tree/Selenium3.5.2) with maven-assembly-plugin:3.1.0, error is thrown because of identical boundaries in Selenium version.

Environment

  • io.appium:java-client:jar:5.0.1
  • Microsoft Windows [Version 10.0.15063]
  • Maven version: 3.5.0
  • Java version: 1.8.0_144, vendor: Oracle Corporation

Details

Error message from Maven:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (make-assembly) on project robotframework-selenium2library-java: Failed to create assembly: Unable to resolve dependencies for assembly 'jar-with-dependencies': Failed to resolve dependencies for assembly: Unable to get dependency information for io.appium:java-client:jar:5.0.1: Invalid version for dependency org.seleniumhq.selenium:selenium-java:jar: Range cannot have identical boundaries: [3.5.2,3.5.2]
[ERROR]   io.appium:java-client:jar:5.0.1

Way To Reproduce Issue

Can be seen by executing mvn clean verify with code from https://github.com/Hi-Fi/robotframework-selenium2library-java/tree/Selenium3.5.2

Hi-Fi added a commit to MarketSquare/robotframework-seleniumlibrary-java that referenced this issue Sep 3, 2017
+ Keeping appium in old version because of appium/java-client#718
@mykola-mokhnach
Copy link
Contributor

@TikhomirovSergey FYI

@TikhomirovSergey
Copy link
Contributor

@Hi-Fi @mykola-mokhnach Yes. I am taking this issue. As we found the rootcause of many issues (#714) I will return the version number to its normal form (3.5.3 or another higher number) in 5.0.3

@TikhomirovSergey TikhomirovSergey self-assigned this Sep 3, 2017
@mykola-mokhnach
Copy link
Contributor

@TikhomirovSergey

This is what I have found on this topic so far:
http://gradle.1045684.n5.nabble.com/Translating-Ivy-dep-version-syntax-to-Maven-in-POM-generation-td5712755.html

Probably, we can use https://github.com/nebula-plugins/nebula-publishing-plugin, which can properly publish version ranges into Maven pom files.

@TikhomirovSergey
Copy link
Contributor

@mykola-mokhnach Ok. Will try the nebula plugin. Thank you.

@realnikunj
Copy link

I am facing this same issue with java-client version 5.0.2

Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (make-assembly) on project mt-ui-utils: Failed to create assembly: Unable to resolve dependencies for assembly 'jar-with-dependencies': Failed to resolve dependencies for assembly: Unable to get dependency information for io.appium:java-client:jar:5.0.2: Invalid version for dependency org.seleniumhq.selenium:selenium-java:jar: Range cannot have identical boundaries: [3.5.3,3.5.3]
io.appium:java-client:jar:5.0.2

@SrinivasanTarget
Copy link
Member

@realnikunj We are working on fix. Will push a release sooner.

@TikhomirovSergey TikhomirovSergey mentioned this issue Sep 7, 2017
4 tasks
@TikhomirovSergey
Copy link
Contributor

5.0.3 is coming ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants