Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316755 - Installation should install dependencies
Summary: Installation should install dependencies
Status: CLOSED WONTFIX
Alias: None
Product: MPC
Classification: Technology
Component: Install (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 09:23 EDT by Krzysztof Kula CLA
Modified: 2015-11-24 12:40 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof Kula CLA 2010-06-14 09:23:53 EDT
When I am installing plugin with dependencies wchitch are available in marketplace, Eclipse should ask me I want to install these dependencies in actual installation.  There should be also checkbox 'do not as again and install all free requeired software'.


-- Configuration Details --
Product: Eclipse 1.3.0.20100526-1935 (org.eclipse.epp.package.php.product)
Installed Features:
 org.eclipse.epp.mpc 1.0.0.v20100528-2359
Comment 1 David Green CLA 2010-06-14 10:36:35 EDT
Thanks for the enhancement request.  Is there a specific solution in the marketplace that you're having troubles installing?

The installation process uses p2 metadata to determine dependencies when resolving an install operation.  The marketplace itself is not a p2 repository and cannot be used to resolve dependencies, however individual solutions provide their own p2 repositories.

Solution providers can and should ensure that their repositories contain or link to all of the dependencies required to install their solutions.  Currently MPC uses the Helios repository to resolve common dependencies, however solution providers can use composite update sites to ensure that any dependencies required by their solution are available during install.

Is there a specific scenario or use case that you'd like to see supported?
Comment 2 Krzysztof Kula CLA 2010-06-14 17:37:21 EDT
I have problem with http://www.springsource.com/products/sts?__utma=1.360660731.1276290596.1276290596.1276550192.2&__utmb=1.6.10.1276550192&__utmc=1&__utmx=-&__utmz=1.1276550192.2.2.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=spring&__utmv=-&__utmk=86274968  SpringSource Tool Suite(especially for Roo), it depends on AJDT-AspectJ and I have error from atlassian( I have never used this before and first was WTF what is AJDT??? then googling to find AspectJ plugin). I am beginning in Eclipse, I always get angry when I can't install simple plugin to help me working. It is horrible and sick when plugin whitch is indended to speed my work takes several hours or even hour to run. Always when I work on tools more than 10-20 minuts I start to thinking if that plugin really save me that time? Many times I choose NetBeans or use Eclipse without plugins becouse I have no time and patience for fighting with them to get them working. And I know many peoples that do like me (especially in PHP coding.
So global repository will be nice solution from my point. As an example when in NetBeans I want to install plugin that depends on other plugin it show me window with additional plugins that it will install with my selected plugin. 
I always think that simple thinkgs should be done easly with flat learning curve. 

I know that what I am writing here is not so simple and that's why I really like Eclipse Marketplace with plugin search from within IDE :) 

Sory for my english but I hope that it is understandable.
Comment 3 Carsten Reckord CLA 2015-11-24 12:40:24 EST
This bug hasn't seen any activity in a long time. Spring IDE and Roo Support install fine through Marketplace by now. Also, there really isn't much we can do at the MPC level about missing dependencies, since MPC actually hasn't any knowledge about which repositories could provide a feature.

We're already using the repositories in the client's repository list to resolve dependencies, including the pertinent Eclipse simrel repository (e.g. for Mars) so in most instances this should "just work". We could go out of our way to index all repositories listed on the marketplace, but I believe that it's ultimately the solution provider's responsibility to ensure that dependencies can be resolved. They can use composite repositories or repository references to achieve this. Also, the Marketplace Install Error reports should give solution providers a good indication if there is a problem with their entry - and we plan to do further install checks in bug 481160 to inform them about problems more proactively.

So I'm inclined to close this as WONTFIX in favor of bug 481160. But please let me know if you encounter similar dependency issues, so we can look at how to detect these issues and react to them.