Eclipse 3.7 Migration

[Chad La Joie]

Okay, I managed to send the update to the wrong address.  Here it is:

Okay, all the changes have been committed.

First, I everyone should review the Eclipse configuration
documentation which has been updated for 3.7
https://wiki.shibboleth.net/confluence/display/DEV/Configuring+Eclipse

If you're upgrading from an older Eclipse instance I recommend that
once you've installed 3.7 you run Eclipse from the command line using
the '--clean' option.  That'll remove various caches and metadata for
plugins that are no longer installed.

Once you have Eclipse installed and configured, then:
1. Remove the projects from your workspace (you don't need to delete
them from disk)
2. Perform an SVN update, from the command line (or with some other
tool outside of Eclipse) on all the projects you follow
3. Import (Import -> Maven -> Existing Maven Projects) the projects
back in to your Eclipse workspace

Some additional things to note:
 - I installed a certificate from a well-known CA on
svn.shibboleth.net so if you get a message that the cert has changed
when doing any update, that's why
 - There is a bug with the latest version of the SVN plugin (this is
true regardless of whether you're running Eclipse 3.6 or 3.7) where
the SVN cache isn't properly updated and so the iconography shown by
Eclipse may not be correct (e.g., it may show something has changed
even after it has been committed).
 - A couple unit tests are failing now where they didn't before.  I
haven't yet tracked this down but my suspicion is a bug in the Maven
surefire plugin.
 - In the OpenSAML and IdP v3 modules you'll end up with a directory
called .settings.OLD.  Just delete this.


On Thu, Aug 4, 2011 at 07:10, Chad La Joie <lajoie at itumi.biz> wrote:
> Okay, I've been doing some testing with this and everything seems to
> be working okay.  So I will be committing the changes related to this
> this weekend.  I'll given an update once its done.
>
> On Sun, Jul 24, 2011 at 22:02, Chad La Joie <lajoie at itumi.biz> wrote:
>> Ian and I were chatting this afternoon and both of us have been playing
>> around with Eclipse 3.7 which was released a few weeks ago.  As part of
>> the v3.7 release the Maven integration plugin to which we were moving
>> (m2eclipse) has been integrated into the Java IDE distributions of
>> Eclipse.  However, in the process of moving from m2eclipse version 0.12
>> (the latest release available in Eclipse 3.6) to version 1.0 (the one
>> that ships with Eclipse 3.7), some breaking changes were made.  You can
>> read about them here[1] and here[2].
>>
>> Aside from the fixups needed for the maven integration plugin everything
>> else seems to work okay.  Therefore I'd like to migrate to 3.7.  To do
>> this I'd like to do the following:
>>
>> - Create one super POM that manages all repositories, distribution
>> management, plugin management, project metadata (license, organization,
>> etc.), the release profile, and *maybe* some common dependencies (e.g.,
>> slf4j, logback).
>>
>> - Have all currently maintained and in development projects use the
>> aforementioned super POM
>>
>> - Move all currently maintained and in development project to use
>> m2eclipse v1.0 (this will mean no projects will use IAM any more).
>>
>> The super POM should help keep a lot of the material in our POMs in
>> synch.  Moving everything to a single maven integration plugin will
>> simplify our Eclipse installs and project build behavior.
>>
>> My plan is to make this change over the first weekend in August (i.e.,
>> in two weeks).
>>
>> [1]
>> http://blog.subshell.com/devblog/2011/06/changing-from-m2eclipse-to-m2e-eclipse-indigo.html
>> [2] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
>> --
>> Chad La Joie
>> http://itumi.biz
>> trusted identities, delivered
>>
>
>
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered