Summary: | Need attribute for target tag to indicate hidden/internal target | ||
---|---|---|---|
Product: | Ant | Reporter: | Chris Janicki <apache> |
Component: | Core | Assignee: | Ant Notifications List <notifications> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 1.5.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Chris Janicki
2003-09-24 22:31:46 UTC
Actually this is a simpler defect than proper public/private attrs; the user just wants the IDE to differentiate entry points from internal ones. Chris -the <target> element has a description attribute. Once you set the description on a target, you are saying that this is public and others are private. Ant on the command line, and in some IDEs (IntelliJ for example) use presence/absence of a description as a cue for visibility in listing targets. I dont know about netbeans -I would assume it does, but if it doesnt, well, you could fix it :) Also, we do have an 'ant list targets' feature. Type "ant -projecthelp" at the command line. Yes thogh this is an overloading of the meaning of the description tag by the ide's. It seems wrong to put 2 meanings on one tag. Net beans does not hide any targets. They display all top level elements, including properties, and taskdefs, and I suspect with the advent of top level tasks (which I never use because of the access control pattern I describe in bug 22020) this will become even more messy in net beans. If someone here is active in netbeans some additional special handling of antfiles would be good. Heaven only knows if I will ever have the time to start developing for net beans too :) What the IDE's are doing is guessing. It would be nice if we could tell them so they don't have to guess :) Thanks Steve... I see your point, but I agree with Gus: I think that making the description attribute perform dual duties is not the optimal design. Private targets may still benefit from descriptions. For example, I'd hope that my IDE could turn on/off visibility of private targets for editing vs. running. When visible (e.g. during editing) I think the private task descriptions have merit, for example, it could be displayed in a status label. (At least that's the way I'd code NetBeans ;-) Regarding the -projecthelp argument, you're 100% right... thanks. But I may open a future enhancement request to deprecate that name... kinda long, and not intuitive enough (for me at least) to understand it when I was quickly looking for it. dont open an new enh req till you've looked at ant1.6, due in beta next week, OK? you may find ant -p does what you want |