[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2246) P2 vs Installer ?

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438836#action_12438836 ] 

Nick Boldt commented on JBIDE-2246:
-----------------------------------

You're right -- I was looking for a JIRA to contain the work of adding p2 metadata to the existing JBDS/JBT update site.

I understood the issue here was not to change the way the installer works but to provide the end user with more control when installing plugins.

Perhaps we need to back up and decide what the problem is -- does the installer (which I've as yet never seen or used) lack granularity? Or are we just looking to make the update sites p2-enabled and thus more performant?

p2 still uses features as its base unit of install, so if we want more granular features to be installable, we need smaller features. We can have nested features so that people have options (install the whole foo SDK, including source and doc) or just the foo runtime). 

> P2 vs Installer ?
> -----------------
>
>                 Key: JBIDE-2246
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2246
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng, Eclipse Migration
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 3.0.0.GA
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Is P2 stable/good enough for basing our updatesites on ? 
> Can we use it to have a more finegrained control in the installer (eg. only install some parts?)
> Can it be used to install other things than plugins ? (e.g. JBossAS ?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira