Skip to content

allure-selenide: up selenide version and don't expose selenide to pom.xml#670

Merged
baev merged 2 commits into
allure-framework:masterfrom
BorisOsipov:update_selenide
Oct 26, 2021
Merged

allure-selenide: up selenide version and don't expose selenide to pom.xml#670
baev merged 2 commits into
allure-framework:masterfrom
BorisOsipov:update_selenide

Conversation

@BorisOsipov
Copy link
Copy Markdown
Contributor

@BorisOsipov BorisOsipov commented Oct 26, 2021

Context

Update selenide version to latest. Don't add selenide deps to published pom.xml to avoid versions conflict for maven users.

Checklist

@baev baev added the type:dependencies Pull requests that update a dependency label Oct 26, 2021
@baev baev merged commit bb1821b into allure-framework:master Oct 26, 2021
@baev
Copy link
Copy Markdown
Member

baev commented Oct 26, 2021

@BorisOsipov thanks!

@BorisOsipov
Copy link
Copy Markdown
Contributor Author

BorisOsipov commented Oct 26, 2021

@baev thank you for quick response. Any plans on 2.15.1 or 2.16.0 release?

Now we are a bit suffering after Selenium 4 release. For maven user maven dependency resolution puts old selenium in classpath due deps from allure-selenide:2.15.0

@baev
Copy link
Copy Markdown
Member

baev commented Oct 26, 2021

yep, expecting 2.16.0 later this week. Need to add few more changes and then we all set

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

theme:build theme:selenide type:dependencies Pull requests that update a dependency

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants