On Jun 1, 2012, at 18:32 , Nick Boldt wrote:
Well, let's review:
a) Eclipse Marketplace does not include the feature.
b) it's not categorized and not in the Abridged or any other categories.
c) Central does not include the feature, and it isn't part of any of the Core or SOA
Tools features / connectors.
d) It's only visible if you uncheck "show categorized features" via the p2
install UI, which is the workflow we're trying to discourage by virtue of now
providing both Central and Marketplace.
So... other than having a user add the zip/site to their Eclipse/JBDS, and uncheck the
"show categorized features" view, no one will ever see this.
But we can look at a new (and more awkward) process for publishing the plugin independent
of the rest of the site for 3.3.1/5.0.1.
Thats *always* been the goal for that plugin, to both avoid this issue of having it in
places where it should not be AND to allow updating this without having to update the full
updatesite.
Dont understand why it ever was put into the updatesite.
/max
We could even consider putting the plugin into Nexus (not even
publishing it as a p2 artifact, simply as an m2 one) and referencing it from the
directory.xml file there.
Place your comments / suggestions here:
https://issues.jboss.org/browse/JBIDE-11111
N
On 06/01/2012 10:24 AM, Max Rydahl Andersen wrote:
>
> On Jun 1, 2012, at 16:10 , Nick Boldt wrote:
>
>> The plugin is on the site purely as a convenience -- it's published at the
same time as all the soa tooling plugins. The feature wraps the plugin so it can appear on
the site. Again, a convenience.
>>
>> When it says "do not install" it means "do not install"
because it's not meant to be installed. It's meant to be discovered by Central.
>
> users does not read - not sure why we keep assuming this.
>
> Is this going to be visible on user visible updatesites ?
>
> Can't we remove this since it really is not related to any p2/updatesite is it ?
> /max
>
>>
>> N
>>
>>
>> On 06/01/2012 06:00 AM, Max Rydahl Andersen wrote:
>>> the discovery plugins are not intended to be in any updatesite - its just
pointed to by central.
>>>
>>> Nick ?
>>>
>>> and this is not really jbosstools specific.
>>> /max
>>>
>>> On Jun 1, 2012, at 9:27 , Andrej Podhradsky wrote:
>>>
>>>> Hi all,
>>>>
>>>> I would like to ask why there is
com.jboss.jbds.central.discovery.soa-tooling.feature in SOA Tooling update site [1].
>>>>
>>>> The description contains the following:
>>>> "JBoss Central Discovery - do not install this feature; instead, it
will be discovered and used with JBoss Central."
>>>>
>>>> Nevertheless, I tried to install it and the installation fails due to MD5
checksum. So, this feature really cannot be installed, only if I turn off md5 checking
;-)
>>>>
>>>> What's the purpose of this feature? Can JBoss Central use it without
installation?
>>>>
>>>> [1]
http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa...
>>>>
>>>> Best Regards
>>>>
>>>> --
>>>> Andrej Podhradsky
>>>> Quality Assurance Associate
>>>> JBoss SOA Platform
>>>> IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools& Dev Studio
>>
http://nick.divbyzero.com
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com