Page 1 of 5 123 ... LastLast
Results 1 to 10 of 49

Thread: Sencha GXT 3.0 Maven support

  1. #1
    Sencha User
    Join Date
    Oct 2011
    Posts
    40

    Default Sencha GXT 3.0 Maven support

    Please subscribe to this forum post if you like to learn more about Sencha GXT 3.0 Maven support.
    Edmund Leung
    Sencha Product Management

  2. #2
    Ext GWT Premium Member matienzar's Avatar
    Join Date
    Jun 2007
    Location
    Spain
    Posts
    17

    Default

    Why can I access private maven repository of GXT 3.0.0 final release
    Marcial Atinzar Navarro
    Analista de Sistemas de Informacin

    [email protected]
    www.umivale.es
    www.sumaintermutual.es

  3. #3
    Ext GWT Premium Member
    Join Date
    Jan 2009
    Location
    Franktown, CO
    Posts
    440

    Default

    Why isn't 3.0 available yet for paid customers?

  4. #4
    Sencha User
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,737

    Default

    The commercially licensed release is presently available for download at http://www.sencha.com/products/gxt/download/ - the 'getting started' with a commercial license doesn't apply if you already have one, just download that and use it under your existing GXT 3 license.

    Getting Maven set up is taking longer than we had anticipated, and we hope to have both the commercial and open source releases available in maven repositories soon.

  5. #5
    Ext GWT Premium Member
    Join Date
    Jan 2009
    Location
    Franktown, CO
    Posts
    440

    Default

    I need it in maven so the manual download is a big step backwards...so we will have to wait for your maven distribution to become available unless it becomes critical here. Btw, I read that the non-gpl version will be on your private repo? Do you have the URL of that yet? (We will have to add that URL to our Nexus proxy server and I have to get IT involved to add that...I could get that part going here if you know for sure what the URL will be.)

  6. #6

    Default

    It's inconvenient that it isn't in the repo, but you can can still use the manual download with maven. That's what the command mvn:install is for.

  7. #7
    Ext GWT Premium Member
    Join Date
    Jan 2009
    Location
    Franktown, CO
    Posts
    440

    Default

    No not really...that's fine for single developer project with no CI system. Because we have corporate automated build system...all artifacts must come from Nexus server.

  8. #8

    Default

    We do automated builds too, and there are quite a few libraries we use that are not in the maven repos. We set up a script in our CI system to run prior to build that copies those jars and runs mvn:install on them. It's straightforward. I'd argue that if such a simple inconvenience throws a wrench into your entire deal, then you've got other problems.

  9. #9
    Ext GWT Premium Member
    Join Date
    Jan 2009
    Location
    Franktown, CO
    Posts
    440

    Default

    This discussion is way off topic...but using a corporate Maven proxy server is the Maven way, it works exceptionally well...no need to work around it.

  10. #10

    Default

    Yea we are, I was trying to give you a suggestion. mvn:install is a feature of maven, not a workaround. Though, it does seem like your process is too rigid to accommodate an external file after all.

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •