jakarta-bsf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant elder <ant.el...@gmail.com>
Subject Re: BSF 3.0-beta3 release artifact review
Date Mon, 23 Mar 2009 12:36:14 GMT
On Sun, Mar 22, 2009 at 10:04 PM, Rony G. Flatscher
<Rony.Flatscher@wu-wien.ac.at> wrote:
> Hi ant,
>>>    * problem creating the package, missing "mvn.bat" in "bsf-engines"
>>>      (using maven 2.1.0 on XP SP3 and JDK 4.2, JDK 5, JDK 6):
>>>
>>>      install-engines:
>>>      [INFO]
>>>      ------------------------------------------------------------------------
>>>      [ERROR] BUILD ERROR
>>>      [INFO]
>>>      ------------------------------------------------------------------------
>>>      [INFO] An Ant BuildException has occured: The following error
>>>      occurred while executing this line:
>>>      F:\work\svn\bsf\bsf3\bsf-engines\build.xml:39: Execute failed:
>>>      java.io.IOException: Cannot run program "mvn.bat" (in directory
>>>      "F:\work\svn\bsf\bsf3\bsf-engines"): CreateProcess error=5,
>>>      Zugriff verweigert
>>>
>>>      [INFO]
>>>      ------------------------------------------------------------------------
>>>      [INFO] Trace
>>>      org.apache.maven.lifecycle.LifecycleExecutionException: An Ant
>>>      BuildException has occured: The following error occurred while
>>>      executing this line:
>>>      F:\work\svn\bsf\bsf3\bsf-engines\build.xml:39: Execute failed:
>>>      java.io.IOException: Cannot run program "mvn.bat" (in directory
>>>      "F:\work\svn\bsf\bsf3\bsf-engines"): CreateProcess error=5,
>>>      Zugriff verweigert
>>>              at
>>>      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>>>      ... cut ...
>>>
>>>
>>
>> I'm not sure whats causing that, googling on "CreateProcess error=5"
>> various hits talk about permission problems and make suggestions like
>> "Please check the
>> permissions on these executables and their parent directories", could
>> there be some config thing you can change with your maven or bsf
>> directories?
>>
> Well, I went back and made all directories up to and including the root
> fully accessible to everyone, using the Windows command line utility
> "cacls" (change access control lists) and made sure that also the ant
> and maven files and jars were set to full access to everyone. And lo and
> behold after doing the latter, was the error overcome.
>
> Now it builds, however, one remark: one must juse Java 1.5 to build
> because using 1.4.2 yields:
>
> ------------- cut here --------------
>
> [INFO] Building Apache BSF Utils
> [INFO]    task-segment: [install]
> [INFO] ------------------------------------------------------------------------
> [INFO] [resources:resources]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e.
build is platform dependent!
> [INFO] Copying 2 resources
> [INFO] [compiler:compile]
> Compiling 14 source files to F:\work\svn\bsf\bsf3\bsf-utils\target\classes
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> F:\work\svn\bsf\bsf3\bsf-utils\src\main\java\org\apache\bsf\xml\JavaScriptE4XAxiomHelper.java:[95,20]
cannot resolve symbol
> symbol  : class Factory
> location: class org.mozilla.javascript.xml.XMLLib
>
> F:\work\svn\bsf\bsf3\bsf-utils\src\main\java\org\apache\bsf\xml\JavaScriptE4XAxiomHelper.java:[96,48]
cannot resolve symbol
> symbol  : variable Factory
> location: class org.mozilla.javascript.xml.XMLLib
>
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: Compilation failure
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371
> )
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:324)
>        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.CompilationFailureException: Compilation failure
>        at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429)
>        at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110)
>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>        ... 16 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Sun Mar 22 21:58:33 CET 2009
> [INFO] Final Memory: 13M/24M
> [INFO] ------------------------------------------------------------------------
>
> ------------- cut here --------------
>
> Regards,
>
> ---rony
>

I've just tried using JDK 1.4.2 and it builds ok for me. There was a
problem with bsf-utils using a backlevel version of javascript that
was fixed in r757154, is it possible you've not picked up that change?

   ...ant

---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Mime
View raw message