[jbosstools-issues] [JBoss JIRA] (JBTIS-358) Use wrapper features to simplify the install and clean up the Marketplace UI?

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025021#comment-13025021 ] 

Nick Boldt edited comment on JBTIS-358 at 12/3/14 8:48 PM:
-----------------------------------------------------------

So here's another approach to managing these wrapper features: generating the feature.xml (a simple list of contained features) from the <connectorDescriptor> in the discovery plugin.xml file.

https://github.com/jbosstools/jbosstools-integration-stack/pull/255

What this does:
* creates a boilerplate feature.xml that can then be committed to github

What this does not do:
* pull the connector name or description (though that could be done easily) and insert that into the feature.xml
* generate feature.properties (using values from the plugin.xml) 
* generate pom.xml (using values from the plugin.xml)
* generate generic build.properties, license.html
* merge in a static list of other required features (ie., JBDS/JBT/Eclipse dependencies)

let me know if any of the above additional features are of value, or if simply having the list of features is enough. 

I believe this simple tool would allow us to commit features to github (eg., similar to those in https://github.com/jbosstools/jbosstools-integration-stack/pull/249 ), then update them as needed should new ones be added to the Discovery plugin or the contents of existing ones change. But we could make it more complicated and snazzy if needed. :)

Feedback welcome, [~maxandersen] [~pleacu]. 

Also, if [~mickael_istria] knows a way to call the same build plugin N times (to generate N feature.xml files from the same maven reactor) I'd love to know how to do that. Played with the iterator plugin ( http://khmarbaise.github.io/iterator-maven-plugin/ ) but it didn't work for me - didn't understand what a transformationSet was.


was (Author: nickboldt):
So here's another approach to managing these wrapper features: generating the feature.xml (a simple list of contained features) from the <connectorDescriptor> in the discovery plugin.xml file.

https://github.com/jbosstools/jbosstools-integration-stack/pull/255

What this does:
* creates a boilerplate feature.xml that can then be committed to github

What this does not do:
* pull the connector name or description (though that could be done easily) and insert that into the feature.xml
* generate feature.properties (using values from the plugin.xml) 
* generate pom.xml (using values from the plugin.xml)
* generate generic build.properties, license.html
* merge in a static list of other required features (ie., JBDS/JBT/Eclipse dependencies)

let me know if any of the above additional features are of value, or if simply having the list of features is enough. 

I believe this simple tool would allow us to commit features to github, then update them as needed should new ones be added to the Discovery plugin or the contents of existing ones change. But we could make it more complicated and snazzy if needed. :)

Feedback welcome, [~maxandersen] [~pleacu]. 

Also, if [~mickael_istria] knows a way to call the same build plugin N times (to generate N feature.xml files from the same maven reactor) I'd love to know how to do that. Played with the iterator plugin ( http://khmarbaise.github.io/iterator-maven-plugin/ ) but it didn't work for me - didn't understand what a transformationSet was.

> Use wrapper features to simplify the install and clean up the Marketplace UI?
> -----------------------------------------------------------------------------
>
>                 Key: JBTIS-358
>                 URL: https://issues.jboss.org/browse/JBTIS-358
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: distribution
>    Affects Versions: 7.0.3.GA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 7.1.0.GA-JBDSIS
>
>         Attachments: is-marketplace1.png, is-marketplace2.png
>
>
> For 7.1.0, could consider having wrapper features to simplify the install and clean up the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI, we could list only 3 features.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)