Build failed in Jenkins: scalafx #332

1 view
Skip to first unread message

Build Daemon

unread,
Nov 3, 2013, 11:32:53 PM11/3/13
to scalaf...@googlegroups.com, jps...@gmail.com, jsa...@users.sf.net, pe...@peter-pc.belkin, A...@cua.li, steve...@gmail.com, peterp...@peters-macbook-pro.local, Rafael@rafael-hp, rladst...@gmail.com, peter....@gmail.com, rafael...@gmail.com, Alain.Fag...@gmail.com
See <http://jfxtras.com/jenkins/job/scalafx/332/changes>

Changes:

[Jarek Sacha <jps...@gmail.com>] Proposed solution to Issue 102: Use of "code blocks" for event handlers can lead to buggy code.

"Code blocks" can no longer be used for event handling. There is new method that created simple event handler called`handle` that replaces implicit conversion of "code blocks" into event handlers. To migrate old code replace code like:

button.onAction = {
println("Handling button action")
doSomething()
}

with

button.onAction = handle {
println("Handling button action")
doSomething()
}

Notice `handle` after the `=`. Closure handles work as before.

Tests in `KeyFrameSpec` were expanded to handle all three simple event handling variants.

------------------------------------------
Started by an SCM change
Building in workspace <http://jfxtras.com/jenkins/job/scalafx/ws/>
[workspace] $ hg showconfig paths.default
[workspace] $ hg pull --rev default
[workspace] $ hg update --clean --rev default
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
[workspace] $ hg --config extensions.purge= clean --all
[workspace] $ hg log --rev . --template {node}
[workspace] $ hg log --rev 9880409675ed7e9f0d728903840d6ebf05e7dfc4
[workspace] $ hg log --template "<changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev default:0 --follow --prune 9880409675ed7e9f0d728903840d6ebf05e7dfc4
[workspace] $ java -XX:MaxPermSize=256m -Dsbt.log.noformat=true -jar /opt/sbt/sbt-launch-0.11.2.jar test package
Getting org.scala-tools.sbt sbt_2.9.1 0.13.0 ...

:: problems summary ::
:::: WARNINGS
module not found: org.scala-tools.sbt#sbt_2.9.1;0.13.0

==== local: tried

/var/lib/jenkins/.ivy2/local/org.scala-tools.sbt/sbt_2.9.1/0.13.0/ivys/ivy.xml

==== typesafe-ivy-releases: tried

http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt_2.9.1/0.13.0/ivys/ivy.xml

==== Maven Central: tried

http://repo1.maven.org/maven2/org/scala-tools/sbt/sbt_2.9.1/0.13.0/sbt_2.9.1-0.13.0.pom

==== Scala-Tools Maven2 Repository: tried

http://scala-tools.org/repo-releases/org/scala-tools/sbt/sbt_2.9.1/0.13.0/sbt_2.9.1-0.13.0.pom

==== Scala-Tools Maven2 Snapshots Repository: tried

http://scala-tools.org/repo-snapshots/org/scala-tools/sbt/sbt_2.9.1/0.13.0/sbt_2.9.1-0.13.0.pom

::::::::::::::::::::::::::::::::::::::::::::::

:: UNRESOLVED DEPENDENCIES ::

::::::::::::::::::::::::::::::::::::::::::::::

:: org.scala-tools.sbt#sbt_2.9.1;0.13.0: not found

::::::::::::::::::::::::::::::::::::::::::::::



:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.scala-tools.sbt#sbt_2.9.1;0.13.0: not found
Error during sbt execution: Error retrieving required libraries
(see /var/lib/jenkins/.sbt/boot/update.log for complete log)
Error: Could not retrieve sbt 0.13.0
Build step 'Build using sbt' changed build result to FAILURE
Build step 'Build using sbt' marked build as failure
Archiving artifacts
Recording test results
Failed to send e-mail to Alain.Fagot.Bearez because no e-mail address is known, and no default e-mail domain is configured
Invalid address: Daniel Al...@TUBARAO.requisito.net.br
Failed to send e-mail to rafael.afonso because no e-mail address is known, and no default e-mail domain is configured
Failed to send e-mail to prasee because no e-mail address is known, and no default e-mail domain is configured
Failed to send e-mail to prasannakumar because no e-mail address is known, and no default e-mail domain is configured
Reply all
Reply to author
Forward
0 new messages