removing OpenQA repo from ERSelenium pom because OpenQA is off the air #504
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…the air. archiva.openqa.org redirects to www.openqa.org announcing that OpenQA is off the air. The result of this was that the html announcemnet was finding it's way into the maven repository as the pom for this artifact. That is obviously an invalid pom and caused problems compiling. Reloading the artifact in the local repository works (as long as you get rid of the old pom.
pascalrobert
pushed a commit
that referenced
this pull request
Nov 3, 2013
removing OpenQA repo from ERSelenium pom because OpenQA is off the air
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
archiva.openqa.org redirects to www.openqa.org announcing that OpenQA is off the air. The result of this was that the html announcemnet was finding it's way into the maven repository as the pom for this artifact. That is obviously an invalid pom and caused problems compiling. Reloading the artifact in the local repository works (as long as you get rid of the old pom.