[jbosstools-issues] [JBoss JIRA] (JBDS-2460) replace included p2-director.zip with upstream version from tycho-standalone-p2-director

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-2460:
----------------------------------

Any reason why this forked code can't move to github instead? [~maxandersen], do you see a reason to keep this internal?
                
> replace included p2-director.zip with upstream version from tycho-standalone-p2-director
> ----------------------------------------------------------------------------------------
>
>                 Key: JBDS-2460
>                 URL: https://issues.jboss.org/browse/JBDS-2460
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: 3rdPartyDependencies, Build, installer
>    Affects Versions: 7.0.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 7.0.0.Alpha2
>
>
> To build JBDS installer we need p2-director.zip [0], which is 9M and doesn't include sources. Ideally, we could just use something from Eclipse.org at build-time, and COULD include sources.
> [0] https://svn.jboss.org/repos/devstudio/trunk/product/installer/p2-director.zip
> I looked at tycho-standalone-p2-director [1,2] but it's only an update site -- it lacks equinox.launcher fragments for the various platforms on which we run.
> [1] https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalone-p2-director
> [2] http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-standalone-p2-director/0.16.0/tycho-standalone-p2-director-0.16.0.zip
> So... maybe we need to do something similar but include the binary bits too, so that we can produce something similar to what's in this zip [3] ?

--
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