Because I use the .target as a target platform in eclipse too. So I
don't have to maintain 2 environments, one for the build, one for the
development. Downside is it brings SDKs during the CLI build, but I'm OK
with it.
Using
Why do you need SDK features? Surely you only depend on binaries, not
sources?
On 06/15/2011 05:36 PM, Fred Bricon wrote:
> The maven/seam tests are back to blue.
> The m2e-wtp e37 is failing because someone at eclipse wiped the
>
http://download.eclipse.org/webtools/repository/indigo/ update site.
> Using the jbosstools mirror didn't help, because it's missing some SDKs.
> Anyone knows where I can find the webtools bits now???
> The e36 job succeeds though and still publishes stuff.
>
> Regards,
>
> Fred Bricon
>
> On 06/15/2011 06:59 PM, Nick Boldt wrote:
>> Nice work, everyone!
>>
>> = Maintenance Branch: 3.2.x / 4.x =
>>
>> Currently, only 2 jobs are non-blue - bpel and .continuous:
>>
>> * bpel apparently now depends on archives (or has always depended on
>> archives), so I've updated the swimlanes & job linkages accordingly
>>
>> * continuous "will it all compile?" job: hudson glitch; respinning
>>
>> --
>>
>> = Trunk: 3.3.0 / 5.0 =
>>
>> Currently, only 4 jobs are non-blue - AS, .tests, m2e-wtp, and forge:
>>
>> * AS: 2 test failures, which Rob is working to fix
>>
>> * tests "all JBT tests in a single place" job: since June 13,
we're
>> down to just 1 long-running Maven test failure! -
>>
org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.org.jboss.tools.maven.ui.bot.test.CreateMavenizedSeamProjectTest
>>
>>
>>
>> See:
>>
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
>>
>>
>>
>> * m2e-wtp: missing WTP dep? respinning anyway
>>
>> See:
>>
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
>>
>>
>>
>> * forge: hudson glitch; respinning
>>
>