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:
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.
I just tried to import some projects into a fresh Eclipse into which I had just installed m2e 1.2 and it appears to continue to want to go to http://repository.tesla.io:8081/nexus/, which due to corporate firewall stuff is not reachable:
Problems occurred while performing installation: Error(s) occurred gathering items for installation
Error(s) occurred gathering items for installation
Am I missing something? Do I have some old info cached somewhere?
Nat
On Sun, Oct 7, 2012 at 2:45 PM, Jason van Zyl <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.
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 <youngm@xxxxxxxxx>
wrote:
Excellent! Thanks Jason.
Mike
On Thu, Oct 4, 2012 at 12:57 PM,
Jason van Zyl <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 <youngm@xxxxxxxxx>
wrote:
Looking at the non
test version it appears to not use 8081
for the main discovery downloads:
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.
