[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17964: --------------------------------------------- [~pleacu] examples of "solutions" on eclipse marketplace is Talend: http://marketplace.eclipse.org/content/talend-esb-studio-standard-edition and Bonita http://marketplace.eclipse.org/content/bonita-bpm Notice how they look like normal entries and is possible to be found in both web and eclipse UI - but just dont have a separate updatesite. This is how I suggest for JBDS IS 7 we make an entry and provide screenshots/info on how to install it. We can still add tags to dev studio entries so they show up too to make them easy to get to. If we wanted to make it installable directly we would need to consider/solve: 1) only have one updatesite url that the entry can point to (if we only put integrationstack current url into the entry users will not get access to jboss central nor updates to JBDS - at least not in a consistent manner) 2) we see alot of value in being on the top 10 list - if we start spreading it to integration stack - is that helping our EAP/JavaEE needs and how about JBoss Developer progress that we would be dropping in this list ? 3) if integration stack becomes separate entry, how about the subparts ? like Fuse and Teeid - should they too ? Who will test/maintain these - marketplace does not do any consistency checks etc. its all up to us to make sure things work. QE would need to test these additional mechanisms and which one of these would we document ? 4) In JBDS 8, Fuse integrates jmx with server tooling and JBDS 8.1 or 9 Fabric8 might need to move down too. Giving more consistency to users and simpler code to maintain - but making how JBDSIS gets delivered and what dependencies it different than JBDS 7. in any case - #1 alone is not something that is trivial/free to change in JBDS 7. JBDS 8.next or/and JBDS 9 timeframe we could look at doing something smarter. * Like have the installers (JBDS-3087) install them together (requires more QE, release coordination - JBDSIS is no longer "just" an addon) * Look at reducing "core jbds" to something even smaller (need to hear what features are considered "not relevant") * Utilize the drag'n'drop feature we have for JBDSIS installs. * Have JBDSIS installation info show up as the first thing after install if it is present. -- This message was sent by Atlassian JIRA (v6.2.6#6264)