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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18541:
----------------------------------------

Having compositeArtifacts different is normal, because the "references" repo doesn't contain any artifacts, it contains just references.
Are IS component inheriting your pom configuration? If yes, then you only need to change the IS parent pom.
Note that Mojo is currently a SNAPSHOT version, so we'll probably need to release it before using it more widely.

> Support generation of update sites both with and without references to upstream TP content
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18541
>                 URL: https://issues.jboss.org/browse/JBIDE-18541
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.2.0.CR2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.0.Final
>
>         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)