Bug 295265 - Should be able to specify a name pattern to determine if a file is a build file
Summary: Should be able to specify a name pattern to determine if a file is a build file
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-16 11:24 EST by Michael Rennie CLA
Modified: 2019-09-06 15:35 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2009-11-16 11:24:21 EST 
always to I20091110-0800

FUP to bug 295192

We should have a mechanism to specify a pattern for a build file name to say that these are known build files.

For example we have checks that anything *.xml is a build file, but we should make this customizable to allow something like *.ant as well.
Comment 1 Michael Rennie CLA 2009-11-16 11:29:01 EST 
It would be slick if we could just leverage the information from content types, which shows build.xml, *.xml, *.ant, *.ent and *.macrodef as being build files that the Ant editor should open.

I would say that the rest of tooling should also treat these patterns as acceptable build files for launching, etc.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:35:56 EDT 
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.