Sencha GXT 3.0 Maven support

[4723]

Nexus is not too rigid. Instead mvn:install on any PC , allow you to easily install new artifact via GUI on your central CI server.

[mingfai]

I just wonder why Sencha knows how to deploy the RC2 release to maven central, but forget how to do so for the final 3.0 relase

[bbg]

What's wrong? Why the final 3.0.0 version is not available in the maven repository?

[Colin Alworth]

I'm pleased to announce that our Maven repository is ready to be used. This took longer than we had anticipated, but we wanted to be confident that it was ready for public use before making it known. Two main repositories are available, one for commercially licensed artifacts, and another for GPLv3 licenses artifacts - more details on our licenses can be found at http://www.sencha.com/products/gxt/license/ or by contacting licensing@sencha.com with any questions.

Commercially licensed repository:
URL: https://maven.sencha.com/repo/commercial-release/
Suggested pom.xml repository declaration:

        <repository>
            <id>sencha-commercial-release</id>
            <name>Commercially licensed Sencha artifacts</name>
            <url>https://maven.sencha.com/repo/commercial-release/</url>
        </repository>

Open source licensed repository:
URL: https://maven.sencha.com/repo/gpl-release/
Suggested pom.xml repository declaration:

        <repository>
            <id>sencha-gpl-release</id>
            <name>Open source licensed Sencha artifacts</name>
            <url>https://maven.sencha.com/repo/gpl-release/</url>
        </repository>

If your organization maintains an internal Maven repository, we suggest adding these to ensure that all developers are using the correctly licensed artifacts.

Going forward, Maven central will be updated with only the GPL licensed artifacts. They will be in central shortly after these repositories are updated, to ensure that any commercially licensed clients don't accidentally pull in open sourced jars instead of those in our repositories.

[icfantv]

The only hiccup we ran into when updating Nexus was to ensure that (and this was strictly an artifact of how we set up and use Nexus) the new Repository entry we created in Nexus for the GXT repo was available in our "public" repository. If this wasn't added, Nexus would neither fetch nor proxy Maven requests for the 3.0.0 version.

[schorse]

Ups...

This is really bad idea to use different maven repositories for the commertial and GPL version. Now you have two different versions of 'com.sencha.gxt:gxt:gxt-3.0.0' with different content:

Commercially licensed: sha1 ed0a029e3760d60ff2e27049800b0ca2a2f8cad9
Open source licensed: sha1 93f0081a53b1a6693799027e9acd77c455239ad2

Now you run into trouble if you using gxt in opensource and commertial projects.

It would be better to have a different 'version' or 'artifactId' for the two versions.

[DavidHoffer]

Yeah, when I saw that they created two repos one for each license, that raised more questions than answers. For folks using a proxy they have to pick one or the other...and then get the search order right...and if the GPL one will be pushed to Central the order would have to be before that...not normally the case. Then for individual users that need both licences they have even bigger problems as since they have the same GAV whichever gets to their local repo first will win.

It seems a much better solution would be to use a different GAV to make it simple, clear and explicit which is requested.

[Colin Alworth]

Thanks for the feedback. Our main issue/concern with a separate GAV is maintaining double the pom files (keeping the artifactId different as well as the license section of the parent, and keeping all children pointing to the correct parent), or releasing two versions and expecting people to keep the versions in line. Using the classifier doesn't make sense, as each artifact already has multiple classifiers (javadoc, sources, and in the case of gxt-examples, classes).

Thoughts? what would be the least intrusive, but also reasonably maintainable?

[bbg]

For example https://maven.sencha.com/repo/gpl-release/
is 403: Forbidden.

What is the hell?

[Colin Alworth]

Thanks, bbg, I'm looking into it. I'll reply when this is resolved.