Eclipse Community Forums: Eclipse Platform » BUG? PDE creating build.xml ignores Java settings

Help

Home

Home » Eclipse Projects » Eclipse Platform » BUG? PDE creating build.xml ignores Java settings

Show: Today's Messages :: Show Polls :: Message Navigator

BUG? PDE creating build.xml ignores Java settings [message #143245]

Mon, 13 October 2003 18:23

Clemens Drews

Messages: 8
Registered: July 2009

Junior Member

Hi,
The build.xml file needed for exporting (read creating) a plugin seems to be
created without looking at the Java Version preferences.
You can reproduce this bug when creating a Plugin (say the Hello World
Plugin example), insert an assertion anywhere in the sourcecode. Doing this
you must switch the compiler compatibility to 1.4. If you do so either in
the project preferences or in the eclipse global preferences and then create
the build.xml file (right mouse click on plugin.xml->create build.xml) the
resulting code contains the line on top:
<property name="javacSource" value="1.3"/>

<property name="javacTarget" value="1.1"/>

which should be 1.4 both times.

Is there a workaround? Am I missing something. So far I generated those
scripts and the set

custom=true

in the build.properties then edited the build.xml to reflect the correct
setting.

Is there a better way? This bug was present in verion 3.0 M3 and now in M4.

- Clemens

Report message to a moderator

Re: BUG? PDE creating build.xml ignores Java settings [message #143265 is a reply to message #143245]

Mon, 13 October 2003 19:08

Clemens Drews

Messages: 8
Registered: July 2009

Junior Member

OK, did a little more research... I guess the culprit is in
org.eclipse.pde.internal.build.builder.ModelBuildScriptGener ator

----

449: script.printProperty(PROPERTY_JAVAC_SOURCE, "1.4"); //$NON-NLS-1$

450: script.printProperty(PROPERTY_JAVAC_TARGET, "1.4"); //$NON-NLS-1$

---
Is this worth filing a bug report?
- Clemens

"Clemens Drews" <cdrews@us.ibm.com> wrote in message
news:bmesuv$jh9$1@eclipse.org...
> Hi,
> The build.xml file needed for exporting (read creating) a plugin seems to
be
> created without looking at the Java Version preferences.
> You can reproduce this bug when creating a Plugin (say the Hello World
> Plugin example), insert an assertion anywhere in the sourcecode. Doing
this
> you must switch the compiler compatibility to 1.4. If you do so either in
> the project preferences or in the eclipse global preferences and then
create
> the build.xml file (right mouse click on plugin.xml->create build.xml) the
> resulting code contains the line on top:
> <property name="javacSource" value="1.3"/>
>
> <property name="javacTarget" value="1.1"/>
>
> which should be 1.4 both times.
>
> Is there a workaround? Am I missing something. So far I generated those
> scripts and the set
>
> custom=true
>
> in the build.properties then edited the build.xml to reflect the correct
> setting.
>
> Is there a better way? This bug was present in verion 3.0 M3 and now in
M4.
>
> - Clemens
>
>
>
>

Report message to a moderator

Re: BUG? PDE creating build.xml ignores Java settings [message #143285 is a reply to message #143265]

Mon, 13 October 2003 19:10

Clemens Drews

Messages: 8
Registered: July 2009

Junior Member

Sorry for any confusion, the String "1.4" below is what I hardcoded to make
my projects run, it used to be "1.3" for source compatibility and "1.1" for
Target VM.\
- Clemens

"Clemens Drews" <cdrews@us.ibm.com> wrote in message
news:bmet7r$jp8$1@eclipse.org...
> OK, did a little more research... I guess the culprit is in
> org.eclipse.pde.internal.build.builder.ModelBuildScriptGener ator
>
> ----
>
> 449: script.printProperty(PROPERTY_JAVAC_SOURCE, "1.4"); //$NON-NLS-1$
>
> 450: script.printProperty(PROPERTY_JAVAC_TARGET, "1.4"); //$NON-NLS-1$
>
> ---
> Is this worth filing a bug report?
> - Clemens
>
> "Clemens Drews" <cdrews@us.ibm.com> wrote in message
> news:bmesuv$jh9$1@eclipse.org...
> > Hi,
> > The build.xml file needed for exporting (read creating) a plugin seems
to
> be
> > created without looking at the Java Version preferences.
> > You can reproduce this bug when creating a Plugin (say the Hello World
> > Plugin example), insert an assertion anywhere in the sourcecode. Doing
> this
> > you must switch the compiler compatibility to 1.4. If you do so either
in
> > the project preferences or in the eclipse global preferences and then
> create
> > the build.xml file (right mouse click on plugin.xml->create build.xml)
the
> > resulting code contains the line on top:
> > <property name="javacSource" value="1.3"/>
> >
> > <property name="javacTarget" value="1.1"/>
> >
> > which should be 1.4 both times.
> >
> > Is there a workaround? Am I missing something. So far I generated those
> > scripts and the set
> >
> > custom=true
> >
> > in the build.properties then edited the build.xml to reflect the correct
> > setting.
> >
> > Is there a better way? This bug was present in verion 3.0 M3 and now in
> M4.
> >
> > - Clemens
> >
> >
> >
> >
>
>

Report message to a moderator

Re: BUG? PDE creating build.xml ignores Java settings [message #149193 is a reply to message #143245]

Fri, 24 October 2003 19:10

Eclipse User

Originally posted by: ed.burnette.REMOVE.THIS.sas.com

This one confused me too. PDE has its own Java version preferences in Window
> Preferences > Plug-in Development > Build Options.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=44821, especially at the
end.

--
Ed Burnette, co-author Eclipse in Action (www.manning.com/gallardo)

"Clemens Drews" <cdrews@us.ibm.com> wrote in message
news:bmesuv$jh9$1@eclipse.org...
> Hi,
> The build.xml file needed for exporting (read creating) a plugin seems to
be
> created without looking at the Java Version preferences.
> You can reproduce this bug when creating a Plugin (say the Hello World
> Plugin example), insert an assertion anywhere in the sourcecode. Doing
this
> you must switch the compiler compatibility to 1.4. If you do so either in
> the project preferences or in the eclipse global preferences and then
create
> the build.xml file (right mouse click on plugin.xml->create build.xml) the
> resulting code contains the line on top:
> <property name="javacSource" value="1.3"/>
>
> <property name="javacTarget" value="1.1"/>
>
> which should be 1.4 both times.
>
> Is there a workaround? Am I missing something. So far I generated those
> scripts and the set
>

Report message to a moderator

Previous Topic:	Eclipse "HELP" Link
Next Topic:	new Eclipse article: Mutatis mutandis - Using Preference Pages as Property Pages

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Nov 08 21:56:30 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter