I am pretty sure this was when the demo was introduced.

Christian

Am 30.05.2012 11:44, schrieb Achim Nierbeck:
No Idea where to look for.
I suggest taking a look when was the first time those demos failed and
start digging there.

Achim

2012/5/30 Christian Schneider<[email protected]>:
Any idea where to look for ? I currently have no clue what could be wrong.
The strange thing is that it fails very late. Basically after the build is
finished.

Christian

Am 30.05.2012 11:19, schrieb Achim Nierbeck:

AFAIK the my-kar deployer demo fails due to some refactorings so I
suggest fixing those instead of disabling the demo

Achim

2012/5/30 Christian Schneider<[email protected]>:
The build is running again.

There are two issues though:

- We have test failures. I think they result from our integration tests
using artifacts from the remote repo instead of using the most current
ones.
Not sure though
. The build fails at deploying the my-kar.pom which seems to be part of
the
deployer demo (see below). We had that problem before already not sure
what
is going on there. I will try to disable this.

Christian

--

org.apache.maven.artifact.deployer.ArtifactDeploymentException

  
<http://stacktrace.jenkins-ci.org/search?query=org.apache.maven.artifact.deployer.ArtifactDeploymentException>:
Failed to deploy artifacts: Could not transfer artifact
org.apache.karaf.demos:my-kar:pom:1.0 from/to apache.snapshots.https
(https://repository.apache.org/content/repositories/snapshots): Failed to
transfer

file:https://repository.apache.org/content/repositories/snapshots/org/apache/karaf/demos/my-kar/1.0/my-kar-1.0.pom.
Return code is: 400, ReasonPhrase:Bad Request.


  
atorg.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141)

  
<http://stacktrace.jenkins-ci.org/search/?query=org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy&entity=method>


  
athudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:182)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.reporters.MavenArtifactRecord.deploy&entity=method>

  athudson.maven.RedeployPublisher.perform(RedeployPublisher.java:174)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.RedeployPublisher.perform&entity=method>

  athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.perform&entity=method>


  athudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractRunner.perform&entity=method>


  
athudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps&entity=method>


  
athudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:994)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$RunnerImpl.post2&entity=method>

  athudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractRunner.post&entity=method>
        athudson.model.Run.run(Run.java:1459)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.run&entity=method>

  athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>

  athudson.model.ResourceController.execute(ResourceController.java:88)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>
        athudson.model.Executor.run(Executor.java:239)

  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>



Am 30.05.2012 09:28, schrieb Christian Schneider:

Currently our jenkins build fails at the missing karaf-maven-plugin. We
already discussed about this and I would like to fix the build by not
using
the lifecycle extensions for our
own feature definitions.

https://issues.apache.org/jira/browse/KARAF-1509

Is everyone ok with this?

Chistian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Reply via email to