is missing the feature.
You could try building the target platform locally and then point
Eclipse at that instead.
For details on how to do so, see
I am using multiple tp and the feature is available from update
site,
but eclipse still complains.
On 11/20/2013 11:30 AM, Nick Boldt wrote:
> Curiously, the update site is missing that feature, yet it was
> mirrored according to the job's console log:
>
>
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
>
>
> So, I've kicked another build (#180) and it should hopefully do a FULL
> publish this time.
>
> On 11/20/2013 01:50 PM, Denis Golovin wrote:
>> On 11/20/2013 08:53 AM, Nick Boldt wrote:
>>> I know we're barely half way through the testing cycle for JBT
>>> 4.1.1.CR1, but in order to be able to get a first Alpha for JBT 4.2 out
>>> by year's end, we need to start looking at building JBT 4.2 on Luna
>>> ASAP.
>>>
>>> To that end, Mickael will be producing a new Luna M3 target platform
>>> this week - watch for that email w/ instructions. You can of course use
>>> the current Luna M2 target platform if you're eager.
>> Nick,
>>
>> Eclipse reports problem for current target platform I get from 4.40.x.
>> branch:
>> - Unable to locate installable unit
>> org.eclipse.m2e.feature.feature.group.
>> Has something changed on
download.jboss.org since Luna M2 TP was
>> declared?
>>
>> Denis
>>
>>>
>>> The goal is to test building your projects w/ Luna, so that if you're a
>>> project who tends to be broken every year by upstream API changes in
>>> platform or WTP (eg., hibernate tools), you can find those problems and
>>> fix them ASAP. Or if necessary, report problems upstream.
>>>
>>> If all goes to plan, the hope is to have a JBT 4.2.0.Alpha1 build by
>>> the
>>> first week of December.
>>>
>>> Stay tuned!
>>>
>>
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio