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/jbtistarge... url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarge... <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarge... url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarge... </references> {code}