Home » Archived » Buckminster » PDE JUnit Test with buckminster headless for eclipse 3.5(Is there a way to run PDE JUnit test whith buckminster headless 1.1 for eclipse 3.5)
| |
| Re: PDE JUnit Test with buckminster headless for eclipse 3.5 [message #537557 is a reply to message #537543] |
Wed, 02 June 2010 21:12   |
|
Hi Charles,
Using a 3.5 target platform with Buckminster 3.6 builder is a valid scenario. Would that help you?
- thomas
On 06/02/2010 09:50 PM, Achim Demelt wrote:
> Charles,
>
> Unfortunately, no. JDT and PDE underwent some major refactoring early in the
> 3.6 cycle that was necessary to implement headless launching of JUnit tests.
> There is no way to make this work based on Eclipse 3.5.
>
> Achim
>
> Charles Bonneau wrote:
>
>> Hi !
>> We are developing plug-ins and we want to use Buckminster (with Hudson) to
>> automate the building tasks. For now, we used PDE JUnit test launch
>> configuration to test our plug-ins. Is there a way to launch these PDE
>> JUnit tests in buckminster headless 1.1 (version for eclipse 3.5) ?
>>
>> Thank you.
>>
>> Charles
>
|
|
| |
| Re: PDE JUnit Test with buckminster headless for eclipse 3.5 [message #537927 is a reply to message #537557] |
Fri, 04 June 2010 08:07 |
 Carsten Reckord
Messages: 139
Registered: July 2009 |
Senior Member |
|
|
Hi Thomas, hi Charles,
Just note that in eclipse 3.6 there seem to have been some changes in the Java compiler and bundle dependencies that will make it barf on
some code that compiled fine with 3.5 [*]. So while building a 3.5 target platform with 3.6 is fine, it's probably not so great to use a
Buckminster 3.6 builder on your build server while still developing with 3.5 (but with helios waiting in the wings why would you... ;)
Cheers,
Carsten
*) We noted some problems with Generics, where the 3.6 compiler was a bit more picky - also more correct ;P - than 3.5. And some bundle
dependencies that strangely enough worked implicitly in 3.5 needed to be declared explicitly in 3.6 (Class could not be found but is
indirectly referenced) - again, correctly so I believe...
On 02.06.2010 23:12, Thomas Hallgren wrote:
> Hi Charles,
>
> Using a 3.5 target platform with Buckminster 3.6 builder is a valid scenario. Would that help you?
>
> - thomas
>
>
> On 06/02/2010 09:50 PM, Achim Demelt wrote:
>> Charles,
>>
>> Unfortunately, no. JDT and PDE underwent some major refactoring early in the
>> 3.6 cycle that was necessary to implement headless launching of JUnit tests.
>> There is no way to make this work based on Eclipse 3.5.
>>
>> Achim
>>
>> Charles Bonneau wrote:
>>
>>> Hi !
>>> We are developing plug-ins and we want to use Buckminster (with Hudson) to
>>> automate the building tasks. For now, we used PDE JUnit test launch
>>> configuration to test our plug-ins. Is there a way to launch these PDE
>>> JUnit tests in buckminster headless 1.1 (version for eclipse 3.5) ?
>>>
>>> Thank you.
>>>
>>> Charles
>
|
|
|
| Re: PDE JUnit Test with buckminster headless for eclipse 3.5 [message #537962 is a reply to message #537927] |
Fri, 04 June 2010 10:43 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Do you have project specific settings for these things?
(If not - it is a really good idea as you are otherwise exposed to the
default configuration of the IDE - the errors and warnings, which Java
compliance level to use etc. are not part of the target platform.).
- henrik
On 6/4/10 10:07 AM, Carsten Reckord wrote:
> Hi Thomas, hi Charles,
>
> Just note that in eclipse 3.6 there seem to have been some changes in
> the Java compiler and bundle dependencies that will make it barf on some
> code that compiled fine with 3.5 [*]. So while building a 3.5 target
> platform with 3.6 is fine, it's probably not so great to use a
> Buckminster 3.6 builder on your build server while still developing with
> 3.5 (but with helios waiting in the wings why would you... ;)
>
> Cheers,
> Carsten
>
> *) We noted some problems with Generics, where the 3.6 compiler was a
> bit more picky - also more correct ;P - than 3.5. And some bundle
> dependencies that strangely enough worked implicitly in 3.5 needed to be
> declared explicitly in 3.6 (Class could not be found but is indirectly
> referenced) - again, correctly so I believe...
>
>
> On 02.06.2010 23:12, Thomas Hallgren wrote:
>> Hi Charles,
>>
>> Using a 3.5 target platform with Buckminster 3.6 builder is a valid
>> scenario. Would that help you?
>>
>> - thomas
>>
>>
>> On 06/02/2010 09:50 PM, Achim Demelt wrote:
>>> Charles,
>>>
>>> Unfortunately, no. JDT and PDE underwent some major refactoring early
>>> in the
>>> 3.6 cycle that was necessary to implement headless launching of JUnit
>>> tests.
>>> There is no way to make this work based on Eclipse 3.5.
>>>
>>> Achim
>>>
>>> Charles Bonneau wrote:
>>>
>>>> Hi !
>>>> We are developing plug-ins and we want to use Buckminster (with
>>>> Hudson) to
>>>> automate the building tasks. For now, we used PDE JUnit test launch
>>>> configuration to test our plug-ins. Is there a way to launch these PDE
>>>> JUnit tests in buckminster headless 1.1 (version for eclipse 3.5) ?
>>>>
>>>> Thank you.
>>>>
>>>> Charles
>>
|
|
|
| Re: PDE JUnit Test with buckminster headless for eclipse 3.5 [message #537995 is a reply to message #537927] |
Fri, 04 June 2010 12:44 |
|
This blog explains the compiler changes in detail and is perhaps useful reading.
http://lt-rider.blogspot.com/2010/05/jdt-manifest-classpath- classpath.html
- thomas
On 06/04/2010 10:07 AM, Carsten Reckord wrote:
> Hi Thomas, hi Charles,
>
> Just note that in eclipse 3.6 there seem to have been some changes in
> the Java compiler and bundle dependencies that will make it barf on some
> code that compiled fine with 3.5 [*]. So while building a 3.5 target
> platform with 3.6 is fine, it's probably not so great to use a
> Buckminster 3.6 builder on your build server while still developing with
> 3.5 (but with helios waiting in the wings why would you... ;)
>
> Cheers,
> Carsten
>
> *) We noted some problems with Generics, where the 3.6 compiler was a
> bit more picky - also more correct ;P - than 3.5. And some bundle
> dependencies that strangely enough worked implicitly in 3.5 needed to be
> declared explicitly in 3.6 (Class could not be found but is indirectly
> referenced) - again, correctly so I believe...
>
>
> On 02.06.2010 23:12, Thomas Hallgren wrote:
>> Hi Charles,
>>
>> Using a 3.5 target platform with Buckminster 3.6 builder is a valid
>> scenario. Would that help you?
>>
>> - thomas
>>
>>
>> On 06/02/2010 09:50 PM, Achim Demelt wrote:
>>> Charles,
>>>
>>> Unfortunately, no. JDT and PDE underwent some major refactoring early
>>> in the
>>> 3.6 cycle that was necessary to implement headless launching of JUnit
>>> tests.
>>> There is no way to make this work based on Eclipse 3.5.
>>>
>>> Achim
>>>
>>> Charles Bonneau wrote:
>>>
>>>> Hi !
>>>> We are developing plug-ins and we want to use Buckminster (with
>>>> Hudson) to
>>>> automate the building tasks. For now, we used PDE JUnit test launch
>>>> configuration to test our plug-ins. Is there a way to launch these PDE
>>>> JUnit tests in buckminster headless 1.1 (version for eclipse 3.5) ?
>>>>
>>>> Thank you.
>>>>
>>>> Charles
>>
|
|
|
| Re: PDE JUnit Test with buckminster headless for eclipse 3.5 [message #538098 is a reply to message #537995] |
Sat, 05 June 2010 01:05 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Thanks Thomas, I had not seen that.
Good to know.
- henrik
On 6/4/10 2:44 PM, Thomas Hallgren wrote:
> This blog explains the compiler changes in detail and is perhaps useful
> reading.
>
> http://lt-rider.blogspot.com/2010/05/jdt-manifest-classpath- classpath.html
>
> - thomas
>
> On 06/04/2010 10:07 AM, Carsten Reckord wrote:
>> Hi Thomas, hi Charles,
>>
>> Just note that in eclipse 3.6 there seem to have been some changes in
>> the Java compiler and bundle dependencies that will make it barf on some
>> code that compiled fine with 3.5 [*]. So while building a 3.5 target
>> platform with 3.6 is fine, it's probably not so great to use a
>> Buckminster 3.6 builder on your build server while still developing with
>> 3.5 (but with helios waiting in the wings why would you... ;)
>>
>> Cheers,
>> Carsten
>>
>> *) We noted some problems with Generics, where the 3.6 compiler was a
>> bit more picky - also more correct ;P - than 3.5. And some bundle
>> dependencies that strangely enough worked implicitly in 3.5 needed to be
>> declared explicitly in 3.6 (Class could not be found but is indirectly
>> referenced) - again, correctly so I believe...
>>
>>
>> On 02.06.2010 23:12, Thomas Hallgren wrote:
>>> Hi Charles,
>>>
>>> Using a 3.5 target platform with Buckminster 3.6 builder is a valid
>>> scenario. Would that help you?
>>>
>>> - thomas
>>>
>>>
>>> On 06/02/2010 09:50 PM, Achim Demelt wrote:
>>>> Charles,
>>>>
>>>> Unfortunately, no. JDT and PDE underwent some major refactoring early
>>>> in the
>>>> 3.6 cycle that was necessary to implement headless launching of JUnit
>>>> tests.
>>>> There is no way to make this work based on Eclipse 3.5.
>>>>
>>>> Achim
>>>>
>>>> Charles Bonneau wrote:
>>>>
>>>>> Hi !
>>>>> We are developing plug-ins and we want to use Buckminster (with
>>>>> Hudson) to
>>>>> automate the building tasks. For now, we used PDE JUnit test launch
>>>>> configuration to test our plug-ins. Is there a way to launch these PDE
>>>>> JUnit tests in buckminster headless 1.1 (version for eclipse 3.5) ?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Charles
>>>
>
|
|
|
Goto Forum:
Current Time: Wed Apr 24 23:45:27 GMT 2024
Powered by FUDForum. Page generated in 0.03627 seconds |
] 
Search
Help
Register
Login
Home
