[TheJasper]

Hello,
I hope someone can help me. I have a slightly annoying problem in that MyEclipse won’t recognize xml files as ant files unless they are called build.xml. Naturally I am working on a project where there multiple ant files and they aren’t all called build.xml. While I can think of a dozen and one workarounds for this problem it probably shouldn’t even happen, not to mention that workarounds are seldom as efficient as having things work the right way.

I have tried setting ant as being the default for xml files but that doesnt seem to work and is also slightly undesirable.

System information included below. Any help would be appreciated.

mvg,
Jasper

*** Date:
Tuesday, October 7, 2008 11:32:14 AM CEST

** System properties:
OS=Linux
OS version=2.6.26-1-amd64
Java version=1.6.0_03

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715

*** Eclipse details:
Eclipse SDK

Version: 3.3.2
Build id: M20080221-1800

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse startup command=-os
linux
-ws
gtk
-arch
x86_64
-showsplash
-launcher
/home/jasper.floor/apps/europa/eclipse
-name
Eclipse
–launcher.library
/home/jasper.floor/apps/europa/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.3.R33x_v20080118/eclipse_1023.so
-startup
/home/jasper.floor/apps/europa/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
d0006
-vm
/home/jasper.floor/apps/europa/jre/bin/java

[Loyal Water]

Jasper,
This is a known issue and the dev team is already working on this. I’m sorry you ran into this issue.

The workaround is to go to Windows > Preferences > General > Content Type > Text > XML > Ant Build file and add the name of the build file if its not build.xml.

[monroe]

I hit the same problem… and after a couple of hour of head scratching (and cursing about why don’t the Eclipse Docs match it’s behaviour) found this post.

Any estimate when a patch will be available or info on what priority level this bug is? Also, do you know if this problem is for 6.5 only or does it exist in the 7.0 M2 as well?

While I’m on my soap box… have you guys thought about having some sort of “window” into whatever system you use to manage issues? Something that people can search for known issues in a specific version. It would be MUCH better than wading thru the posts here wondering if that two year old post applies to the version you’re running. Maybe something as simple as a periodically posted list / report of known issues that’s pulled from your system.

[Loyal Water]

monroe,
Im afraid this issue exists in 7.0M2 as well. This bug would be fixed in the next release. Sorry for the inconvenience.

[jhm]

Because Ant introduces the <import> task in 1.6.0, importing a file named something else could be very popular. So buildfiles could be modularized.

[Ton Huisman]

From the Project explorer you could right-click the file, and select Open With…/Other…/Ant Editor. That’s a bit cumbersome, but it’s doable 😉

HTH
Ton

[Riyad Kalla]

Guys,

Unfortunately it’s impossible for us to know ahead of time all the different names that might be used for Ant builds scripts, the *correct* way to set this up is using the steps that Nipun posted above (by adding your file name to the content type list).

There *is* the potential for some automatic detection in a future release, but I don’t think that is coming in 7.0 after management recoped a few things; I just want to make sure everyone is on the same page here.

NOTE: Setting the File Association/Editor defaults is not the best way to handle this (the Content Type settings is)… also as Ton pointed out, for quick-and-dirty, you can right-click on the file and use the Ant Editor from open With and the platform will remember that choice.

[jhm]

Ant buildfiles have the root tag <project>. You could parse that …
Other formats like ON or Java are experimental and shouldnt be supported…
ON: http://marc.info/?l=ant-dev&m=122705740029316&w=2
Java: http://svn.apache.org/viewvc/ant/sandbox/javafront/

[Srivatsan Sundararajan]

jhm,

That is exactly right and something we have on our list to look into assuming management prioritizes the work for an upcoming release.

[Author]

Posts