Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Confirmation of need for "ouput..=."?

I think this is needed by PDE-BUILD to allow our binary (class folders) to be used for compilation at build time. (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=99286 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=146042)

I still think we will have issues in PDE/BUILD if we remove this entry.

Tom



Inactive hide details for David M Williams---12/07/2009 10:05:34 AM---With the new M4-ish Eclipse IDE, there is better checkingDavid M Williams---12/07/2009 10:05:34 AM---With the new M4-ish Eclipse IDE, there is better checking of build.properties values.


From:

David M Williams/Raleigh/IBM@IBMUS

To:

Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

Date:

12/07/2009 10:05 AM

Subject:

[orbit-dev] Confirmation of need for "ouput..=."?





With the new M4-ish Eclipse IDE, there is better checking of build.properties values.

One of those "errors" says

The folder "." does not exist in the workspace

where ever we have
output..=.

in our build.properties files.

But we do still need those output directives there, right?
http://wiki.eclipse.org/Adding_Bundles_to_Orbit#build.properties_entries_and_.classpath_file

I think this was to work around some PDE bug, but I couldn't find reference to it.

Anyone know if its still a bug, and we still need the work around?

I mostly wanted to make sure Orbit committers didn't start removing them, since after all, Eclipse says its an error! :)

Unless its ok to remove now?!

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev


GIF image

GIF image


Back to the top