Great.
So please report you "/" problem to buildr jira.
Then you can run

buildr -e hudson test

This will disable axis2-war tests, wich I believe work only for Intalio guys.
And please report your results.

On 25 February 2010 15:49, Jan Sinschek <su...@gmx.net> wrote:
> Rafal Rusin wrote:
>>
>> Please use ODE-1.X branch
>> (http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X/) instead
>> of 1.3.3 sources.
>>
>>
>
> oh, i thought 1.x was just a way of referring to the latest release of the
> version 1 branch of ODE.
> So I got this from svn. Next there was a fix needed on buildr, as it
> recurses infinitely in
> C:\Me\Apps\jruby-1.4.0\lib\ruby\gems\1.8\gems\buildr-1.3.5-java\lib\buildr\core\build.rb:375
> looking for git config files until it arrives at a "/", which it never will
> on windows. I dirtyfixed this to
> File.expand_path(Dir.pwd) != '/' && File.expand_path(Dir.pwd) != 'C:/'  &&
> Dir.chdir('..') do
> for the time being, but i guess a more approriate filesystemroot facility
> should be rather be used, so I shall bugreport that.
> After this fix, the build works fine, but the testing does not, yet,
> spawning
>
> C:\APACHE_ODE_1.X>buildr test
> (in C:/APACHE_ODE_1.X, development)
> Testing ode
> Compiling ode:bpel-api-jca into
> C:/APACHE_ODE_1.X/bpel-api-jca/target/classes
> Compiling ode:dao-hibernate into
> C:/APACHE_ODE_1.X/dao-hibernate/target/classes
> Note:
> C:\APACHE_ODE_1.X\dao-hibernate\src\main\java\org\apache\ode\daohib\bpel\ql\HibernateInstancesQueryCompiler.java
> u
> ses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Compiling ode:dao-hibernate:test into
> C:/APACHE_ODE_1.X/dao-hibernate/target/test/classes
> Compiling ode:jbi-karaf-commands into
> C:/APACHE_ODE_1.X/jbi-karaf-commands/target/classes
> Testing ode:agents
> Testing ode:axis2
> Testing ode:axis2-war
> Compiling ode:axis2-war:test into
> C:/APACHE_ODE_1.X/axis2-war/target/test/classes
> Note:
> C:\APACHE_ODE_1.X\axis2-war\src\test\java\org\apache\ode\axis2\management\InstanceManagementTest.java
> uses uncheck
> ed or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Running tests in ode:axis2-war
> Running TestNG in ode:axis2-war
> Die Befehlszeile ist zu lang.
> ←[31mTest framework error: No such file or directory - File not found -
> C:/APACHE_ODE_1.X/axis2-war/reports/testng/testn
> g-failed.xml←[0m
> ←[31mThe following tests failed:
> org.apache.ode.axis2.BpelActivityTest
> org.apache.ode.axis2.EndpointConfigurationTest
> org.apache.ode.axis2.EndpointTimeoutsTest
> org.apache.ode.axis2.FailureInvokeTest
> org.apache.ode.axis2.MessageStructureTest
> org.apache.ode.axis2.ServiceFaultCatchTest
> org.apache.ode.axis2.SoapHeader2Test
> org.apache.ode.axis2.SoapHeaderTest
> org.apache.ode.axis2.XSDReferencesDeployTest
> org.apache.ode.axis2.correlation.CorrelationJoinHibTest
> org.apache.ode.axis2.correlation.CorrelationJoinLazyHibTest
> org.apache.ode.axis2.correlation.CorrelationJoinLazyTest
> org.apache.ode.axis2.correlation.CorrelationJoinTest
> org.apache.ode.axis2.correlation.CorrelationMultiHibTest
> org.apache.ode.axis2.correlation.CorrelationMultiTest
> org.apache.ode.axis2.httpbinding.HttpBindingTest
> org.apache.ode.axis2.hydration.InstanceCountTest
> org.apache.ode.axis2.hydration.ProcessCountTest
> org.apache.ode.axis2.hydration.ProcessSizeTest
> org.apache.ode.axis2.instancecleanup.CleanFailureHibTest
> org.apache.ode.axis2.instancecleanup.CleanFailureTest
> org.apache.ode.axis2.instancecleanup.CleanFaultHibTest
> org.apache.ode.axis2.instancecleanup.CleanFaultTest
> org.apache.ode.axis2.instancecleanup.CleanSuccessHibTest
> org.apache.ode.axis2.instancecleanup.CleanSuccessTest
> org.apache.ode.axis2.management.DeploymentTest
> org.apache.ode.axis2.management.InstanceManagementTest
> org.apache.ode.axis2.management.RetireTest
> org.apache.ode.axis2.rampart.basic.SecuredProcessesTest
> org.apache.ode.axis2.rampart.basic.SecuredServicesTest
> org.apache.ode.axis2.rampart.policy.SecuredProcessesTest
> org.apache.ode.axis2.rampart.policy.SecuredServicesTest←[0m
> Buildr aborted!
> ←[31mTests failed!←[0m
>
> (See full trace by running task with --trace)
>
> C:\APACHE_ODE_1.X>
>
> Note the German line in between complaining that "the command is too long",
> which persisted even though I had moved the ODE source directory to "C:\"
> instead of any of its subfolders.
> I might try reducing this to C:\O\ as my source directory, but this appears
> rather silly and unstable.  When I first ran the test, it performed
> succesfully a lot of tests before these; I am rather curious why they did
> not show up the second time around.
>
> sincerely,
> jan
>
>
>> On 25 February 2010 12:29, Jan Sinschek <su...@gmx.net> wrote:
>>
>>>
>>> So I installed jruby for windows after removing ruby (from the path) ,
>>> and
>>> got me what buildr --version identifies as
>>> Buildr 1.3.5 (JRuby 1.4.0)
>>> After applying the BUILDR-348 fix, this, just like ruby's buildr used to,
>>> gives me
>>>
>>>
>>>>
>>>> buildr package test=no
>>>>
>>>
>>> ←[34m./tasks/derby.rake:22: Deprecated: See documentation for new way to
>>> access Java code.←[0m
>>> ←[34m./tasks/derby.rake:22: Deprecated: Append to Java.classpath
>>> instead.←[0m
>>> (in C:/Users/CSinschek/Desktop/Attestation/apache-ode-sources-1.3.3,
>>> development)
>>> Buildr aborted!
>>> ←[31mRubyGem version error: buildr(1.3.5 not ~> 1.2.4)
>>> ←[0m
>>>
>>> (See full trace by running task with --trace)
>>>
>>> Now I remember once finding this "~> 1.2.4"  requirement verbatim in the
>>> rakefile and changing it to "~> 1.3.5". That, however, led to another
>>> fault,
>>> so I instead installed version 1.2.4 of buildr, which worked to a point.
>>> JRuby, however, does not seems to be able to install buildr 1.2.4, giving
>>> me
>>> "[...] extconf.rb:20:in `include': undefined method `+' for nil:NilClass
>>> (NoMethodError)
>>>      from extconf.rb:34
>>> ERROR:  Error installing buildr: [...]"
>>>
>>> So I tried again with the modification to the rakefile of apache 1.3, to
>>> Rakefile:17> gem "buildr", "~>1.3.5, getting me where I am now, with this
>>> trace:
>>>
>>> C:\Users\CSinschek\Desktop\Attestation\apache-ode-sources-1.3.3>buildr
>>> --trace _1.3.5_  package test=no
>>> ←[34m./tasks/derby.rake:22: Deprecated: See documentation for new way to
>>> access Java code.←[0m
>>> ←[34m./tasks/derby.rake:22: Deprecated: Append to Java.classpath
>>> instead.←[0m
>>> (in C:/Users/CSinschek/Desktop/Attestation/apache-ode-sources-1.3.3,
>>> development)
>>> Buildr aborted!
>>> ←[31mundefined method `alias_method_chain' for
>>> #<Class:Buildr::Release>←[0m
>>>
>>> C:/Users/CSinschek/Desktop/Attestation/apache-ode-sources-1.3.3/Rakefile:157
>>>
>>> C:/Users/CSinschek/Desktop/Attestation/apache-ode-sources-1.3.3/Rakefile:398:in
>>> `load'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:398:in
>>> `raw_load_buildfil
>>> e'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:218:in
>>> `load_buildfile'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:496:in
>>> `standard_exceptio
>>> n_handling'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:213:in
>>> `load_buildfile'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:137:in
>>> `run'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:496:in
>>> `standard_exceptio
>>> n_handling'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/core/application.rb:135:in
>>> `run'
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/bin/buildr:19
>>>
>>> C:/Me/Apps/jruby-1.4.0/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/bin/buildr:19:in
>>> `load'
>>> C:\Me\Apps\jruby-1.4.0\bin\buildr:19
>>>
>>> From here, I cannot really where it is alias_method_chain shold be
>>> defined
>>> so that it could be found (maybe to be found in buildr 1.2.4?). Any more
>>> ideas? Or does the error concering "1.2.4" want to tell me something I
>>> did
>>> not understand? Any help appreciated
>>>
>>>
>>> regards,
>>> jan
>>>
>>>
>>>
>>> Rafal Rusin wrote:
>>>
>>>>
>>>> On 24 February 2010 13:21, Jan Sinschek <su...@gmx.net> wrote:
>>>>
>>>>
>>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I wanted to start developing on windows ODE, but encountered a number
>>>>> of
>>>>> problems along the way. In terms of documentation:
>>>>> There are three instances of documentation telling me what to do
>>>>> 1) The INSTALL file in the distribution
>>>>> 2) http://ode.apache.org/building-ode.html
>>>>> 3) http://ode.apache.org/eclipse-ide.html
>>>>>
>>>>>
>>>>
>>>> Please go ahead with http://ode.apache.org/building-ode.html.
>>>>
>>>>
>>>>
>>>>>
>>>>> Neither of these work very well, using either ODE 1.3 or 2.0 beta I
>>>>> encounter different errors that I might want to discuss separately.
>>>>> What's
>>>>> surely wrong:
>>>>> ODE 2.0's install guideline wants me to use rake, equals to 2), but in
>>>>> contrast to 3). ODE 2.0, however, no longer has a rakefile.
>>>>>
>>>>> Currently, when compiling ODE 1.3, buildr gets stuck, I might look up
>>>>> where.
>>>>> When building ODE 2.0, buildr complains early on that
>>>>> .../apache-ode-src-2.0-beta2/tasks/derby.rake:22: undefined method
>>>>> `classpath' for Buildr::Java:Module (NoMethodError)
>>>>> This might just be saying that there is something missing on my
>>>>> classpath,
>>>>> but I couldn't tell from the trace or the source line, either.
>>>>>
>>>>> What would you recommend I try? Building version 1.3, 2.0, or a later
>>>>> git
>>>>> checkout?
>>>>> Can I expect to be luckier building on linux (This might not be an
>>>>> option
>>>>> for our team, though)?
>>>>>
>>>>> sincerely,
>>>>> Jan Sinschek
>>>>>
>>>>>
>>>>>
>>>>
>>>> Please use ODE-1.X, jruby with buildr-348 patch and run
>>>> buildr package test=no
>>>>
>>>> This is described in building-ode.html.
>>>> If this doesn't work, create a jira entry.
>>>>
>>>> Regards,
>>>>
>>>>
>>>
>>>
>>
>>
>> Regards,
>>
>
>


Regards,
-- 
Rafał Rusin
http://rrusin.blogspot.com
http://www.touk.pl
http://top.touk.pl

Reply via email to