Thanks once again to our community for the heads up - apparently our server monitoring efforts from the last outage did nothing to inform us of this next issue, and we'll be working on this to improve it.
Regarding the maven build with same artifact ids for the two releases (GPL and Commercial):
I don't know your internal development structure (maven modules etc.), but couldn't you just create another maven module, which uses the maven assembly plugin to package the classes and the GPL license file with an artifact id like "gxt-gpl"? Then you have the two releases separated, but you don't have to change anything for your development, because it's just packaging.
If so, verify that the id of the server entry in your settings.xml with those credentials matches the id of the repo in your pom file, and that this repo entry is the /support-commercial-release/ repo.
If it all still looks like it should make sense, please post the log of your maven build when it fails to see more specifically what the error is.
I see 3.0.2 is available for commercial users? Why doesn't it contain 3.0.2?
P.S. I don't understand Colin's previous post. In the past I do not think we had to login to Artifactory (not sure what that would be for). Did something change in how we integrate GXT with our build? We use a corporate Nexus maven proxy and if something changed regarding where the commercial artifacts are hosted and/or login I will need to get with them to make Nexus changes. Please advise if this changed.
If you are authenticated, this url will show 3.0.0, 3.0.0b, 3.0.1, and 3.0.2. Otherwise this will only show the public releases.
If you set up your credentials in Nexus, it will be able to pull these support only artifacts for your organization. We've had several teams already make this change successfully with their own Nexus servers, so we're reasonably sure that this is set up and configured correctly.