mugle-dev team mailing list archive

[Matt Giuca <731919@xxxxxxxxxxxxxxxxxx>]

Unfortunately, the only choice is to either a) rename the class, b)
refer to both User classes by their fully-qualified names
au.edu.unimelb.csse.mugle.server.model.User and
com.google.appengine.api.users.User, or c) do what Prageeth said and
import just one class, and refer to the other by its fully-qualified
name.

I would prefer doing (c), but it may simply be easier to rename the User
class if this is going to cause a lot of typing. So perhaps rename
au.edu.unimelb.csse.mugle.server.model.User to MugleUser. This is what I
have done in the past when using GAE.

As an aside, can we stop filing bugs which are not really bugs at all,
but discussion points? That's what the mailing list is for. I am closing
this bug as Invalid.

** Changed in: mugle
       Status: New => Invalid

-- 
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:
  Invalid

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?