4:56 p.m.
Mickael Istria created JBDS-2168:
------------------------------------
Summary: Review and improve mechanism to provide 3rd-party features
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
Spring & Mylyn are examples of where the 3rd party feature(s) provide more than we
want to include; thus, we either wrap their plugins (mylyn) or a subset of their features
(Spring) to restrict what the customer gets on installation.
IMHO, this is a better approach than just saying "go install it yourself" or
pointing at the 3rd party site directly.
If we're going to take the time to provide our own mirror of the bits (for the
purposes of controlling what appears in Central and on Extras), why not take the extra
branding/control step and wrap w/ features too?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria reassigned JBDS-2168:
------------------------------------
Assignee: Max Rydahl Andersen (was: Mickael Istria)
We need to make a choice on this:
* Do we directly provide 3rd-party features?
* Do we wrap them in a "require" way to provide our own grain and label in UI,
but let people install other versions from external sites?
* Do we wrap them im an "include" way to provide our own grain and label in UI,
but force people to use the version we decide for each feature and force them to update
3rd-party features only via provisioning?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:13 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2168:
-------------------------------------------
What does "our own grain" mean ?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2168:
--------------------------------------
What does "our own grain" mean ?
It means that we can ship different "set of features" from what is originally
shipped. For example, we do that for our Subclipse feature: it actually contains also most
of optional extension of Subclipse, that make sense in our product.
So the end-users see only 1 JBDS/Subclipse feature (that will install 5 Subclipse
features) where using directly Subclipse would show 5 different Subclipse feature.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2168:
-------------------------------------------
Ok got it - then yes, that makes sense we do that and yes, we provide the JBDS features in
a fashion that we can be sure they will install the right versions and if not they can
uninstall/remove them and add manually others.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2168:
-------------------------------------------
Ok got it - then yes, that makes sense we do that and yes, we provide the JBDS features in
a fashion that we can be sure they will install the right versions and if not they can
uninstall/remove them and add manually others.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Work on JBDS-2168 started by Mickael Istria.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2168:
--------------------------------------
let's go for "includes" then.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria reassigned JBDS-2168:
------------------------------------
Assignee: Mickael Istria (was: Max Rydahl Andersen)
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2168:
--------------------------------------
com.jboss.jbds.mylyn.feature contains a lot of stuff. How to decide what we
"include" and what we "require"?
I think we could:
* require all org.eclipse.[!mylyn] bundles, which should be provided by the platform
* Include all non-Eclpse bundles, which are not singleton, so no risk of conflict
* Inclide all com.atlassian plugins, which are the one we support into JBDS
* Include all Mylyn features, which are the one we support into JBDS.
Thoughts?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
Require: won't be on the resulting update site
Include: WILL be on the resulting update site
As there is no other place to provide the features for a JBDS user (because we don't
want them getting the bits from eclipse.org or jboss.org, but only the site on
devstudio.jboss.com), they need to be INCLUDED.
If the dependency exists on the target platform, then it can be simply REQUIRED.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:17 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2168:
-------------------------------------------
mylyn bundle have had many issues - never understood why we had *everything* in it - does
it still provide egit mylyn and svn myln so you cant install it without egit nor svn ?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:57 a.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
Idea was to make Central/Extras include fewer things.
"Want Mylyn? Here's a single all-in-one JBoss-supported bundle of Mylyn
stuff."
rather than
"Want Mylyn? Well, do you want support for Egit? Then pick this connector. Want SVN
support? Then pick THIS connector..."
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:29 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2168:
-------------------------------------------
Nick, that is fine but this drags in alot of stuff - i.e. most that uses egit doesn't
want to have svn installed or viceversa.
Its a balance to make - i.e. for GWT it could make sense to install all of GWT related in
one go, but just because you are a Mylyn user doesn't make it relevant to install all
general Mylyn extensions.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:51 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
So what I'm getting from this is that the preference is to have MULTIPLE connectors on
Central for the following feature groups:
* Mylyn (no Git, no SVN)
* Mylyn for Git (includes Git so it'll be installed if not already)
* Git (no Mylyn)
* Mylyn for SVN (includes SVN so it'll be installed if not already)
* SVN (no Mylyn)
That gives everyone the options they need to install any or all of the 5 pieces they might
want.
Related note: more combinations == more com.jboss.jbds.* features we have to maintain as
mylyn requires a wrapper so it won't include extraneous stuff we don't want to
provide.
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 p.m.
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria resolved JBDS-2168.
----------------------------------
Resolution: Duplicate Issue
Duplicate of JBIDE-13125
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.0.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4178
days inactive
4366
days old
jbosstools-issues@lists.jboss.org
18 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Mickael Istria (JIRA)
-
Nick Boldt (JIRA)