#65 IBuildfileManipulator cannot handle multiple associations

[Remy Chi Jian Suen]

IBuildfileManipulator has a getTarget(IFile) method that returns the target that a file is currently associated with. However, if the file is being compiled on two or more targets, there is no documentation as to which target will be returned.

[Bernhard Brem]

Logged In: YES
user_id=1245734
Originator: NO

We have to look where this is needed:Since a file can have more targets we will have here problems......

[Remy Chi Jian Suen]

Logged In: YES
user_id=1299552
Originator: YES

I'm also wondering as to whether we should diverge away from a "target-based" system or not. I mean, SharpDevelop and Visual Studio has a build file in the backend but the user never actually sees it. Eclipse doesn't even use a build file to do the compilation as it reads all the necessary information from the .classpath file and the MANIFEST.MF if applicable (in the case of OSGi bundles). From what I heard, MonoDevelop uses a similar approach to Eclipse with no actual build file.

[Bernhard Brem]

Logged In: YES
user_id=1245734
Originator: NO

The difference is Visual Studio knows about solutions. Each solution can have many projects. So You are able to build various artefacts which belong together and have to be built in a special order by building the solution.

I myself have at least one project where I have to generate different targets which should belong together and result in one build directory.

[Bernhard Brem]

Logged In: YES
user_id=1245734
Originator: NO

The only occurance where this is called is in codeInformator line 647. It should be easy to replace it here by the function returning all targets....

[Bernhard Brem]

Logged In: YES
user_id=1245734
Originator: NO

Fixed in cvs: Removed this method and replaced by the method delivering all target files