Community
Participate
Working Groups
Please considre an example: I'd like to copy from multiple source folders into one bin folder like this: web --> bin conf --> bin\WEB-INF src --> bin\WEB-INF\classes test --> bin\WEB-INF\classes Please also suppose that there are no conflicts - so each folder has a different content and there is no chance to overwrite previous builded files. Behavior of exporting in Eclipse 3.1M3 may be incorect. First I tryed to do like this: I have set default output folder to bin\WEB-INF\classes So my folder where map like this: web --> bin conf --> default src --> default test --> default export order: web conf test src It seem to be ok, but it forgot to copy all hbm.xml files which are located in src file next to *.java. for more detail my folder contains this type of files. web --> bin *.jsp, *.html conf --> bin\WEB-INF *.xml, *.properties src --> bin\WEB-INF\classes *.java, *.hbml.xml test --> bin\WEB-INF\classes *.java So, next time i tryed to change export order to src test conf web In this case, it forgot to copy conf folder content. So my last export order start to do real correct job: web src test conf I think this behavior is not really user frendly, don't you think? Best wishes Andrej Zachar
In additional, i'd like to report also this strang behaviour: Eclipse do a problem "Project was not build due to "resource bin/web- in/classes" doesn't exist. It happens when you want to create a default output folder into the nested folder of an another ouput folder. My project look like this: WEB -> bin (WEB source folder doesn't contains classes folder) +-WEB-INF +-taglib src -> default default output folder is set to "bin\web-inf-classes" So, if you want to build my project, eclipse first copy web folder into bin, which doesn't have folder classes. That is still ok. But when it want to copy compiled source files into default output folder, he say that this directory doesn't exist. That is not ok, by my opinion. I prefere that eclipse would check if folders exists and if not he should create them. Thanks for your notice of my "user frendly bugs" :))) Best wishes to the another develop. Your user Andrej Zachar
Can you attach your project? Or a test project that shows us the problems?
Nested output folders are not allowed for multiple source folders. It should be an error to set the default output folder to '/bin/a/b' AND also set the output folder of another source folder to '/bin'. The error is caught if the default is set to '/bin/a', but not '/bin/a/b'.
We are using JDT/Core code to check if this is a valid configuration. Moving to JDT/Core to reject such a configuration.
Jerome - is this still an issue (CP validation) ?
Created attachment 38150 [details] Proposed patch and regression test This patch prevents the nesting of the project's default output inside a custom output.
Since existing clients may rely on the current behavior and it is late in the 3.2 release cycle, will keep this patch for post 3.2.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
