Bug 39164 - antlr task doesn't create output directory
Summary: antlr task doesn't create output directory
Alias: None
Product: Ant
Classification: Unclassified
Component: Optional Tasks (show other bugs)
Version: 1.6.5
Hardware: Other other
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Ant Notifications List
Keywords: PatchAvailable
Depends on:
Reported: 2006-03-31 08:55 UTC by Nikolay Metchev
Modified: 2009-07-31 06:37 UTC (History)
0 users

patch to create output directory (959 bytes, patch)
2006-04-12 09:45 UTC, Nikolay Metchev
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Metchev 2006-03-31 08:55:40 UTC
It would be nice if the antlr task created the output directory automatically or
had an option allowing you to do so. At the moment if the output directory
doesn't exist you get a build failure which is a shame.
Comment 1 Matt Benson 2006-04-11 21:31:33 UTC
e.g., <javac> doesn't do this.  Why should the (barely-supported) ANTLR task?
Comment 2 Nikolay Metchev 2006-04-11 22:52:25 UTC
javac is very different.  The packages themselves do get created by the java 
Antlr on the other hand doesen't understand packages even though it is most 
commonly used to create files in a package. That is why the output directory 
has to be specified all the way including the package.
Antlr is either supported or it isn't? If it is supported I don't see why it 
would be too much to ask to enhance it a little.
Comment 3 Jeffrey E. Care 2006-04-11 22:58:13 UTC
Did you attach a patch with your desired enhancement?
Comment 4 Nikolay Metchev 2006-04-12 09:45:34 UTC
Created attachment 18076 [details]
patch to create output directory
Comment 5 Nikolay Metchev 2006-04-12 09:46:14 UTC
I have now attached a patch
Comment 6 Matt Benson 2006-04-12 14:53:14 UTC
In all honesty, I looked into this when the issue was first raised, but found
that this task has a testcase that explicitly tests that output dirs are not
created.  I will reopen and if I or some other committer takes a notion to make
the change _and_ augment the junit test, who knows?