-
15. Re: Giving the Android extension a name that sticks
The general practice here, from my experience, is adding an underscore at the end of the package name. (i.e., native_). I think that's reasonable. We don't want to get too concerned about it as it will autocomplete just fine.
Also, shouldn't we be switching to the root package org.arquillian?
-
16. Re: Giving the Android extension a name that sticks
Yeah, we could go for that native_ string, it is better than my _native but still not my cup of tea anyway ... nevermind. native_ is good.
Regarding of the name of root packages, I could go for it easilly but wouldn't be there a clash with groupId of Maven? Extensions have groupId org.jboss.arquillian.extension and containers have it like org.jboss.arquillian.container, as any other Arquillian container and extension does. I think the name of any root package should be the same as much as possible as groupId ...
-
17. Re: Giving the Android extension a name that sticks
Stefen, this is a new module so we can start of here with org.arquillian. Arquillian Core will follow in 2.0.