Community
Participate
Working Groups
I recently tried to set up a plugin project to have two source folders: one for production code, one for tests. I wanted the project to output a jar for each folder. I ended up getting warnings that were extremely difficult to overcome. It took a lot of googling and a lot of trial and error. It shouldn't be that difficult. I've created a screen movie to show the experience (attached)
Here's the movie (it was too large to attach). https://docs.google.com/leaf?id=0B_Y45JVQqy1WZThlODQ4ZDItYTIwZS00ZGJmLTg0ZjctNDdhYjM0YmRlMDIy&hl=en&authkey=COKyiM0E
Summary: - I have a plug-in and want to have 2 nested JARs: production.jar and tests.jar - I set up 2 source folders - in the Runtime tab of the Manifest editor I create the 2 JARs (and remove the "." entry) - In order to get the output to go to the right JARs, I have to go into the Java project properties, select the Java Build Path, and then in the Source Folders tab, then select I want separate output folders - then set up a new output folder for each source folder The resulting build.properties should look something like this: output.production.jar = bin.production/ output.tests.jar = bin.tests/ bin.includes = META-INF/,\ production.jar,\ tests.jar source.production.jar = production/ source.tests.jar = tests/
(In reply to comment #2) Thanks for the summary. A few corrections: > - then set up a new output folder for each source folder You actually only need to set the output folder for the 'test' folder, since the 'src' one will go to 'bin' by default. > The resulting build.properties should look something like this: > > output.production.jar = bin.production/ > output.tests.jar = bin.tests/ > bin.includes = META-INF/,\ > production.jar,\ > tests.jar > source.production.jar = production/ > source.tests.jar = tests/ The output.<jarname> directives in the build.properties are extraneous and probably best omitted. Those properties are generated on the fly based on the project Java Build Path properties. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=253950#c2 Also, I failed to mention what I think to be the biggest problem--what is most likely to frustrate the user. The warnings show up in build.properties. Someone seeing those warnings and not fully understanding them will naturally suspect something misconfigured or lacking in that file. Yet, the warnings cannot be fixed there. They require changes in the project properties, and those changes are quite buried/obscure. I think the warning message should go further in pointing the user in the right direction.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
