Spring IDE 2.0 M2 released

[Torsten Juergeleit]

Why is it that the site.xml on the update site still says category name="Spring IDE 2.0 M1"

Is the version on the update site M1 or M2 ?

Within the site.xml are two categories defined:

<site>
         :
   <feature 
       url="features/org.springframework.ide.eclipse_1.9.0.jar" 
       id="org.springframework.ide.eclipse" version="1.9.0">
       <category name="Spring IDE 2.0 M1"/>
   </feature>

   <feature
       url="features/org.springframework.ide.eclipse.feature_2.0.0.v200701250610.jar"
       id="org.springframework.ide.eclipse.feature" version="2.0.0.v200701250610">
       <category name="Spring IDE 2.0 M2" />
   </feature> 

   <category-def name="Spring IDE 2.0 M1" label="Spring IDE 2.0 M1"/>
   <category-def name="Spring IDE 2.0 M2" label="Spring IDE 2.0 M2"/>
</site>

So the category "Spring IDE 2.0 M2" refers to the new version.

[Christian Dupuis]

Hi Sebastian,

I've created a ticket at http://springide.org/project/ticket/448.

Btw. Gruesse nach Wiesbaden.

Christian

[Torsten Juergeleit]

Hi,

just FYI, using the latest nightly build (Spring IDE 2.0.0.v200701250610) doesn't solve the problem (for me ...

Sebastian

Please check the version number (especially the timestamp) of the installed Spring IDE feature and it's plugins via Eclipse's About menu.

As last resort you should delete all Spring IDE feature and plugins (org.springframework.ide.eclipse.*) from your Eclipse installation and re-install M2 via the update manager.

[Torsten Juergeleit]

I'm using Eclipse 3.3M4 and WTP2.0M4 (and deps) and I get the following error:

Unexpected exception parsing XML document from file [.../applicationContext.xml]; nested exception is java.lang.LinkageError: loader constraint violation: when resolving method "org.springframework.ide.eclipse.core.io.xml.LineNumberPreservingDOMParser.setEntityResolver(Lorg/xml/sax/EntityResolver;)V" the class loader (...)

Please provide the full stacktrace (we need the line numbers :-). You can post it here or better add it to the ticket Christian has created for this issue.

[manifoldronin]

WebTools is THE (optional) dependency. For details please refer to the installation guide.

Without WebTools Spring IDE is still working. But some features (mostly the BeansXmlEditor) are not available because they are depending on WebTools.

Well, until JST/WST was installed, I couldn't see anything related to Spring IDE. "Anything" as in I couldn't even add the Spring nature. Doesn't sound very "optional" to me.

[Torsten Juergeleit]

Well, until JST/WST was installed, I couldn't see anything related to Spring IDE. "Anything" as in I couldn't even add the Spring nature. Doesn't sound very "optional" to me.

You're right. Starting with Spring IDE 2.0 one must install WST. Introducing this dependency allowed us to drop our own version of the Xerces XML parser shipped with Spring IDE's Core plugin and leverage the Xerces plugin from WLST instead.

So we have to update the list of required software for Spring IDE 2.0

[sbeigel]

Hi,

Please provide the full stacktrace (we need the line numbers :-). You can post it here or better add it to the ticket Christian has created for this issue.

As far as I can see there is no stacktrace (at least I can't find any in the .log file or console view. There is an error entry in the Problems view (the one that I copied abbreviated in my original post). Here is the original item directly copied from the Problems view:

Severity and Description	Path	Resource	Location	Creation Time	Id
Unexpected exception parsing XML document from file [C:/workspace_test/test/src/applicationContext.xml]; nested exception is java.lang.LinkageError: loader constraint violation: when resolving method "org.springframework.ide.eclipse.core.io.xml.LineNumberPreservingDOMParser.setEntityResolver(Lorg/xml/sax/EntityResolver;)V" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/springframework/ide/eclipse/core/io/xml/XercesDocumentLoader, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/springframework/ide/eclipse/core/io/xml/LineNumberPreservingDOMParser, have different Class objects for the type org/xml/sax/EntityResolver used in the signature	test/src	applicationContext.xml	Unknown	1170061696236	3

The same behavior occurs using a fresh Eclipse 3.3M4/WTP2.0M4 (and deps) installation using a clean (brand new) workspace.

Spring IDE version is: 2.0.0.v200701250610

I tried both Java 1.6 and 1.5 -- no difference.

Thank you -- und Grüße nach Frankfurt!
Sebastian

[Torsten Juergeleit]

There is an error entry in the Problems view (the one that I copied abbreviated in my original post). Here is the original item directly copied from the Problems view:

Severity and Description	Path	Resource	Location	Creation Time	Id
Unexpected exception parsing XML document from file [C:/workspace_test/test/src/applicationContext.xml]; nested exception is java.lang.LinkageError: loader constraint violation: when resolving method "org.springframework.ide.eclipse.core.io.xml.LineNumberPreservingDOMParser.setEntityResolver(Lorg/xml/sax/EntityResolver;)V" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/springframework/ide/eclipse/core/io/xml/XercesDocumentLoader, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/springframework/ide/eclipse/core/io/xml/LineNumberPreservingDOMParser, have different Class objects for the type org/xml/sax/EntityResolver used in the signature	test/src	applicationContext.xml	Unknown	1170061696236	3

Please double-click on the coresponding entry in the problems view and copy the stacktrace from the problem details dialog.

[sbeigel]

Please double-click on the coresponding entry in the problems view and copy the stacktrace from the problem details dialog.

?! For me, double-clicking an entry in the problems view opens the file containing the error.

Even the entry's properties (context menu -> Properties) doesn't give more information than what I posted already.

Where can I find the actual stack trace?

Sebastian

[Torsten Juergeleit]

?! For me, double-clicking an entry in the problems view opens the file containing the error.

You're right. I mixed up the Problems view with the Error Log view...
So if the Error Log view is empty then we're out of luck

But regarding the issue you're seeing I added my take on this to the corresponding ticket.