Home » Eclipse Projects » Plugin Development Environment (PDE) » Exporting plugins or product: javacSource gets set to 1.3
| Exporting plugins or product: javacSource gets set to 1.3 [message #35406] |
Wed, 03 December 2008 10:18  |
Eclipse User |
|
|
|
Originally posted by: Marcus.Ilgner.gerig.de
Hi all,
I'm currently trying to export my application, either as a product or
plugin, but in both cases, the build hangs after a while, apparently
having entered an endless loop (CPU high, impossible to stop, have to
SIGKILL Eclipse).
After some investigation I finally found that Eclipse is apparently using
Ant in this step instead of the compiler it normally uses.
To do that it creates build.xml files, which contain, for no apparent
reason:
<property name="javacSource" value="1.3"/>
<property name="javacTarget" value="1.2"/>
which is, of course, wrong and a likely suspect for the cause of my
problem since it will render mostly all plugins unable to compile.
Now my question: how can I change that setting? I have gone on a fruitless
search for some template build.xml and also tried to override this value
by setting those properties to "1.5" in the Ant preferences page.
I read about the same problem happening around 2005. The conversation
there mentioned some option to manually set the language level in the
export wizard but I have been unable to locate anything like this.
I'd be grateful for any tips. This is currently a major showstopper. :/
Best regards
Marcus
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #35581 is a reply to message #35406] |
Wed, 03 December 2008 20:18  |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
See
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
for details on setting source and target levels for export/headless
build. The recommended method would be to set
Bundle-RequiredExecutionEnvironment for your bundles, particularly if
they require a 1.5 vm to run.
The actual properties used in the build.xml by the javac task are
"bundleJavacSource" and "bundleJavacTarget" whose values are set
according to what execution environments are needed/available. (Setting
up the available environments here is done automatically by PDE/UI based
on your installed JREs). The 1.3/1.2 are the fallback defaults if
nothing else is specified.
-Andrew
Marcus Ilgner wrote:
> Hi all,
>
> I'm currently trying to export my application, either as a product or
> plugin, but in both cases, the build hangs after a while, apparently
> having entered an endless loop (CPU high, impossible to stop, have to
> SIGKILL Eclipse).
> After some investigation I finally found that Eclipse is apparently
> using Ant in this step instead of the compiler it normally uses.
> To do that it creates build.xml files, which contain, for no apparent
> reason:
>
> <property name="javacSource" value="1.3"/>
> <property name="javacTarget" value="1.2"/>
>
> which is, of course, wrong and a likely suspect for the cause of my
> problem since it will render mostly all plugins unable to compile.
> Now my question: how can I change that setting? I have gone on a
> fruitless search for some template build.xml and also tried to override
> this value by setting those properties to "1.5" in the Ant preferences
> page.
>
> I read about the same problem happening around 2005. The conversation
> there mentioned some option to manually set the language level in the
> export wizard but I have been unable to locate anything like this.
>
> I'd be grateful for any tips. This is currently a major showstopper. :/
>
> Best regards
> Marcus
>
>
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #35649 is a reply to message #35581] |
Thu, 04 December 2008 11:15 |
| Eclipse User |
|
|
|
Originally posted by: Marcus.Ilgner.gerig.de
Hi Andrew,
Andrew Niefer wrote:
> See
>
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
> for details on setting source and target levels for export/headless
> build. The recommended method would be to set
> Bundle-RequiredExecutionEnvironment for your bundles, particularly if
> they require a 1.5 vm to run.
>
> The actual properties used in the build.xml by the javac task are
> "bundleJavacSource" and "bundleJavacTarget" whose values are set
> according to what execution environments are needed/available. (Setting
> up the available environments here is done automatically by PDE/UI based
> on your installed JREs). The 1.3/1.2 are the fallback defaults if
> nothing else is specified.
Thanks for the hint! I checked this and found that all my bundles already
had
Bundle-RequiredExecutionEnvironment: J2SE-1.5
set in their manifest. Yet the build file generated for them still had the
incorrect values for javacSource and javacTarget.
So I modified the build.properties file across all my bundles to
explicitly set the variables.
Now the build.xml gets generated correctly, but the export process still
hangs at the same point. Seems like there's another problem hidden
somewhere.
Any ideas?
Greetings
Marcus
> Marcus Ilgner wrote:
>> Hi all,
>>
>> I'm currently trying to export my application, either as a product or
>> plugin, but in both cases, the build hangs after a while, apparently
>> having entered an endless loop (CPU high, impossible to stop, have to
>> SIGKILL Eclipse).
>> After some investigation I finally found that Eclipse is apparently
>> using Ant in this step instead of the compiler it normally uses.
>> To do that it creates build.xml files, which contain, for no apparent
>> reason:
>>
>> <property name="javacSource" value="1.3"/>
>> <property name="javacTarget" value="1.2"/>
>>
>> which is, of course, wrong and a likely suspect for the cause of my
>> problem since it will render mostly all plugins unable to compile.
>> Now my question: how can I change that setting? I have gone on a
>> fruitless search for some template build.xml and also tried to override
>> this value by setting those properties to "1.5" in the Ant preferences
>> page.
>>
>> I read about the same problem happening around 2005. The conversation
>> there mentioned some option to manually set the language level in the
>> export wizard but I have been unable to locate anything like this.
>>
>> I'd be grateful for any tips. This is currently a major showstopper. :/
>>
>> Best regards
>> Marcus
>>
>>
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #35851 is a reply to message #35649] |
Thu, 04 December 2008 17:57 |
| Eclipse User |
|
|
|
Originally posted by: Marcus.Ilgner.gerig.de
Update:
now it seems like everything compiles ok, since the export finishes
successfully as long as I don't check Mac OS X in the target platform list.
Sooner or later I'll need a Mac OS X (Intel) executable but for the time
being I can work around this, so the urgency has been removed from this
issue for me.
Thanks for your help, Andrew.
Best regards
Marcus
Marcus Ilgner wrote:
> Hi Andrew,
> Andrew Niefer wrote:
>> See
>>
>
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
>> for details on setting source and target levels for export/headless
>> build. The recommended method would be to set
>> Bundle-RequiredExecutionEnvironment for your bundles, particularly if
>> they require a 1.5 vm to run.
>>
>> The actual properties used in the build.xml by the javac task are
>> "bundleJavacSource" and "bundleJavacTarget" whose values are set
>> according to what execution environments are needed/available. (Setting
>> up the available environments here is done automatically by PDE/UI based
>> on your installed JREs). The 1.3/1.2 are the fallback defaults if
>> nothing else is specified.
> Thanks for the hint! I checked this and found that all my bundles already
> had
> Bundle-RequiredExecutionEnvironment: J2SE-1.5
> set in their manifest. Yet the build file generated for them still had the
> incorrect values for javacSource and javacTarget.
> So I modified the build.properties file across all my bundles to
> explicitly set the variables.
> Now the build.xml gets generated correctly, but the export process still
> hangs at the same point. Seems like there's another problem hidden
> somewhere.
> Any ideas?
> Greetings
> Marcus
>> Marcus Ilgner wrote:
>>> Hi all,
>>>
>>> I'm currently trying to export my application, either as a product or
>>> plugin, but in both cases, the build hangs after a while, apparently
>>> having entered an endless loop (CPU high, impossible to stop, have to
>>> SIGKILL Eclipse).
>>> After some investigation I finally found that Eclipse is apparently
>>> using Ant in this step instead of the compiler it normally uses.
>>> To do that it creates build.xml files, which contain, for no apparent
>>> reason:
>>>
>>> <property name="javacSource" value="1.3"/>
>>> <property name="javacTarget" value="1.2"/>
>>>
>>> which is, of course, wrong and a likely suspect for the cause of my
>>> problem since it will render mostly all plugins unable to compile.
>>> Now my question: how can I change that setting? I have gone on a
>>> fruitless search for some template build.xml and also tried to override
>>> this value by setting those properties to "1.5" in the Ant preferences
>>> page.
>>>
>>> I read about the same problem happening around 2005. The conversation
>>> there mentioned some option to manually set the language level in the
>>> export wizard but I have been unable to locate anything like this.
>>>
>>> I'd be grateful for any tips. This is currently a major showstopper. :/
>>>
>>> Best regards
>>> Marcus
>>>
>>>
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #586348 is a reply to message #35406] |
Wed, 03 December 2008 20:18 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
See
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
for details on setting source and target levels for export/headless
build. The recommended method would be to set
Bundle-RequiredExecutionEnvironment for your bundles, particularly if
they require a 1.5 vm to run.
The actual properties used in the build.xml by the javac task are
"bundleJavacSource" and "bundleJavacTarget" whose values are set
according to what execution environments are needed/available. (Setting
up the available environments here is done automatically by PDE/UI based
on your installed JREs). The 1.3/1.2 are the fallback defaults if
nothing else is specified.
-Andrew
Marcus Ilgner wrote:
> Hi all,
>
> I'm currently trying to export my application, either as a product or
> plugin, but in both cases, the build hangs after a while, apparently
> having entered an endless loop (CPU high, impossible to stop, have to
> SIGKILL Eclipse).
> After some investigation I finally found that Eclipse is apparently
> using Ant in this step instead of the compiler it normally uses.
> To do that it creates build.xml files, which contain, for no apparent
> reason:
>
> <property name="javacSource" value="1.3"/>
> <property name="javacTarget" value="1.2"/>
>
> which is, of course, wrong and a likely suspect for the cause of my
> problem since it will render mostly all plugins unable to compile.
> Now my question: how can I change that setting? I have gone on a
> fruitless search for some template build.xml and also tried to override
> this value by setting those properties to "1.5" in the Ant preferences
> page.
>
> I read about the same problem happening around 2005. The conversation
> there mentioned some option to manually set the language level in the
> export wizard but I have been unable to locate anything like this.
>
> I'd be grateful for any tips. This is currently a major showstopper. :/
>
> Best regards
> Marcus
>
>
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #586371 is a reply to message #35581] |
Thu, 04 December 2008 11:15 |
Marcus Ilgner
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Hi Andrew,
Andrew Niefer wrote:
> See
>
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
> for details on setting source and target levels for export/headless
> build. The recommended method would be to set
> Bundle-RequiredExecutionEnvironment for your bundles, particularly if
> they require a 1.5 vm to run.
>
> The actual properties used in the build.xml by the javac task are
> "bundleJavacSource" and "bundleJavacTarget" whose values are set
> according to what execution environments are needed/available. (Setting
> up the available environments here is done automatically by PDE/UI based
> on your installed JREs). The 1.3/1.2 are the fallback defaults if
> nothing else is specified.
Thanks for the hint! I checked this and found that all my bundles already
had
Bundle-RequiredExecutionEnvironment: J2SE-1.5
set in their manifest. Yet the build file generated for them still had the
incorrect values for javacSource and javacTarget.
So I modified the build.properties file across all my bundles to
explicitly set the variables.
Now the build.xml gets generated correctly, but the export process still
hangs at the same point. Seems like there's another problem hidden
somewhere.
Any ideas?
Greetings
Marcus
> Marcus Ilgner wrote:
>> Hi all,
>>
>> I'm currently trying to export my application, either as a product or
>> plugin, but in both cases, the build hangs after a while, apparently
>> having entered an endless loop (CPU high, impossible to stop, have to
>> SIGKILL Eclipse).
>> After some investigation I finally found that Eclipse is apparently
>> using Ant in this step instead of the compiler it normally uses.
>> To do that it creates build.xml files, which contain, for no apparent
>> reason:
>>
>> <property name="javacSource" value="1.3"/>
>> <property name="javacTarget" value="1.2"/>
>>
>> which is, of course, wrong and a likely suspect for the cause of my
>> problem since it will render mostly all plugins unable to compile.
>> Now my question: how can I change that setting? I have gone on a
>> fruitless search for some template build.xml and also tried to override
>> this value by setting those properties to "1.5" in the Ant preferences
>> page.
>>
>> I read about the same problem happening around 2005. The conversation
>> there mentioned some option to manually set the language level in the
>> export wizard but I have been unable to locate anything like this.
>>
>> I'd be grateful for any tips. This is currently a major showstopper. :/
>>
>> Best regards
>> Marcus
>>
>>
|
|
|
| Re: Exporting plugins or product: javacSource gets set to 1.3 [message #586444 is a reply to message #35649] |
Thu, 04 December 2008 17:57 |
Marcus Ilgner
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Update:
now it seems like everything compiles ok, since the export finishes
successfully as long as I don't check Mac OS X in the target platform list.
Sooner or later I'll need a Mac OS X (Intel) executable but for the time
being I can work around this, so the urgency has been removed from this
issue for me.
Thanks for your help, Andrew.
Best regards
Marcus
Marcus Ilgner wrote:
> Hi Andrew,
> Andrew Niefer wrote:
>> See
>>
>
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_compilation_env.htm
>> for details on setting source and target levels for export/headless
>> build. The recommended method would be to set
>> Bundle-RequiredExecutionEnvironment for your bundles, particularly if
>> they require a 1.5 vm to run.
>>
>> The actual properties used in the build.xml by the javac task are
>> "bundleJavacSource" and "bundleJavacTarget" whose values are set
>> according to what execution environments are needed/available. (Setting
>> up the available environments here is done automatically by PDE/UI based
>> on your installed JREs). The 1.3/1.2 are the fallback defaults if
>> nothing else is specified.
> Thanks for the hint! I checked this and found that all my bundles already
> had
> Bundle-RequiredExecutionEnvironment: J2SE-1.5
> set in their manifest. Yet the build file generated for them still had the
> incorrect values for javacSource and javacTarget.
> So I modified the build.properties file across all my bundles to
> explicitly set the variables.
> Now the build.xml gets generated correctly, but the export process still
> hangs at the same point. Seems like there's another problem hidden
> somewhere.
> Any ideas?
> Greetings
> Marcus
>> Marcus Ilgner wrote:
>>> Hi all,
>>>
>>> I'm currently trying to export my application, either as a product or
>>> plugin, but in both cases, the build hangs after a while, apparently
>>> having entered an endless loop (CPU high, impossible to stop, have to
>>> SIGKILL Eclipse).
>>> After some investigation I finally found that Eclipse is apparently
>>> using Ant in this step instead of the compiler it normally uses.
>>> To do that it creates build.xml files, which contain, for no apparent
>>> reason:
>>>
>>> <property name="javacSource" value="1.3"/>
>>> <property name="javacTarget" value="1.2"/>
>>>
>>> which is, of course, wrong and a likely suspect for the cause of my
>>> problem since it will render mostly all plugins unable to compile.
>>> Now my question: how can I change that setting? I have gone on a
>>> fruitless search for some template build.xml and also tried to override
>>> this value by setting those properties to "1.5" in the Ant preferences
>>> page.
>>>
>>> I read about the same problem happening around 2005. The conversation
>>> there mentioned some option to manually set the language level in the
>>> export wizard but I have been unable to locate anything like this.
>>>
>>> I'd be grateful for any tips. This is currently a major showstopper. :/
>>>
>>> Best regards
>>> Marcus
>>>
>>>
|
|
|
Goto Forum:
Current Time: Tue Apr 23 12:13:24 GMT 2024
Powered by FUDForum. Page generated in 0.04230 seconds |
] 
Search
Help
Register
Login
Home
