Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] After STS 3.3.0 (Kepler), getting two different very annoying exceptions when opening any file in two particular Maven projects

Yes, should have been the e43 update site.  So, somehow you have e37
bits installed into your STS (didn't even think that was possible).
That would explain the problems you had earlier.  You may be able to
uninstall AJDT and reinstall the later version.  You should also track
down any other e37 bits installed.  But, it may just be simpler to
start from scratch.

ps- apologies for hijacking the m2e mailing list with something not
quite relevant...

On Fri, Jul 19, 2013 at 12:59 PM, KARR, DAVID <dk068x@xxxxxxx> wrote:
>> -----Original Message-----
>> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On
>> Behalf Of Andrew Eisenberg
>> Sent: Friday, July 19, 2013 11:44 AM
>> To: Maven Integration for Eclipse users mailing list
>> Subject: Re: [m2e-users] After STS 3.3.0 (Kepler), getting two different very
>> annoying exceptions when opening any file in two particular Maven projects
>>
>> One of the benefits of downloading a pre-packaged distro is that all
>> the pieces you need come pre-installed. I'm guessing that one of the
>> update sites you used before grabbed some Juno-based plugins.
>>
>> This latest problem is likely because you didn't install the Spring
>> IDE AJDT integration and the Spring IDE AOP integration.  Not sure
>> which part of your code is requiring this, but I think that's the
>> issue.  You will also need to install AJDT (AspectJ development
>> tools).  This update site should have everything you need:
>>
>> http://dist.springsource.com/release/TOOLS/update/e4.2
>>
>> (de-select group items by category and you will be able to see AJDT there).
>
> That's for 4.2.  Did you really intend that, instead of 4.3?
>
> I currently have:
>
> * AspectJ Development Tools     2.2.3.e37x-RELEASE-20130225-2000        org.eclipse.ajdt.feature.group  Eclipse AspectJ Development Tools
> * Spring IDE AJDT Integration (optional)        3.3.0.201307091516-RELEASE      org.springframework.ide.eclipse.ajdt.feature.feature.group      Spring IDE
> Developers
> * Spring IDE AOP Extension (optional)   3.3.0.201307091516-RELEASE      org.springframework.ide.eclipse.aop.feature.feature.group       Spring IDE Developers
>
> This update site has this:
> * AspectJ Development Tools     2.2.3.e42x-RELEASE-20130625-1400
> * Spring IDE AJDT Integration (optional)        3.3.0.201307091516-RELEASE
> * Spring IDE AOP Extension (optional)   3.3.0.201307091516-RELEASE
>
> I tried changing that update site path to 4.3, and I found this:
> * AspectJ Development Tools     2.2.3.e43x-RELEASE-20130627-0800
> * Spring IDE AJDT Integration (optional)        3.3.0.201307091516-RELEASE
> * Spring IDE AOP Extension (optional)   3.3.0.201307091516-RELEASE
>
> The last two from both sites are identical to what I have, but my ADT appears to be older than the 4.2 version, which is older than the 4.3 version. What should I do here?
>
>> On Fri, Jul 19, 2013 at 10:32 AM, KARR, DAVID <dk068x@xxxxxxx> wrote:
>> >> -----Original Message-----
>> >> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx]
>> On
>> >> Behalf Of Igor Fedorenko
>> >> Sent: Thursday, July 18, 2013 8:22 PM
>> >> To: m2e-users@xxxxxxxxxxx
>> >> Subject: Re: [m2e-users] After STS 3.3.0 (Kepler), getting two different
>> very
>> >> annoying exceptions when opening any file in two particular Maven projects
>> >>
>> >> Are you able to reproduce these problems with fresh/clean m2e install on
>> >> one of Eclipse packages available from download.eclipse.org? If not,
>> >> you probably want to report these to vmware.
>> >
>> > I tried starting with the Eclipse Kepler release and then installing the
>> Spring components on top of that.  I did not get these symptoms.  I just get
>> a different one.
>> >
>> > I get the following compilation error in my Java project (this is the exact
>> text):
>> >
>> > "Build path is incomplete. Cannot find class file for Could not initialize
>> class
>> org.springframework.ide.eclipse.springframework.aop.aspectj.AspectJExpression
>> Pointcut"
>> >
>> > Besides being a scrambled error message, it seems like a Spring IDE
>> specific problem. I can't even figure out where that class is (I've searched
>> pretty deeply through my workspace and distro), not to mention not knowing
>> where it's being used.
>> >
>> >> On 2013-07-18 7:26 PM, KARR, DAVID wrote:
>> >> > 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
>> >> problem.
>> >> >
>> >> > 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 project:
>> >> >
>> >> > "java.lang.NoClassDefFoundError:
>> >> org/eclipse/jpt/common/utility/internal/AsynchronousCommandExecutor"
>> >> >
>> >> > 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
>> >> problem.
>> >> >
>> >> > 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.
>> >> > _______________________________________________
>> >> > m2e-users mailing list
>> >> > m2e-users@xxxxxxxxxxx
>> >> > https://dev.eclipse.org/mailman/listinfo/m2e-users
>> >> >
>> >> _______________________________________________
>> >> m2e-users mailing list
>> >> m2e-users@xxxxxxxxxxx
>> >> https://dev.eclipse.org/mailman/listinfo/m2e-users
>> > _______________________________________________
>> > m2e-users mailing list
>> > m2e-users@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/m2e-users
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users


Back to the top