MyEclipse :: View topic - Eclipse 3.1M5 compatibility...?

MyEclipse: Eclipse 3.1M5 compatibility...?

markhm - Feb 19, 2005 - 01:16 PM
Post subject: Eclipse 3.1M5 compatibility...?

All,

Eclipse 3.1M5 is making it's way to the mirrors. I found it here:

http://mirror.tiscali.dk/eclipse/downloads/

Will MyEclipseIDE work without a problem with 3.1M5?

Thanks,
- Mark

support-rkalla - Feb 19, 2005 - 03:21 PM
Post subject:

Quote:

Will MyEclipseIDE work without a problem with 3.1M5?

We are waiting for you to tell us ;)

campers - Feb 20, 2005 - 09:09 AM
Post subject:

I didnt have any luck with the deployments and my projects MyEclipse-Web properties page :(

markhm - Feb 20, 2005 - 10:26 AM
Post subject:

support-rkalla wrote:

Quote:

Will MyEclipseIDE work without a problem with 3.1M5?

We are waiting for you to tell us ;)

Okay, okay... :-)

I didn't find any problems thus far, but I only did some very limited testing.
I was able to start my Tomcat-server in 3.1M5 with settings I had defined in an 3.1M4-workspace.

Cheers,
- Mark

ggerard - Feb 20, 2005 - 03:45 PM
Post subject:

I get a null pointer exception in "DeploymentBuilder"

java.lang.NullPointerException
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.webProjectBuildDelta(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.webProjectBuildDelta(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.buildDelta(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:581)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:757)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:160)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:198)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:227)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:757)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:230)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:249)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:278)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:138)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:199)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

ggerard - Feb 20, 2005 - 05:43 PM
Post subject:

This shows up in the log:

!SESSION 2005-02-20 09:37:59.419 -----------------------------------------------
eclipse.buildId=I20050218-1600
java.version=1.5.0_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.core.resources 4 2 2005-02-20 09:37:59.421
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.LinkageError: loader constraints violated when linking org/xml/sax/EntityResolver class
at org.jdom.input.SAXBuilder.configureParser(SAXBuilder.java:506)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:351)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:673)
at com.genuitec.eclipse.j2eedt.metadata.ProjectModule.unmarshal(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EEProject.loadMetaData(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EEProject.<init>(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.WebProject.<init>(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.WebProject.<init>(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EECore.getWebProjectsList(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EECore.getWebProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor.?(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor.access$0(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor$B.visit(Unknown Source)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor.resourceChanged(Unknown Source)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:285)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:757)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:279)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:153)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:177)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:917)
at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:979)
at org.eclipse.core.internal.resources.Workspace.save(Workspace.java:1736)
at org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor$2.run(IDEWorkbenchAdvisor.java:282)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:111)

awf999 - Feb 28, 2005 - 03:04 PM
Post subject:

I have gotten addicted to using generics in Java 5. Unfortunately, M4 generic support is not as good as M5's. Is the ME team planning on releasing a M5 compatiable version of ME or will you be waiting until the M6 release?

thanks

support-scott - Feb 28, 2005 - 03:15 PM
Post subject:

Actually, there are a few compatibility problems with 3.8.4 and M5 due to some changes to the underlying Eclipse frameworks. So, 3.8.4 will not be totally reliable on M5. As far as future plans go, we'll continue to release betas for whatever release of the M1 stream is current as it coincides with our normal release schedules. Whether or not a specific patch for 3.8.4 will be issued for M5 is still under review since we haven't yet scoped the work due to our commitments building version 4.0 and getting stuff together for the team going to EclipseCon.

yunkipaik - Mar 10, 2005 - 10:34 PM
Post subject:

Please release a patch to 3.8.4 that will support M5.
I need it personally.
Thank you.

GrimShieldsson - Mar 12, 2005 - 05:14 PM
Post subject:

M4 doesn't cut it for me either. I'd reall ylike a work around or fix for this.

ffray - Mar 23, 2005 - 08:15 AM
Post subject:

I had to update to M5, because in M4 there were some errors in the Java-Compiler such as
generating erroneus bytecode for enums.
Now myeclipse doesnt work anymore, so it would be great to support M5 or M6 which will get released
in 2 weeks from now.

Thanks in advance!

noviforum - Mar 25, 2005 - 12:20 PM
Post subject:

Hello, I had Eclipse 3.0.1 and MyEclipse (unfortuantely I can not remeber which version) installed prior I had to reinstall the whole OS again. I did a fresh install of Eclipse 3.1M5a and MyEclipse 3.8.4+QF2-BetaFor3.1

Now I can not Remove Web Project Capabilities nor Add it to my previous working project.

What is the latest known working pair of Eclipse and MyEclipse? Is there some config file in my project which I can manualy remove to remedy the situation or anything at all to make it work?

-bob

support-rkalla - Mar 25, 2005 - 05:05 PM
Post subject:

Bob,
You must use Eclipse 3.1M4, that's why in the download notes for that version, we say "This release will only work with Eclipse 3.1 M4", we weren't kidding ;)

sureshs - Apr 03, 2005 - 05:31 AM
Post subject:

So, any idea when the version compatible with 3.1M5 may become available? Also, when will 4.0 be ready as per your current roadmap?

support-rkalla - Apr 04, 2005 - 04:21 AM
Post subject:

4.0 is planned for late April, at that time we will make a release in line with the current Eclipse release (M6?) and continue to support 3.1 until final GA release. Sorry for the delays, we cannot derail to do an M5-specific release as we are in the home stretch for the 4.0 release.

snpe - Apr 04, 2005 - 02:14 PM
Post subject:

m6 is API freeze release and it is the best that ME work with M6

regards

support-rkalla - Apr 04, 2005 - 02:45 PM
Post subject:

This is our plan for 4.0. I'm sure we will roll out a M6 compatible release during beta for all our 3.1 users to bang on.

dan_morrow - Apr 08, 2005 - 02:56 PM
Post subject:

I need a version of MyEclipse that runs on M5 because I am interested in using the "Eclipse Web Tools Platform" which only runs on M5. Come on! You're only one digit away! Please reconsider your anti M5 stance. Thanks.

support-rkalla - Apr 08, 2005 - 03:02 PM
Post subject:

No M5 compatible release will be made, a M6 compatible one is getting ready to be released in the next few days.

MyEclipse builds ONTOP of WTP, trying to use WTP and MyEclipse side by side will not work well. It would be a lot like trying to use Windows 2000 and Windows XP at the same time, you can't, one builds ontop of the other.

dan_morrow - Apr 08, 2005 - 06:43 PM
Post subject:

support-rkalla wrote:

Um, OK. But here's the thing. The reason I'm interested in MyEclipse is because it can easily browse a database, and create Hibernate classes. The reason I'm interested in WTP is because it knows about Web Services (you can point it to a WSDL file, and it will generate stub code). And you can create new Web Services, and generate new WSDLs, etc.

So, basically I'm writing some middleware which acts as a Web Service, and gets it's data from a database using Hibernate.

Please understand, I'm very new to Eclipse development, (not to mention MyEclipse) and I'm just trying to find the best set of tools for the job. And unfortunately, it looks like the best set of tools are in two places?

Any suggestions about how to proceed would be most helpful.

Thanks,
-Dan.

support-rkalla - Apr 08, 2005 - 06:48 PM
Post subject:

Quote:

WTP is because it knows about Web Services (you can point it to a WSDL file, and it will generate stub code). And you can create new Web Services, and generate new WSDLs, etc.

Aye, we are hoping to get web services into our 4.0 release, if not it will be in the 4.1 release immediately following up. Sorry for putting you in the position of needing to balance the two right now. It is an unfortunate prerequisite but because MyEclipse builds on WTP (just like it is built ontop of Eclipse) if you swap out incompatible versions of WTP out from under MyEclipse, you will start getting exceptions galore, broken editors, "Cannot create Part" business and a whole slew of problems. This issue will more than go away once WTP stabalizes and we pull up more inline with it's production releases, but now during the pre-1.0 cycles it's a bit of a cat and mouse game, which is why the versions are so sensative.

Quote:

Any suggestions about how to proceed would be most helpful.

Hang in there, we are headed towards where you need us to be very quickly and appologize for the inconvenience.

nabil - Apr 08, 2005 - 06:56 PM
Post subject:

Eclipse M* are development releases and are not meant for production use (big API changes, bugs, etc between M releases) it's up to tools providers to support any milestone release from eclipse. MyEclipse guys are hard at work on the 4.0 release, that from the look at the roadmap, will have WS support, and I would assume it will make use of the Web Tools Proj. so it might worth the wait for a while or keeping up with 2 dev. envs for a while. I would also assume that Web Tools will be ported to the M6 release soon (hopfully ?) and you may ( or may not, since editors from Web Tools may conflict with editors from MyEclipse) be able to use with MyEclipse with it.

The bootom line, the M5 isn't going to be around for long as new Ms are released, you shouldn't, ideally, be basing your production on an M release, if you do, try seperating modules that depend on an M from ones that depend on MyEclipse/Eclipse stable release.

Good luck with your development and welcome to the Eclipse/MyEclipse camp :)

edit: p.s., what rkalla said!

snpe - Apr 08, 2005 - 11:06 PM
Post subject:

Nabil,
I don't agree - I work with eclipse 3.1 from m3 and it is very stable (I have no one crash)
The main advantage is java 5.0 (annotation, generic, etc).I will not return to java 1.4 and I try/work ME with 3.1 only

regards

nabil - Apr 08, 2005 - 11:47 PM
Post subject:

it's a mileston release, it's a product in development no matter how stable it might be, it shouldn't be used for production. Things change and most people can't afford losing time migrating/patching/fixing code. By most people I mean 3rd-party plug-in providers liek MyEclipse. M6 is API freeze, that's why it would make sense for MyEclipse to be ported to it, not much will change from now on.

my 2 cents