[jbosstools-issues] [JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content
Max Rydahl Andersen (JIRA)
issues at jboss.org
Wed Oct 15 13:45:37 EDT 2014
[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012292#comment-13012292 ]
Max Rydahl Andersen commented on JBTIS-339:
-------------------------------------------
[~leacu] the "fuseide independent installable update site" is *just* for community testing, right ? the supported version will come from JBDSIS updatesites and planned to be put on marketplace. correct ?
btw. if fuseide updates into JBTIS anyway - is there a reason for them to not just tell users to use the JBTIS update site ?
> 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)
More information about the jbosstools-issues
mailing list