Community
Participate
Working Groups
I'm opening this request on behalf of customer of an adopter product. The request is to have an Ant task that will generate a jar file but take into consideration linked source folders. Currently, the Apache <jar> task only handles one source directory.
Hi, is there any status on this request?
No work has been allocated for this request. Could they not just use fileset or dirset and copy what they need to one dir then Jar it?
The basic problem is that the Ant task does not understand Eclipse linked folders, probably because they are entirely virtual. A number of Ant task specifications are built into the Eclipse platform. For example, the various Export operations all delegate to built-in Ant tasks. Consequently, there is no practical way to implement a work around. When, for example, exporting a jar, fragment, or feature where the underlying project includes a linked folder (in this case the "src" folder), the export will fail with D:\EclipseWorkSpace35\net.certiv.specdsl\build.xml:190: srcdir "D:\EclipseWorkSpace35\net.certiv.specdsl\src" does not exist! at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:871) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) While it may be possible to completely recreate a jar export ant task, re-engineering the feature export is not practical. Is there agreement that this is a bug that should be fixed? Is it even possible for the Ant task to recognize the presence of an Eclipse linked folder?
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.
