You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2009/10/31 11:23:31 UTC

Compiling ESME offline

There are a few of us who have trouble compiling ESME when offline.
Although I have everything in the maven repository, I get errors when
doing a "mvn install". Is there something we can do about this - maybe
change the pom.xml?

D.

Re: Compiling ESME offline

Posted by David Pollak <fe...@gmail.com>.
I was just able to build ESME with a clean pull and and empty .m2
directory... weird.

On Tue, Nov 3, 2009 at 6:39 AM, Xuefeng Wu <be...@gmail.com> wrote:

> Thank you for your response.
>
> @D
> I checked out new from SVN but failed too.
>
> @David
> I run 'mvn -U clean install jetty:run' and failed too , get the same error:
> command line returned non-zero value:1
> I didn't rename .m2 folder and my other maven projects are working.
>
>
>
> On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> <fe...@gmail.com>wrote:
>
> > Did you do a successful "mvn -U clean install jetty:run" before trying to
> > apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
> > process?
> >
> > On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >
> > > I run mvn clean install -e
> > > get:
> > >
> > > [WARNING] 204 errors found
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [ERROR] BUILD FAILURE
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] command line returned non-zero value:1
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Trace
> > > org.apache.maven.BuildFailureException: command line returned non-zero
> > > value:1
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > > ultLifecycleExecutor.java:715)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> > > fecycle(DefaultLifecycleExecutor.java:556)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> > > ltLifecycleExecutor.java:535)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > > dleFailures(DefaultLifecycleExecutor.java:387)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > > ts(DefaultLifecycleExecutor.java:348)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> > > fecycleExecutor.java:180)
> > >        at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> > >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> > >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> > >        at
> > > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> > > 0)
> > >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >        at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > > java:39)
> > >        at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > > sorImpl.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.MojoFailureException: command line
> > > returned n
> > > on-zero value:1
> > >        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> > >        at
> > > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> > > rt.java:124)
> > >        at
> > > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> > > port.java:54)
> > >        at
> > > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> > > 208)
> > >        at
> > > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> > > rt.java:29)
> > >        at
> > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> > > nManager.java:490)
> > >        at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > > ultLifecycleExecutor.java:694)
> > >        ... 17 more
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Total time: 23 seconds
> > >
> > >
> > >
> > > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
> wrote:
> > >
> > > > > Yes
> > > > > I'm on line and run mvn jetty:run and get the same error:
> > > > >
> > > > > What's the mean " command line returned non-zero value:1" in maven?
> > > >
> > > > Depends on these "204 errors found". Why don't you do as maven
> > > > suggests and "run Maven with the -e switch"?
> > > >
> > >
> > >
> > >
> > > --
> > > Scala中文社区:  http://groups.google.com/group/scalacn
> > >
> >
> >
> >
> > --
> > Lift, the simply functional web framework http://liftweb.net
> > Beginning Scala http://www.apress.com/book/view/1430219890
> > Follow me: http://twitter.com/dpp
> > Surf the harmonics
> >
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
I'm using this environment

Maven version: 2.0.9
Java version: 1.6.0_03
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

and it works.

Let me the latest maven version to see if I get the same error.

D.

On Fri, Nov 6, 2009 at 8:06 AM, Richard Hirsch <hi...@gmail.com> wrote:
> Definitely a tough problem.
>
> Let's try this:
>
> 1. Delete ,m2 repository
> 2. Get the latest code drop from the SVN and put it in a new directory
> 3. Do a  "mvn -X clean install > trace"
> 4. Upload the trace to the Jira Item.
>
> D.
>
> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> I comment the opendmk but didn't find scala-stats and configgy is dependency
>> exception the repository.
>> I uploaded the maven log.
>>
>> I think I didn't change anything, and other scala lift projects are working
>> well in the same environment.
>>
>>
>> On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hi...@gmail.com>wrote:
>>
>>> What about changing the pom.xml and removing the dependencies for
>>> scala-stats, configgy and opendmk. You will get compile errors but I
>>> want to see if that solves basic problem.
>>>
>>> I'll compare your environment to my environment at work and see if I
>>> see other diffs.
>>>
>>> Are you sure that nothing else changed in your env?
>>>
>>> D.
>>>
>>> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> > @D
>>> > Oops
>>> > I deleted  the .m2 repository but failed too....
>>> >
>>> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
>>> >wrote:
>>> >
>>> >> Looked at the log in the Jira item and compared it to my own log. I
>>> >> only see a few differences related to the dependencies  related to JMX
>>> >> functionality.
>>> >>
>>> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>>> >> updates from scala-stats
>>> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>>> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>>> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>>> >>
>>> >>
>>> >> Did you try and delete the .m2 repository. If you don't want to delete
>>> >> it what about renaming it.
>>> >>
>>> >> D.
>>> >>
>>> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> > Done,
>>> >> > attached
>>> >> >
>>> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
>>> >> >wrote:
>>> >> >
>>> >> >> Saw Jira item. Thanks.
>>> >> >>
>>> >> >> But we still need to see the entire log.  Could you attach it to the
>>> >> >> item as an attachment.
>>> >> >>
>>> >> >> The one link you posted in the Jira item about the Lift error in
>>> >> >> Hudson looks very similar. Once we get the entire maven log, it will
>>> >> >> be a lot easier to see if this is the problem.
>>> >> >>
>>> >> >> D.
>>> >> >>
>>> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> >> > @D.
>>> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
>>> >> >> >
>>> >> >> > Thanks.
>>> >> >> >
>>> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>>> hirsch.dick@gmail.com
>>> >> >> >wrote:
>>> >> >> >
>>> >> >> >> Why don't you create a Jira item and attach the entire trace as an
>>> >> >> >> attachment. Like this "mvn clean install > mytrace".
>>> >> >> >>
>>> >> >> >> We can then get a better idea of what is going on.
>>> >> >> >>
>>> >> >> >> D.
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
>>> wrote:
>>> >> >> >> > Thank you for your response.
>>> >> >> >> >
>>> >> >> >> > @D
>>> >> >> >> > I checked out new from SVN but failed too.
>>> >> >> >> >
>>> >> >> >> > @David
>>> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
>>> >> same
>>> >> >> >> error:
>>> >> >> >> > command line returned non-zero value:1
>>> >> >> >> > I didn't rename .m2 folder and my other maven projects are
>>> working.
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>>> >> >> >> > <fe...@gmail.com>wrote:
>>> >> >> >> >
>>> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run" before
>>> >> >> trying
>>> >> >> >> to
>>> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
>>> starting
>>> >> >> the
>>> >> >> >> >> process?
>>> >> >> >> >>
>>> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
>>> >> wrote:
>>> >> >> >> >>
>>> >> >> >> >> > I run mvn clean install -e
>>> >> >> >> >> > get:
>>> >> >> >> >> >
>>> >> >> >> >> > [WARNING] 204 errors found
>>> >> >> >> >> > [INFO]
>>> >> >> >> >> >
>>> >> >> >>
>>> >> ------------------------------------------------------------------------
>>> >> >> >> >> > [ERROR] BUILD FAILURE
>>> >> >> >> >> > [INFO]
>>> >> >> >> >> >
>>> >> >> >>
>>> >> ------------------------------------------------------------------------
>>> >> >> >> >> > [INFO] command line returned non-zero value:1
>>> >> >> >> >> > [INFO]
>>> >> >> >> >> >
>>> >> >> >>
>>> >> ------------------------------------------------------------------------
>>> >> >> >> >> > [INFO] Trace
>>> >> >> >> >> > org.apache.maven.BuildFailureException: command line returned
>>> >> >> non-zero
>>> >> >> >> >> > value:1
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> >> >> > ultLifecycleExecutor.java:715)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> >> >> >> >> > ltLifecycleExecutor.java:535)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> >> >> >> >> > fecycleExecutor.java:180)
>>> >> >> >> >> >        at
>>> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> >> >> >> >> >        at
>>> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> >> >> >> >> >        at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>>> >> >> >> >> > 0)
>>> >> >> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >> >> Method)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> >> >> >> >> > java:39)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> >> >> >> >> > sorImpl.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.MojoFailureException:
>>> command
>>> >> >> line
>>> >> >> >> >> > returned n
>>> >> >> >> >> > on-zero value:1
>>> >> >> >> >> >        at
>>> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>>> >> >> >> >> > rt.java:124)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>>> >> >> >> >> > port.java:54)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>>> >> >> >> >> > 208)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>>> >> >> >> >> > rt.java:29)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> >> >> >> >> > nManager.java:490)
>>> >> >> >> >> >        at
>>> >> >> >> >> >
>>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> >> >> > ultLifecycleExecutor.java:694)
>>> >> >> >> >> >        ... 17 more
>>> >> >> >> >> > [INFO]
>>> >> >> >> >> >
>>> >> >> >>
>>> >> ------------------------------------------------------------------------
>>> >> >> >> >> > [INFO] Total time: 23 seconds
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>>> >> vdichev@gmail.com>
>>> >> >> >> wrote:
>>> >> >> >> >> >
>>> >> >> >> >> > > > Yes
>>> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
>>> >> >> >> >> > > >
>>> >> >> >> >> > > > What's the mean " command line returned non-zero value:1"
>>> in
>>> >> >> >> maven?
>>> >> >> >> >> > >
>>> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
>>> maven
>>> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>>> >> >> >> >> > >
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> > --
>>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >> >> >
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >> --
>>> >> >> >> >> Lift, the simply functional web framework http://liftweb.net
>>> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>>> >> >> >> >> Follow me: http://twitter.com/dpp
>>> >> >> >> >> Surf the harmonics
>>> >> >> >> >>
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > --
>>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >> >
>>> >> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > --
>>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >
>>>
>>
>>
>>
>> --
>> Scala中文社区:  http://groups.google.com/group/scalacn
>>
>

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Great.

After the cool stuff that you have done for us, I thought I should
return the favor and help you as well. :->

D.

On Sun, Nov 8, 2009 at 8:54 AM, Xuefeng Wu <be...@gmail.com> wrote:
> @D
> It worked after I changed network and delete  .m2 repository.
>
> Thank you for your patient and help.
>
>
> 2009/11/6 Xuefeng Wu <be...@gmail.com>
>
>> I don't know which one is incorrect.
>> I will delete .m2 repository and try again when change network .
>>
>> On Fri, Nov 6, 2009 at 5:19 PM, Richard Hirsch <hi...@gmail.com>wrote:
>>
>>> you could try and install the dependencies manually.
>>>
>>> D.
>>>
>>> 2009/11/6 Xuefeng Wu <be...@gmail.com>:
>>> > @D
>>> > Yes, I think so.
>>> > One of my old lift project is very simple,
>>> > and occur the same problem.
>>> >
>>> > I found that one of dependence jar file is not downloaded completely.
>>> > After I delete the jar file and mvn  again. the simple project worked
>>> again.
>>> >
>>> >
>>> > On Fri, Nov 6, 2009 at 5:05 PM, Richard Hirsch <hirsch.dick@gmail.com
>>> >wrote:
>>> >
>>> >> The build was successful.
>>> >>
>>> >> Could it be that some network issues are preventing you from accessing
>>> >> particular Jar files?
>>> >>
>>> >> D.
>>> >>
>>> >> On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com>
>>> >> wrote:
>>> >> > OK.
>>> >> >
>>> >> > I just installed apache-maven-2.2.1.
>>> >> >
>>> >> > I'm doing a build (mvn clean install) after deleting my .m2
>>> directory.
>>> >> >
>>> >> > I'll update this thread with the results when the build is finished.
>>> >> >
>>> >> > D.
>>> >> >
>>> >> > On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> >> @D
>>> >> >> Thank you for your patient,
>>> >> >>
>>> >> >> I uploaded the trace in Jira now
>>> >> >>
>>> >> >> And one of my old lift project cause the same probleam
>>> >> >> and it worked after use 'mvn -X clean install'.
>>> >> >>
>>> >> >> I think maybe some of .m2 repository is broken.
>>> >> >>
>>> >> >> I deleted ,m2 repository but didn't work and
>>> >> >> I think maybe  maven cannot download full jar files because network.
>>> >> >> I will try again in anther network environment.
>>> >> >>
>>> >> >> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <
>>> hirsch.dick@gmail.com
>>> >> >wrote:
>>> >> >>
>>> >> >>> Definitely a tough problem.
>>> >> >>>
>>> >> >>> Let's try this:
>>> >> >>>
>>> >> >>> 1. Delete ,m2 repository
>>> >> >>> 2. Get the latest code drop from the SVN and put it in a new
>>> directory
>>> >> >>> 3. Do a  "mvn -X clean install > trace"
>>> >> >>> 4. Upload the trace to the Jira Item.
>>> >> >>>
>>> >> >>> D.
>>> >> >>>
>>> >> >>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com>
>>> wrote:
>>> >> >>> > I comment the opendmk but didn't find scala-stats and configgy is
>>> >> >>> dependency
>>> >> >>> > exception the repository.
>>> >> >>> > I uploaded the maven log.
>>> >> >>> >
>>> >> >>> > I think I didn't change anything, and other scala lift projects
>>> are
>>> >> >>> working
>>> >> >>> > well in the same environment.
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <
>>> >> hirsch.dick@gmail.com
>>> >> >>> >wrote:
>>> >> >>> >
>>> >> >>> >> What about changing the pom.xml and removing the dependencies
>>> for
>>> >> >>> >> scala-stats, configgy and opendmk. You will get compile errors
>>> but I
>>> >> >>> >> want to see if that solves basic problem.
>>> >> >>> >>
>>> >> >>> >> I'll compare your environment to my environment at work and see
>>> if I
>>> >> >>> >> see other diffs.
>>> >> >>> >>
>>> >> >>> >> Are you sure that nothing else changed in your env?
>>> >> >>> >>
>>> >> >>> >> D.
>>> >> >>> >>
>>> >> >>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com>
>>> >> wrote:
>>> >> >>> >> > @D
>>> >> >>> >> > Oops
>>> >> >>> >> > I deleted  the .m2 repository but failed too....
>>> >> >>> >> >
>>> >> >>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <
>>> >> hirsch.dick@gmail.com
>>> >> >>> >> >wrote:
>>> >> >>> >> >
>>> >> >>> >> >> Looked at the log in the Jira item and compared it to my own
>>> log.
>>> >> I
>>> >> >>> >> >> only see a few differences related to the dependencies
>>>  related
>>> >> to
>>> >> >>> JMX
>>> >> >>> >> >> functionality.
>>> >> >>> >> >>
>>> >> >>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking
>>> for
>>> >> >>> >> >> updates from scala-stats
>>> >> >>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
>>> >> local =
>>> >> >>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>>> >> >>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >> >> Did you try and delete the .m2 repository. If you don't want
>>> to
>>> >> >>> delete
>>> >> >>> >> >> it what about renaming it.
>>> >> >>> >> >>
>>> >> >>> >> >> D.
>>> >> >>> >> >>
>>> >> >>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <benewu@gmail.com
>>> >
>>> >> wrote:
>>> >> >>> >> >> > Done,
>>> >> >>> >> >> > attached
>>> >> >>> >> >> >
>>> >> >>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
>>> >> >>> hirsch.dick@gmail.com
>>> >> >>> >> >> >wrote:
>>> >> >>> >> >> >
>>> >> >>> >> >> >> Saw Jira item. Thanks.
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> But we still need to see the entire log.  Could you attach
>>> it
>>> >> to
>>> >> >>> the
>>> >> >>> >> >> >> item as an attachment.
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> The one link you posted in the Jira item about the Lift
>>> error
>>> >> in
>>> >> >>> >> >> >> Hudson looks very similar. Once we get the entire maven
>>> log,
>>> >> it
>>> >> >>> will
>>> >> >>> >> >> >> be a lot easier to see if this is the problem.
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> D.
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <
>>> benewu@gmail.com>
>>> >> >>> wrote:
>>> >> >>> >> >> >> > @D.
>>> >> >>> >> >> >> > I created
>>> https://issues.apache.org/jira/browse/ESME-118
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> > Thanks.
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>>> >> >>> >> hirsch.dick@gmail.com
>>> >> >>> >> >> >> >wrote:
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >> Why don't you create a Jira item and attach the entire
>>> >> trace as
>>> >> >>> an
>>> >> >>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> We can then get a better idea of what is going on.
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> D.
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <
>>> >> benewu@gmail.com>
>>> >> >>> >> wrote:
>>> >> >>> >> >> >> >> > Thank you for your response.
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> > @D
>>> >> >>> >> >> >> >> > I checked out new from SVN but failed too.
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> > @David
>>> >> >>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too
>>> ,
>>> >> get
>>> >> >>> the
>>> >> >>> >> >> same
>>> >> >>> >> >> >> >> error:
>>> >> >>> >> >> >> >> > command line returned non-zero value:1
>>> >> >>> >> >> >> >> > I didn't rename .m2 folder and my other maven
>>> projects
>>> >> are
>>> >> >>> >> working.
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>>> >> >>> >> >> >> >> > <fe...@gmail.com>wrote:
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> >> Did you do a successful "mvn -U clean install
>>> jetty:run"
>>> >> >>> before
>>> >> >>> >> >> >> trying
>>> >> >>> >> >> >> >> to
>>> >> >>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2
>>> >> before
>>> >> >>> >> starting
>>> >> >>> >> >> >> the
>>> >> >>> >> >> >> >> >> process?
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
>>> >> >>> benewu@gmail.com>
>>> >> >>> >> >> wrote:
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >> > I run mvn clean install -e
>>> >> >>> >> >> >> >> >> > get:
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> > [WARNING] 204 errors found
>>> >> >>> >> >> >> >> >> > [INFO]
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >>
>>> >> >>> >> >>
>>> >> >>>
>>> >>
>>> ------------------------------------------------------------------------
>>> >> >>> >> >> >> >> >> > [ERROR] BUILD FAILURE
>>> >> >>> >> >> >> >> >> > [INFO]
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >>
>>> >> >>> >> >>
>>> >> >>>
>>> >>
>>> ------------------------------------------------------------------------
>>> >> >>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
>>> >> >>> >> >> >> >> >> > [INFO]
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >>
>>> >> >>> >> >>
>>> >> >>>
>>> >>
>>> ------------------------------------------------------------------------
>>> >> >>> >> >> >> >> >> > [INFO] Trace
>>> >> >>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command
>>> line
>>> >> >>> returned
>>> >> >>> >> >> >> non-zero
>>> >> >>> >> >> >> >> >> > value:1
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> >> >>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> >> >>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> >> >>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> >> >>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> >> >>> >> >> >> >> >> > fecycleExecutor.java:180)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >>
>>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >>
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>>> >> >>> >> >> >> >> >> > 0)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >> >>> >> >> >> Method)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> >> >>> >> >> >> >> >> > java:39)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> >> >>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
>>> >> >>> >> command
>>> >> >>> >> >> >> line
>>> >> >>> >> >> >> >> >> > returned n
>>> >> >>> >> >> >> >> >> > on-zero value:1
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >>
>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>>> >> >>> >> >> >> >> >> > rt.java:124)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>>> >> >>> >> >> >> >> >> > port.java:54)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>>> >> >>> >> >> >> >> >> > 208)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>>> >> >>> >> >> >> >> >> > rt.java:29)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> >> >>> >> >> >> >> >> > nManager.java:490)
>>> >> >>> >> >> >> >> >> >        at
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
>>> >> >>> >> >> >> >> >> >        ... 17 more
>>> >> >>> >> >> >> >> >> > [INFO]
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >>
>>> >> >>> >> >>
>>> >> >>>
>>> >>
>>> ------------------------------------------------------------------------
>>> >> >>> >> >> >> >> >> > [INFO] Total time: 23 seconds
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>>> >> >>> >> >> vdichev@gmail.com>
>>> >> >>> >> >> >> >> wrote:
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> > > > Yes
>>> >> >>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the
>>> same
>>> >> >>> error:
>>> >> >>> >> >> >> >> >> > > >
>>> >> >>> >> >> >> >> >> > > > What's the mean " command line returned
>>> non-zero
>>> >> >>> value:1"
>>> >> >>> >> in
>>> >> >>> >> >> >> >> maven?
>>> >> >>> >> >> >> >> >> > >
>>> >> >>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't
>>> you
>>> >> do as
>>> >> >>> >> maven
>>> >> >>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>>> >> >>> >> >> >> >> >> > >
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >> > --
>>> >> >>> >> >> >> >> >> > Scala中文社区:
>>> http://groups.google.com/group/scalacn
>>> >> >>> >> >> >> >> >> >
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >> --
>>> >> >>> >> >> >> >> >> Lift, the simply functional web framework
>>> >> >>> http://liftweb.net
>>> >> >>> >> >> >> >> >> Beginning Scala
>>> >> http://www.apress.com/book/view/1430219890
>>> >> >>> >> >> >> >> >> Follow me: http://twitter.com/dpp
>>> >> >>> >> >> >> >> >> Surf the harmonics
>>> >> >>> >> >> >> >> >>
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >> > --
>>> >> >>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>> >> >> >> >> >
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> > --
>>> >> >>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >>
>>> >> >>> >> >> >
>>> >> >>> >> >> >
>>> >> >>> >> >> >
>>> >> >>> >> >> > --
>>> >> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>> >> >> >
>>> >> >>> >> >>
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> > --
>>> >> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>> >> >
>>> >> >>> >>
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>> >
>>> >> >>>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >>
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >
>>>
>>
>>
>>
>> --
>> Scala中文社区:  http://groups.google.com/group/scalacn
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
@D
It worked after I changed network and delete  .m2 repository.

Thank you for your patient and help.


2009/11/6 Xuefeng Wu <be...@gmail.com>

> I don't know which one is incorrect.
> I will delete .m2 repository and try again when change network .
>
> On Fri, Nov 6, 2009 at 5:19 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> you could try and install the dependencies manually.
>>
>> D.
>>
>> 2009/11/6 Xuefeng Wu <be...@gmail.com>:
>> > @D
>> > Yes, I think so.
>> > One of my old lift project is very simple,
>> > and occur the same problem.
>> >
>> > I found that one of dependence jar file is not downloaded completely.
>> > After I delete the jar file and mvn  again. the simple project worked
>> again.
>> >
>> >
>> > On Fri, Nov 6, 2009 at 5:05 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> The build was successful.
>> >>
>> >> Could it be that some network issues are preventing you from accessing
>> >> particular Jar files?
>> >>
>> >> D.
>> >>
>> >> On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com>
>> >> wrote:
>> >> > OK.
>> >> >
>> >> > I just installed apache-maven-2.2.1.
>> >> >
>> >> > I'm doing a build (mvn clean install) after deleting my .m2
>> directory.
>> >> >
>> >> > I'll update this thread with the results when the build is finished.
>> >> >
>> >> > D.
>> >> >
>> >> > On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> >> @D
>> >> >> Thank you for your patient,
>> >> >>
>> >> >> I uploaded the trace in Jira now
>> >> >>
>> >> >> And one of my old lift project cause the same probleam
>> >> >> and it worked after use 'mvn -X clean install'.
>> >> >>
>> >> >> I think maybe some of .m2 repository is broken.
>> >> >>
>> >> >> I deleted ,m2 repository but didn't work and
>> >> >> I think maybe  maven cannot download full jar files because network.
>> >> >> I will try again in anther network environment.
>> >> >>
>> >> >> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <
>> hirsch.dick@gmail.com
>> >> >wrote:
>> >> >>
>> >> >>> Definitely a tough problem.
>> >> >>>
>> >> >>> Let's try this:
>> >> >>>
>> >> >>> 1. Delete ,m2 repository
>> >> >>> 2. Get the latest code drop from the SVN and put it in a new
>> directory
>> >> >>> 3. Do a  "mvn -X clean install > trace"
>> >> >>> 4. Upload the trace to the Jira Item.
>> >> >>>
>> >> >>> D.
>> >> >>>
>> >> >>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >> >>> > I comment the opendmk but didn't find scala-stats and configgy is
>> >> >>> dependency
>> >> >>> > exception the repository.
>> >> >>> > I uploaded the maven log.
>> >> >>> >
>> >> >>> > I think I didn't change anything, and other scala lift projects
>> are
>> >> >>> working
>> >> >>> > well in the same environment.
>> >> >>> >
>> >> >>> >
>> >> >>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <
>> >> hirsch.dick@gmail.com
>> >> >>> >wrote:
>> >> >>> >
>> >> >>> >> What about changing the pom.xml and removing the dependencies
>> for
>> >> >>> >> scala-stats, configgy and opendmk. You will get compile errors
>> but I
>> >> >>> >> want to see if that solves basic problem.
>> >> >>> >>
>> >> >>> >> I'll compare your environment to my environment at work and see
>> if I
>> >> >>> >> see other diffs.
>> >> >>> >>
>> >> >>> >> Are you sure that nothing else changed in your env?
>> >> >>> >>
>> >> >>> >> D.
>> >> >>> >>
>> >> >>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com>
>> >> wrote:
>> >> >>> >> > @D
>> >> >>> >> > Oops
>> >> >>> >> > I deleted  the .m2 repository but failed too....
>> >> >>> >> >
>> >> >>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <
>> >> hirsch.dick@gmail.com
>> >> >>> >> >wrote:
>> >> >>> >> >
>> >> >>> >> >> Looked at the log in the Jira item and compared it to my own
>> log.
>> >> I
>> >> >>> >> >> only see a few differences related to the dependencies
>>  related
>> >> to
>> >> >>> JMX
>> >> >>> >> >> functionality.
>> >> >>> >> >>
>> >> >>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking
>> for
>> >> >>> >> >> updates from scala-stats
>> >> >>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
>> >> local =
>> >> >>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>> >> >>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >> >> Did you try and delete the .m2 repository. If you don't want
>> to
>> >> >>> delete
>> >> >>> >> >> it what about renaming it.
>> >> >>> >> >>
>> >> >>> >> >> D.
>> >> >>> >> >>
>> >> >>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <benewu@gmail.com
>> >
>> >> wrote:
>> >> >>> >> >> > Done,
>> >> >>> >> >> > attached
>> >> >>> >> >> >
>> >> >>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
>> >> >>> hirsch.dick@gmail.com
>> >> >>> >> >> >wrote:
>> >> >>> >> >> >
>> >> >>> >> >> >> Saw Jira item. Thanks.
>> >> >>> >> >> >>
>> >> >>> >> >> >> But we still need to see the entire log.  Could you attach
>> it
>> >> to
>> >> >>> the
>> >> >>> >> >> >> item as an attachment.
>> >> >>> >> >> >>
>> >> >>> >> >> >> The one link you posted in the Jira item about the Lift
>> error
>> >> in
>> >> >>> >> >> >> Hudson looks very similar. Once we get the entire maven
>> log,
>> >> it
>> >> >>> will
>> >> >>> >> >> >> be a lot easier to see if this is the problem.
>> >> >>> >> >> >>
>> >> >>> >> >> >> D.
>> >> >>> >> >> >>
>> >> >>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <
>> benewu@gmail.com>
>> >> >>> wrote:
>> >> >>> >> >> >> > @D.
>> >> >>> >> >> >> > I created
>> https://issues.apache.org/jira/browse/ESME-118
>> >> >>> >> >> >> >
>> >> >>> >> >> >> > Thanks.
>> >> >>> >> >> >> >
>> >> >>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>> >> >>> >> hirsch.dick@gmail.com
>> >> >>> >> >> >> >wrote:
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >> Why don't you create a Jira item and attach the entire
>> >> trace as
>> >> >>> an
>> >> >>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> We can then get a better idea of what is going on.
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> D.
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <
>> >> benewu@gmail.com>
>> >> >>> >> wrote:
>> >> >>> >> >> >> >> > Thank you for your response.
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> > @D
>> >> >>> >> >> >> >> > I checked out new from SVN but failed too.
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> > @David
>> >> >>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too
>> ,
>> >> get
>> >> >>> the
>> >> >>> >> >> same
>> >> >>> >> >> >> >> error:
>> >> >>> >> >> >> >> > command line returned non-zero value:1
>> >> >>> >> >> >> >> > I didn't rename .m2 folder and my other maven
>> projects
>> >> are
>> >> >>> >> working.
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >> >>> >> >> >> >> > <fe...@gmail.com>wrote:
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> >> Did you do a successful "mvn -U clean install
>> jetty:run"
>> >> >>> before
>> >> >>> >> >> >> trying
>> >> >>> >> >> >> >> to
>> >> >>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2
>> >> before
>> >> >>> >> starting
>> >> >>> >> >> >> the
>> >> >>> >> >> >> >> >> process?
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
>> >> >>> benewu@gmail.com>
>> >> >>> >> >> wrote:
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >> > I run mvn clean install -e
>> >> >>> >> >> >> >> >> > get:
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> > [WARNING] 204 errors found
>> >> >>> >> >> >> >> >> > [INFO]
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >>
>> >> >>> >> >>
>> >> >>>
>> >>
>> ------------------------------------------------------------------------
>> >> >>> >> >> >> >> >> > [ERROR] BUILD FAILURE
>> >> >>> >> >> >> >> >> > [INFO]
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >>
>> >> >>> >> >>
>> >> >>>
>> >>
>> ------------------------------------------------------------------------
>> >> >>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
>> >> >>> >> >> >> >> >> > [INFO]
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >>
>> >> >>> >> >>
>> >> >>>
>> >>
>> ------------------------------------------------------------------------
>> >> >>> >> >> >> >> >> > [INFO] Trace
>> >> >>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command
>> line
>> >> >>> returned
>> >> >>> >> >> >> non-zero
>> >> >>> >> >> >> >> >> > value:1
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >>> >> >> >> >> >> > fecycleExecutor.java:180)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >>
>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >>
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> >>> >> >> >> >> >> > 0)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >> >>> >> >> >> Method)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >>> >> >> >> >> >> > java:39)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
>> >> >>> >> command
>> >> >>> >> >> >> line
>> >> >>> >> >> >> >> >> > returned n
>> >> >>> >> >> >> >> >> > on-zero value:1
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >>
>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> >>> >> >> >> >> >> > rt.java:124)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> >>> >> >> >> >> >> > port.java:54)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> >>> >> >> >> >> >> > 208)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> >>> >> >> >> >> >> > rt.java:29)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >>> >> >> >> >> >> > nManager.java:490)
>> >> >>> >> >> >> >> >> >        at
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >>
>> >> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
>> >> >>> >> >> >> >> >> >        ... 17 more
>> >> >>> >> >> >> >> >> > [INFO]
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >>
>> >> >>> >> >>
>> >> >>>
>> >>
>> ------------------------------------------------------------------------
>> >> >>> >> >> >> >> >> > [INFO] Total time: 23 seconds
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>> >> >>> >> >> vdichev@gmail.com>
>> >> >>> >> >> >> >> wrote:
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> > > > Yes
>> >> >>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the
>> same
>> >> >>> error:
>> >> >>> >> >> >> >> >> > > >
>> >> >>> >> >> >> >> >> > > > What's the mean " command line returned
>> non-zero
>> >> >>> value:1"
>> >> >>> >> in
>> >> >>> >> >> >> >> maven?
>> >> >>> >> >> >> >> >> > >
>> >> >>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't
>> you
>> >> do as
>> >> >>> >> maven
>> >> >>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>> >> >>> >> >> >> >> >> > >
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >> > --
>> >> >>> >> >> >> >> >> > Scala中文社区:
>> http://groups.google.com/group/scalacn
>> >> >>> >> >> >> >> >> >
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >> --
>> >> >>> >> >> >> >> >> Lift, the simply functional web framework
>> >> >>> http://liftweb.net
>> >> >>> >> >> >> >> >> Beginning Scala
>> >> http://www.apress.com/book/view/1430219890
>> >> >>> >> >> >> >> >> Follow me: http://twitter.com/dpp
>> >> >>> >> >> >> >> >> Surf the harmonics
>> >> >>> >> >> >> >> >>
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >> > --
>> >> >>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>> >> >> >> >> >
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >
>> >> >>> >> >> >> > --
>> >> >>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>> >> >> >> >
>> >> >>> >> >> >>
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> > --
>> >> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>> >> >> >
>> >> >>> >> >>
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> > --
>> >> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>> >> >
>> >> >>> >>
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > --
>> >> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>> >
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >>
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
I don't know which one is incorrect.
I will delete .m2 repository and try again when change network .

On Fri, Nov 6, 2009 at 5:19 PM, Richard Hirsch <hi...@gmail.com>wrote:

> you could try and install the dependencies manually.
>
> D.
>
> 2009/11/6 Xuefeng Wu <be...@gmail.com>:
> > @D
> > Yes, I think so.
> > One of my old lift project is very simple,
> > and occur the same problem.
> >
> > I found that one of dependence jar file is not downloaded completely.
> > After I delete the jar file and mvn  again. the simple project worked
> again.
> >
> >
> > On Fri, Nov 6, 2009 at 5:05 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> The build was successful.
> >>
> >> Could it be that some network issues are preventing you from accessing
> >> particular Jar files?
> >>
> >> D.
> >>
> >> On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com>
> >> wrote:
> >> > OK.
> >> >
> >> > I just installed apache-maven-2.2.1.
> >> >
> >> > I'm doing a build (mvn clean install) after deleting my .m2 directory.
> >> >
> >> > I'll update this thread with the results when the build is finished.
> >> >
> >> > D.
> >> >
> >> > On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> >> @D
> >> >> Thank you for your patient,
> >> >>
> >> >> I uploaded the trace in Jira now
> >> >>
> >> >> And one of my old lift project cause the same probleam
> >> >> and it worked after use 'mvn -X clean install'.
> >> >>
> >> >> I think maybe some of .m2 repository is broken.
> >> >>
> >> >> I deleted ,m2 repository but didn't work and
> >> >> I think maybe  maven cannot download full jar files because network.
> >> >> I will try again in anther network environment.
> >> >>
> >> >> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <
> hirsch.dick@gmail.com
> >> >wrote:
> >> >>
> >> >>> Definitely a tough problem.
> >> >>>
> >> >>> Let's try this:
> >> >>>
> >> >>> 1. Delete ,m2 repository
> >> >>> 2. Get the latest code drop from the SVN and put it in a new
> directory
> >> >>> 3. Do a  "mvn -X clean install > trace"
> >> >>> 4. Upload the trace to the Jira Item.
> >> >>>
> >> >>> D.
> >> >>>
> >> >>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >> >>> > I comment the opendmk but didn't find scala-stats and configgy is
> >> >>> dependency
> >> >>> > exception the repository.
> >> >>> > I uploaded the maven log.
> >> >>> >
> >> >>> > I think I didn't change anything, and other scala lift projects
> are
> >> >>> working
> >> >>> > well in the same environment.
> >> >>> >
> >> >>> >
> >> >>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <
> >> hirsch.dick@gmail.com
> >> >>> >wrote:
> >> >>> >
> >> >>> >> What about changing the pom.xml and removing the dependencies for
> >> >>> >> scala-stats, configgy and opendmk. You will get compile errors
> but I
> >> >>> >> want to see if that solves basic problem.
> >> >>> >>
> >> >>> >> I'll compare your environment to my environment at work and see
> if I
> >> >>> >> see other diffs.
> >> >>> >>
> >> >>> >> Are you sure that nothing else changed in your env?
> >> >>> >>
> >> >>> >> D.
> >> >>> >>
> >> >>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com>
> >> wrote:
> >> >>> >> > @D
> >> >>> >> > Oops
> >> >>> >> > I deleted  the .m2 repository but failed too....
> >> >>> >> >
> >> >>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <
> >> hirsch.dick@gmail.com
> >> >>> >> >wrote:
> >> >>> >> >
> >> >>> >> >> Looked at the log in the Jira item and compared it to my own
> log.
> >> I
> >> >>> >> >> only see a few differences related to the dependencies
>  related
> >> to
> >> >>> JMX
> >> >>> >> >> functionality.
> >> >>> >> >>
> >> >>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking
> for
> >> >>> >> >> updates from scala-stats
> >> >>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
> >> local =
> >> >>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> >> >>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >> Did you try and delete the .m2 repository. If you don't want
> to
> >> >>> delete
> >> >>> >> >> it what about renaming it.
> >> >>> >> >>
> >> >>> >> >> D.
> >> >>> >> >>
> >> >>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com>
> >> wrote:
> >> >>> >> >> > Done,
> >> >>> >> >> > attached
> >> >>> >> >> >
> >> >>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
> >> >>> hirsch.dick@gmail.com
> >> >>> >> >> >wrote:
> >> >>> >> >> >
> >> >>> >> >> >> Saw Jira item. Thanks.
> >> >>> >> >> >>
> >> >>> >> >> >> But we still need to see the entire log.  Could you attach
> it
> >> to
> >> >>> the
> >> >>> >> >> >> item as an attachment.
> >> >>> >> >> >>
> >> >>> >> >> >> The one link you posted in the Jira item about the Lift
> error
> >> in
> >> >>> >> >> >> Hudson looks very similar. Once we get the entire maven
> log,
> >> it
> >> >>> will
> >> >>> >> >> >> be a lot easier to see if this is the problem.
> >> >>> >> >> >>
> >> >>> >> >> >> D.
> >> >>> >> >> >>
> >> >>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <
> benewu@gmail.com>
> >> >>> wrote:
> >> >>> >> >> >> > @D.
> >> >>> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
> >> >>> >> >> >> >
> >> >>> >> >> >> > Thanks.
> >> >>> >> >> >> >
> >> >>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
> >> >>> >> hirsch.dick@gmail.com
> >> >>> >> >> >> >wrote:
> >> >>> >> >> >> >
> >> >>> >> >> >> >> Why don't you create a Jira item and attach the entire
> >> trace as
> >> >>> an
> >> >>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> We can then get a better idea of what is going on.
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> D.
> >> >>> >> >> >> >>
> >> >>> >> >> >> >>
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <
> >> benewu@gmail.com>
> >> >>> >> wrote:
> >> >>> >> >> >> >> > Thank you for your response.
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> > @D
> >> >>> >> >> >> >> > I checked out new from SVN but failed too.
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> > @David
> >> >>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too
> ,
> >> get
> >> >>> the
> >> >>> >> >> same
> >> >>> >> >> >> >> error:
> >> >>> >> >> >> >> > command line returned non-zero value:1
> >> >>> >> >> >> >> > I didn't rename .m2 folder and my other maven projects
> >> are
> >> >>> >> working.
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >> >>> >> >> >> >> > <fe...@gmail.com>wrote:
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> >> Did you do a successful "mvn -U clean install
> jetty:run"
> >> >>> before
> >> >>> >> >> >> trying
> >> >>> >> >> >> >> to
> >> >>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2
> >> before
> >> >>> >> starting
> >> >>> >> >> >> the
> >> >>> >> >> >> >> >> process?
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
> >> >>> benewu@gmail.com>
> >> >>> >> >> wrote:
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >> > I run mvn clean install -e
> >> >>> >> >> >> >> >> > get:
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> > [WARNING] 204 errors found
> >> >>> >> >> >> >> >> > [INFO]
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >>
> >> >>> >> >>
> >> >>>
> >> ------------------------------------------------------------------------
> >> >>> >> >> >> >> >> > [ERROR] BUILD FAILURE
> >> >>> >> >> >> >> >> > [INFO]
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >>
> >> >>> >> >>
> >> >>>
> >> ------------------------------------------------------------------------
> >> >>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
> >> >>> >> >> >> >> >> > [INFO]
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >>
> >> >>> >> >>
> >> >>>
> >> ------------------------------------------------------------------------
> >> >>> >> >> >> >> >> > [INFO] Trace
> >> >>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command
> line
> >> >>> returned
> >> >>> >> >> >> non-zero
> >> >>> >> >> >> >> >> > value:1
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >>> >> >> >> >> >> > fecycleExecutor.java:180)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >>
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >>
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> >>> >> >> >> >> >> > 0)
> >> >>> >> >> >> >> >> >        at
> >> >>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >>> >> >> >> Method)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >>> >> >> >> >> >> > java:39)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
> >> >>> >> command
> >> >>> >> >> >> line
> >> >>> >> >> >> >> >> > returned n
> >> >>> >> >> >> >> >> > on-zero value:1
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> >>> >> >> >> >> >> > rt.java:124)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> >>> >> >> >> >> >> > port.java:54)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> >>> >> >> >> >> >> > 208)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> >>> >> >> >> >> >> > rt.java:29)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >>> >> >> >> >> >> > nManager.java:490)
> >> >>> >> >> >> >> >> >        at
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >>
> >> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
> >> >>> >> >> >> >> >> >        ... 17 more
> >> >>> >> >> >> >> >> > [INFO]
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >>
> >> >>> >> >>
> >> >>>
> >> ------------------------------------------------------------------------
> >> >>> >> >> >> >> >> > [INFO] Total time: 23 seconds
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> >> >>> >> >> vdichev@gmail.com>
> >> >>> >> >> >> >> wrote:
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> > > > Yes
> >> >>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the
> same
> >> >>> error:
> >> >>> >> >> >> >> >> > > >
> >> >>> >> >> >> >> >> > > > What's the mean " command line returned
> non-zero
> >> >>> value:1"
> >> >>> >> in
> >> >>> >> >> >> >> maven?
> >> >>> >> >> >> >> >> > >
> >> >>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't
> you
> >> do as
> >> >>> >> maven
> >> >>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
> >> >>> >> >> >> >> >> > >
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >> > --
> >> >>> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >> >> >> >> >> >
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >> --
> >> >>> >> >> >> >> >> Lift, the simply functional web framework
> >> >>> http://liftweb.net
> >> >>> >> >> >> >> >> Beginning Scala
> >> http://www.apress.com/book/view/1430219890
> >> >>> >> >> >> >> >> Follow me: http://twitter.com/dpp
> >> >>> >> >> >> >> >> Surf the harmonics
> >> >>> >> >> >> >> >>
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >> > --
> >> >>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >> >> >> >> >
> >> >>> >> >> >> >>
> >> >>> >> >> >> >
> >> >>> >> >> >> >
> >> >>> >> >> >> >
> >> >>> >> >> >> > --
> >> >>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >> >> >> >
> >> >>> >> >> >>
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> > --
> >> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >> >> >
> >> >>> >> >>
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > --
> >> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >> >
> >> >>> >>
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > --
> >> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Scala中文社区:  http://groups.google.com/group/scalacn
> >> >>
> >> >
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
you could try and install the dependencies manually.

D.

2009/11/6 Xuefeng Wu <be...@gmail.com>:
> @D
> Yes, I think so.
> One of my old lift project is very simple,
> and occur the same problem.
>
> I found that one of dependence jar file is not downloaded completely.
> After I delete the jar file and mvn  again. the simple project worked again.
>
>
> On Fri, Nov 6, 2009 at 5:05 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> The build was successful.
>>
>> Could it be that some network issues are preventing you from accessing
>> particular Jar files?
>>
>> D.
>>
>> On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com>
>> wrote:
>> > OK.
>> >
>> > I just installed apache-maven-2.2.1.
>> >
>> > I'm doing a build (mvn clean install) after deleting my .m2 directory.
>> >
>> > I'll update this thread with the results when the build is finished.
>> >
>> > D.
>> >
>> > On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> @D
>> >> Thank you for your patient,
>> >>
>> >> I uploaded the trace in Jira now
>> >>
>> >> And one of my old lift project cause the same probleam
>> >> and it worked after use 'mvn -X clean install'.
>> >>
>> >> I think maybe some of .m2 repository is broken.
>> >>
>> >> I deleted ,m2 repository but didn't work and
>> >> I think maybe  maven cannot download full jar files because network.
>> >> I will try again in anther network environment.
>> >>
>> >> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >>
>> >>> Definitely a tough problem.
>> >>>
>> >>> Let's try this:
>> >>>
>> >>> 1. Delete ,m2 repository
>> >>> 2. Get the latest code drop from the SVN and put it in a new directory
>> >>> 3. Do a  "mvn -X clean install > trace"
>> >>> 4. Upload the trace to the Jira Item.
>> >>>
>> >>> D.
>> >>>
>> >>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >>> > I comment the opendmk but didn't find scala-stats and configgy is
>> >>> dependency
>> >>> > exception the repository.
>> >>> > I uploaded the maven log.
>> >>> >
>> >>> > I think I didn't change anything, and other scala lift projects are
>> >>> working
>> >>> > well in the same environment.
>> >>> >
>> >>> >
>> >>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <
>> hirsch.dick@gmail.com
>> >>> >wrote:
>> >>> >
>> >>> >> What about changing the pom.xml and removing the dependencies for
>> >>> >> scala-stats, configgy and opendmk. You will get compile errors but I
>> >>> >> want to see if that solves basic problem.
>> >>> >>
>> >>> >> I'll compare your environment to my environment at work and see if I
>> >>> >> see other diffs.
>> >>> >>
>> >>> >> Are you sure that nothing else changed in your env?
>> >>> >>
>> >>> >> D.
>> >>> >>
>> >>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >>> >> > @D
>> >>> >> > Oops
>> >>> >> > I deleted  the .m2 repository but failed too....
>> >>> >> >
>> >>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <
>> hirsch.dick@gmail.com
>> >>> >> >wrote:
>> >>> >> >
>> >>> >> >> Looked at the log in the Jira item and compared it to my own log.
>> I
>> >>> >> >> only see a few differences related to the dependencies  related
>> to
>> >>> JMX
>> >>> >> >> functionality.
>> >>> >> >>
>> >>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>> >>> >> >> updates from scala-stats
>> >>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
>> local =
>> >>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>> >>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> Did you try and delete the .m2 repository. If you don't want to
>> >>> delete
>> >>> >> >> it what about renaming it.
>> >>> >> >>
>> >>> >> >> D.
>> >>> >> >>
>> >>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >>> >> >> > Done,
>> >>> >> >> > attached
>> >>> >> >> >
>> >>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
>> >>> hirsch.dick@gmail.com
>> >>> >> >> >wrote:
>> >>> >> >> >
>> >>> >> >> >> Saw Jira item. Thanks.
>> >>> >> >> >>
>> >>> >> >> >> But we still need to see the entire log.  Could you attach it
>> to
>> >>> the
>> >>> >> >> >> item as an attachment.
>> >>> >> >> >>
>> >>> >> >> >> The one link you posted in the Jira item about the Lift error
>> in
>> >>> >> >> >> Hudson looks very similar. Once we get the entire maven log,
>> it
>> >>> will
>> >>> >> >> >> be a lot easier to see if this is the problem.
>> >>> >> >> >>
>> >>> >> >> >> D.
>> >>> >> >> >>
>> >>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com>
>> >>> wrote:
>> >>> >> >> >> > @D.
>> >>> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
>> >>> >> >> >> >
>> >>> >> >> >> > Thanks.
>> >>> >> >> >> >
>> >>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>> >>> >> hirsch.dick@gmail.com
>> >>> >> >> >> >wrote:
>> >>> >> >> >> >
>> >>> >> >> >> >> Why don't you create a Jira item and attach the entire
>> trace as
>> >>> an
>> >>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
>> >>> >> >> >> >>
>> >>> >> >> >> >> We can then get a better idea of what is going on.
>> >>> >> >> >> >>
>> >>> >> >> >> >> D.
>> >>> >> >> >> >>
>> >>> >> >> >> >>
>> >>> >> >> >> >>
>> >>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <
>> benewu@gmail.com>
>> >>> >> wrote:
>> >>> >> >> >> >> > Thank you for your response.
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > @D
>> >>> >> >> >> >> > I checked out new from SVN but failed too.
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > @David
>> >>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too ,
>> get
>> >>> the
>> >>> >> >> same
>> >>> >> >> >> >> error:
>> >>> >> >> >> >> > command line returned non-zero value:1
>> >>> >> >> >> >> > I didn't rename .m2 folder and my other maven projects
>> are
>> >>> >> working.
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >>> >> >> >> >> > <fe...@gmail.com>wrote:
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run"
>> >>> before
>> >>> >> >> >> trying
>> >>> >> >> >> >> to
>> >>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2
>> before
>> >>> >> starting
>> >>> >> >> >> the
>> >>> >> >> >> >> >> process?
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
>> >>> benewu@gmail.com>
>> >>> >> >> wrote:
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> > I run mvn clean install -e
>> >>> >> >> >> >> >> > get:
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > [WARNING] 204 errors found
>> >>> >> >> >> >> >> > [INFO]
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >>
>> >>>
>> ------------------------------------------------------------------------
>> >>> >> >> >> >> >> > [ERROR] BUILD FAILURE
>> >>> >> >> >> >> >> > [INFO]
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >>
>> >>>
>> ------------------------------------------------------------------------
>> >>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
>> >>> >> >> >> >> >> > [INFO]
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >>
>> >>>
>> ------------------------------------------------------------------------
>> >>> >> >> >> >> >> > [INFO] Trace
>> >>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command line
>> >>> returned
>> >>> >> >> >> non-zero
>> >>> >> >> >> >> >> > value:1
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >>> >> >> >> >> >> > fecycleExecutor.java:180)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >>
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >>> >> >> >> >> >> >        at
>> >>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >>> >> >> >> >> >> > 0)
>> >>> >> >> >> >> >> >        at
>> >>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>> >> >> >> Method)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>> >> >> >> >> >> > java:39)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
>> >>> >> command
>> >>> >> >> >> line
>> >>> >> >> >> >> >> > returned n
>> >>> >> >> >> >> >> > on-zero value:1
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >>> >> >> >> >> >> > rt.java:124)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >>> >> >> >> >> >> > port.java:54)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >>> >> >> >> >> >> > 208)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >>> >> >> >> >> >> > rt.java:29)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >>> >> >> >> >> >> > nManager.java:490)
>> >>> >> >> >> >> >> >        at
>> >>> >> >> >> >> >> >
>> >>> >> >> >>
>> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
>> >>> >> >> >> >> >> >        ... 17 more
>> >>> >> >> >> >> >> > [INFO]
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >>
>> >>>
>> ------------------------------------------------------------------------
>> >>> >> >> >> >> >> > [INFO] Total time: 23 seconds
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>> >>> >> >> vdichev@gmail.com>
>> >>> >> >> >> >> wrote:
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > > > Yes
>> >>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same
>> >>> error:
>> >>> >> >> >> >> >> > > >
>> >>> >> >> >> >> >> > > > What's the mean " command line returned non-zero
>> >>> value:1"
>> >>> >> in
>> >>> >> >> >> >> maven?
>> >>> >> >> >> >> >> > >
>> >>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't you
>> do as
>> >>> >> maven
>> >>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>> >>> >> >> >> >> >> > >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > --
>> >>> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> --
>> >>> >> >> >> >> >> Lift, the simply functional web framework
>> >>> http://liftweb.net
>> >>> >> >> >> >> >> Beginning Scala
>> http://www.apress.com/book/view/1430219890
>> >>> >> >> >> >> >> Follow me: http://twitter.com/dpp
>> >>> >> >> >> >> >> Surf the harmonics
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > --
>> >>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >> >> >> > --
>> >>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >> >> >> >
>> >>> >> >> >>
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> > --
>> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >> >> >
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >> >
>> >>> >>
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >>> >
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Scala中文社区:  http://groups.google.com/group/scalacn
>> >>
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
@D
Yes, I think so.
One of my old lift project is very simple,
and occur the same problem.

I found that one of dependence jar file is not downloaded completely.
After I delete the jar file and mvn  again. the simple project worked again.


On Fri, Nov 6, 2009 at 5:05 PM, Richard Hirsch <hi...@gmail.com>wrote:

> The build was successful.
>
> Could it be that some network issues are preventing you from accessing
> particular Jar files?
>
> D.
>
> On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com>
> wrote:
> > OK.
> >
> > I just installed apache-maven-2.2.1.
> >
> > I'm doing a build (mvn clean install) after deleting my .m2 directory.
> >
> > I'll update this thread with the results when the build is finished.
> >
> > D.
> >
> > On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> @D
> >> Thank you for your patient,
> >>
> >> I uploaded the trace in Jira now
> >>
> >> And one of my old lift project cause the same probleam
> >> and it worked after use 'mvn -X clean install'.
> >>
> >> I think maybe some of .m2 repository is broken.
> >>
> >> I deleted ,m2 repository but didn't work and
> >> I think maybe  maven cannot download full jar files because network.
> >> I will try again in anther network environment.
> >>
> >> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >>
> >>> Definitely a tough problem.
> >>>
> >>> Let's try this:
> >>>
> >>> 1. Delete ,m2 repository
> >>> 2. Get the latest code drop from the SVN and put it in a new directory
> >>> 3. Do a  "mvn -X clean install > trace"
> >>> 4. Upload the trace to the Jira Item.
> >>>
> >>> D.
> >>>
> >>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >>> > I comment the opendmk but didn't find scala-stats and configgy is
> >>> dependency
> >>> > exception the repository.
> >>> > I uploaded the maven log.
> >>> >
> >>> > I think I didn't change anything, and other scala lift projects are
> >>> working
> >>> > well in the same environment.
> >>> >
> >>> >
> >>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <
> hirsch.dick@gmail.com
> >>> >wrote:
> >>> >
> >>> >> What about changing the pom.xml and removing the dependencies for
> >>> >> scala-stats, configgy and opendmk. You will get compile errors but I
> >>> >> want to see if that solves basic problem.
> >>> >>
> >>> >> I'll compare your environment to my environment at work and see if I
> >>> >> see other diffs.
> >>> >>
> >>> >> Are you sure that nothing else changed in your env?
> >>> >>
> >>> >> D.
> >>> >>
> >>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >>> >> > @D
> >>> >> > Oops
> >>> >> > I deleted  the .m2 repository but failed too....
> >>> >> >
> >>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <
> hirsch.dick@gmail.com
> >>> >> >wrote:
> >>> >> >
> >>> >> >> Looked at the log in the Jira item and compared it to my own log.
> I
> >>> >> >> only see a few differences related to the dependencies  related
> to
> >>> JMX
> >>> >> >> functionality.
> >>> >> >>
> >>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> >>> >> >> updates from scala-stats
> >>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
> local =
> >>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> >>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
> >>> >> >>
> >>> >> >>
> >>> >> >> Did you try and delete the .m2 repository. If you don't want to
> >>> delete
> >>> >> >> it what about renaming it.
> >>> >> >>
> >>> >> >> D.
> >>> >> >>
> >>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >>> >> >> > Done,
> >>> >> >> > attached
> >>> >> >> >
> >>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
> >>> hirsch.dick@gmail.com
> >>> >> >> >wrote:
> >>> >> >> >
> >>> >> >> >> Saw Jira item. Thanks.
> >>> >> >> >>
> >>> >> >> >> But we still need to see the entire log.  Could you attach it
> to
> >>> the
> >>> >> >> >> item as an attachment.
> >>> >> >> >>
> >>> >> >> >> The one link you posted in the Jira item about the Lift error
> in
> >>> >> >> >> Hudson looks very similar. Once we get the entire maven log,
> it
> >>> will
> >>> >> >> >> be a lot easier to see if this is the problem.
> >>> >> >> >>
> >>> >> >> >> D.
> >>> >> >> >>
> >>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com>
> >>> wrote:
> >>> >> >> >> > @D.
> >>> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
> >>> >> >> >> >
> >>> >> >> >> > Thanks.
> >>> >> >> >> >
> >>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
> >>> >> hirsch.dick@gmail.com
> >>> >> >> >> >wrote:
> >>> >> >> >> >
> >>> >> >> >> >> Why don't you create a Jira item and attach the entire
> trace as
> >>> an
> >>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
> >>> >> >> >> >>
> >>> >> >> >> >> We can then get a better idea of what is going on.
> >>> >> >> >> >>
> >>> >> >> >> >> D.
> >>> >> >> >> >>
> >>> >> >> >> >>
> >>> >> >> >> >>
> >>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <
> benewu@gmail.com>
> >>> >> wrote:
> >>> >> >> >> >> > Thank you for your response.
> >>> >> >> >> >> >
> >>> >> >> >> >> > @D
> >>> >> >> >> >> > I checked out new from SVN but failed too.
> >>> >> >> >> >> >
> >>> >> >> >> >> > @David
> >>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too ,
> get
> >>> the
> >>> >> >> same
> >>> >> >> >> >> error:
> >>> >> >> >> >> > command line returned non-zero value:1
> >>> >> >> >> >> > I didn't rename .m2 folder and my other maven projects
> are
> >>> >> working.
> >>> >> >> >> >> >
> >>> >> >> >> >> >
> >>> >> >> >> >> >
> >>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >>> >> >> >> >> > <fe...@gmail.com>wrote:
> >>> >> >> >> >> >
> >>> >> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run"
> >>> before
> >>> >> >> >> trying
> >>> >> >> >> >> to
> >>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2
> before
> >>> >> starting
> >>> >> >> >> the
> >>> >> >> >> >> >> process?
> >>> >> >> >> >> >>
> >>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
> >>> benewu@gmail.com>
> >>> >> >> wrote:
> >>> >> >> >> >> >>
> >>> >> >> >> >> >> > I run mvn clean install -e
> >>> >> >> >> >> >> > get:
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> > [WARNING] 204 errors found
> >>> >> >> >> >> >> > [INFO]
> >>> >> >> >> >> >> >
> >>> >> >> >> >>
> >>> >> >>
> >>>
> ------------------------------------------------------------------------
> >>> >> >> >> >> >> > [ERROR] BUILD FAILURE
> >>> >> >> >> >> >> > [INFO]
> >>> >> >> >> >> >> >
> >>> >> >> >> >>
> >>> >> >>
> >>>
> ------------------------------------------------------------------------
> >>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
> >>> >> >> >> >> >> > [INFO]
> >>> >> >> >> >> >> >
> >>> >> >> >> >>
> >>> >> >>
> >>>
> ------------------------------------------------------------------------
> >>> >> >> >> >> >> > [INFO] Trace
> >>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command line
> >>> returned
> >>> >> >> >> non-zero
> >>> >> >> >> >> >> > value:1
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >>> >> >> >> >> >> > fecycleExecutor.java:180)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >>
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >>> >> >> >> >> >> >        at
> >>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >>> >> >> >> >> >> > 0)
> >>> >> >> >> >> >> >        at
> >>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>> >> >> >> Method)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >>> >> >> >> >> >> > java:39)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
> >>> >> command
> >>> >> >> >> line
> >>> >> >> >> >> >> > returned n
> >>> >> >> >> >> >> > on-zero value:1
> >>> >> >> >> >> >> >        at
> >>> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >>> >> >> >> >> >> > rt.java:124)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >>> >> >> >> >> >> > port.java:54)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >>> >> >> >> >> >> > 208)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >>> >> >> >> >> >> > rt.java:29)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >>> >> >> >> >> >> > nManager.java:490)
> >>> >> >> >> >> >> >        at
> >>> >> >> >> >> >> >
> >>> >> >> >>
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
> >>> >> >> >> >> >> >        ... 17 more
> >>> >> >> >> >> >> > [INFO]
> >>> >> >> >> >> >> >
> >>> >> >> >> >>
> >>> >> >>
> >>>
> ------------------------------------------------------------------------
> >>> >> >> >> >> >> > [INFO] Total time: 23 seconds
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> >>> >> >> vdichev@gmail.com>
> >>> >> >> >> >> wrote:
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> > > > Yes
> >>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same
> >>> error:
> >>> >> >> >> >> >> > > >
> >>> >> >> >> >> >> > > > What's the mean " command line returned non-zero
> >>> value:1"
> >>> >> in
> >>> >> >> >> >> maven?
> >>> >> >> >> >> >> > >
> >>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't you
> do as
> >>> >> maven
> >>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
> >>> >> >> >> >> >> > >
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >> > --
> >>> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >> >> >> >> >
> >>> >> >> >> >> >>
> >>> >> >> >> >> >>
> >>> >> >> >> >> >>
> >>> >> >> >> >> >> --
> >>> >> >> >> >> >> Lift, the simply functional web framework
> >>> http://liftweb.net
> >>> >> >> >> >> >> Beginning Scala
> http://www.apress.com/book/view/1430219890
> >>> >> >> >> >> >> Follow me: http://twitter.com/dpp
> >>> >> >> >> >> >> Surf the harmonics
> >>> >> >> >> >> >>
> >>> >> >> >> >> >
> >>> >> >> >> >> >
> >>> >> >> >> >> >
> >>> >> >> >> >> > --
> >>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >> >> >> >
> >>> >> >> >> >>
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> > --
> >>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >> >> >
> >>> >> >> >>
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> > --
> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >> >
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> Scala中文社区:  http://groups.google.com/group/scalacn
> >>
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
The build was successful.

Could it be that some network issues are preventing you from accessing
particular Jar files?

D.

On Fri, Nov 6, 2009 at 9:52 AM, Richard Hirsch <hi...@gmail.com> wrote:
> OK.
>
> I just installed apache-maven-2.2.1.
>
> I'm doing a build (mvn clean install) after deleting my .m2 directory.
>
> I'll update this thread with the results when the build is finished.
>
> D.
>
> On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> @D
>> Thank you for your patient,
>>
>> I uploaded the trace in Jira now
>>
>> And one of my old lift project cause the same probleam
>> and it worked after use 'mvn -X clean install'.
>>
>> I think maybe some of .m2 repository is broken.
>>
>> I deleted ,m2 repository but didn't work and
>> I think maybe  maven cannot download full jar files because network.
>> I will try again in anther network environment.
>>
>> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <hi...@gmail.com>wrote:
>>
>>> Definitely a tough problem.
>>>
>>> Let's try this:
>>>
>>> 1. Delete ,m2 repository
>>> 2. Get the latest code drop from the SVN and put it in a new directory
>>> 3. Do a  "mvn -X clean install > trace"
>>> 4. Upload the trace to the Jira Item.
>>>
>>> D.
>>>
>>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> > I comment the opendmk but didn't find scala-stats and configgy is
>>> dependency
>>> > exception the repository.
>>> > I uploaded the maven log.
>>> >
>>> > I think I didn't change anything, and other scala lift projects are
>>> working
>>> > well in the same environment.
>>> >
>>> >
>>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hirsch.dick@gmail.com
>>> >wrote:
>>> >
>>> >> What about changing the pom.xml and removing the dependencies for
>>> >> scala-stats, configgy and opendmk. You will get compile errors but I
>>> >> want to see if that solves basic problem.
>>> >>
>>> >> I'll compare your environment to my environment at work and see if I
>>> >> see other diffs.
>>> >>
>>> >> Are you sure that nothing else changed in your env?
>>> >>
>>> >> D.
>>> >>
>>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> > @D
>>> >> > Oops
>>> >> > I deleted  the .m2 repository but failed too....
>>> >> >
>>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
>>> >> >wrote:
>>> >> >
>>> >> >> Looked at the log in the Jira item and compared it to my own log. I
>>> >> >> only see a few differences related to the dependencies  related to
>>> JMX
>>> >> >> functionality.
>>> >> >>
>>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>>> >> >> updates from scala-stats
>>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>>> >> >>
>>> >> >>
>>> >> >> Did you try and delete the .m2 repository. If you don't want to
>>> delete
>>> >> >> it what about renaming it.
>>> >> >>
>>> >> >> D.
>>> >> >>
>>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> >> > Done,
>>> >> >> > attached
>>> >> >> >
>>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
>>> hirsch.dick@gmail.com
>>> >> >> >wrote:
>>> >> >> >
>>> >> >> >> Saw Jira item. Thanks.
>>> >> >> >>
>>> >> >> >> But we still need to see the entire log.  Could you attach it to
>>> the
>>> >> >> >> item as an attachment.
>>> >> >> >>
>>> >> >> >> The one link you posted in the Jira item about the Lift error in
>>> >> >> >> Hudson looks very similar. Once we get the entire maven log, it
>>> will
>>> >> >> >> be a lot easier to see if this is the problem.
>>> >> >> >>
>>> >> >> >> D.
>>> >> >> >>
>>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com>
>>> wrote:
>>> >> >> >> > @D.
>>> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
>>> >> >> >> >
>>> >> >> >> > Thanks.
>>> >> >> >> >
>>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>>> >> hirsch.dick@gmail.com
>>> >> >> >> >wrote:
>>> >> >> >> >
>>> >> >> >> >> Why don't you create a Jira item and attach the entire trace as
>>> an
>>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
>>> >> >> >> >>
>>> >> >> >> >> We can then get a better idea of what is going on.
>>> >> >> >> >>
>>> >> >> >> >> D.
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
>>> >> wrote:
>>> >> >> >> >> > Thank you for your response.
>>> >> >> >> >> >
>>> >> >> >> >> > @D
>>> >> >> >> >> > I checked out new from SVN but failed too.
>>> >> >> >> >> >
>>> >> >> >> >> > @David
>>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get
>>> the
>>> >> >> same
>>> >> >> >> >> error:
>>> >> >> >> >> > command line returned non-zero value:1
>>> >> >> >> >> > I didn't rename .m2 folder and my other maven projects are
>>> >> working.
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>>> >> >> >> >> > <fe...@gmail.com>wrote:
>>> >> >> >> >> >
>>> >> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run"
>>> before
>>> >> >> >> trying
>>> >> >> >> >> to
>>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
>>> >> starting
>>> >> >> >> the
>>> >> >> >> >> >> process?
>>> >> >> >> >> >>
>>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
>>> benewu@gmail.com>
>>> >> >> wrote:
>>> >> >> >> >> >>
>>> >> >> >> >> >> > I run mvn clean install -e
>>> >> >> >> >> >> > get:
>>> >> >> >> >> >> >
>>> >> >> >> >> >> > [WARNING] 204 errors found
>>> >> >> >> >> >> > [INFO]
>>> >> >> >> >> >> >
>>> >> >> >> >>
>>> >> >>
>>> ------------------------------------------------------------------------
>>> >> >> >> >> >> > [ERROR] BUILD FAILURE
>>> >> >> >> >> >> > [INFO]
>>> >> >> >> >> >> >
>>> >> >> >> >>
>>> >> >>
>>> ------------------------------------------------------------------------
>>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
>>> >> >> >> >> >> > [INFO]
>>> >> >> >> >> >> >
>>> >> >> >> >>
>>> >> >>
>>> ------------------------------------------------------------------------
>>> >> >> >> >> >> > [INFO] Trace
>>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command line
>>> returned
>>> >> >> >> non-zero
>>> >> >> >> >> >> > value:1
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> >> >> >> >> >> > fecycleExecutor.java:180)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> >> >> >> >> >> >        at
>>> >> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> >> >> >> >> >> >        at
>>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>>> >> >> >> >> >> > 0)
>>> >> >> >> >> >> >        at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >> >> >> Method)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> >> >> >> >> >> > java:39)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
>>> >> command
>>> >> >> >> line
>>> >> >> >> >> >> > returned n
>>> >> >> >> >> >> > on-zero value:1
>>> >> >> >> >> >> >        at
>>> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>>> >> >> >> >> >> > rt.java:124)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>>> >> >> >> >> >> > port.java:54)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>>> >> >> >> >> >> > 208)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>>> >> >> >> >> >> > rt.java:29)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> >> >> >> >> >> > nManager.java:490)
>>> >> >> >> >> >> >        at
>>> >> >> >> >> >> >
>>> >> >> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
>>> >> >> >> >> >> >        ... 17 more
>>> >> >> >> >> >> > [INFO]
>>> >> >> >> >> >> >
>>> >> >> >> >>
>>> >> >>
>>> ------------------------------------------------------------------------
>>> >> >> >> >> >> > [INFO] Total time: 23 seconds
>>> >> >> >> >> >> >
>>> >> >> >> >> >> >
>>> >> >> >> >> >> >
>>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>>> >> >> vdichev@gmail.com>
>>> >> >> >> >> wrote:
>>> >> >> >> >> >> >
>>> >> >> >> >> >> > > > Yes
>>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same
>>> error:
>>> >> >> >> >> >> > > >
>>> >> >> >> >> >> > > > What's the mean " command line returned non-zero
>>> value:1"
>>> >> in
>>> >> >> >> >> maven?
>>> >> >> >> >> >> > >
>>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
>>> >> maven
>>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>>> >> >> >> >> >> > >
>>> >> >> >> >> >> >
>>> >> >> >> >> >> >
>>> >> >> >> >> >> >
>>> >> >> >> >> >> > --
>>> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >> >> >> >
>>> >> >> >> >> >>
>>> >> >> >> >> >>
>>> >> >> >> >> >>
>>> >> >> >> >> >> --
>>> >> >> >> >> >> Lift, the simply functional web framework
>>> http://liftweb.net
>>> >> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>>> >> >> >> >> >> Follow me: http://twitter.com/dpp
>>> >> >> >> >> >> Surf the harmonics
>>> >> >> >> >> >>
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> >
>>> >> >> >> >> > --
>>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >> >> >
>>> >> >> >> >>
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > --
>>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >> >
>>> >> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > --
>>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >
>>>
>>
>>
>>
>> --
>> Scala中文社区:  http://groups.google.com/group/scalacn
>>
>

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
OK.

I just installed apache-maven-2.2.1.

I'm doing a build (mvn clean install) after deleting my .m2 directory.

I'll update this thread with the results when the build is finished.

D.

On Fri, Nov 6, 2009 at 9:43 AM, Xuefeng Wu <be...@gmail.com> wrote:
> @D
> Thank you for your patient,
>
> I uploaded the trace in Jira now
>
> And one of my old lift project cause the same probleam
> and it worked after use 'mvn -X clean install'.
>
> I think maybe some of .m2 repository is broken.
>
> I deleted ,m2 repository but didn't work and
> I think maybe  maven cannot download full jar files because network.
> I will try again in anther network environment.
>
> On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> Definitely a tough problem.
>>
>> Let's try this:
>>
>> 1. Delete ,m2 repository
>> 2. Get the latest code drop from the SVN and put it in a new directory
>> 3. Do a  "mvn -X clean install > trace"
>> 4. Upload the trace to the Jira Item.
>>
>> D.
>>
>> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> > I comment the opendmk but didn't find scala-stats and configgy is
>> dependency
>> > exception the repository.
>> > I uploaded the maven log.
>> >
>> > I think I didn't change anything, and other scala lift projects are
>> working
>> > well in the same environment.
>> >
>> >
>> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> What about changing the pom.xml and removing the dependencies for
>> >> scala-stats, configgy and opendmk. You will get compile errors but I
>> >> want to see if that solves basic problem.
>> >>
>> >> I'll compare your environment to my environment at work and see if I
>> >> see other diffs.
>> >>
>> >> Are you sure that nothing else changed in your env?
>> >>
>> >> D.
>> >>
>> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> > @D
>> >> > Oops
>> >> > I deleted  the .m2 repository but failed too....
>> >> >
>> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >> >wrote:
>> >> >
>> >> >> Looked at the log in the Jira item and compared it to my own log. I
>> >> >> only see a few differences related to the dependencies  related to
>> JMX
>> >> >> functionality.
>> >> >>
>> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>> >> >> updates from scala-stats
>> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>> >> >>
>> >> >>
>> >> >> Did you try and delete the .m2 repository. If you don't want to
>> delete
>> >> >> it what about renaming it.
>> >> >>
>> >> >> D.
>> >> >>
>> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> >> > Done,
>> >> >> > attached
>> >> >> >
>> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
>> hirsch.dick@gmail.com
>> >> >> >wrote:
>> >> >> >
>> >> >> >> Saw Jira item. Thanks.
>> >> >> >>
>> >> >> >> But we still need to see the entire log.  Could you attach it to
>> the
>> >> >> >> item as an attachment.
>> >> >> >>
>> >> >> >> The one link you posted in the Jira item about the Lift error in
>> >> >> >> Hudson looks very similar. Once we get the entire maven log, it
>> will
>> >> >> >> be a lot easier to see if this is the problem.
>> >> >> >>
>> >> >> >> D.
>> >> >> >>
>> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >> >> >> > @D.
>> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
>> >> >> >> >
>> >> >> >> > Thanks.
>> >> >> >> >
>> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>> >> hirsch.dick@gmail.com
>> >> >> >> >wrote:
>> >> >> >> >
>> >> >> >> >> Why don't you create a Jira item and attach the entire trace as
>> an
>> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
>> >> >> >> >>
>> >> >> >> >> We can then get a better idea of what is going on.
>> >> >> >> >>
>> >> >> >> >> D.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
>> >> wrote:
>> >> >> >> >> > Thank you for your response.
>> >> >> >> >> >
>> >> >> >> >> > @D
>> >> >> >> >> > I checked out new from SVN but failed too.
>> >> >> >> >> >
>> >> >> >> >> > @David
>> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get
>> the
>> >> >> same
>> >> >> >> >> error:
>> >> >> >> >> > command line returned non-zero value:1
>> >> >> >> >> > I didn't rename .m2 folder and my other maven projects are
>> >> working.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >> >> >> >> > <fe...@gmail.com>wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run"
>> before
>> >> >> >> trying
>> >> >> >> >> to
>> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
>> >> starting
>> >> >> >> the
>> >> >> >> >> >> process?
>> >> >> >> >> >>
>> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
>> benewu@gmail.com>
>> >> >> wrote:
>> >> >> >> >> >>
>> >> >> >> >> >> > I run mvn clean install -e
>> >> >> >> >> >> > get:
>> >> >> >> >> >> >
>> >> >> >> >> >> > [WARNING] 204 errors found
>> >> >> >> >> >> > [INFO]
>> >> >> >> >> >> >
>> >> >> >> >>
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> >> >> > [ERROR] BUILD FAILURE
>> >> >> >> >> >> > [INFO]
>> >> >> >> >> >> >
>> >> >> >> >>
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> >> >> > [INFO] command line returned non-zero value:1
>> >> >> >> >> >> > [INFO]
>> >> >> >> >> >> >
>> >> >> >> >>
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> >> >> > [INFO] Trace
>> >> >> >> >> >> > org.apache.maven.BuildFailureException: command line
>> returned
>> >> >> >> non-zero
>> >> >> >> >> >> > value:1
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> >> >> > ultLifecycleExecutor.java:715)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >> >> >> >> > ltLifecycleExecutor.java:535)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >> >> >> >> > fecycleExecutor.java:180)
>> >> >> >> >> >> >        at
>> >> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >> >> >> >> >        at
>> >> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >> >> >> >> >        at
>> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> >> >> >> >> > 0)
>> >> >> >> >> >> >        at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >> >> >> Method)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >> >> >> >> > java:39)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >> >> >> >> > sorImpl.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.MojoFailureException:
>> >> command
>> >> >> >> line
>> >> >> >> >> >> > returned n
>> >> >> >> >> >> > on-zero value:1
>> >> >> >> >> >> >        at
>> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> >> >> >> >> > rt.java:124)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> >> >> >> >> > port.java:54)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> >> >> >> >> > 208)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> >> >> >> >> > rt.java:29)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >> >> >> >> > nManager.java:490)
>> >> >> >> >> >> >        at
>> >> >> >> >> >> >
>> >> >> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> >> >> > ultLifecycleExecutor.java:694)
>> >> >> >> >> >> >        ... 17 more
>> >> >> >> >> >> > [INFO]
>> >> >> >> >> >> >
>> >> >> >> >>
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> >> >> > [INFO] Total time: 23 seconds
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>> >> >> vdichev@gmail.com>
>> >> >> >> >> wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> > > > Yes
>> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same
>> error:
>> >> >> >> >> >> > > >
>> >> >> >> >> >> > > > What's the mean " command line returned non-zero
>> value:1"
>> >> in
>> >> >> >> >> maven?
>> >> >> >> >> >> > >
>> >> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
>> >> maven
>> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>> >> >> >> >> >> > >
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > --
>> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Lift, the simply functional web framework
>> http://liftweb.net
>> >> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>> >> >> >> >> >> Follow me: http://twitter.com/dpp
>> >> >> >> >> >> Surf the harmonics
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
@D
Thank you for your patient,

I uploaded the trace in Jira now

And one of my old lift project cause the same probleam
and it worked after use 'mvn -X clean install'.

I think maybe some of .m2 repository is broken.

I deleted ,m2 repository but didn't work and
I think maybe  maven cannot download full jar files because network.
I will try again in anther network environment.

On Fri, Nov 6, 2009 at 3:06 PM, Richard Hirsch <hi...@gmail.com>wrote:

> Definitely a tough problem.
>
> Let's try this:
>
> 1. Delete ,m2 repository
> 2. Get the latest code drop from the SVN and put it in a new directory
> 3. Do a  "mvn -X clean install > trace"
> 4. Upload the trace to the Jira Item.
>
> D.
>
> On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
> > I comment the opendmk but didn't find scala-stats and configgy is
> dependency
> > exception the repository.
> > I uploaded the maven log.
> >
> > I think I didn't change anything, and other scala lift projects are
> working
> > well in the same environment.
> >
> >
> > On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> What about changing the pom.xml and removing the dependencies for
> >> scala-stats, configgy and opendmk. You will get compile errors but I
> >> want to see if that solves basic problem.
> >>
> >> I'll compare your environment to my environment at work and see if I
> >> see other diffs.
> >>
> >> Are you sure that nothing else changed in your env?
> >>
> >> D.
> >>
> >> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> > @D
> >> > Oops
> >> > I deleted  the .m2 repository but failed too....
> >> >
> >> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
> >> >wrote:
> >> >
> >> >> Looked at the log in the Jira item and compared it to my own log. I
> >> >> only see a few differences related to the dependencies  related to
> JMX
> >> >> functionality.
> >> >>
> >> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> >> >> updates from scala-stats
> >> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> >> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> >> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
> >> >>
> >> >>
> >> >> Did you try and delete the .m2 repository. If you don't want to
> delete
> >> >> it what about renaming it.
> >> >>
> >> >> D.
> >> >>
> >> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> >> > Done,
> >> >> > attached
> >> >> >
> >> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <
> hirsch.dick@gmail.com
> >> >> >wrote:
> >> >> >
> >> >> >> Saw Jira item. Thanks.
> >> >> >>
> >> >> >> But we still need to see the entire log.  Could you attach it to
> the
> >> >> >> item as an attachment.
> >> >> >>
> >> >> >> The one link you posted in the Jira item about the Lift error in
> >> >> >> Hudson looks very similar. Once we get the entire maven log, it
> will
> >> >> >> be a lot easier to see if this is the problem.
> >> >> >>
> >> >> >> D.
> >> >> >>
> >> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >> >> >> > @D.
> >> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
> >> >> >> >
> >> >> >> > Thanks.
> >> >> >> >
> >> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
> >> hirsch.dick@gmail.com
> >> >> >> >wrote:
> >> >> >> >
> >> >> >> >> Why don't you create a Jira item and attach the entire trace as
> an
> >> >> >> >> attachment. Like this "mvn clean install > mytrace".
> >> >> >> >>
> >> >> >> >> We can then get a better idea of what is going on.
> >> >> >> >>
> >> >> >> >> D.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
> >> wrote:
> >> >> >> >> > Thank you for your response.
> >> >> >> >> >
> >> >> >> >> > @D
> >> >> >> >> > I checked out new from SVN but failed too.
> >> >> >> >> >
> >> >> >> >> > @David
> >> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get
> the
> >> >> same
> >> >> >> >> error:
> >> >> >> >> > command line returned non-zero value:1
> >> >> >> >> > I didn't rename .m2 folder and my other maven projects are
> >> working.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >> >> >> >> > <fe...@gmail.com>wrote:
> >> >> >> >> >
> >> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run"
> before
> >> >> >> trying
> >> >> >> >> to
> >> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
> >> starting
> >> >> >> the
> >> >> >> >> >> process?
> >> >> >> >> >>
> >> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <
> benewu@gmail.com>
> >> >> wrote:
> >> >> >> >> >>
> >> >> >> >> >> > I run mvn clean install -e
> >> >> >> >> >> > get:
> >> >> >> >> >> >
> >> >> >> >> >> > [WARNING] 204 errors found
> >> >> >> >> >> > [INFO]
> >> >> >> >> >> >
> >> >> >> >>
> >> >>
> ------------------------------------------------------------------------
> >> >> >> >> >> > [ERROR] BUILD FAILURE
> >> >> >> >> >> > [INFO]
> >> >> >> >> >> >
> >> >> >> >>
> >> >>
> ------------------------------------------------------------------------
> >> >> >> >> >> > [INFO] command line returned non-zero value:1
> >> >> >> >> >> > [INFO]
> >> >> >> >> >> >
> >> >> >> >>
> >> >>
> ------------------------------------------------------------------------
> >> >> >> >> >> > [INFO] Trace
> >> >> >> >> >> > org.apache.maven.BuildFailureException: command line
> returned
> >> >> >> non-zero
> >> >> >> >> >> > value:1
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> >> >> > ultLifecycleExecutor.java:715)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >> >> >> >> > ltLifecycleExecutor.java:535)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >> >> >> >> > fecycleExecutor.java:180)
> >> >> >> >> >> >        at
> >> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >> >> >> >> >        at
> >> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >> >> >> >> >        at
> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> >> >> >> >> > 0)
> >> >> >> >> >> >        at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >> >> Method)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >> >> >> >> > java:39)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >> >> >> >> > sorImpl.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.MojoFailureException:
> >> command
> >> >> >> line
> >> >> >> >> >> > returned n
> >> >> >> >> >> > on-zero value:1
> >> >> >> >> >> >        at
> >> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> >> >> >> >> > rt.java:124)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> >> >> >> >> > port.java:54)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> >> >> >> >> > 208)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> >> >> >> >> > rt.java:29)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >> >> >> >> > nManager.java:490)
> >> >> >> >> >> >        at
> >> >> >> >> >> >
> >> >> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> >> >> > ultLifecycleExecutor.java:694)
> >> >> >> >> >> >        ... 17 more
> >> >> >> >> >> > [INFO]
> >> >> >> >> >> >
> >> >> >> >>
> >> >>
> ------------------------------------------------------------------------
> >> >> >> >> >> > [INFO] Total time: 23 seconds
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> >> >> vdichev@gmail.com>
> >> >> >> >> wrote:
> >> >> >> >> >> >
> >> >> >> >> >> > > > Yes
> >> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same
> error:
> >> >> >> >> >> > > >
> >> >> >> >> >> > > > What's the mean " command line returned non-zero
> value:1"
> >> in
> >> >> >> >> maven?
> >> >> >> >> >> > >
> >> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
> >> maven
> >> >> >> >> >> > > suggests and "run Maven with the -e switch"?
> >> >> >> >> >> > >
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Lift, the simply functional web framework
> http://liftweb.net
> >> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >> >> >> >> >> Follow me: http://twitter.com/dpp
> >> >> >> >> >> Surf the harmonics
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Definitely a tough problem.

Let's try this:

1. Delete ,m2 repository
2. Get the latest code drop from the SVN and put it in a new directory
3. Do a  "mvn -X clean install > trace"
4. Upload the trace to the Jira Item.

D.

On Fri, Nov 6, 2009 at 7:37 AM, Xuefeng Wu <be...@gmail.com> wrote:
> I comment the opendmk but didn't find scala-stats and configgy is dependency
> exception the repository.
> I uploaded the maven log.
>
> I think I didn't change anything, and other scala lift projects are working
> well in the same environment.
>
>
> On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> What about changing the pom.xml and removing the dependencies for
>> scala-stats, configgy and opendmk. You will get compile errors but I
>> want to see if that solves basic problem.
>>
>> I'll compare your environment to my environment at work and see if I
>> see other diffs.
>>
>> Are you sure that nothing else changed in your env?
>>
>> D.
>>
>> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> > @D
>> > Oops
>> > I deleted  the .m2 repository but failed too....
>> >
>> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> Looked at the log in the Jira item and compared it to my own log. I
>> >> only see a few differences related to the dependencies  related to JMX
>> >> functionality.
>> >>
>> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>> >> updates from scala-stats
>> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>> >>
>> >>
>> >> Did you try and delete the .m2 repository. If you don't want to delete
>> >> it what about renaming it.
>> >>
>> >> D.
>> >>
>> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> > Done,
>> >> > attached
>> >> >
>> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >> >wrote:
>> >> >
>> >> >> Saw Jira item. Thanks.
>> >> >>
>> >> >> But we still need to see the entire log.  Could you attach it to the
>> >> >> item as an attachment.
>> >> >>
>> >> >> The one link you posted in the Jira item about the Lift error in
>> >> >> Hudson looks very similar. Once we get the entire maven log, it will
>> >> >> be a lot easier to see if this is the problem.
>> >> >>
>> >> >> D.
>> >> >>
>> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> >> > @D.
>> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
>> >> >> >
>> >> >> > Thanks.
>> >> >> >
>> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
>> hirsch.dick@gmail.com
>> >> >> >wrote:
>> >> >> >
>> >> >> >> Why don't you create a Jira item and attach the entire trace as an
>> >> >> >> attachment. Like this "mvn clean install > mytrace".
>> >> >> >>
>> >> >> >> We can then get a better idea of what is going on.
>> >> >> >>
>> >> >> >> D.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >> >> >> > Thank you for your response.
>> >> >> >> >
>> >> >> >> > @D
>> >> >> >> > I checked out new from SVN but failed too.
>> >> >> >> >
>> >> >> >> > @David
>> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
>> >> same
>> >> >> >> error:
>> >> >> >> > command line returned non-zero value:1
>> >> >> >> > I didn't rename .m2 folder and my other maven projects are
>> working.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >> >> >> > <fe...@gmail.com>wrote:
>> >> >> >> >
>> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run" before
>> >> >> trying
>> >> >> >> to
>> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
>> starting
>> >> >> the
>> >> >> >> >> process?
>> >> >> >> >>
>> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
>> >> wrote:
>> >> >> >> >>
>> >> >> >> >> > I run mvn clean install -e
>> >> >> >> >> > get:
>> >> >> >> >> >
>> >> >> >> >> > [WARNING] 204 errors found
>> >> >> >> >> > [INFO]
>> >> >> >> >> >
>> >> >> >>
>> >> ------------------------------------------------------------------------
>> >> >> >> >> > [ERROR] BUILD FAILURE
>> >> >> >> >> > [INFO]
>> >> >> >> >> >
>> >> >> >>
>> >> ------------------------------------------------------------------------
>> >> >> >> >> > [INFO] command line returned non-zero value:1
>> >> >> >> >> > [INFO]
>> >> >> >> >> >
>> >> >> >>
>> >> ------------------------------------------------------------------------
>> >> >> >> >> > [INFO] Trace
>> >> >> >> >> > org.apache.maven.BuildFailureException: command line returned
>> >> >> non-zero
>> >> >> >> >> > value:1
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> >> > ultLifecycleExecutor.java:715)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >> >> >> > ltLifecycleExecutor.java:535)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >> >> >> > fecycleExecutor.java:180)
>> >> >> >> >> >        at
>> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >> >> >> >        at
>> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >> >> >> >        at
>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> >> >> >> > 0)
>> >> >> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >> >> Method)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >> >> >> > java:39)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >> >> >> > sorImpl.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.MojoFailureException:
>> command
>> >> >> line
>> >> >> >> >> > returned n
>> >> >> >> >> > on-zero value:1
>> >> >> >> >> >        at
>> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> >> >> >> > rt.java:124)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> >> >> >> > port.java:54)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> >> >> >> > 208)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> >> >> >> > rt.java:29)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >> >> >> > nManager.java:490)
>> >> >> >> >> >        at
>> >> >> >> >> >
>> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> >> > ultLifecycleExecutor.java:694)
>> >> >> >> >> >        ... 17 more
>> >> >> >> >> > [INFO]
>> >> >> >> >> >
>> >> >> >>
>> >> ------------------------------------------------------------------------
>> >> >> >> >> > [INFO] Total time: 23 seconds
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>> >> vdichev@gmail.com>
>> >> >> >> wrote:
>> >> >> >> >> >
>> >> >> >> >> > > > Yes
>> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
>> >> >> >> >> > > >
>> >> >> >> >> > > > What's the mean " command line returned non-zero value:1"
>> in
>> >> >> >> maven?
>> >> >> >> >> > >
>> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
>> maven
>> >> >> >> >> > > suggests and "run Maven with the -e switch"?
>> >> >> >> >> > >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Lift, the simply functional web framework http://liftweb.net
>> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>> >> >> >> >> Follow me: http://twitter.com/dpp
>> >> >> >> >> Surf the harmonics
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
I comment the opendmk but didn't find scala-stats and configgy is dependency
exception the repository.
I uploaded the maven log.

I think I didn't change anything, and other scala lift projects are working
well in the same environment.


On Fri, Nov 6, 2009 at 1:28 PM, Richard Hirsch <hi...@gmail.com>wrote:

> What about changing the pom.xml and removing the dependencies for
> scala-stats, configgy and opendmk. You will get compile errors but I
> want to see if that solves basic problem.
>
> I'll compare your environment to my environment at work and see if I
> see other diffs.
>
> Are you sure that nothing else changed in your env?
>
> D.
>
> On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
> > @D
> > Oops
> > I deleted  the .m2 repository but failed too....
> >
> > On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> Looked at the log in the Jira item and compared it to my own log. I
> >> only see a few differences related to the dependencies  related to JMX
> >> functionality.
> >>
> >> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> >> updates from scala-stats
> >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> >> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> >> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
> >>
> >>
> >> Did you try and delete the .m2 repository. If you don't want to delete
> >> it what about renaming it.
> >>
> >> D.
> >>
> >> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> > Done,
> >> > attached
> >> >
> >> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
> >> >wrote:
> >> >
> >> >> Saw Jira item. Thanks.
> >> >>
> >> >> But we still need to see the entire log.  Could you attach it to the
> >> >> item as an attachment.
> >> >>
> >> >> The one link you posted in the Jira item about the Lift error in
> >> >> Hudson looks very similar. Once we get the entire maven log, it will
> >> >> be a lot easier to see if this is the problem.
> >> >>
> >> >> D.
> >> >>
> >> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> >> > @D.
> >> >> > I created https://issues.apache.org/jira/browse/ESME-118
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
> hirsch.dick@gmail.com
> >> >> >wrote:
> >> >> >
> >> >> >> Why don't you create a Jira item and attach the entire trace as an
> >> >> >> attachment. Like this "mvn clean install > mytrace".
> >> >> >>
> >> >> >> We can then get a better idea of what is going on.
> >> >> >>
> >> >> >> D.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >> >> >> > Thank you for your response.
> >> >> >> >
> >> >> >> > @D
> >> >> >> > I checked out new from SVN but failed too.
> >> >> >> >
> >> >> >> > @David
> >> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
> >> same
> >> >> >> error:
> >> >> >> > command line returned non-zero value:1
> >> >> >> > I didn't rename .m2 folder and my other maven projects are
> working.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >> >> >> > <fe...@gmail.com>wrote:
> >> >> >> >
> >> >> >> >> Did you do a successful "mvn -U clean install jetty:run" before
> >> >> trying
> >> >> >> to
> >> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
> starting
> >> >> the
> >> >> >> >> process?
> >> >> >> >>
> >> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
> >> wrote:
> >> >> >> >>
> >> >> >> >> > I run mvn clean install -e
> >> >> >> >> > get:
> >> >> >> >> >
> >> >> >> >> > [WARNING] 204 errors found
> >> >> >> >> > [INFO]
> >> >> >> >> >
> >> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> > [ERROR] BUILD FAILURE
> >> >> >> >> > [INFO]
> >> >> >> >> >
> >> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> > [INFO] command line returned non-zero value:1
> >> >> >> >> > [INFO]
> >> >> >> >> >
> >> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> > [INFO] Trace
> >> >> >> >> > org.apache.maven.BuildFailureException: command line returned
> >> >> non-zero
> >> >> >> >> > value:1
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> >> > ultLifecycleExecutor.java:715)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >> >> >> > ltLifecycleExecutor.java:535)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >> >> >> > fecycleExecutor.java:180)
> >> >> >> >> >        at
> >> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >> >> >> >        at
> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >> >> >> >        at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> >> >> >> > 0)
> >> >> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >> Method)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >> >> >> > java:39)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >> >> >> > sorImpl.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.MojoFailureException:
> command
> >> >> line
> >> >> >> >> > returned n
> >> >> >> >> > on-zero value:1
> >> >> >> >> >        at
> >> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> >> >> >> > rt.java:124)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> >> >> >> > port.java:54)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> >> >> >> > 208)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> >> >> >> > rt.java:29)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >> >> >> > nManager.java:490)
> >> >> >> >> >        at
> >> >> >> >> >
> >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> >> > ultLifecycleExecutor.java:694)
> >> >> >> >> >        ... 17 more
> >> >> >> >> > [INFO]
> >> >> >> >> >
> >> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> > [INFO] Total time: 23 seconds
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> >> vdichev@gmail.com>
> >> >> >> wrote:
> >> >> >> >> >
> >> >> >> >> > > > Yes
> >> >> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
> >> >> >> >> > > >
> >> >> >> >> > > > What's the mean " command line returned non-zero value:1"
> in
> >> >> >> maven?
> >> >> >> >> > >
> >> >> >> >> > > Depends on these "204 errors found". Why don't you do as
> maven
> >> >> >> >> > > suggests and "run Maven with the -e switch"?
> >> >> >> >> > >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Lift, the simply functional web framework http://liftweb.net
> >> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >> >> >> >> Follow me: http://twitter.com/dpp
> >> >> >> >> Surf the harmonics
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
What about changing the pom.xml and removing the dependencies for
scala-stats, configgy and opendmk. You will get compile errors but I
want to see if that solves basic problem.

I'll compare your environment to my environment at work and see if I
see other diffs.

Are you sure that nothing else changed in your env?

D.

On Fri, Nov 6, 2009 at 5:33 AM, Xuefeng Wu <be...@gmail.com> wrote:
> @D
> Oops
> I deleted  the .m2 repository but failed too....
>
> On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> Looked at the log in the Jira item and compared it to my own log. I
>> only see a few differences related to the dependencies  related to JMX
>> functionality.
>>
>> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
>> updates from scala-stats
>> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
>> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>>
>>
>> Did you try and delete the .m2 repository. If you don't want to delete
>> it what about renaming it.
>>
>> D.
>>
>> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> > Done,
>> > attached
>> >
>> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> Saw Jira item. Thanks.
>> >>
>> >> But we still need to see the entire log.  Could you attach it to the
>> >> item as an attachment.
>> >>
>> >> The one link you posted in the Jira item about the Lift error in
>> >> Hudson looks very similar. Once we get the entire maven log, it will
>> >> be a lot easier to see if this is the problem.
>> >>
>> >> D.
>> >>
>> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> > @D.
>> >> > I created https://issues.apache.org/jira/browse/ESME-118
>> >> >
>> >> > Thanks.
>> >> >
>> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hirsch.dick@gmail.com
>> >> >wrote:
>> >> >
>> >> >> Why don't you create a Jira item and attach the entire trace as an
>> >> >> attachment. Like this "mvn clean install > mytrace".
>> >> >>
>> >> >> We can then get a better idea of what is going on.
>> >> >>
>> >> >> D.
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> >> > Thank you for your response.
>> >> >> >
>> >> >> > @D
>> >> >> > I checked out new from SVN but failed too.
>> >> >> >
>> >> >> > @David
>> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
>> same
>> >> >> error:
>> >> >> > command line returned non-zero value:1
>> >> >> > I didn't rename .m2 folder and my other maven projects are working.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >> >> > <fe...@gmail.com>wrote:
>> >> >> >
>> >> >> >> Did you do a successful "mvn -U clean install jetty:run" before
>> >> trying
>> >> >> to
>> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting
>> >> the
>> >> >> >> process?
>> >> >> >>
>> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
>> wrote:
>> >> >> >>
>> >> >> >> > I run mvn clean install -e
>> >> >> >> > get:
>> >> >> >> >
>> >> >> >> > [WARNING] 204 errors found
>> >> >> >> > [INFO]
>> >> >> >> >
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> > [ERROR] BUILD FAILURE
>> >> >> >> > [INFO]
>> >> >> >> >
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> > [INFO] command line returned non-zero value:1
>> >> >> >> > [INFO]
>> >> >> >> >
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> > [INFO] Trace
>> >> >> >> > org.apache.maven.BuildFailureException: command line returned
>> >> non-zero
>> >> >> >> > value:1
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> > ultLifecycleExecutor.java:715)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >> >> > ltLifecycleExecutor.java:535)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >> >> > fecycleExecutor.java:180)
>> >> >> >> >        at
>> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >> >> >        at
>> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> >> >> > 0)
>> >> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >> Method)
>> >> >> >> >        at
>> >> >> >> >
>> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >> >> > java:39)
>> >> >> >> >        at
>> >> >> >> >
>> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >> >> > sorImpl.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.MojoFailureException: command
>> >> line
>> >> >> >> > returned n
>> >> >> >> > on-zero value:1
>> >> >> >> >        at
>> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> >> >> > rt.java:124)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> >> >> > port.java:54)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> >> >> > 208)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> >> >> > rt.java:29)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >> >> > nManager.java:490)
>> >> >> >> >        at
>> >> >> >> >
>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> >> > ultLifecycleExecutor.java:694)
>> >> >> >> >        ... 17 more
>> >> >> >> > [INFO]
>> >> >> >> >
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> >> > [INFO] Total time: 23 seconds
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
>> vdichev@gmail.com>
>> >> >> wrote:
>> >> >> >> >
>> >> >> >> > > > Yes
>> >> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
>> >> >> >> > > >
>> >> >> >> > > > What's the mean " command line returned non-zero value:1" in
>> >> >> maven?
>> >> >> >> > >
>> >> >> >> > > Depends on these "204 errors found". Why don't you do as maven
>> >> >> >> > > suggests and "run Maven with the -e switch"?
>> >> >> >> > >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Lift, the simply functional web framework http://liftweb.net
>> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>> >> >> >> Follow me: http://twitter.com/dpp
>> >> >> >> Surf the harmonics
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
@D
Oops
I deleted  the .m2 repository but failed too....

On Wed, Nov 4, 2009 at 8:13 PM, Richard Hirsch <hi...@gmail.com>wrote:

> Looked at the log in the Jira item and compared it to my own log. I
> only see a few differences related to the dependencies  related to JMX
> functionality.
>
> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> updates from scala-stats
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>
>
> Did you try and delete the .m2 repository. If you don't want to delete
> it what about renaming it.
>
> D.
>
> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
> > Done,
> > attached
> >
> > On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> Saw Jira item. Thanks.
> >>
> >> But we still need to see the entire log.  Could you attach it to the
> >> item as an attachment.
> >>
> >> The one link you posted in the Jira item about the Lift error in
> >> Hudson looks very similar. Once we get the entire maven log, it will
> >> be a lot easier to see if this is the problem.
> >>
> >> D.
> >>
> >> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> > @D.
> >> > I created https://issues.apache.org/jira/browse/ESME-118
> >> >
> >> > Thanks.
> >> >
> >> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hirsch.dick@gmail.com
> >> >wrote:
> >> >
> >> >> Why don't you create a Jira item and attach the entire trace as an
> >> >> attachment. Like this "mvn clean install > mytrace".
> >> >>
> >> >> We can then get a better idea of what is going on.
> >> >>
> >> >> D.
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
> >> >> > Thank you for your response.
> >> >> >
> >> >> > @D
> >> >> > I checked out new from SVN but failed too.
> >> >> >
> >> >> > @David
> >> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
> same
> >> >> error:
> >> >> > command line returned non-zero value:1
> >> >> > I didn't rename .m2 folder and my other maven projects are working.
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >> >> > <fe...@gmail.com>wrote:
> >> >> >
> >> >> >> Did you do a successful "mvn -U clean install jetty:run" before
> >> trying
> >> >> to
> >> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting
> >> the
> >> >> >> process?
> >> >> >>
> >> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >> >> >>
> >> >> >> > I run mvn clean install -e
> >> >> >> > get:
> >> >> >> >
> >> >> >> > [WARNING] 204 errors found
> >> >> >> > [INFO]
> >> >> >> >
> >> >>
> ------------------------------------------------------------------------
> >> >> >> > [ERROR] BUILD FAILURE
> >> >> >> > [INFO]
> >> >> >> >
> >> >>
> ------------------------------------------------------------------------
> >> >> >> > [INFO] command line returned non-zero value:1
> >> >> >> > [INFO]
> >> >> >> >
> >> >>
> ------------------------------------------------------------------------
> >> >> >> > [INFO] Trace
> >> >> >> > org.apache.maven.BuildFailureException: command line returned
> >> non-zero
> >> >> >> > value:1
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> > ultLifecycleExecutor.java:715)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >> >> > ltLifecycleExecutor.java:535)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >> >> > fecycleExecutor.java:180)
> >> >> >> >        at
> >> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >> >> >        at
> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> >> >> > 0)
> >> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> Method)
> >> >> >> >        at
> >> >> >> >
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >> >> > java:39)
> >> >> >> >        at
> >> >> >> >
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >> >> > sorImpl.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.MojoFailureException: command
> >> line
> >> >> >> > returned n
> >> >> >> > on-zero value:1
> >> >> >> >        at
> >> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >> >> >        at
> >> >> >> >
> >> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> >> >> > rt.java:124)
> >> >> >> >        at
> >> >> >> >
> >> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> >> >> > port.java:54)
> >> >> >> >        at
> >> >> >> >
> >> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> >> >> > 208)
> >> >> >> >        at
> >> >> >> >
> >> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> >> >> > rt.java:29)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >> >> > nManager.java:490)
> >> >> >> >        at
> >> >> >> >
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> >> > ultLifecycleExecutor.java:694)
> >> >> >> >        ... 17 more
> >> >> >> > [INFO]
> >> >> >> >
> >> >>
> ------------------------------------------------------------------------
> >> >> >> > [INFO] Total time: 23 seconds
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> vdichev@gmail.com>
> >> >> wrote:
> >> >> >> >
> >> >> >> > > > Yes
> >> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
> >> >> >> > > >
> >> >> >> > > > What's the mean " command line returned non-zero value:1" in
> >> >> maven?
> >> >> >> > >
> >> >> >> > > Depends on these "204 errors found". Why don't you do as maven
> >> >> >> > > suggests and "run Maven with the -e switch"?
> >> >> >> > >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Lift, the simply functional web framework http://liftweb.net
> >> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >> >> >> Follow me: http://twitter.com/dpp
> >> >> >> Surf the harmonics
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
Thank you for your help and I will try ASAP.



On Wed, Nov 4, 2009 at 11:02 PM, Richard Hirsch <hi...@gmail.com>wrote:

> @Xuefeng still having problems? Since the latest code drop works on
> Hudson, it must be something in your environment. Hast something
> changed recently?
>
> D.
>
> On Wed, Nov 4, 2009 at 1:13 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> > Looked at the log in the Jira item and compared it to my own log. I
> > only see a few differences related to the dependencies  related to JMX
> > functionality.
> >
> > [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> > updates from scala-stats
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> > '<HTML><HEAD><TITLE>NetScreen' - RETRYING
> >
> >
> > Did you try and delete the .m2 repository. If you don't want to delete
> > it what about renaming it.
> >
> > D.
> >
> > On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> Done,
> >> attached
> >>
> >> On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >>
> >>> Saw Jira item. Thanks.
> >>>
> >>> But we still need to see the entire log.  Could you attach it to the
> >>> item as an attachment.
> >>>
> >>> The one link you posted in the Jira item about the Lift error in
> >>> Hudson looks very similar. Once we get the entire maven log, it will
> >>> be a lot easier to see if this is the problem.
> >>>
> >>> D.
> >>>
> >>> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >>> > @D.
> >>> > I created https://issues.apache.org/jira/browse/ESME-118
> >>> >
> >>> > Thanks.
> >>> >
> >>> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <
> hirsch.dick@gmail.com
> >>> >wrote:
> >>> >
> >>> >> Why don't you create a Jira item and attach the entire trace as an
> >>> >> attachment. Like this "mvn clean install > mytrace".
> >>> >>
> >>> >> We can then get a better idea of what is going on.
> >>> >>
> >>> >> D.
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >>> >> > Thank you for your response.
> >>> >> >
> >>> >> > @D
> >>> >> > I checked out new from SVN but failed too.
> >>> >> >
> >>> >> > @David
> >>> >> > I run 'mvn -U clean install jetty:run' and failed too , get the
> same
> >>> >> error:
> >>> >> > command line returned non-zero value:1
> >>> >> > I didn't rename .m2 folder and my other maven projects are
> working.
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >>> >> > <fe...@gmail.com>wrote:
> >>> >> >
> >>> >> >> Did you do a successful "mvn -U clean install jetty:run" before
> >>> trying
> >>> >> to
> >>> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before
> starting
> >>> the
> >>> >> >> process?
> >>> >> >>
> >>> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com>
> wrote:
> >>> >> >>
> >>> >> >> > I run mvn clean install -e
> >>> >> >> > get:
> >>> >> >> >
> >>> >> >> > [WARNING] 204 errors found
> >>> >> >> > [INFO]
> >>> >> >> >
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >> > [ERROR] BUILD FAILURE
> >>> >> >> > [INFO]
> >>> >> >> >
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >> > [INFO] command line returned non-zero value:1
> >>> >> >> > [INFO]
> >>> >> >> >
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >> > [INFO] Trace
> >>> >> >> > org.apache.maven.BuildFailureException: command line returned
> >>> non-zero
> >>> >> >> > value:1
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >>> >> >> > ultLifecycleExecutor.java:715)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >>> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >>> >> >> > ltLifecycleExecutor.java:535)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >>> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >>> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >>> >> >> > fecycleExecutor.java:180)
> >>> >> >> >        at
> >>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >>> >> >> >        at
> >>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >>> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >>> >> >> > 0)
> >>> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>> Method)
> >>> >> >> >        at
> >>> >> >> >
> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >>> >> >> > java:39)
> >>> >> >> >        at
> >>> >> >> >
> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >>> >> >> > sorImpl.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.MojoFailureException:
> command
> >>> line
> >>> >> >> > returned n
> >>> >> >> > on-zero value:1
> >>> >> >> >        at
> >>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >>> >> >> > rt.java:124)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >>> >> >> > port.java:54)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >>> >> >> > 208)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >>> >> >> > rt.java:29)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >>> >> >> > nManager.java:490)
> >>> >> >> >        at
> >>> >> >> >
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >>> >> >> > ultLifecycleExecutor.java:694)
> >>> >> >> >        ... 17 more
> >>> >> >> > [INFO]
> >>> >> >> >
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >> > [INFO] Total time: 23 seconds
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <
> vdichev@gmail.com>
> >>> >> wrote:
> >>> >> >> >
> >>> >> >> > > > Yes
> >>> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
> >>> >> >> > > >
> >>> >> >> > > > What's the mean " command line returned non-zero value:1"
> in
> >>> >> maven?
> >>> >> >> > >
> >>> >> >> > > Depends on these "204 errors found". Why don't you do as
> maven
> >>> >> >> > > suggests and "run Maven with the -e switch"?
> >>> >> >> > >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> > --
> >>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >> --
> >>> >> >> Lift, the simply functional web framework http://liftweb.net
> >>> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >>> >> >> Follow me: http://twitter.com/dpp
> >>> >> >> Surf the harmonics
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >> >
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Scala中文社区:  http://groups.google.com/group/scalacn
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> Scala中文社区:  http://groups.google.com/group/scalacn
> >>
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
@Xuefeng still having problems? Since the latest code drop works on
Hudson, it must be something in your environment. Hast something
changed recently?

D.

On Wed, Nov 4, 2009 at 1:13 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Looked at the log in the Jira item and compared it to my own log. I
> only see a few differences related to the dependencies  related to JMX
> functionality.
>
> [INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
> updates from scala-stats
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
> '<HTML><HEAD><TITLE>NetScreen' - RETRYING
>
>
> Did you try and delete the .m2 repository. If you don't want to delete
> it what about renaming it.
>
> D.
>
> On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> Done,
>> attached
>>
>> On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hi...@gmail.com>wrote:
>>
>>> Saw Jira item. Thanks.
>>>
>>> But we still need to see the entire log.  Could you attach it to the
>>> item as an attachment.
>>>
>>> The one link you posted in the Jira item about the Lift error in
>>> Hudson looks very similar. Once we get the entire maven log, it will
>>> be a lot easier to see if this is the problem.
>>>
>>> D.
>>>
>>> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> > @D.
>>> > I created https://issues.apache.org/jira/browse/ESME-118
>>> >
>>> > Thanks.
>>> >
>>> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hirsch.dick@gmail.com
>>> >wrote:
>>> >
>>> >> Why don't you create a Jira item and attach the entire trace as an
>>> >> attachment. Like this "mvn clean install > mytrace".
>>> >>
>>> >> We can then get a better idea of what is going on.
>>> >>
>>> >> D.
>>> >>
>>> >>
>>> >>
>>> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> > Thank you for your response.
>>> >> >
>>> >> > @D
>>> >> > I checked out new from SVN but failed too.
>>> >> >
>>> >> > @David
>>> >> > I run 'mvn -U clean install jetty:run' and failed too , get the same
>>> >> error:
>>> >> > command line returned non-zero value:1
>>> >> > I didn't rename .m2 folder and my other maven projects are working.
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>>> >> > <fe...@gmail.com>wrote:
>>> >> >
>>> >> >> Did you do a successful "mvn -U clean install jetty:run" before
>>> trying
>>> >> to
>>> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting
>>> the
>>> >> >> process?
>>> >> >>
>>> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>> >> >>
>>> >> >> > I run mvn clean install -e
>>> >> >> > get:
>>> >> >> >
>>> >> >> > [WARNING] 204 errors found
>>> >> >> > [INFO]
>>> >> >> >
>>> >> ------------------------------------------------------------------------
>>> >> >> > [ERROR] BUILD FAILURE
>>> >> >> > [INFO]
>>> >> >> >
>>> >> ------------------------------------------------------------------------
>>> >> >> > [INFO] command line returned non-zero value:1
>>> >> >> > [INFO]
>>> >> >> >
>>> >> ------------------------------------------------------------------------
>>> >> >> > [INFO] Trace
>>> >> >> > org.apache.maven.BuildFailureException: command line returned
>>> non-zero
>>> >> >> > value:1
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> > ultLifecycleExecutor.java:715)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> >> >> > ltLifecycleExecutor.java:535)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> >> >> > ts(DefaultLifecycleExecutor.java:348)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> >> >> > fecycleExecutor.java:180)
>>> >> >> >        at
>>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> >> >> >        at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>>> >> >> > 0)
>>> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> >> >> >        at
>>> >> >> >
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> >> >> > java:39)
>>> >> >> >        at
>>> >> >> >
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> >> >> > sorImpl.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.MojoFailureException: command
>>> line
>>> >> >> > returned n
>>> >> >> > on-zero value:1
>>> >> >> >        at
>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >> >        at
>>> >> >> >
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>>> >> >> > rt.java:124)
>>> >> >> >        at
>>> >> >> >
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>>> >> >> > port.java:54)
>>> >> >> >        at
>>> >> >> >
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>>> >> >> > 208)
>>> >> >> >        at
>>> >> >> >
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>>> >> >> > rt.java:29)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> >> >> > nManager.java:490)
>>> >> >> >        at
>>> >> >> >
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >> > ultLifecycleExecutor.java:694)
>>> >> >> >        ... 17 more
>>> >> >> > [INFO]
>>> >> >> >
>>> >> ------------------------------------------------------------------------
>>> >> >> > [INFO] Total time: 23 seconds
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
>>> >> wrote:
>>> >> >> >
>>> >> >> > > > Yes
>>> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
>>> >> >> > > >
>>> >> >> > > > What's the mean " command line returned non-zero value:1" in
>>> >> maven?
>>> >> >> > >
>>> >> >> > > Depends on these "204 errors found". Why don't you do as maven
>>> >> >> > > suggests and "run Maven with the -e switch"?
>>> >> >> > >
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > --
>>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Lift, the simply functional web framework http://liftweb.net
>>> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>>> >> >> Follow me: http://twitter.com/dpp
>>> >> >> Surf the harmonics
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Scala中文社区:  http://groups.google.com/group/scalacn
>>> >
>>>
>>
>>
>>
>> --
>> Scala中文社区:  http://groups.google.com/group/scalacn
>>
>

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Looked at the log in the Jira item and compared it to my own log. I
only see a few differences related to the dependencies  related to JMX
functionality.

[INFO] snapshot net.liftweb:lift-util:1.1-SNAPSHOT: checking for
updates from scala-stats
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'464631c2d7f564b00fe7028f09455d658b1265c6'; remote =
'<HTML><HEAD><TITLE>NetScreen' - RETRYING


Did you try and delete the .m2 repository. If you don't want to delete
it what about renaming it.

D.

On Wed, Nov 4, 2009 at 6:29 AM, Xuefeng Wu <be...@gmail.com> wrote:
> Done,
> attached
>
> On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> Saw Jira item. Thanks.
>>
>> But we still need to see the entire log.  Could you attach it to the
>> item as an attachment.
>>
>> The one link you posted in the Jira item about the Lift error in
>> Hudson looks very similar. Once we get the entire maven log, it will
>> be a lot easier to see if this is the problem.
>>
>> D.
>>
>> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> > @D.
>> > I created https://issues.apache.org/jira/browse/ESME-118
>> >
>> > Thanks.
>> >
>> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> Why don't you create a Jira item and attach the entire trace as an
>> >> attachment. Like this "mvn clean install > mytrace".
>> >>
>> >> We can then get a better idea of what is going on.
>> >>
>> >> D.
>> >>
>> >>
>> >>
>> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> > Thank you for your response.
>> >> >
>> >> > @D
>> >> > I checked out new from SVN but failed too.
>> >> >
>> >> > @David
>> >> > I run 'mvn -U clean install jetty:run' and failed too , get the same
>> >> error:
>> >> > command line returned non-zero value:1
>> >> > I didn't rename .m2 folder and my other maven projects are working.
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> >> > <fe...@gmail.com>wrote:
>> >> >
>> >> >> Did you do a successful "mvn -U clean install jetty:run" before
>> trying
>> >> to
>> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting
>> the
>> >> >> process?
>> >> >>
>> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >> >>
>> >> >> > I run mvn clean install -e
>> >> >> > get:
>> >> >> >
>> >> >> > [WARNING] 204 errors found
>> >> >> > [INFO]
>> >> >> >
>> >> ------------------------------------------------------------------------
>> >> >> > [ERROR] BUILD FAILURE
>> >> >> > [INFO]
>> >> >> >
>> >> ------------------------------------------------------------------------
>> >> >> > [INFO] command line returned non-zero value:1
>> >> >> > [INFO]
>> >> >> >
>> >> ------------------------------------------------------------------------
>> >> >> > [INFO] Trace
>> >> >> > org.apache.maven.BuildFailureException: command line returned
>> non-zero
>> >> >> > value:1
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> > ultLifecycleExecutor.java:715)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >> > ltLifecycleExecutor.java:535)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >> > fecycleExecutor.java:180)
>> >> >> >        at
>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >> >        at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> >> > 0)
>> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> >> >> >        at
>> >> >> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >> > java:39)
>> >> >> >        at
>> >> >> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >> > sorImpl.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.MojoFailureException: command
>> line
>> >> >> > returned n
>> >> >> > on-zero value:1
>> >> >> >        at
>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >> >        at
>> >> >> >
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> >> > rt.java:124)
>> >> >> >        at
>> >> >> >
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> >> > port.java:54)
>> >> >> >        at
>> >> >> >
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> >> > 208)
>> >> >> >        at
>> >> >> >
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> >> > rt.java:29)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >> > nManager.java:490)
>> >> >> >        at
>> >> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >> > ultLifecycleExecutor.java:694)
>> >> >> >        ... 17 more
>> >> >> > [INFO]
>> >> >> >
>> >> ------------------------------------------------------------------------
>> >> >> > [INFO] Total time: 23 seconds
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
>> >> wrote:
>> >> >> >
>> >> >> > > > Yes
>> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
>> >> >> > > >
>> >> >> > > > What's the mean " command line returned non-zero value:1" in
>> >> maven?
>> >> >> > >
>> >> >> > > Depends on these "204 errors found". Why don't you do as maven
>> >> >> > > suggests and "run Maven with the -e switch"?
>> >> >> > >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Lift, the simply functional web framework http://liftweb.net
>> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>> >> >> Follow me: http://twitter.com/dpp
>> >> >> Surf the harmonics
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
Done,
attached

On Wed, Nov 4, 2009 at 1:07 PM, Richard Hirsch <hi...@gmail.com>wrote:

> Saw Jira item. Thanks.
>
> But we still need to see the entire log.  Could you attach it to the
> item as an attachment.
>
> The one link you posted in the Jira item about the Lift error in
> Hudson looks very similar. Once we get the entire maven log, it will
> be a lot easier to see if this is the problem.
>
> D.
>
> On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
> > @D.
> > I created https://issues.apache.org/jira/browse/ESME-118
> >
> > Thanks.
> >
> > On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> Why don't you create a Jira item and attach the entire trace as an
> >> attachment. Like this "mvn clean install > mytrace".
> >>
> >> We can then get a better idea of what is going on.
> >>
> >> D.
> >>
> >>
> >>
> >> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
> >> > Thank you for your response.
> >> >
> >> > @D
> >> > I checked out new from SVN but failed too.
> >> >
> >> > @David
> >> > I run 'mvn -U clean install jetty:run' and failed too , get the same
> >> error:
> >> > command line returned non-zero value:1
> >> > I didn't rename .m2 folder and my other maven projects are working.
> >> >
> >> >
> >> >
> >> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> >> > <fe...@gmail.com>wrote:
> >> >
> >> >> Did you do a successful "mvn -U clean install jetty:run" before
> trying
> >> to
> >> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting
> the
> >> >> process?
> >> >>
> >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >> >>
> >> >> > I run mvn clean install -e
> >> >> > get:
> >> >> >
> >> >> > [WARNING] 204 errors found
> >> >> > [INFO]
> >> >> >
> >> ------------------------------------------------------------------------
> >> >> > [ERROR] BUILD FAILURE
> >> >> > [INFO]
> >> >> >
> >> ------------------------------------------------------------------------
> >> >> > [INFO] command line returned non-zero value:1
> >> >> > [INFO]
> >> >> >
> >> ------------------------------------------------------------------------
> >> >> > [INFO] Trace
> >> >> > org.apache.maven.BuildFailureException: command line returned
> non-zero
> >> >> > value:1
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> > ultLifecycleExecutor.java:715)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >> > ltLifecycleExecutor.java:535)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >> > fecycleExecutor.java:180)
> >> >> >        at
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >> >        at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >> >        at
> >> >> >
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> >> > 0)
> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> >> >> >        at
> >> >> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >> > java:39)
> >> >> >        at
> >> >> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >> > sorImpl.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.MojoFailureException: command
> line
> >> >> > returned n
> >> >> > on-zero value:1
> >> >> >        at
> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >> >        at
> >> >> >
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> >> > rt.java:124)
> >> >> >        at
> >> >> >
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> >> > port.java:54)
> >> >> >        at
> >> >> >
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> >> > 208)
> >> >> >        at
> >> >> >
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> >> > rt.java:29)
> >> >> >        at
> >> >> >
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >> > nManager.java:490)
> >> >> >        at
> >> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >> > ultLifecycleExecutor.java:694)
> >> >> >        ... 17 more
> >> >> > [INFO]
> >> >> >
> >> ------------------------------------------------------------------------
> >> >> > [INFO] Total time: 23 seconds
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
> >> wrote:
> >> >> >
> >> >> > > > Yes
> >> >> > > > I'm on line and run mvn jetty:run and get the same error:
> >> >> > > >
> >> >> > > > What's the mean " command line returned non-zero value:1" in
> >> maven?
> >> >> > >
> >> >> > > Depends on these "204 errors found". Why don't you do as maven
> >> >> > > suggests and "run Maven with the -e switch"?
> >> >> > >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Lift, the simply functional web framework http://liftweb.net
> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >> >> Follow me: http://twitter.com/dpp
> >> >> Surf the harmonics
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Saw Jira item. Thanks.

But we still need to see the entire log.  Could you attach it to the
item as an attachment.

The one link you posted in the Jira item about the Lift error in
Hudson looks very similar. Once we get the entire maven log, it will
be a lot easier to see if this is the problem.

D.

On Wed, Nov 4, 2009 at 2:27 AM, Xuefeng Wu <be...@gmail.com> wrote:
> @D.
> I created https://issues.apache.org/jira/browse/ESME-118
>
> Thanks.
>
> On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> Why don't you create a Jira item and attach the entire trace as an
>> attachment. Like this "mvn clean install > mytrace".
>>
>> We can then get a better idea of what is going on.
>>
>> D.
>>
>>
>>
>> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
>> > Thank you for your response.
>> >
>> > @D
>> > I checked out new from SVN but failed too.
>> >
>> > @David
>> > I run 'mvn -U clean install jetty:run' and failed too , get the same
>> error:
>> > command line returned non-zero value:1
>> > I didn't rename .m2 folder and my other maven projects are working.
>> >
>> >
>> >
>> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
>> > <fe...@gmail.com>wrote:
>> >
>> >> Did you do a successful "mvn -U clean install jetty:run" before trying
>> to
>> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
>> >> process?
>> >>
>> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
>> >>
>> >> > I run mvn clean install -e
>> >> > get:
>> >> >
>> >> > [WARNING] 204 errors found
>> >> > [INFO]
>> >> >
>> ------------------------------------------------------------------------
>> >> > [ERROR] BUILD FAILURE
>> >> > [INFO]
>> >> >
>> ------------------------------------------------------------------------
>> >> > [INFO] command line returned non-zero value:1
>> >> > [INFO]
>> >> >
>> ------------------------------------------------------------------------
>> >> > [INFO] Trace
>> >> > org.apache.maven.BuildFailureException: command line returned non-zero
>> >> > value:1
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> > ultLifecycleExecutor.java:715)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> > fecycle(DefaultLifecycleExecutor.java:556)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> > ltLifecycleExecutor.java:535)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> > ts(DefaultLifecycleExecutor.java:348)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> > fecycleExecutor.java:180)
>> >> >        at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >> >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> >        at
>> >> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> >> > 0)
>> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> >        at
>> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> > java:39)
>> >> >        at
>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> > sorImpl.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.MojoFailureException: command line
>> >> > returned n
>> >> > on-zero value:1
>> >> >        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >        at
>> >> > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> >> > rt.java:124)
>> >> >        at
>> >> > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> >> > port.java:54)
>> >> >        at
>> >> > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> >> > 208)
>> >> >        at
>> >> > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> >> > rt.java:29)
>> >> >        at
>> >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> > nManager.java:490)
>> >> >        at
>> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> > ultLifecycleExecutor.java:694)
>> >> >        ... 17 more
>> >> > [INFO]
>> >> >
>> ------------------------------------------------------------------------
>> >> > [INFO] Total time: 23 seconds
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
>> wrote:
>> >> >
>> >> > > > Yes
>> >> > > > I'm on line and run mvn jetty:run and get the same error:
>> >> > > >
>> >> > > > What's the mean " command line returned non-zero value:1" in
>> maven?
>> >> > >
>> >> > > Depends on these "204 errors found". Why don't you do as maven
>> >> > > suggests and "run Maven with the -e switch"?
>> >> > >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Lift, the simply functional web framework http://liftweb.net
>> >> Beginning Scala http://www.apress.com/book/view/1430219890
>> >> Follow me: http://twitter.com/dpp
>> >> Surf the harmonics
>> >>
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
@D.
I created https://issues.apache.org/jira/browse/ESME-118

Thanks.

On Wed, Nov 4, 2009 at 1:29 AM, Richard Hirsch <hi...@gmail.com>wrote:

> Why don't you create a Jira item and attach the entire trace as an
> attachment. Like this "mvn clean install > mytrace".
>
> We can then get a better idea of what is going on.
>
> D.
>
>
>
> On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
> > Thank you for your response.
> >
> > @D
> > I checked out new from SVN but failed too.
> >
> > @David
> > I run 'mvn -U clean install jetty:run' and failed too , get the same
> error:
> > command line returned non-zero value:1
> > I didn't rename .m2 folder and my other maven projects are working.
> >
> >
> >
> > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> > <fe...@gmail.com>wrote:
> >
> >> Did you do a successful "mvn -U clean install jetty:run" before trying
> to
> >> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
> >> process?
> >>
> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
> >>
> >> > I run mvn clean install -e
> >> > get:
> >> >
> >> > [WARNING] 204 errors found
> >> > [INFO]
> >> >
> ------------------------------------------------------------------------
> >> > [ERROR] BUILD FAILURE
> >> > [INFO]
> >> >
> ------------------------------------------------------------------------
> >> > [INFO] command line returned non-zero value:1
> >> > [INFO]
> >> >
> ------------------------------------------------------------------------
> >> > [INFO] Trace
> >> > org.apache.maven.BuildFailureException: command line returned non-zero
> >> > value:1
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> > ultLifecycleExecutor.java:715)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> > fecycle(DefaultLifecycleExecutor.java:556)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> > ltLifecycleExecutor.java:535)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> > dleFailures(DefaultLifecycleExecutor.java:387)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> > ts(DefaultLifecycleExecutor.java:348)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> > fecycleExecutor.java:180)
> >> >        at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >> >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> >        at
> >> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> >> > 0)
> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> >        at
> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> > java:39)
> >> >        at
> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> > sorImpl.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.MojoFailureException: command line
> >> > returned n
> >> > on-zero value:1
> >> >        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >        at
> >> > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> >> > rt.java:124)
> >> >        at
> >> > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> >> > port.java:54)
> >> >        at
> >> > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> >> > 208)
> >> >        at
> >> > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> >> > rt.java:29)
> >> >        at
> >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> > nManager.java:490)
> >> >        at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> > ultLifecycleExecutor.java:694)
> >> >        ... 17 more
> >> > [INFO]
> >> >
> ------------------------------------------------------------------------
> >> > [INFO] Total time: 23 seconds
> >> >
> >> >
> >> >
> >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com>
> wrote:
> >> >
> >> > > > Yes
> >> > > > I'm on line and run mvn jetty:run and get the same error:
> >> > > >
> >> > > > What's the mean " command line returned non-zero value:1" in
> maven?
> >> > >
> >> > > Depends on these "204 errors found". Why don't you do as maven
> >> > > suggests and "run Maven with the -e switch"?
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Scala中文社区:  http://groups.google.com/group/scalacn
> >> >
> >>
> >>
> >>
> >> --
> >> Lift, the simply functional web framework http://liftweb.net
> >> Beginning Scala http://www.apress.com/book/view/1430219890
> >> Follow me: http://twitter.com/dpp
> >> Surf the harmonics
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Why don't you create a Jira item and attach the entire trace as an
attachment. Like this "mvn clean install > mytrace".

We can then get a better idea of what is going on.

D.



On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <be...@gmail.com> wrote:
> Thank you for your response.
>
> @D
> I checked out new from SVN but failed too.
>
> @David
> I run 'mvn -U clean install jetty:run' and failed too , get the same error:
> command line returned non-zero value:1
> I didn't rename .m2 folder and my other maven projects are working.
>
>
>
> On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
> <fe...@gmail.com>wrote:
>
>> Did you do a successful "mvn -U clean install jetty:run" before trying to
>> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
>> process?
>>
>> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
>>
>> > I run mvn clean install -e
>> > get:
>> >
>> > [WARNING] 204 errors found
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [ERROR] BUILD FAILURE
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] command line returned non-zero value:1
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Trace
>> > org.apache.maven.BuildFailureException: command line returned non-zero
>> > value:1
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> > ultLifecycleExecutor.java:715)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> > fecycle(DefaultLifecycleExecutor.java:556)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> > ltLifecycleExecutor.java:535)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> > dleFailures(DefaultLifecycleExecutor.java:387)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> > ts(DefaultLifecycleExecutor.java:348)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> > fecycleExecutor.java:180)
>> >        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >        at
>> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> > 0)
>> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >        at
>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> > java:39)
>> >        at
>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> > sorImpl.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.MojoFailureException: command line
>> > returned n
>> > on-zero value:1
>> >        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >        at
>> > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
>> > rt.java:124)
>> >        at
>> > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
>> > port.java:54)
>> >        at
>> > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
>> > 208)
>> >        at
>> > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
>> > rt.java:29)
>> >        at
>> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> > nManager.java:490)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> > ultLifecycleExecutor.java:694)
>> >        ... 17 more
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Total time: 23 seconds
>> >
>> >
>> >
>> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com> wrote:
>> >
>> > > > Yes
>> > > > I'm on line and run mvn jetty:run and get the same error:
>> > > >
>> > > > What's the mean " command line returned non-zero value:1" in maven?
>> > >
>> > > Depends on these "204 errors found". Why don't you do as maven
>> > > suggests and "run Maven with the -e switch"?
>> > >
>> >
>> >
>> >
>> > --
>> > Scala中文社区:  http://groups.google.com/group/scalacn
>> >
>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Surf the harmonics
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
Thank you for your response.

@D
I checked out new from SVN but failed too.

@David
I run 'mvn -U clean install jetty:run' and failed too , get the same error:
command line returned non-zero value:1
I didn't rename .m2 folder and my other maven projects are working.



On Tue, Nov 3, 2009 at 9:59 PM, David Pollak
<fe...@gmail.com>wrote:

> Did you do a successful "mvn -U clean install jetty:run" before trying to
> apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
> process?
>
> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:
>
> > I run mvn clean install -e
> > get:
> >
> > [WARNING] 204 errors found
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] command line returned non-zero value:1
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Trace
> > org.apache.maven.BuildFailureException: command line returned non-zero
> > value:1
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:715)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> > fecycle(DefaultLifecycleExecutor.java:556)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> > ltLifecycleExecutor.java:535)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > dleFailures(DefaultLifecycleExecutor.java:387)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > ts(DefaultLifecycleExecutor.java:348)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> > fecycleExecutor.java:180)
> >        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >        at
> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> > 0)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> >        at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > sorImpl.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.MojoFailureException: command line
> > returned n
> > on-zero value:1
> >        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >        at
> > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> > rt.java:124)
> >        at
> > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> > port.java:54)
> >        at
> > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> > 208)
> >        at
> > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> > rt.java:29)
> >        at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> > nManager.java:490)
> >        at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:694)
> >        ... 17 more
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 23 seconds
> >
> >
> >
> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com> wrote:
> >
> > > > Yes
> > > > I'm on line and run mvn jetty:run and get the same error:
> > > >
> > > > What's the mean " command line returned non-zero value:1" in maven?
> > >
> > > Depends on these "204 errors found". Why don't you do as maven
> > > suggests and "run Maven with the -e switch"?
> > >
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by David Pollak <fe...@gmail.com>.
Did you do a successful "mvn -U clean install jetty:run" before trying to
apply the "-o" switch?  Did you do an rm -rf ~/.m2 before starting the
process?

On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <be...@gmail.com> wrote:

> I run mvn clean install -e
> get:
>
> [WARNING] 204 errors found
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] command line returned non-zero value:1
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: command line returned non-zero
> value:1
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:715)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:180)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>        at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.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.MojoFailureException: command line
> returned n
> on-zero value:1
>        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> rt.java:124)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> port.java:54)
>        at
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> 208)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> rt.java:29)
>        at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
>        ... 17 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 23 seconds
>
>
>
> On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com> wrote:
>
> > > Yes
> > > I'm on line and run mvn jetty:run and get the same error:
> > >
> > > What's the mean " command line returned non-zero value:1" in maven?
> >
> > Depends on these "204 errors found". Why don't you do as maven
> > suggests and "run Maven with the -e switch"?
> >
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Have you tried a new SVN "get" in a different directory and then a
"mvn install" in this new directory. Maybe something is corrupted?

D.

On Tue, Nov 3, 2009 at 2:52 PM, Xuefeng Wu <be...@gmail.com> wrote:
> I run mvn clean install -e
> get:
>
> [WARNING] 204 errors found
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] command line returned non-zero value:1
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: command line returned non-zero
> value:1
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:715)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:180)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>        at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.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.MojoFailureException: command line
> returned n
> on-zero value:1
>        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
> rt.java:124)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
> port.java:54)
>        at
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
> 208)
>        at
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
> rt.java:29)
>        at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
>        ... 17 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 23 seconds
>
>
>
> On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com> wrote:
>
>> > Yes
>> > I'm on line and run mvn jetty:run and get the same error:
>> >
>> > What's the mean " command line returned non-zero value:1" in maven?
>>
>> Depends on these "204 errors found". Why don't you do as maven
>> suggests and "run Maven with the -e switch"?
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
I run mvn clean install -e
get:

[WARNING] 204 errors found
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] command line returned non-zero value:1
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: command line returned non-zero
value:1
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:715)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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.MojoFailureException: command line
returned n
on-zero value:1
        at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
        at
org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo
rt.java:124)
        at
org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup
port.java:54)
        at
org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:
208)
        at
org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo
rt.java:29)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
        ... 17 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 23 seconds



On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <vd...@gmail.com> wrote:

> > Yes
> > I'm on line and run mvn jetty:run and get the same error:
> >
> > What's the mean " command line returned non-zero value:1" in maven?
>
> Depends on these "204 errors found". Why don't you do as maven
> suggests and "run Maven with the -e switch"?
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Vassil Dichev <vd...@gmail.com>.
> Yes
> I'm on line and run mvn jetty:run and get the same error:
>
> What's the mean " command line returned non-zero value:1" in maven?

Depends on these "204 errors found". Why don't you do as maven
suggests and "run Maven with the -e switch"?

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
Yes
I'm on line and run mvn jetty:run and get the same error:

What's the mean " command line returned non-zero value:1" in maven?

[WARNING] 204 errors found
[INFO] -------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] -------------------------------------------------------
[INFO] command line returned non-zero value:1

On Tue, Nov 3, 2009 at 3:22 PM, Richard Hirsch <hi...@gmail.com>wrote:

> Does the online build ("mvn clean install") still work?
>
> On Tue, Nov 3, 2009 at 7:31 AM, Xuefeng Wu <be...@gmail.com> wrote:
> > I build failed but I do not think it's because offline.
> >
> > When I run mvn -o clean install
> > I get this:
> >
> > [WARNING] 204 errors found
> > [INFO] ----------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO] ----------------------------------------------------------
> > [INFO] command line returned non-zero value:1
> > [INFO] ----------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> >
> >
> >
> > On Sat, Oct 31, 2009 at 6:23 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> There are a few of us who have trouble compiling ESME when offline.
> >> Although I have everything in the maven repository, I get errors when
> >> doing a "mvn install". Is there something we can do about this - maybe
> >> change the pom.xml?
> >>
> >> D.
> >>
> >
> >
> >
> > --
> > Scala中文社区:  http://groups.google.com/group/scalacn
> >
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Does the online build ("mvn clean install") still work?

On Tue, Nov 3, 2009 at 7:31 AM, Xuefeng Wu <be...@gmail.com> wrote:
> I build failed but I do not think it's because offline.
>
> When I run mvn -o clean install
> I get this:
>
> [WARNING] 204 errors found
> [INFO] ----------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ----------------------------------------------------------
> [INFO] command line returned non-zero value:1
> [INFO] ----------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
>
>
>
> On Sat, Oct 31, 2009 at 6:23 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> There are a few of us who have trouble compiling ESME when offline.
>> Although I have everything in the maven repository, I get errors when
>> doing a "mvn install". Is there something we can do about this - maybe
>> change the pom.xml?
>>
>> D.
>>
>
>
>
> --
> Scala中文社区:  http://groups.google.com/group/scalacn
>

Re: Compiling ESME offline

Posted by Xuefeng Wu <be...@gmail.com>.
I build failed but I do not think it's because offline.

When I run mvn -o clean install
I get this:

[WARNING] 204 errors found
[INFO] ----------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ----------------------------------------------------------
[INFO] command line returned non-zero value:1
[INFO] ----------------------------------------------------------
[INFO] For more information, run Maven with the -e switch



On Sat, Oct 31, 2009 at 6:23 PM, Richard Hirsch <hi...@gmail.com>wrote:

> There are a few of us who have trouble compiling ESME when offline.
> Although I have everything in the maven repository, I get errors when
> doing a "mvn install". Is there something we can do about this - maybe
> change the pom.xml?
>
> D.
>



-- 
Scala中文社区:  http://groups.google.com/group/scalacn

Re: Compiling ESME offline

Posted by Anne Kathrine Petterøe <ak...@gmail.com>.
Solved the problem for me too!

/Anne

On 2. nov. 2009, at 09.58, Richard Hirsch wrote:

> Solved my problem as well.
>
> I also updated the openid4java version to 0.9.5 as described in the
> lift list (http://github.com/dpp/liftweb/issues/closed/#issue/109).
>
> While I was working on the pom.xml, I also turned off the warnings for
> the yuicompressor. We can turn them back on at a later date but they
> created extra log entries during the compile task.
>
> Thanks.
>
> D.
>
> On Sun, Nov 1, 2009 at 6:16 PM, Ethan Jewett <es...@gmail.com>  
> wrote:
>> This seems to have worked for me. Thank you! That will help a lot.
>>
>> Ethan
>>
>> On Sun, Nov 1, 2009 at 8:34 AM, David Pollak
>> <fe...@gmail.com> wrote:
>>> Please delete your local Maven repository (on Unix-y systems rm - 
>>> rf ~/.m2)
>>>
>>> Try a clean build and then an offline build.  There was a bug in  
>>> an older
>>> Maven-Scala plugin that prohibited offline builds.  It was fixed a  
>>> long time
>>> ago, but you may still be using that version.  Also, what version  
>>> of Maven
>>> are you using?
>>>
>>> On Sun, Nov 1, 2009 at 6:17 AM, Richard Hirsch <hirsch.dick@gmail.com 
>>> >wrote:
>>>
>>>> NFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Failed to resolve artifact.
>>>>
>>>> Missing:
>>>> ----------
>>>> 1) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>>>
>>>> 2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>>>
>>>> 3) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>>>
>>>> 4) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>>>
>>>> 5) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>>>
>>>> 6) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>>>
>>>>  Try downloading the file manually from the project website.
>>>>
>>>>  Then, install it using the command:
>>>>      mvn install:install-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>>
>>>>  Alternatively, if you host your own repository you can deploy  
>>>> the file
>>>> there:
>>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>
>>>>  Path to dependency:
>>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>        2) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>>>
>>>> ----------
>>>> 6 required artifacts are missing.
>>>>
>>>> for artifact:
>>>>  org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>>
>>>> from the specified remote repositories:
>>>>  scala-stats (http://www.lag.net/nest),
>>>>  compass-project.org (http://repo.compass-project.org),
>>>>  scala-tools.org (http://scala-tools.org/repo-releases),
>>>>  opendmk (http://maven.tigase.org/),
>>>>  configgy (http://www.lag.net/repo),
>>>>  scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots),
>>>>  central (http://repo1.maven.org/maven2)
>>>>
>>>>
>>>> NOTE: Maven is executing in offline mode. Any artifacts not  
>>>> already in
>>>> your local
>>>> repository will be inaccessible.
>>>>
>>>>
>>>>
>>>> On Sat, Oct 31, 2009 at 4:08 PM, David Pollak
>>>> <fe...@gmail.com> wrote:
>>>>> Please try:
>>>>>
>>>>> mvn -o clean install
>>>>>
>>>>> What's the error?
>>>>>
>>>>> On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hirsch.dick@gmail.com
>>>>> wrote:
>>>>>
>>>>>> There are a few of us who have trouble compiling ESME when  
>>>>>> offline.
>>>>>> Although I have everything in the maven repository, I get  
>>>>>> errors when
>>>>>> doing a "mvn install". Is there something we can do about this  
>>>>>> - maybe
>>>>>> change the pom.xml?
>>>>>>
>>>>>> D.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lift, the simply functional web framework http://liftweb.net
>>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>> Follow me: http://twitter.com/dpp
>>>>> Surf the harmonics
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Surf the harmonics
>>>
>>


Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
Solved my problem as well.

I also updated the openid4java version to 0.9.5 as described in the
lift list (http://github.com/dpp/liftweb/issues/closed/#issue/109).

While I was working on the pom.xml, I also turned off the warnings for
the yuicompressor. We can turn them back on at a later date but they
created extra log entries during the compile task.

Thanks.

D.

On Sun, Nov 1, 2009 at 6:16 PM, Ethan Jewett <es...@gmail.com> wrote:
> This seems to have worked for me. Thank you! That will help a lot.
>
> Ethan
>
> On Sun, Nov 1, 2009 at 8:34 AM, David Pollak
> <fe...@gmail.com> wrote:
>> Please delete your local Maven repository (on Unix-y systems rm -rf ~/.m2)
>>
>> Try a clean build and then an offline build.  There was a bug in an older
>> Maven-Scala plugin that prohibited offline builds.  It was fixed a long time
>> ago, but you may still be using that version.  Also, what version of Maven
>> are you using?
>>
>> On Sun, Nov 1, 2009 at 6:17 AM, Richard Hirsch <hi...@gmail.com>wrote:
>>
>>> NFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Failed to resolve artifact.
>>>
>>> Missing:
>>> ----------
>>> 1) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>>
>>> 2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>>
>>> 3) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>>
>>> 4) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>>
>>> 5) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>>
>>> 6) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>>
>>>  Try downloading the file manually from the project website.
>>>
>>>  Then, install it using the command:
>>>      mvn install:install-file -DgroupId=net.liftweb
>>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>  Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>>  Path to dependency:
>>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>        2) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>>
>>> ----------
>>> 6 required artifacts are missing.
>>>
>>> for artifact:
>>>  org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>>
>>> from the specified remote repositories:
>>>  scala-stats (http://www.lag.net/nest),
>>>  compass-project.org (http://repo.compass-project.org),
>>>  scala-tools.org (http://scala-tools.org/repo-releases),
>>>  opendmk (http://maven.tigase.org/),
>>>  configgy (http://www.lag.net/repo),
>>>  scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots),
>>>  central (http://repo1.maven.org/maven2)
>>>
>>>
>>> NOTE: Maven is executing in offline mode. Any artifacts not already in
>>> your local
>>> repository will be inaccessible.
>>>
>>>
>>>
>>> On Sat, Oct 31, 2009 at 4:08 PM, David Pollak
>>> <fe...@gmail.com> wrote:
>>> > Please try:
>>> >
>>> > mvn -o clean install
>>> >
>>> > What's the error?
>>> >
>>> > On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hirsch.dick@gmail.com
>>> >wrote:
>>> >
>>> >> There are a few of us who have trouble compiling ESME when offline.
>>> >> Although I have everything in the maven repository, I get errors when
>>> >> doing a "mvn install". Is there something we can do about this - maybe
>>> >> change the pom.xml?
>>> >>
>>> >> D.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Lift, the simply functional web framework http://liftweb.net
>>> > Beginning Scala http://www.apress.com/book/view/1430219890
>>> > Follow me: http://twitter.com/dpp
>>> > Surf the harmonics
>>> >
>>>
>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Surf the harmonics
>>
>

Re: Compiling ESME offline

Posted by Ethan Jewett <es...@gmail.com>.
This seems to have worked for me. Thank you! That will help a lot.

Ethan

On Sun, Nov 1, 2009 at 8:34 AM, David Pollak
<fe...@gmail.com> wrote:
> Please delete your local Maven repository (on Unix-y systems rm -rf ~/.m2)
>
> Try a clean build and then an offline build.  There was a bug in an older
> Maven-Scala plugin that prohibited offline builds.  It was fixed a long time
> ago, but you may still be using that version.  Also, what version of Maven
> are you using?
>
> On Sun, Nov 1, 2009 at 6:17 AM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> NFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>>
>> 2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>>
>> 3) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>>
>> 4) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>>
>> 5) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>>
>> 6) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>      mvn install:install-file -DgroupId=net.liftweb
>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>      mvn deploy:deploy-file -DgroupId=net.liftweb
>> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>        2) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>>
>> ----------
>> 6 required artifacts are missing.
>>
>> for artifact:
>>  org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>>
>> from the specified remote repositories:
>>  scala-stats (http://www.lag.net/nest),
>>  compass-project.org (http://repo.compass-project.org),
>>  scala-tools.org (http://scala-tools.org/repo-releases),
>>  opendmk (http://maven.tigase.org/),
>>  configgy (http://www.lag.net/repo),
>>  scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots),
>>  central (http://repo1.maven.org/maven2)
>>
>>
>> NOTE: Maven is executing in offline mode. Any artifacts not already in
>> your local
>> repository will be inaccessible.
>>
>>
>>
>> On Sat, Oct 31, 2009 at 4:08 PM, David Pollak
>> <fe...@gmail.com> wrote:
>> > Please try:
>> >
>> > mvn -o clean install
>> >
>> > What's the error?
>> >
>> > On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>> >
>> >> There are a few of us who have trouble compiling ESME when offline.
>> >> Although I have everything in the maven repository, I get errors when
>> >> doing a "mvn install". Is there something we can do about this - maybe
>> >> change the pom.xml?
>> >>
>> >> D.
>> >>
>> >
>> >
>> >
>> > --
>> > Lift, the simply functional web framework http://liftweb.net
>> > Beginning Scala http://www.apress.com/book/view/1430219890
>> > Follow me: http://twitter.com/dpp
>> > Surf the harmonics
>> >
>>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>

Re: Compiling ESME offline

Posted by David Pollak <fe...@gmail.com>.
Please delete your local Maven repository (on Unix-y systems rm -rf ~/.m2)

Try a clean build and then an offline build.  There was a bug in an older
Maven-Scala plugin that prohibited offline builds.  It was fixed a long time
ago, but you may still be using that version.  Also, what version of Maven
are you using?

On Sun, Nov 1, 2009 at 6:17 AM, Richard Hirsch <hi...@gmail.com>wrote:

> NFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-util:jar:1.1-SNAPSHOT
>
> 2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT
>
> 3) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT
>
> 4) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT
>
> 5) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-openid:jar:1.1-SNAPSHOT
>
> 6) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb
> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>      mvn deploy:deploy-file -DgroupId=net.liftweb
> -DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>        2) net.liftweb:lift-textile:jar:1.1-SNAPSHOT
>
> ----------
> 6 required artifacts are missing.
>
> for artifact:
>  org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
>
> from the specified remote repositories:
>  scala-stats (http://www.lag.net/nest),
>  compass-project.org (http://repo.compass-project.org),
>  scala-tools.org (http://scala-tools.org/repo-releases),
>  opendmk (http://maven.tigase.org/),
>  configgy (http://www.lag.net/repo),
>  scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots),
>  central (http://repo1.maven.org/maven2)
>
>
> NOTE: Maven is executing in offline mode. Any artifacts not already in
> your local
> repository will be inaccessible.
>
>
>
> On Sat, Oct 31, 2009 at 4:08 PM, David Pollak
> <fe...@gmail.com> wrote:
> > Please try:
> >
> > mvn -o clean install
> >
> > What's the error?
> >
> > On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
> >
> >> There are a few of us who have trouble compiling ESME when offline.
> >> Although I have everything in the maven repository, I get errors when
> >> doing a "mvn install". Is there something we can do about this - maybe
> >> change the pom.xml?
> >>
> >> D.
> >>
> >
> >
> >
> > --
> > Lift, the simply functional web framework http://liftweb.net
> > Beginning Scala http://www.apress.com/book/view/1430219890
> > Follow me: http://twitter.com/dpp
> > Surf the harmonics
> >
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Re: Compiling ESME offline

Posted by Richard Hirsch <hi...@gmail.com>.
NFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) net.liftweb:lift-util:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-util -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-util:jar:1.1-SNAPSHOT

2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-webkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-webkit:jar:1.1-SNAPSHOT

3) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-mapper -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-mapper:jar:1.1-SNAPSHOT

4) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-testkit -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-testkit:jar:1.1-SNAPSHOT

5) net.liftweb:lift-openid:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-openid -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-openid:jar:1.1-SNAPSHOT

6) net.liftweb:lift-textile:jar:1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=net.liftweb
-DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=net.liftweb
-DartifactId=lift-textile -Dversion=1.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.esme:esme-server:war:0.3.0-SNAPSHOT
  	2) net.liftweb:lift-textile:jar:1.1-SNAPSHOT

----------
6 required artifacts are missing.

for artifact:
  org.apache.esme:esme-server:war:0.3.0-SNAPSHOT

from the specified remote repositories:
  scala-stats (http://www.lag.net/nest),
  compass-project.org (http://repo.compass-project.org),
  scala-tools.org (http://scala-tools.org/repo-releases),
  opendmk (http://maven.tigase.org/),
  configgy (http://www.lag.net/repo),
  scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots),
  central (http://repo1.maven.org/maven2)


NOTE: Maven is executing in offline mode. Any artifacts not already in
your local
repository will be inaccessible.



On Sat, Oct 31, 2009 at 4:08 PM, David Pollak
<fe...@gmail.com> wrote:
> Please try:
>
> mvn -o clean install
>
> What's the error?
>
> On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> There are a few of us who have trouble compiling ESME when offline.
>> Although I have everything in the maven repository, I get errors when
>> doing a "mvn install". Is there something we can do about this - maybe
>> change the pom.xml?
>>
>> D.
>>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>

Re: Compiling ESME offline

Posted by David Pollak <fe...@gmail.com>.
Please try:

mvn -o clean install

What's the error?

On Sat, Oct 31, 2009 at 3:23 AM, Richard Hirsch <hi...@gmail.com>wrote:

> There are a few of us who have trouble compiling ESME when offline.
> Although I have everything in the maven repository, I get errors when
> doing a "mvn install". Is there something we can do about this - maybe
> change the pom.xml?
>
> D.
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics