[vgriffin]

I’m developing projects using MyEclipse. I want to deploy the project source to another system which does not have MyEclipse. All of the libraries on both systems are in the same ABSOLUTE directory (/opt/dtv/lib…). The source files are not in the same directory although the lower-level structure is the same on both systems. I want to create ant files that can be used by operations staff to build from my released source. I had hoped that the export ant buildfiles function would work for me. The problem is that all of my libraries appear as relative paths (../../../../opt/dtv/lib…) instead of absolute paths (/opt/dtv/lib…) Is there a way to get absolute path output? I’ve tried various library and variable options, but have not been successful. I hope I’ve just overlooked something.

If I cannot create absolute paths, it would be acceptable to use an internal relative path where my user libraries are all inside my project directory. This would only be acceptable if I do not have to recreate the user libraries for each project.

I really don’t want to have to edit the generated ant file.

[Riyad Kalla]

vgriffin,
Unfortunately the export Ant functionality is provided by the base Eclipse install not MyEclipse, so it’s hard to say what it is and isn’t able to do (so we don’t offer any tips on how to use it right at the moment). If you ask at the Eclipse newsgroup people may have a better idea on how to get the results you need.

[vgriffin]

Is there an ant sequence I can use to invoke the export buildfile process? (I’d need the non-eclipse version.) If I can do that, I can follow it with a command to modify the library paths.

[Riyad Kalla]

Unfortuately I don’t know that.

[vgriffin]

Is there anywhere I can find out?

[Riyad Kalla]

I’m sure you could get some direction from the Eclipse newsgroup, maybe the JDT newsgroup more specifically?

[Author]

Posts