Thanks Tim

It seems that scala-tools.org is back up now, but even so I get this
error:

$ mvn scala:doc -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Lift
[INFO]   Lift Utils
[INFO]   Lift Actor
[INFO]   Lift WebKit
[INFO]   Lift OSGi
[INFO]   Lift Widgets
[INFO]   Lift Mapper
[INFO]   Lift Machine
[INFO]   Lift Record
[INFO]   Lift Textile
[INFO]   Lift Facebook
[INFO]   Lift AMQP
[INFO]   Lift XMPP
[INFO]   Lift OpenID
[INFO]   Lift OAuth
[INFO]   Lift PayPal
[INFO]   Lift TestKit
[INFO]   Lift Core (full lift)
[INFO]   Lift JPA
[INFO]   Lift Sites
[INFO]   Lift Example
[INFO]   OSGi Examples for Lift - Hello
[INFO]   OSGi Examples for Lift
[INFO]   Skittr Example
[INFO]   HelloLift example application
[INFO]   HelloDarwin tutorial application
[INFO]   JPA Demo Master
[INFO]   JPADemo-spa
[INFO]   JPADemo-web
[INFO]   HTTP Authentication example
[INFO]   lift-archetype-blank
[INFO]   lift-archetype-basic
[INFO]   lift-archetype-jpa-basic
[INFO]   lift-archetype-jpa-blank
[INFO]   lift-archetype-jpa-blank-single
[INFO] Searching repository for plugin with prefix: 'scala'.
WAGON_VERSION: 1.0-beta-2
[INFO]
------------------------------------------------------------------------
[INFO] Building Lift
[INFO]    task-segment: [scala:doc]
[INFO]
------------------------------------------------------------------------
[INFO] [scala:doc]
[INFO] Checking for multiple versions of scala
[WARNING] No source files found in /Users/george/Sites/git/liftweb/src/
main/scala
[INFO]
------------------------------------------------------------------------
[INFO] Building Lift Utils
[INFO]    task-segment: [scala:doc]
[INFO]
------------------------------------------------------------------------
[INFO] [scala:doc]
[INFO] Checking for multiple versions of scala
[INFO] Checking for multiple versions of scala
[INFO] delete :/Users/george/Sites/git/liftweb/lift-util/target/site/
scaladocs/scaladocs
[WARNING] warning: there were unchecked warnings; re-run with -
unchecked for details
[INFO] failed to find baseUri for org.slf4j.Logger :: org.slf4j
[INFO] failed to find baseUri for org.slf4j.Logger :: org.slf4j
[INFO] failed to find baseUri for org.apache.log4j.Logger ::
org.apache.log4j
[INFO] failed to find baseUri for org.apache.log4j.Logger ::
org.apache.log4j
[INFO] failed to find baseUri for org.apache.log4j.Level ::
org.apache.log4j
[INFO] failed to find baseUri for org.apache.log4j.Priority ::
org.apache.log4j
[WARNING] one warning found
[INFO]
------------------------------------------------------------------------
[INFO] Building Lift Actor
[INFO]    task-segment: [scala:doc]
[INFO]
------------------------------------------------------------------------
[INFO] [scala:doc]
[INFO] Checking for multiple versions of scala
[INFO] Checking for multiple versions of scala
[INFO] delete :/Users/george/Sites/git/liftweb/lift-actor/target/site/
scaladocs/scaladocs
[WARNING] /Users/george/Sites/git/liftweb/lift-actor/src/main/scala/
net/liftweb/actor/LAFuture.scala:20: error: not found: value Helpers
[WARNING] import Helpers._
[WARNING]        ^
[WARNING] /Users/george/Sites/git/liftweb/lift-actor/src/main/scala/
net/liftweb/actor/LAPinger.scala:18: error: not found: value Helpers
[WARNING] import Helpers.TimeSpan
[WARNING]        ^
[WARNING] /Users/george/Sites/git/liftweb/lift-actor/src/main/scala/
net/liftweb/actor/LiftActor.scala:20: error: not found: value Helpers
[WARNING] import Helpers._
[WARNING]        ^
[WARNING] /Users/george/Sites/git/liftweb/lift-actor/src/main/scala/
net/liftweb/actor/LiftActor.scala:179: error: missing parameter type
for expanded function ((x0$1) => x0$1 match {
[WARNING]   case (e @ _) => Log.error("Error processing Actor ".$plus
(this), e)
[WARNING] })
[WARNING]   protected def exceptionHandler: PartialFunction[Throwable,
Unit] = {
[WARNING]
^
[WARNING] four errors found
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] wrap: org.apache.maven.reporting.MavenReportException: wrap:
command line returned non-zero value:1

[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: wrap:
org.apache.maven.reporting.MavenReportException: wrap: command line
returned non-zero value:1
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:584)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
(DefaultLifecycleExecutor.java:513)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:483)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:331)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:292)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
        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.classworlds.Launcher.launchEnhanced(Launcher.java:
315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: wrap:
org.apache.maven.reporting.MavenReportException: wrap: command line
returned non-zero value:1
        at org.scala_tools.maven.ScalaMojoSupport.execute
(ScalaMojoSupport.java:311)
        at org.scala_tools.maven.ScalaDocMojo.execute(ScalaDocMojo.java:35)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:453)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:559)
        ... 16 more
Caused by: org.apache.maven.reporting.MavenReportException: wrap:
command line returned non-zero value:1
        at org.scala_tools.maven.ScalaDocMojo.generate(ScalaDocMojo.java:294)
        at org.scala_tools.maven.ScalaDocMojo.doExecute(ScalaDocMojo.java:
225)
        at org.scala_tools.maven.ScalaMojoSupport.execute
(ScalaMojoSupport.java:303)
        ... 19 more
Caused by: org.apache.maven.plugin.MojoFailureException: command line
returned non-zero value:1
        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:224)
        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:194)
        at org.scala_tools.maven.ScalaDocMojo.generate(ScalaDocMojo.java:288)
        ... 21 more

Not sure what to do about this...

George

On Jun 27, 2:31 pm, Timothy Perrett <[email protected]> wrote:
> But of course! Clone the lift source repo onto your local machine then do
> the following:
>
> cd <the place you cloned lift>
> mvn scala:doc
>
> Cheers, Tim
>
> On 27/06/2009 14:07, "george" <[email protected]> wrote:
>
>
>
>
>
> > Is there any way to locally generate the Lift API scaladocs without
> > needing scala-tools.org?
>
> > George
>
> > On Jun 27, 1:16 pm, Josh Suereth <[email protected]> wrote:
> >> Hi, I forwarded the email to [email protected], but I have not received
> >> it back (meaning is has not been sent).   I also tried ssh'ing onto the 
> >> box,
> >> and was unsuccessful.  That's being my powers of admin for
> >> scala-tools.orguntil we can get it active again.
>
> >> David Pollak and Derek Chen-Becker are the other admins (for future
> >> reference).
>
> >> - Josh
>
> >> On Sat, Jun 27, 2009 at 5:28 AM, marius d. <[email protected]> wrote:
>
> >>> dunno who can help .. I sent an email on scala-list but nothing yet
>
> >>> On Jun 27, 12:17 pm, Timothy Perrett <[email protected]> wrote:
> >>>> @marius Is there anyone around to checkup on scala-tools? DavidB
> >>>> doesn't monitor the lift list much these days and I'm not sure if
> >>>> there are any other non-American guys (I.e people who are awake now!)
> >>>> to take a look at the server?
>
> >>>> Cheers, Tim
>
> >>>> Sent from my iPhone
>
> >>>> On 27 Jun 2009, at 10:06, "marius d." <[email protected]> wrote:
>
> >>>>> try maven -o ....
>
> >>>>> Marius
>
> >>>>> On Jun 27, 11:46 am, Ellis <[email protected]> wrote:
> >>>>>> Maven is suddenly refusing to compile because scala-tools.org is
> >>>>>> down.  Can the liftweb-snapshot-1.1 POM be changed in order to let
> >>>>>> maven work in offline mode?
>
> >>>>>> Here's an excerpt of the error message when trying to run in offline
> >>>>>> mode:
> >>>>>> $ mvn -o -npu compile
> >>>>>> [INFO]
> >>>>>> NOTE: Maven is executing in offline mode. Any artifacts not already
> >>>>>> in
> >>>>>> your local
> >>>>>> repository will be
> >>>>>> inaccessible.
> >>>>>> ...
> >>>>>> [ERROR] BUILD
> >>>>>> ERROR
> >>>>>> [INFO]
> >>>>>> ---
> >>>>>> ---------------------------------------------------------------------
> >>>>>> [INFO] Failed to resolve
> >>>>>> artifact.
> >>>>>> ...
> >>>>>> Missing:
> >>>>>> ----------
> >>>>>> 1) net.liftweb:lift-util:jar:1.1-SNAPSHOT
> >>>>>> ...
>
> >>>>>> The files DO appear to be in my local repository, last updated via
> >>>>>> maven yesterday at 15:20 GMT:
> >>>>>> $ ls -1 /home/ellis/.m2/repository/net/liftweb/lift-util/1.1-
> >>>>>> SNAPSHOT/
> >>>>>> lift-util-1.1-SNAPSHOT.jar
> >>>>>> lift-util-1.1-SNAPSHOT.jar.sha1
> >>>>>> lift-util-1.1-SNAPSHOT-javadoc.jar.lastUpdated
> >>>>>> lift-util-1.1-SNAPSHOT.pom
> >>>>>> lift-util-1.1-SNAPSHOT.pom.sha1
> >>>>>> lift-util-1.1-SNAPSHOT-sources.jar
> >>>>>> lift-util-1.1-SNAPSHOT-sources.jar.sha1
> >>>>>> maven-metadata-scala-tools.org.snapshots.xml
> >>>>>> maven-metadata-scala-tools.org.snapshots.xml.sha1
> >>>>>> maven-metadata-scala-tools.org.xml
> >>>>>> resolver-status.properties
>
> >>>>>> Any ideas how to force maven to use the files that it was content to
> >>>>>> use yesterday?
>
> >>>>>> Thanks,
> >>>>>> Ellis
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to