zDev - Tycho - OSS
  1. zDev - Tycho - OSS
  2. TYCHO-516

No connector available to access repository of type p2

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11.0
    • Component/s: None
    • Labels:
      None
    • Global Rank:
      3354

      Description

      Getting plenty of warnings like below since maven switch to aether. As far as I understand, these are harmless, but still would be nice to suppress them to avoid possible confusion they may cause.

      10-10-30 1:48:45 AM EDT: [WARN] Failure to transfer org.sonatype.tycho:tycho-p2:0.11.0-SNAPSHOT/maven-metadata.xml from http://download.eclipse.org/releases/helios was cached in the local repository, resolution will not be reattempted until the update interval of helios has elapsed or updates are forced. Original error: Could not transfer metadata org.sonatype.tycho:tycho-p2:0.11.0-SNAPSHOT/maven-metadata.xml from helios (http://download.eclipse.org/releases/helios): No connector available to access repository helios (http://download.eclipse.org/releases/helios) of type p2 using the available factories WagonRepositoryConnectorFactory
      

        Activity

        Show
        Igor Fedorenko added a comment - Should be fixed now https://github.com/sonatype/sonatype-tycho/commit/f54ad4cb7d563007cb5bc69b70c85efd6c8f4bc6
        Hide
        Igor Fedorenko added a comment -

        I still see the problem with today's 0.11.0-SNAPSHOT

        Show
        Igor Fedorenko added a comment - I still see the problem with today's 0.11.0-SNAPSHOT
        Hide
        Igor Fedorenko added a comment -

        After fixing one more cause of this message (https://github.com/sonatype/sonatype-tycho/commit/e6ffb2a7dc9096bb42a01d8c54ce6543c9d7f510) I do not see the problem locally, but CI apparently still has it (https://grid.sonatype.org/ci/job/tycho-its/jdk=java-6x,label=ubuntu/138/console). So, either I did not eliminate the warning in all cases or CI is running outdated tycho snapshot. The latter is much worse than the former.

        Show
        Igor Fedorenko added a comment - After fixing one more cause of this message ( https://github.com/sonatype/sonatype-tycho/commit/e6ffb2a7dc9096bb42a01d8c54ce6543c9d7f510 ) I do not see the problem locally, but CI apparently still has it ( https://grid.sonatype.org/ci/job/tycho-its/jdk=java-6x,label=ubuntu/138/console ). So, either I did not eliminate the warning in all cases or CI is running outdated tycho snapshot. The latter is much worse than the former.
        Hide
        Igor Fedorenko added a comment -

        I think I finally managed to suppress these warning messages. At least I did not see them in the few builds I ran locally. Tycho ITs still emit them, but I hope this is due to the fact that Tycho build "bootstraps" itself with version 0.10.0.

        Show
        Igor Fedorenko added a comment - I think I finally managed to suppress these warning messages. At least I did not see them in the few builds I ran locally. Tycho ITs still emit them, but I hope this is due to the fact that Tycho build "bootstraps" itself with version 0.10.0.
        Hide
        Igor Fedorenko added a comment -
        Show
        Igor Fedorenko added a comment - commit corresponding to my last comment https://github.com/sonatype/sonatype-tycho/commit/08875f13eb410de55cf5ee83e1a9357c6b13c85d
        Hide
        Mikhail Mazursky added a comment -

        This problem still happens (sometimes) when building multimodule project with some of projects using tycho and some not. The error occurs on projects, that are not using tycho (not even in projects that are transitive deps) but are part of the build.

        Tycho 0.14.1
        Maven 3.0.4
        OpenJDK 1.7.0_03 and Oracle JDK 6 too.

        Show
        Mikhail Mazursky added a comment - This problem still happens (sometimes) when building multimodule project with some of projects using tycho and some not. The error occurs on projects, that are not using tycho (not even in projects that are transitive deps) but are part of the build. Tycho 0.14.1 Maven 3.0.4 OpenJDK 1.7.0_03 and Oracle JDK 6 too.
        Hide
        Igor Fedorenko added a comment -

        This is expected when p2 <repository> elements are defined at project level and tycho build extensions in the parent pom that needs to be resolved from remote repositories. This is chicken-and-egg problem, maven has to access remote repositories to resolve parent pom but needs information from the parent pom to load extensions needed to access remote repositories.

        Show
        Igor Fedorenko added a comment - This is expected when p2 <repository> elements are defined at project level and tycho build extensions in the parent pom that needs to be resolved from remote repositories. This is chicken-and-egg problem, maven has to access remote repositories to resolve parent pom but needs information from the parent pom to load extensions needed to access remote repositories.
        Hide
        Mikhail Mazursky added a comment -

        We had exactly the same situation but "reversed": <repository> with p2 layout in parent pom and tycho build extensions in some sub-project (parent for tycho projects). Looks like unrelevant projects were failing on attempts to access p2 repos to resolve some deps.

        Thanks!

        Show
        Mikhail Mazursky added a comment - We had exactly the same situation but "reversed": <repository> with p2 layout in parent pom and tycho build extensions in some sub-project (parent for tycho projects). Looks like unrelevant projects were failing on attempts to access p2 repos to resolve some deps. Thanks!

          People

          • Assignee:
            Igor Fedorenko
            Reporter:
            Igor Fedorenko
            Last Updated By:
            Mikhail Mazursky
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Date of First Response: