Public bug reported:
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?
** Affects: mugle
Importance: Undecided
Status: New
** Description changed:
- Due to the way login is handled by GAE, when ive started to implement the
services for the Simple UI, its complains because im importing both:
+ 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?
--
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?
--
Mailing list: https://launchpad.net/~mugle-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mugle-dev
More help : https://help.launchpad.net/ListHelp
