- This topic has 5 replies, 3 voices, and was last updated 13 years, 11 months ago by
.
-
Posts
-
I’m running Pulse external to my MyEclipse7.5 in which it is proclaiming 29 pending software changes. I cross my fingers and hit the ‘Apply 29 changes’ button, which looks like it will make updates to Maven, Mylyn, BPEL Visual Editor and Dynamic Languages toolkit.
The end result is a morass of dependency conflicts not making a lot of sense:
”
Software being installed: MyEclipse 7.5 (Profile) 2.0.0.0000000037 (com.poweredbypulse.profile-293626-rmb-95405 2.0.0.0000000037)
Only one of the following can be installed at once:
Maven Central repository index 0.9.5.20080717-1820 (org.maven.ide.eclipse.central 0.9.5.20080717-1820)
Maven Central repository index 0.9.6.20080905-0917 (org.maven.ide.eclipse.central 0.9.6.20080905-0917)
Maven Central repository index 0.9.4.20080603-0113 (org.maven.ide.eclipse.central 0.9.4.20080603-0113)
org.maven.ide.eclipse.central 0.9.6.zmyeclipse75020090612
Nexus index for Central Maven repository 0.9.0.20080301-0130-Sonatype (org.maven.ide.eclipse.central 0.9.0.20080301-0130-Sonatype)
Maven Central repository index 0.9.7.200902090938 (org.maven.ide.eclipse.central 0.9.7.200902090938)
Nexus index for Central Maven repository 0.9.1.200803311816 (org.maven.ide.eclipse.central 0.9.1.200803311816)
Cannot satisfy dependency:
From: MyEclipse Enterprise Workbench 7.5.0.zmyeclipse75020090612 (com.genuitec.myeclipse.enterprise.workbench.feature.group 7.5.0.zmyeclipse75020090612)
To: org.maven.ide.eclipse.central [0.9.6.zmyeclipse75020090612]
Cannot satisfy dependency:
From: MyEclipse 7.5 (Profile) 2.0.0.0000000037 (com.poweredbypulse.profile-293626-rmb-95405 2.0.0.0000000037)
To: com.genuitec.myeclipse.enterprise.workbench.feature.group [7.1.0,8.0.0)
Cannot satisfy dependency:
From: MyEclipse 7.5 (Profile) 2.0.0.0000000037 (com.poweredbypulse.profile-293626-rmb-95405 2.0.0.0000000037)
To: org.maven.ide.eclipse.central.feature.feature.group 0.0.0
Cannot satisfy dependency:
From: Nexus index for Central Maven repository (17Mb, Optional) 0.9.0.20080301-0130-Sonatype (org.maven.ide.eclipse.central.feature.feature.group 0.9.0.20080301-0130-Sonatype)
To: org.maven.ide.eclipse.central [0.9.0.20080301-0130-Sonatype]
Cannot satisfy dependency:
From: Nexus index for Central Maven repository (Optional) 0.9.1.200803311600 (org.maven.ide.eclipse.central.feature.feature.group 0.9.1.200803311600)
To: org.maven.ide.eclipse.central [0.9.1.200803311816]
Cannot satisfy dependency:
From: Maven Central repository index (Optional) 0.9.4.20080603-0114 (org.maven.ide.eclipse.central.feature.feature.group 0.9.4.20080603-0114)
To: org.maven.ide.eclipse.central [0.9.4.20080603-0113]
Cannot satisfy dependency:
From: Maven Central repository index (Optional) 0.9.5.20080717-1821 (org.maven.ide.eclipse.central.feature.feature.group 0.9.5.20080717-1821)
To: org.maven.ide.eclipse.central [0.9.5.20080717-1820]
Cannot satisfy dependency:
From: Maven Central repository index (Optional) 0.9.6.20080905-0917 (org.maven.ide.eclipse.central.feature.feature.group 0.9.6.20080905-0917)
To: org.maven.ide.eclipse.central [0.9.6.20080905-0917]
Cannot satisfy dependency:
From: Maven Central repository index (Optional) 0.9.7.200902090947 (org.maven.ide.eclipse.central.feature.feature.group 0.9.7.200902090947)
To: org.maven.ide.eclipse.central [0.9.7.200902090938]
”Why is it trying to update to previous versions of Maven?? Pulse already had figured out I have Maven 0.9.7 installed. So, what are the steps involved in fixing this dependency labyrinth? Should I do something like what is described @ https://www.genuitec.com/forums/topic/pulse-detected-dependency-conflicts-in-updates-resolved/&highlight=pulse+updates ?? Thanks in advance for your help.
lhale,
You mention 29 software changes. Have you added / removed any plugins to your ME 7.5 profile? Unless you add / remove plugin, pending changes cannot show 29 managed changes. Can you send a screenshot which will help me get a visual? Please [PM] the screenshot or alternatively send a mail to support@genuitec.com with this weblink as reference and add ATTN:Joy in the subject. This will help in quick tracing.
Of course I’ve added plug ins, everybody probably does that. I don’t usually remove anything – you never know when you’re going to need it again. But there arises the problem of the installer having to manage all software update dependencies and conflicts, which it appears to do poorly.
What exactly do you want to see? Where do I go from here?
lhale,
You have two threads going where here you need to install just BPEL and in the other one you are installing a host of plugins besides BPEL as well. So I’m not sure what you want to install. In a previous thread I asked you what you wanted to install so I could replicate, but you only responded with what plugins you thought you needed – I’m sorry I did not clarify that further.
MyEclipse 7.5 included a custom version of the m2Eclipse Maven plugins. You seem to have added a number of additional Maven plugins to your profile. These are not compatible with MyEclipse – and there is nothing Pulse (or the Eclipse Update Manager) can do about them. Some plugin you wish to install requests a specific version of the m2eclipse plugin, while MyEclipse itself requires another version. The error message you see there indicates that Pulse simply cannot satisfy both requirements.
You mentioned you tried some tests with Galileo (3.5) but are still using MyEclipse 7.5 which is based on 3.4, not 3.5, MyEclipse 8.5 is based on 3.5 and is more compatible with other plugins that need m2Eclipse (and you may not need additional Maven plugins)
If you wish to manage your dependencies outside Pulse, you are free to do so by downloading the appropriate version of Eclipse (3.4 or 3.5) and using our archived update site for (7.5 for 3.4 and 8.5 for 3.5) which is available on our download page. All your dependencies can then be managed directly with the Eclipse update manager.
If you wish to deploy your bpel to a bpel engine (such as ODE), you need to install lots more than just the BPEL editor. But, I would first like to “get the ball rolling” by successfully installing just the BPEL editor – refer back to all my information provided and please help me get past this first hurdle (notice I say first, as I’m already expecting more after that).
I’m fully aware that M.E. 7.5 runs on Eclipse 3.4, which is what I got. But I also have Eclipse 3.5 (without M.E.) on my system because on M.E. 7.5 my Maven2 stuff is all goofed up (please help fix), Pulse can’t clean up the dependencies (please see other thread and help fix), I can’t install the BPEL editor (please help fix) and there’s a handful of other things wrong with ME 7.5. I can tell you that the Maven2 support NEVER worked from the moment I installed M.E. 7.5 over M.E. 7.0. So, you can clearly see my reservations when you suggest I install M.E. 8.5 – I clearly don’t have time to waste on re-living the next upgrade nightmare. I’m also afraid of installing the M.E. 8.5 on my nicely working Galileo for fears it will totally screw it up (at least the BPELeditor, BPEL deployer, Hibernate editor,JBoss tools and Maven2 are all working). Can you give me assurances that an M.E. 8.5 install on my Galileo would go smooth without problems? Yeah, I didn’t think so.
I don’t want to manage my dependencies – I would like a tool that can FIX the dependency problems so I don’t waste time – Pulse can’t do that. What the Eclipse plug-in community needs is a Maven-like dependency tree that prevents added plug-ins from completely screwing up your Eclipse install.
So, in summary, please look at the places I’m asking you for help and try to help me out here.
If you wish to deploy your bpel to a bpel engine (such as ODE), you need to install lots more than just the BPEL editor. But, I would first like to “get the ball rolling” by successfully installing just the BPEL editor – refer back to all my information provided and please help me get past this first hurdle (notice I say first, as I’m already expecting more after that).
I understand, but from the other thread and from the trace on this one you are attempt to add more than one item at the same time. If you choose to add 5 items and all can’t work at once, we can’t choose the one that will work and install only that. Remove all items and add just the BPEL piece, then move on to other pieces. Please correct me if this is not what you are doing.
I can tell you that the Maven2 support NEVER worked from the moment I installed M.E. 7.5 over M.E. 7.0. So, you can clearly see my reservations when you suggest I install M.E. 8.5 – I clearly don’t have time to waste on re-living the next upgrade nightmare. I’m also afraid of installing the M.E. 8.5 on my nicely working Galileo for fears it will totally screw it up (at least the BPELeditor, BPEL deployer, Hibernate editor,JBoss tools and Maven2 are all working). Can you give me assurances that an M.E. 8.5 install on my Galileo would go smooth without problems? Yeah, I didn’t think so.
Actually, I can. MyEclipse 8.5 will not install over 7.5 due to the fact that one uses 3.4 and the other users 3.5. Beyond this, if you have standalone installs of Eclipse running, MyEclipse will not interfere with these versions of Eclipse (even if you have installed them with Pulse). So you can install 8.5 and still have 7.5 too.
I don’t want to manage my dependencies – I would like a tool that can FIX the dependency problems so I don’t waste time – Pulse can’t do that. What the Eclipse plug-in community needs is a Maven-like dependency tree that prevents added plug-ins from completely screwing up your Eclipse install.
I don’t believe your install is completely screwed up, Pulse (and the Eclipse update manager) would prevent you from installing items that would screw it up, were they all installed at the same time. You need to remove the items you are attempting to install before you can try adding new / different items. So the dependency tree that you are asking for, does, in fact, exist. This tree is what is preventing you from installing a 0.9.0 version of an M2Eclipse plugin in a system which is already running 0.9.6 of M2Eclipse. Do you know how they will interact when in the same system?
If you are already comfortable with 3.5 and a new set of Maven tools, I would strongly recommend trying 8.5; as I said earlier, the Maven tools are much more recent and integrated in such a way that they will be more compatible with other items which need M2Eclipse – you may not need to install any further items.
So – to recap, my suggestions are to either move to 8.5 and add your dependencies there or – remove all the new items you have chosen to add to 7.5 – and start adding them back one at a time. I don’t have a list of all the items you wish to install, so I can’t say if some of these are even going to be compatible with Eclipse 3.4.
Again, I’m sorry you are running into issues, but you are talking here about external plugins and an IDE (MyEclipse) which in some cases does need to integrate customized versions of external features. In some cases, compatibility can be overridden and we have done this where appropriate. This is not such a case.
