[jbosstools-issues] [JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

[Aurélien Pupier (JIRA)]

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

Aurélien Pupier commented on JBTIS-1015:
----------------------------------------

[~pleacu] there will be the exact same issue if we want to mirror locally but as it seems that everybody is happy enough except me with that, we stopped the work on that. it just means that switching of Target Platform is taking much more time than before.

> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
>                 Key: JBTIS-1015
>                 URL: https://issues.jboss.org/browse/JBTIS-1015
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: target-platform
>    Affects Versions: 4.4.1.Final-TP
>            Reporter: Aurélien Pupier
>            Assignee: Paul Leacu
>         Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png, commons.io available in folder.png, commons.io not visible in update site.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if  org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. 
> see [JBTIS-1008] for original discussions



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)