← Back to team overview

mugle-dev team mailing list archive

[Bug 731919] Re: Resolving Namespace Conflicts on imports

 

The simplest way I could think of is to use the whole namespace only for
the google User class. That is, for that particular class, u can do the
normal import of our class and explicitly use the whole namespace on the
google class:

import au.edu.unimelb.csse.mugle.server.model.User;

public class Foo {

    public void Bar() {

         com.google.appengine.api.users.User u = some_statement;
         ...

    }

}

However, this is may not be the best way to do it due to the fact that
you'll have to end up using a long namespace for every instances you
need to use the google User class.

-- 
You received this bug notification because you are a member of MUGLE
Developers, which is subscribed to MUGLE.
https://bugs.launchpad.net/bugs/731919

Title:
  Resolving Namespace Conflicts on imports

Status in Melbourne University Game-based Learning Environment:
  New

Bug description:
  Due to the way login is handled by GAE, when ive started to implement the services for the Simple UI, it complains because im importing both:
  au.edu.unimelb.csse.mugle.server.model.User;
  com.google.appengine.api.users.User;

  Is there a way to get around this without refactoring and renaming the
  User class in our model package?



References