Adding a library a processing project overwrites build path

[GoogleCodeExporter]

I sometime start writing a processing program and sometimes I add another 
project to its build path. this works fine. If I decide to include another 
processing library at a later stage to this project (aka a library which is in 
the libraries folder and which I can include using the processing preferences), 
the build path gets overwritten and not added on.

It would be nice if proclipsing could handle that better, e.g. by maintaning 
its own subset of library dependencies whereas letting other settings as they 
are.

Original issue reported on code.google.com by justjoheinz on 18 Nov 2011 at 6:33

[GoogleCodeExporter]

Yeah, this is annoying.  I'd like to fix it, but it's a bit tricky.  I'm going 
to accept this bug, but to be honest it's a low priority and I'm not sure when 
I'll get to it.  If you'd like to help out and try to fix the issue, 
Proclipsing could sure use the support.

Original comment by maddpar...@gmail.com on 19 Mar 2014 at 9:43

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium