<div class="markdown">
<p dir="auto">On 19 Feb 2016, at 15:31, Nick Boldt wrote:</p>
<blockquote>
<p dir="auto">Incomplete doc which made you run mvn from the wrong folder.</p>
</blockquote>
<p dir="auto">so my question still stands - why is it that we cannot just run <code>mvn verify</code> in TP anymore ?</p>
<p dir="auto">Just wondering since we normally do whatever we can to make builds not require "to know magic" to build.</p>
<p dir="auto">/max</p>
<blockquote>
<p dir="auto">Updated to include more info about multiple/pom.xml vs. unified/pom.xml.</p>
<p dir="auto"><a href="https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328">https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328</a></p>
<p dir="auto">On Fri, Feb 19, 2016 at 2:24 AM, Max Rydahl Andersen<br>
<a href="mailto:manderse@redhat.com">manderse@redhat.com</a> wrote:</p>
<blockquote>
<p dir="auto">Yes - these docs says you can do "mvn clean verify" but that was not the case for the Pr.</p>
<p dir="auto">So that is why I'm asking - why didn't mvn clean verify work ? Incomplete PR or outofdate docs ?</p>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
<blockquote>
<p dir="auto">On 19 Feb 2016, at 06:28, Nick Boldt <a href="mailto:nboldt@redhat.com">nboldt@redhat.com</a> wrote:</p>
<p dir="auto">Building locally:</p>
<p dir="auto"><a href="https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally">https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally</a></p>
<p dir="auto">Verifying local changes to repo references to ensure IU versions are<br>
updated too:</p>
<p dir="auto"><a href="https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files">https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files</a></p>
<p dir="auto">More:</p>
<p dir="auto"><a href="https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse">https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse</a></p>
<p dir="auto">On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen<br>
<a href="mailto:manderse@redhat.com">manderse@redhat.com</a> wrote:</p>
<blockquote>
<p dir="auto">Adding back the list.</p>
<blockquote>
<p dir="auto">I suspect you were in the wrong folder. When I build it, I only build<br>
the multiple/pom.xml, not the unified one.</p>
</blockquote>
<p dir="auto">Gotcha. My bad. I missed the cd. Been too long since I build the tp locally.</p>
<p dir="auto">Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify.</p>
<p dir="auto">/max</p>
<blockquote>
<p dir="auto">N</p>
<p dir="auto">On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen<br>
<a href="mailto:manderse@redhat.com">manderse@redhat.com</a> wrote:</p>
<blockquote>
<p dir="auto">On 18 Feb 2016, at 20:07, Nick Boldt wrote:</p>
<blockquote>
<p dir="auto">Build target-platform:<br>
$ cd /path/to/jbosstools-target-platforms/jbosstools/multiple<br>
$ git fetch origin pull/195/head && git checkout FETCH\_HEAD<br>
$ mvn clean install</p>
</blockquote>
<p dir="auto">I tried this and I got:</p>
<p dir="auto">[INFO]<br>
[INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts)<br>
@ jbdevstudio-unified ---<br>
[INFO]<br>
[INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform<br>
(default) @ jbdevstudio-unified ---<br>
[INFO] Validating<br>
/Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target...<br>
[INFO] Adding repository<br>
<a href="https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO">https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO</a><br>
[INFO] Failed, see Error log below<br>
[ERROR] Validation found errors in 1 .target files:<br>
Could not resolve content of jbdevstudio-unified.target</p>
<p dir="auto">Known issue ?</p>
<p dir="auto">so in short, i'm all for getting the changes in but I cannot build any of<br>
the suggested PR's<br>
so I can't verify them. :/</p>
<p dir="auto">/max</p>
<blockquote>
<p dir="auto">Then, to test the new "multiple" target platform against your component's<br>
build:<br>
$ cd /path/to/your/jbosstools-component<br>
$ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT<br>
-Dtpc.targetKind=multiple</p>
</blockquote>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
</blockquote>
<p dir="auto">--<br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a href="http://nick.divbyzero.com">http://nick.divbyzero.com</a></p>
</blockquote>
</blockquote>
<p dir="auto">--<br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a href="http://nick.divbyzero.com">http://nick.divbyzero.com</a></p>
</blockquote>
</blockquote>
<p dir="auto">-- <br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a href="http://nick.divbyzero.com">http://nick.divbyzero.com</a></p>
</blockquote>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
</div>