> Yes it works now (and tests passed) on my machine after your commit today
I can confirm this. Thanks Ted.
$ mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000)
Maven home: /usr/share/maven
Java version: 1.6.0_35, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"
$ mvn test
…
------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.drill.plan.ParsePlanTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec
Running org.apache.drill.plan.physical.operators.ScanJsonTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec
Results :
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.637s
[INFO] Finished at: Thu Oct 18 09:04:18 IST 2012
[INFO] Final Memory: 12M/81M
[INFO] ------------------------------------------------------------------------
Cheers,
Michael
--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/
On 18 Oct 2012, at 00:52, Timothy Chen wrote:
> Yes it works now (and tests passed) on my machine after your commit today
> Ted.
>
> Do incubator apache projects don't get CI?
>
> Tim
>
> On Wed, Oct 17, 2012 at 4:51 PM, Ted Dunning <[email protected]> wrote:
>
>> These are fixed and committed. I think some of it may have been Maven 2
>> versus 3. I have only tested with Maven 3.
>>
>>
>>
>> On Wed, Oct 17, 2012 at 9:36 AM, Arunabha Ghosh <[email protected]
>>> wrote:
>>
>>> Will do by eod today
>>>
>>> On Wed, Oct 17, 2012 at 12:43 AM, Timothy Chen <[email protected]>
>> wrote:
>>>
>>>> I'm getting errors as well, complaining about a missing
>> OperatorReference
>>>> reference:
>>>>
>>>> [ERROR]
>>>>
>>>>
>>>
>> /Users/tnachen/src/incubator-drill/sandbox/plan-parser/src/main/java/org/apache/drill/plan/physical/operators/ScanJson.java:[59,57]
>>>> cannot find symbol
>>>> [ERROR] symbol : class OperatorReference
>>>> [ERROR] location: class
>> org.apache.drill.plan.physical.operators.ScanJson
>>>>
>>>> Tim
>>>>
>>>> On Wed, Oct 17, 2012 at 12:41 AM, Michael Hausenblas <
>>>> [email protected]> wrote:
>>>>
>>>>>
>>>>> I have another issue with building it:
>>>>>
>>>>> $ mvn test -X
>>>>>
>>>>> [ERROR] location: class
>>> org.apache.drill.plan.physical.operators.ScanJson
>>>>> [ERROR] -> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute
>>>>> goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>>>> (default-compile) on project plan-parser: Compilation failure
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>>>> at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>>>> at
>>>>>
>>>>
>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at
>>>>>
>>>>
>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>>
>>>>
>>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>>> at
>>>>>
>>>>
>>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>>> at
>>>>>
>>>>
>>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>>> at
>>>>>
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>>>> Caused by: org.apache.maven.plugin.CompilationFailureException:
>>>>> Compilation failure
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
>>>>> at
>>>>> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>>>> at
>>>>>
>>>>
>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>>>> ... 19 more
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Michael
>>>>>
>>>>> --
>>>>> Michael Hausenblas
>>>>> Ireland, Europe
>>>>> http://mhausenblas.info/
>>>>>
>>>>> On 17 Oct 2012, at 08:30, Arunabha Ghosh wrote:
>>>>>
>>>>>> Hi,
>>>>>> I checked out the drill repo today and attempted to build the
>>>> project.
>>>>>> During the build Maven complained about generics, annotations etc
>> not
>>>>> being
>>>>>> available with the 1.3 compiler
>>>>>>
>>>>>> [ERROR]
>>>>>>
>>>>>
>>>>
>>>
>> /home/arunabha/dev/apache-drill/sandbox/plan-parser/src/main/java/org/apache/drill/plan/physical/operators/Operator.java:[49,50]
>>>>>> error: generics are not supported in -source 1.3
>>>>>> [ERROR]
>>>>>> [ERROR] (use -source 5 or higher to enable generics)
>>>>>>
>>>>>> Adding a section to the pom.xml to explicitly set the compiler to >
>>> 1.5
>>>>>> solved the problem, but I'm wondering if I was doing something
>> wrong
>>> ?
>>>> If
>>>>>> not, I'm happy to send a patch with the fix.
>>>>>>
>>>>>> Arunabha
>>>>>
>>>>>
>>>>
>>>
>>