<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Will this help:<br></div><div><br><em>(Max) Can we start by putting existing devstudio installer there now ? (last time I looked it was not even mentioning it)</em></div><div><br></div><div>I thought that the problem was that after users had installed JBDS, they could not locate the appropriate tooling?<br></div><div><br></div><div><br></div><div>-- Len<br></div><div><br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Max Rydahl Andersen" <manderse@redhat.com><br><b>To: </b>"Aileen Cunningham" <aileenc@redhat.com><br><b>Cc: </b>"soa-pm-list List" <soa-pm-list@redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev@lists.jboss.org>, jbds-is-pm-list@redhat.com, "JDV-PM Mailing List" <jdv-pm@redhat.com>, "Mustafa Musaji" <mmusaji@redhat.com>, "Fuse-pm-list" <fuse-pm-list@redhat.com>, "bpms-pm-list" <bpms-pm-list@redhat.com><br><b>Sent: </b>Monday, November 17, 2014 6:47:13 AM<br><b>Subject: </b>Re: integration stack component installation<br><div><br></div>On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:<br><div><br></div>> Hi Paul,<br>><br>> when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS" <br>> are you talking about a combined installer where you can install JBDS <br>> + IS in 1 action?<br><div><br></div>Yes. But this requires work/QE resources.<br><div><br></div>> People can find the runtime download on JBoss.org fairly easily so <br>> what we need to get to is a 2nd big green download button on the Fuse <br>> product page that installs the relevant Tooling.<br><div><br></div>Can we start by putting existing devstudio installer there now ? (last <br>time I looked it was not even mentioning it)<br><div><br></div>I believe your team is "owner" of those pages or at least should be able <br>to request the best changes to them.<br><div><br></div>If not let me know what pages you believe should be changed and I can <br>help track it down.<br><div><br></div>/max<br><div><br></div>><br>> best regards,<br>> Aileen<br>><br>><br>> ----- Original Message -----<br>>> From: "Paul Leacu" <pleacu@redhat.com><br>>> To: "Kevin Conner" <kconner@redhat.com>, "Max Rydahl Andersen" <br>>> <max.andersen@redhat.com>, "Aileen Cunningham"<br>>> <aileenc@redhat.com><br>>> Cc: "soa-pm-list List" <soa-pm-list@redhat.com>, "jbosstools-dev <br>>> jbosstools-dev" <jbosstools-dev@lists.jboss.org>,<br>>> jbds-is-pm-list@redhat.com, "JDV-PM Mailing List" <br>>> <jdv-pm@redhat.com>, "Mustafa Musaji" <mmusaji@redhat.com>,<br>>> "Fuse-pm-list" <fuse-pm-list@redhat.com>, "bpms-pm-list" <br>>> <bpms-pm-list@redhat.com><br>>> Sent: Friday, 14 November, 2014 8:43:18 PM<br>>> Subject: integration stack component installation<br>>><br>>><br>>> Greetings,<br>>> At the JBoss f2f last week in Brno there was a meeting to discuss <br>>> the<br>>> ease of installation<br>>> issue (or lack thereof) of integration stack components. Presented <br>>> here<br>>> is a summary of the<br>>> issue and a proposed solution as drafted by the team. Although <br>>> members of<br>>> platform architecture,<br>>> engineering, PM and QE were present - the solution is simply proposed <br>>> at<br>>> this time. We also<br>>> plan to evolve the solution over time - so that the issue will be<br>>> addressed more fully.<br>>><br>>> Your comments are welcome!<br>>><br>>> Thanks,<br>>> --paull<br>>><br>>> ------<br>>><br>>> Issue: Finding integration stack components to install is too <br>>> difficult.<br>>> This was made<br>>> clear by Fuse Tooling usability reviews and is discussed in <br>>> detail<br>>> here:<br>>><br>>> https://mojo.redhat.com/docs/DOC-977658<br>>><br>>> Proposed Solution:<br>>><br>>> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for <br>>> product<br>>> groupings and establish<br>>> JBTIS/ JBDSIS installers based on JBT/ JBDS.<br>>><br>>> Discussion:<br>>> As it exists today, users who search within the standard Eclipse<br>>> Marketplace for keywords<br>>> such as "Camel Editor" or "Fuse" are directed to the JBDS or JBT <br>>> Kepler<br>>> installers. Users<br>>> must select the "more info" link on the Marketplace installer page <br>>> and<br>>> then page down to<br>>> find this text:<br>>><br>>> "Also available is the JBoss Developer Studio Integration Stack, <br>>> which<br>>> includes support for SwitchYard, Camel, Fuse, Fabric8, Drools, <br>>> jBPM,<br>>> ModeShape, Teiid and more. It is available from within JBoss <br>>> Central,<br>>> via the Software/update tab."<br>>><br>>> This is the first mention of Fuse and directs the user to install <br>>> JBDS<br>>> (or JBT) and then,<br>>> after installing/ restarting and as a separate action, use the<br>>> Software/Update tab within<br>>> JBoss Central to find the Fuse tooling. In this case Fuse is part <br>>> of:<br>>><br>>> "JBoss Integration and SOA Development" - (The category description <br>>> does<br>>> mention Fuse.)<br>>><br>>> Solution Details:<br>>><br>>> The extended IS-aware Eclipse Marketplace entries will reference <br>>> the<br>>> existing update site<br>>> and when selecting "Install" you will get a yet-to-be-defined <br>>> subset of<br>>> the Eclipse features that<br>>> will match what you would get when using the install from JBoss <br>>> Central<br>>> today - but without having<br>>> to install Developer Studio plugins separately first.<br>>><br>>> The installer option is to be based on the JBDS installer and will <br>>> be<br>>> made available from the CSP/jboss.org<br>>> download next to the existing installer.<br>>><br>>> JBDS 7.1.1.GA/JBDSIS 7.1.0.GA (Kepler) - What can we do today?<br>>><br>>> - https://issues.jboss.org/browse/JBTIS-354<br>>><br>>> The least required changes would leave the user with a single <br>>> JBDSIS<br>>> installer and a single<br>>> JBTIS installer when searching for "Fuse" or "Data <br>>> Virtualization" for<br>>> example. Upon selecting<br>>> one of these installers the user would see all available<br>>> installation-units (features) available<br>>> in the combined integration stack. Users could then select all <br>>> or<br>>> just the fuse tooling IUs.<br>>> This is the "laundry list" approach.<br>>><br>>> JBDS 8.1.0.GA/JBDSIS 8.0.x.GA (Luna) - Short term for upcoming <br>>> tooling<br>>> releases.<br>>><br>>> - https://issues.jboss.org/browse/JBTIS-355<br>>><br>>> * Add a new com.jboss.devstudio.core.central.feature that <br>>> packages up<br>>> the com.jboss.devstudio.core.central<br>>> plugin and include this in com.jboss.devstudio.core.feature <br>>> (this is<br>>> missing today).<br>>> * Enable usage tracking in JBTIS components' MANIFEST.MF files <br>>> (this<br>>> is under way now)<br>>> - https://issues.jboss.org/browse/JBTIS-290<br>>> * create three connectors, each based on the content in JBDSIS<br>>> discovery plugin.xml's top three<br>>> connector categories<br>>> - https://issues.jboss.org/browse/JBTIS-357<br>>><br>>> 1. Fuse ServiceWorks - ref: JBoss Integration and SOA<br>>> Development<br>>> 2. BRMS/BPMS - ref: JBoss Business Process and <br>>> Rules<br>>> Development<br>>> 3. JBoss Data Virtualization - ref: JBoss Data Virtualization<br>>> Development<br>>><br>>> ** A1: PMs (hey Alan) must come up with appropriate names for 1-3<br>>> above. The naming convention should be<br>>> "compatible" with a Mobile tools install that have been<br>>> requested too.<br>>><br>>> The user searches for "Fuse" from Marketplace and immediately <br>>> finds<br>>> JBDSIS. The installer allows<br>>> the user to select from 1-3 above. The user selects "Fuse<br>>> ServiceWorks" (if that's the name) by<br>>> selecting the radio button (or selects all easily).<br>>><br>>> JBDS 9.0.0.GA/JBDSIS 9.0.x.GA (Mars) - Make it better - continue to<br>>> evolve the solution<br>>><br>>> - https://issues.jboss.org/browse/JBTIS-356/<br>>> https://issues.jboss.org/browse/JBIDE-18734<br>>> Refactor project examples in Central to remove dependencies on <br>>> portal<br>>> & seam (size reduction - avoid<br>>> installing unnecessary plugins).<br>>><br>>> Similar experience to Luna except the installer is much leaner.<br>>><br>>> No default perspective change - potential stretch goal.<br>>><br>>> This subject went back and forth. The user has an established<br>>> perspective when they began the installation<br>>> process and may be installing multiple features which may very well <br>>> have<br>>> different default perspectives.<br>>> Once users manually set their perspective it will be remembered the <br>>> next<br>>> time they start the tool.<br>>><br>>> Alternatively, the installer option definitely should be able to do<br>>> this. When installing into an existing<br>>> Eclipse that is not that trivial, which is one of the reasons why <br>>> JBoss<br>>> Central exists. Central shows<br>>> up across perspectives and when the user selects Fuse the Fuse <br>>> project<br>>> can declare it and would ask users<br>>> if they want to move to the Fuse perspective.<br>>><br>>> We could also look into adding "roles" to Central to make it adopt<br>>> better depending on what interest you<br>>> have as a user.<br>>><br>>> --paull<br>>><br>>><br><div><br></div><br>/max<br>http://about.me/maxandersen<br><div><br></div></blockquote><div><br><br></div><div><br></div><div>-- <br></div><div><span name="x"></span><br>Len DiMaggio (ldimaggi@redhat.com)<br>JBoss by Red Hat<br>314 Littleton Road<br>Westford, MA 01886 USA<br>tel: 978.392.3179<br>cell: 781.472.9912<br>http://www.redhat.com<br>http://community.jboss.org/people/ldimaggio<br><div><br></div><a href="http://www.redhat.com"><img doc="Briefcase/RHxJBpngthumb.png" src="cid:11249b9867e061b5e2ba4e228cbd4638982c8ae3@zimbra" style="border: 0pt none;"></a><br><span name="x"></span><br></div></div></body></html>