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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18541:
------------------------------------

Conceptually, +1. Label-wise, +0.5. Not sure that "direct references" and "composite with references" is clear enough. Maybe...

* "embed-references-in-simple-site" vs.
* "generate-composite-wrapper-site"

I'm also not sure why we would ever want to support the OLD approach, when the new one is:

* better
* more complete
* backward compatible

You could also just add a <legacy>true</legacy> flag, if you really wanted to support the old approach. Or even simpler, just have people use the OLD version of the mojo, if they want the old approach. Then you need only support the NEW way.





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