<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/08/2013 01:04 AM, Denis Golovin
wrote:<br>
</div>
<blockquote cite="mid:52533DE0.4010307@exadel.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">On 10/07/2013 12:36 PM, Nick Boldt
wrote:<br>
</div>
<blockquote cite="mid:52530D21.2030507@redhat.com" type="cite">If
you resolve the multiple target first, you can then use that to
resolve the unified one, as per my instructions below and in the
README. <br>
</blockquote>
I don't resolve anything, build is supposed to do that for me. If
it is not, why all targets are in the same reactor?<br>
</blockquote>
Having unified referencing not existing sites in the same reactor
makes indeed stuff less clear. Those target platforms are supposed
to be built sequentially, and the unified.target requires TP site to
be published remotely. You can override the TP site location for
testing purpose, and in order to test module, you can use the
-Pmultiple profile (cf mail announcing TP changes).<br>
The process for making TP public is<br>
1. Build, validate, deploy multiple<br>
2. Publish unified site (creating when building multiple)<br>
3. Build and validate unified against just published site; and then
deploy it<br>
<br>
<blockquote cite="mid:52533DE0.4010307@exadel.com" type="cite">
<blockquote cite="mid:52530D21.2030507@redhat.com" type="cite">
-DtargetRepositoryUrl=<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="file://path/to/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/">file://path/to/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/</a>
<br>
</blockquote>
<br>
why this -DtargetRepository= is not set by default to local
jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/
which has been built in the same reactor just couple seconds ago?<br>
</blockquote>
IMO, the remote site is a better default value:
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/jbosstools/unified/pom.xml#L16">https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/jbosstools/unified/pom.xml#L16</a><br>
Although it makes local builds fail just after TP change. it
configures a good value which makes sure that if someone runs "mvn
clean install", he'll end up with a TP referencing the remote site
and not the local one.<br>
<blockquote cite="mid:52533DE0.4010307@exadel.com" type="cite"> What
I thought it was verified against the same locations presented in
jbdevstudio-multiple.target.repo, because they should be available
online to let jbdevstudio/multiple build to work and all metadata
is downloaded into local maven repo.<br>
</blockquote>
Multiple are built against the multiple dependency repositories,
unified is built against the "unified" site we create with all
dependencies (which exists for installation purpose).<br>
<br>
<blockquote cite="mid:52533DE0.4010307@exadel.com" type="cite"> BTW
the same problem with jbosstools tp's after -DtargetRepositoryUrl
is set as suggested above<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<pre style="white-space: pre-wrap; word-wrap: break-word; margin: 0px; color: rgb(0, 0, 0); font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);">[INFO] Building JBoss Tools Unified (Aggregate) Target Platform 4.40.0.Alpha1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- target-platform-utils:0.16.0-SNAPSHOT:flatten-target (create-target) @ jbosstools-unified ---
[INFO]
[INFO] <b class="maven-mojo">--- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbosstools-unified ---
</b>[INFO]
[INFO] <b class="maven-mojo">--- target-platform-validation-plugin:0.18.1:validate-target-platform (default) @ jbosstools-unified ---
</b>[INFO] Validating /var/lib/jenkins/workspace/jbosstools-target-platform-luna/jbosstools/unified/target/jbosstools-unified.target...
[INFO] Failed, see Error log below
<span class="error-inline" style="color: rgb(204, 0, 0); font-weight: bold;">[ERROR] Validation found errors in 1 .target files:
</span>Could not resolve content of jbosstools-unified.target
Could not find "org.eclipse.swtbot.eclipse.feature.group/2.1.1.201305311053" in the repositories of the current location</pre>
</blockquote>
Aren't you verifying JBT unified TP against the JBDS unified site?
That could explain why SWTBot is missing.<br>
<br>
<br>
<blockquote cite="mid:52533DE0.4010307@exadel.com" type="cite"> I'll
check modules build later.<br>
</blockquote>
They are actually the ones that require the more effort. So far, I
don't think it's necessary to have so much time spent on the build
of target-platforms. which is not very error-prone.<br>
<br>
Cheers,<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>