[jbosstools-issues] [JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content
Paul Leacu (JIRA)
issues at jboss.org
Wed Oct 15 10:50:35 EDT 2014
[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012155#comment-13012155 ]
Paul Leacu commented on JBTIS-339:
----------------------------------
Ok - good point. So now JBTIS can create a fully resolved "withReferences" composite update site and in theory the existing JBTIS discovery poms should continue to work. I'll verify that. So JBDSIS (which draws from JBTIS) doesn't carry associateSites - it pulls from a mirror-target-to-repo. Is that not affected by this?
We pass into our IS poms upstream discovery and composite urls.
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jbosstools/pom.xml
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/devstudio/pom.xml
The JBTIS/JBDSIS discovery plugins has embedded 8.0-development/central/integration-stack in them - does that need to go?
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jbosstools/discovery/org.jboss.tools.central.discovery.integration-stack/plugin.xml#L27
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/devstudio/discovery/com.jboss.jbds.central.discovery.integration-stack/plugin.xml#L56
I need to get fuseide functional as an independently installable update site (withReferences) and have it supply a "references" plain site to the IS. IS that just adding the same composite reference strategy?
So - I need some help from [~mickael_istria] and [~nickboldt] to just look over the IS poms with me if you can spare the time.
> 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