Unfortunately, I'm still seeing a (failing) attempt to connect to
repository.tesla.io:8081 <http://repository.tesla.io:8081>.  Is there
any chance some sort of cache at my end needs to be reset?
Also, I'm seeing a slightly odd behavior as part of the failure: When I
click "Finish" at the end of the "Setup Maven plugin connectors" dialog,
I briefly see an in-dialog progress bar and the "Finish" button
disables.  Shortly after, that bar disappears, the "Finish" button
re-enables, and the dialog just stays up.  I also see in the status bar
of the (buried) main Eclipse window what appears to be a bit of a URL
(of the repository) and progress indicator.  I'm not sure what the
expected behavior is, but having the "Finish" button re-enable and the
dialog stay up seems odd.  Any idea what's going on here?
On Tue, Oct 9, 2012 at 8:34 AM, Fabio Canepa <
fabio.canepa@xxxxxxxxx 
<mailto:
fabio.canepa@xxxxxxxxx>> wrote:
    Ok I've tested the catalogue from our corporate network and now I
    don't get any reference to repositories on port 8081: everythings
    install correctly (m2e-egit, m2e-subversive, axistool)
    Thanx a lot!
    --
    FAbio
    On Mon, Oct 8, 2012 at 9:22 PM, Jason van Zyl <
jason@xxxxxxxx
    <mailto:
jason@xxxxxxxx>> wrote:
        To help validate that the right catalog and contents are making
        it to Central along with the catalog JARs I have deployed the
        connectors.xml file that is used to generate the content for the
        update manager:
        
http://repo1.maven.org/maven2/.m2e/discovery-catalog/
        Specifically you will see that there is a connectors.xml:
        
http://repo1.maven.org/maven2/.m2e/discovery-catalog/connectors.xml
        And for all the connectors I'm building there should no longer
        be any urls pointing back to the Tesla Nexus instance on port
        8081. I still need to purge the EdgeCast cache but the right
        content is up there now.  While building the catalog the process
        makes sure that the source repository is reachable so if the
        right connectors.xml file makes it up there then the content
        should all be good.
        On Oct 8, 2012, at 11:04 AM, Nathaniel Mishkin
        <mailto:
jason@xxxxxxxx>> wrote:
            Ok, you can now try installing connectors from Central.
            You don't need any extra parameters in the eclipse.ini.
            The release catalog now points to connectors that have
            been deployed to Central. So the downloads should be fast
            and work through port 80. Might be a few kinks to work out
            but I've automated the whole flow so I can fix it quickly.
            On Oct 6, 2012, at 7:55 PM, Eric Dalquist
            <
eric.dalquist@xxxxxxxxxxxxx
            So to test out the new central hosted connectors library
            would I use:
            -Dm2e.discovery.url="" href="http://download.eclipse.org/technology/m2e/discovery/directory-1.1.xml" target="_blank">http://
download.eclipse.org/
technology/m2e/discovery/
directory-1.1.xml
            <
http://download.eclipse.org/technology/m2e/discovery/directory-1.1.xml>
            Thanks,
            -Eric
            On 10/6/12 4:59 PM, Jason van Zyl wrote:
            All the connectors that I am building are now available
            on Central:
            
http://repo1.maven.org/maven2/.m2e/connectors/
            So if anyone is having problems installing them this
            should resolve that.
            I will update the catalog later this weekend and
            republish it.
            On Oct 4, 2012, at 3:29 PM, Mike Youngstrom
            Excellent!  Thanks Jason.
            Mike
            On Thu, Oct 4, 2012 at 12:57 PM, Jason van Zyl
            <
jason@xxxxxxxx <mailto:
jason@xxxxxxxx>> wrote:
                One thing at a time. I've been focused on getting
                the infrastructure up. I will eventually sync the
                connectors to central and then there won't be any
                problems. I have other services running on port 80
                internally on that machine so it's not easy for me
                to flip it right now. I'll switch it as soon as I can.
                On Oct 4, 2012, at 9:06 AM, Mike Youngstrom
                <mailto:
fabio.canepa@xxxxxxxxx>> wrote:
                    Hi,
                    it seems that the new discovery catalog for
                    m2e 1.2 try to contact the service
                    
http://repository.tesla.io:8081/nexus/
                    Port 8081 it's not very "corporate friendly"
                    because usually network firewall permits only
                    traffic on port 80 or 443 and for this reason
                    I cannot install any connector...
                    Is this just a test or is it the final
                    configuration ?
                    The catalog should be plublished on standard
                    port to permit to install the connectors
                    behind coporate network firewall.
                    Regards,
                    --
                    Fabio
                    ______________________________
_________________
                    m2e-users mailing list
                    
m2e-users@xxxxxxxxxxx
                https://dev.eclipse.org/mailman/listinfo/m2e-users
                Thanks,
                Jason
                ------------------------------
----------------------------
                Jason van Zyl
                Founder & CTO, Sonatype
                Founder,  Apache Maven
                
http://twitter.com/jvanzyl
                ------------------------------
---------------------------
                A language that doesn’t affect the way you think about programming is not worth knowing.
                 -- Alan Perlis
                ______________________________
_________________
                m2e-users mailing list
 
                m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
            m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
            https://dev.eclipse.org/mailman/listinfo/m2e-users
            Thanks,
            Jason
            ------------------------------
----------------------------
            Jason van Zyl
            Founder & CTO, Sonatype
            Founder,  Apache Maven
            
http://twitter.com/jvanzyl
            ------------------------------
---------------------------
            Three people can keep a secret provided two of them are dead.
             -- Benjamin Franklin
            ______________________________
_________________
            m2e-users mailing list
 
            m2e-users@xxxxxxxxxxx  <mailto:m2e-users@xxxxxxxxxxx>
            https://dev.eclipse.org/mailman/listinfo/m2e-users
            _______________________________________________
            m2e-users mailing list
            m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
            https://dev.eclipse.org/mailman/listinfo/m2e-users
            Thanks,
            Jason
            ------------------------------
----------------------------
            Jason van Zyl
            Founder & CTO, Sonatype
            Founder,  Apache Maven
            
http://twitter.com/jvanzyl
            ------------------------------
---------------------------
            Simplex sigillum veri. (Simplicity is the seal of truth.)
            ______________________________
_________________
            m2e-users mailing list
 
            m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
        m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
        https://dev.eclipse.org/mailman/listinfo/m2e-users
        Thanks,
        Jason
        ------------------------------
----------------------------
        Jason van Zyl
        Founder & CTO, Sonatype
        Founder,  Apache Maven
        
http://twitter.com/jvanzyl
        ------------------------------
---------------------------
        A man enjoys his work when he understands the whole and when he
        is responsible for the quality of the whole
          -- Christopher Alexander, A Pattern Language
        ______________________________
_________________
        m2e-users mailing list
 
        m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
    m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>