atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1155) Errors in Eclipse when I bring in the latest code
Date Fri, 16 Sep 2016 13:16:21 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496316#comment-15496316
] 

David Radley commented on ATLAS-1155:
-------------------------------------

Googling around it seems that is is not good practice to create Scala empty lists in Java.
The error I reported is reported by many jvms and I could not get rid of the error in an Eclipse
environment. 

The patch I created is to introduce a second Scala constructor which defaults the last parameter
to an empty list in Scala. I now call this new constructor when there are no rows.  

I also saw an error that required me to add a cast in this project- I have fixed that as well.
   

> Errors in Eclipse when I bring in the latest code
> -------------------------------------------------
>
>                 Key: ATLAS-1155
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1155
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8-incubating
>            Reporter: David Radley
>            Assignee: David Radley
>             Fix For: 0.8-incubating
>
>         Attachments: atlas1155.patch
>
>
> I have brought the latest atlas code into an Eclipse environment and see an error in
GraphBackedDiscoveryService, 
> line 154
>  scala.collection.immutable.List.empty()); it says method empty is ambiguous.
> if I replace this expression with null it complies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message