From damason at redhat.com Mon May 7 22:49:01 2012 From: damason at redhat.com (David Mason) Date: Mon, 07 May 2012 18:49:01 -0400 (EDT) Subject: [zanata-devel] Zanata repo split In-Reply-To: <4F9A58CC.1070101@redhat.com> Message-ID: <78aacef8-1866-424e-aaed-b4eeb8beb565@zmail10.collab.prod.int.phx2.redhat.com> Added this information to https://engineering.redhat.com/trac/zanata/wiki/MavenSettings (accessible from https://engineering.redhat.com/trac/zanata/wiki/DevInfo ) Cheers, David Mason Software Engineer L10n Engineering Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 ----- Original Message ----- > From: "Sean Flanigan" > To: "zanata-devel" > Sent: Friday, 27 April, 2012 6:29:00 PM > Subject: [zanata-devel] Zanata repo split > > > I think the repo split has mostly settled down now, but there is a > change you will need to make on your development machines, to make > sure > you can always resolve zanata dependencies (and zanata-parent). > > Just add the attached profile definitions to your ~/.m2/settings.xml > between and . > > This will add the jboss and zanata (cloudbees) repos whenever you do > a > Maven build. You can disable the repos by using -Dzanata.repo.off > and > -Djboss.repo.off. > > > I know it's a nuisance, but we'll need it anyway, so that we can get > the > elements out of our poms. Among other reasons, it's a > requirement if we're going to get Zanata into Maven Central. > > > -- > Sean Flanigan > > Senior Software Engineer > Engineering - Internationalisation > Red Hat > > _______________________________________________ > zanata-devel mailing list > zanata-devel at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-devel From sflaniga at redhat.com Tue May 8 08:14:34 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Tue, 08 May 2012 18:14:34 +1000 Subject: [zanata-devel] Upgrading Eclipse easily (at least for SR upgrades) Message-ID: <4FA8D5EA.4050801@redhat.com> I. To transfer your list of update sites: 1. Run your old Eclipse one last time 2. Go to Window->Preferences->Install/Update->Available Software 3. Select all update sites (click on one, then Ctrl-A), click Export, save the file somewhere 4. Run your new Eclipse, select your workspace 5. Go to Window->Preferences->Install/Update->Available Software 6. Click Import, choose the file from step 3 II. To copy across your old plug-ins: 1. In the new Eclipse, select File->Import->Install->From Existing Installation 2. Select your old eclipse directory, eg ~/apps/eclipse-jee-indigo-SR1-linux-gtk-x86_64/eclipse/ 3. Select the plug-ins/features you want to install, click Finish 4. When it finishes, you can archive/delete your old Eclipse directory -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: