<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">There is no relation between central
repo and
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<a
href="https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/jbosstools/multiple/jbosstools-multiple.target">https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/jbosstools/multiple/jbosstools-multiple.target</a>.
I was using jbosstools-multiple.target in eclipse and problem was
obviously in swallowed OutOfMemory somewhere inside Eclipse. I
changed default settings in eclipse.ini and now everything is
fine.<br>
<br>
Denis<br>
<br>
On 11/20/2013 11:57 AM, Nick Boldt wrote:<br>
</div>
<blockquote cite="mid:528D1421.9060509@redhat.com" type="cite">Yes,
because
<a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Alpha1-SNAPSHOT/REPO/">http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Alpha1-SNAPSHOT/REPO/</a>
is missing the feature.
<br>
<br>
You could try building the target platform locally and then point
Eclipse at that instead.
<br>
<br>
For details on how to do so, see
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/README.md">https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/README.md</a>
<br>
<br>
<br>
<br>
On 11/20/2013 02:47 PM, Denis Golovin wrote:
<br>
<blockquote type="cite">I am using multiple tp and the feature is
available from update site,
<br>
but eclipse still complains.
<br>
<br>
On 11/20/2013 11:30 AM, Nick Boldt wrote:
<br>
<blockquote type="cite">Curiously, the update site is missing
that feature, yet it was
<br>
mirrored according to the job's console log:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/179">https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/179</a>
<br>
<br>
<br>
So, I've kicked another build (#180) and it should hopefully
do a FULL
<br>
publish this time.
<br>
<br>
On 11/20/2013 01:50 PM, Denis Golovin wrote:
<br>
<blockquote type="cite">On 11/20/2013 08:53 AM, Nick Boldt
wrote:
<br>
<blockquote type="cite">I know we're barely half way through
the testing cycle for JBT
<br>
4.1.1.CR1, but in order to be able to get a first Alpha
for JBT 4.2 out
<br>
by year's end, we need to start looking at building JBT
4.2 on Luna
<br>
ASAP.
<br>
<br>
To that end, Mickael will be producing a new Luna M3
target platform
<br>
this week - watch for that email w/ instructions. You can
of course use
<br>
the current Luna M2 target platform if you're eager.
<br>
</blockquote>
Nick,
<br>
<br>
Eclipse reports problem for current target platform I get
from 4.40.x.
<br>
branch:
<br>
- Unable to locate installable unit
<br>
org.eclipse.m2e.feature.feature.group.
<br>
Has something changed on download.jboss.org since Luna M2 TP
was
<br>
declared?
<br>
<br>
Denis
<br>
<br>
<blockquote type="cite">
<br>
The goal is to test building your projects w/ Luna, so
that if you're a
<br>
project who tends to be broken every year by upstream API
changes in
<br>
platform or WTP (eg., hibernate tools), you can find those
problems and
<br>
fix them ASAP. Or if necessary, report problems upstream.
<br>
<br>
If all goes to plan, the hope is to have a JBT
4.2.0.Alpha1 build by
<br>
the
<br>
first week of December.
<br>
<br>
Stay tuned!
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>