Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] was settings.xml on hudson.eclipse.org modified ? (was "Re: egit-github build fails on signing plugin error")

I’m having similar issues trying to use tycho 1.0.13-SNAPSHOT. Something changed on Hudson and my guess is that was a bad idea.

 

Doug.

 

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthias Sohn
Sent: Monday, July 04, 2011 7:55 AM
To: Kevin Sawicki; Cross project issues
Subject: [cross-project-issues-dev] was settings.xml on hudson.eclipse.org modified ? (was "Re: egit-github build fails on signing plugin error")

 

2011/7/3 Kevin Sawicki <kevinsawicki@xxxxxxxxx>

Hey Matthias,

 

The egit-github build started failing with the following error,  it looks like an issue with the signing plug-in.  The egit pom.xml and the egit-github pom.xml seem to use the same configuration and egit is still building so I'm not sure what cause the builds to start to fail.

 

Any ideas?

 

I am wondering if hudson.eclipse.org got a new settings.xml redirecting our request to download the 1.0.1.2-SNAPSHOT version

of the signing plugin from http://intalio.org/public/maven2 to the new Eclipse Nexus instance http://maven.eclipse.org/nexus/content/groups/public/ which doesn't have this version (yet). I searched the cross list but couldn't find any such announcement.

So maybe this happened unintentionally ?

 

The latest egit-github build tried to download the signing plugin from 

 
http://maven.eclipse.org/nexus/content/repositories/milestone-indigo/org/eclipse/dash/maven/eclipse-maven-signing-plugin/1.0.1.2-SNAPSHOT/maven-metadata.xml
but our pom.xml specifies:
 
  <pluginRepositories>
    <pluginRepository>
      <id>maven.eclipse.org</id>
      <url>http://maven.eclipse.org/nexus/content/repositories/milestone-indigo</url>
    </pluginRepository>
    <!-- TODO: need 1.0.1.2-SNAPSHOT of the signing plugin until bugfix for
         https://bugs.eclipse.org/bugs/show_bug.cgi?id=347591
         is available in maven.eclipse.org -->
    <pluginRepository>
      <id>intalio-dash-signing-plugin</id>
      <url>http://intalio.org/public/maven2</url>
      <snapshots>
       <enabled>true</enabled>
      </snapshots>
      <releases>
       <enabled>true</enabled>
      </releases>
    </pluginRepository>
  </pluginRepositories>

 

 

[ERROR] Plugin org.eclipse.dash.maven:eclipse-maven-signing-plugin:1.0.1.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.dash.maven:eclipse-maven-signing-plugin:jar:1.0.1.2-SNAPSHOT: Could not find artifact org.eclipse.dash.maven:eclipse-maven-signing-plugin:pom:1.0.1.2-SNAPSHOT in eclipse-repositories (http://maven.eclipse.org/nexus/content/groups/public/) -> [Help 1]
org.apache.maven.plugin.PluginResolutionException: Plugin org.eclipse.dash.maven:eclipse-maven-signing-plugin:1.0.1.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.dash.maven:eclipse-maven-signing-plugin:jar:1.0.1.2-SNAPSHOT
       at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129)
       at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142)
       at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261)
       at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
       at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:152)
       at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:139)
       at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116)
       at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:129)
       at org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:92)
       at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
       at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
       at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
       at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
       at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
       at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
       at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
       at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
       at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)




--
Matthias


Back to the top