Re: [m2e-users] After STS 3.3.0 (Kepler), getting two different very annoying exceptions when opening any file in two particular Maven projects
> -----Original Message-----
> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On
> Behalf Of KARR, DAVID
> Sent: Thursday, July 18, 2013 8:26 AM
> To: Maven Integration for Eclipse users mailing list
> Subject: [m2e-users] After STS 3.3.0 (Kepler), getting two different very
> annoying exceptions when opening any file in two particular Maven projects
> *** Security Advisory: This Message Originated Outside of AT&T ***.
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> A few days ago I installed STS 3.3.0, which uses Kepler as the base.
> Most of the projects I browse are Ant projects, but two particular ones that
> I spend a lot of time on are Maven projects.
> My initial testing of STS 3.3.0 is ok in general, except for a problem with
> keyboard shortcuts that I see throughout, but I'm seeing particular problems
> with my two Maven projects. I don't see anything obviously related to m2e in
> the stack trace for either problem (I get a different problem in each of the
> two projects), but as these are Maven projects, I wondered whether anyone has
> any ideas about this.
> In one project, which is a Java project, I get the following in an error
> dialog when I open or switch the editor view to any file in that project:
> "java.lang.IllegalArgumentException: Path must include project and resource
> name: /"
> Outside of the stack trace, which doesn't tell me much, it gives me no
> additional information on what path this is referring to.
> I filed <https://bugs.eclipse.org/bugs/show_bug.cgi?id=412793> for this
> On the other project, which is a pure web project with no Java source, I get
> the following error when I open or switch the editor view to any file in that
> The stacktrace is even more confusing, as it appears to be in the JPA space.
> I filed <https://bugs.eclipse.org/bugs/show_bug.cgi?id=413258> for this
> Again, the only reason I'm asking this here is that these are Maven projects,
> and I'm not seeing these symptoms with other non-Maven projects.
> Any useful ideas would be appreciated.
I've managed to resolve these problems. The root of the problem is that I tend to export and reimport my update sites when I create a new workspace, even with a new version. Some of these older update sites apparently include plugin versions that are incompatible with other plugins. I'm not sure of all the mechanics, but when I reinstalled the distro and removed the older update sites, I no longer was offered updates that messed me up.