[jbosstools-issues] [JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content

[Paul Leacu (JIRA)]

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

Paul Leacu commented on JBTIS-339:
----------------------------------

[~mickael_istria] - I see you've merged the PR for this feature in repository-utils 0.21.1-SNAPSHOT.   I need to create the JBTIS 4.2.0.Beta1 release early next week so I'll need the updated tycho-plugins - is it available?  I believe the withReferences vs "plain" approach satisfies the primary use case.
   Thanks!

> Support generation of update sites both with and without references to upstream TP content
> ------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-339
>                 URL: https://issues.jboss.org/browse/JBTIS-339
>             Project: JBoss Tools Integration Stack
>          Issue Type: Feature Request
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>         Attachments: content.xml.new, content.xml.orig
>
>
> Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
> * One plain content only, without any reference: for downstream project aggregation
> * One that also references its dependencies for easy install and testers
> Example:
> {code}
> /integration-stack  <-- composited without side effects into /earlyaccess/development/luna/
>   content.jar
>   artifacts.jar
>   /withdeps  <--- good for testing/single installs
>      /compositeContent.xml  -> ../ and ../targetplatform-link/
>     /compositeArtifacts.xml
>  /targetplatform-link  <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
>    content.xml -> associate pointer to TP using ONLY:
>    <references size="4">
>       <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
>       <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
>       <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-tp.4.2.3" url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-tp.4.2.3"/>
>       <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-tp.4.2.3" url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-tp.4.2.3"/>
>    </references>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)