Community
Participate
Working Groups
A project can have several source dirs, but it seems impossible to attach more than one to a jar file
Good point, however if source folders are rooted in the same tree, then you may simply use this tree as the source attachment, and we should infer the proper rootpath from there. src/ src1/ src2/ In theory, using 'src/' should suffice... can you give it a try ?
I checked that if the source folders are rooted to the same tree (I use the project folder as the root), one souce zip can contain all source files for the binary jar.
Philippe, do you plan any action to support multiple source dirs or actual behavior is acceptable? I believe this is good enough, because the project root can always be used to support such a case. If a package is defined on more than one project, then I guess it ends up split into two different jars which could be mapped to the corresponding project root. Ok to close?
Multiple source attachments would require an API change. It would need to become critical in order to get more attention. Given there is a workaround, I am enclined to rather close this issue.
Would this work with those settings: /src <- goes in jar /stubs/Orbix <- goes in jar /test/src <- doesn't go in jar /functionnal_test/src <- doesn't go in jar is there a preformance issue ?
You can give it a try. According to your example: /src <- goes in jar /stubs/Orbix <- goes in jar /test/src <- doesn't go in jar /functionnal_test/src <- doesn't go in jar Put the parent of all these folders as the source attachement. src and stubs/Orbix should be detected as root paths. You won't notice the performance. This code is quite fast. Only the first level of package fragments is tested. Let me know if you see a major performance issue, but I doubt it.
Could you please confirm if your test case is properly handled? I don't see any reason why it would not. If this is the case, I will close this PR. Thanks.
Close as WORKSFORME.
