| build path output [message #1044739] |
Fri, 19 April 2013 05:12  |
 Kevin Hagel
Messages: 15
Registered: December 2012 |
Junior Member |
|
|
In Java the CPlistElement has
public static final String OUTPUT= "output"; //$NON-NLS-1$
but dltk's BPListElement doesn't have it.
I'd like to be able to create a buildpath entry similar to the classpath entry
<classpathentry kind="output" path="bin"/>
in other words
<buildpathentry kind="output" path="bin"/>
Has anybody dealt with this kind of problem before?
I'm extending DLTK's ProjectCreator, taking over the initBuildPath method ... doesn't seem to be available in there.
|
|
|
| Re: build path output [message #1049912 is a reply to message #1044739] |
Fri, 26 April 2013 08:48  |
Kevin Hagel
Messages: 15
Registered: December 2012 |
Junior Member |
|
|
In much of org.eclipse.dltk.internal.core.ScriptProject you see the following kinds of comments:
/**
* Saves the buildpath in a shareable format (VCM-wise) only when necessary,
* that is, if it is semantically different from the existing one in file.
* Will never write an identical one.
*
* @param newBuildpath
* IBuildpathEntry[]
* @param newOutputLocation
* IPath
* @return boolean Return whether the .buildpath file was modified.
* @throws ModelException
*/
public boolean saveBuildpath(IBuildpathEntry[] newBuildpath)
newOutputLocation ... yet there never is an argument for it, it's never encoded nor decoded.
I can manually add
<buildpathentry kind="src" path="src" output="bin"/>
to the .buildpath, it validates but the output attribute is never collected anywhere.
This is a problem for me, I need to be able to do this. How is it that the outputlocation is in the comments, but never in the code?
[Updated on: Fri, 26 April 2013 09:34] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.01488 seconds
] 
Search
Help
Register
Login
Home
