Bug 232691 - Support Ant Build File Name Patterns
Summary: Support Ant Build File Name Patterns
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-18 05:48 EDT by Michael Rumpf CLA
Modified: 2019-09-06 16:12 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rumpf CLA 2008-05-18 05:48:31 EDT
In the Eclipse Ant preferences dialog you can enter only single files and "build.xml" is pre-configured.

in our project we have a many build different files implementing different concerns:
build-bootstrap.xml,
build-report.xml
build.xml (imports the other files)
  build-db.xml,
  build-doc.xml,
  build-ear.xml,
  build-ejb.xml,
  build-test.xml,
  build-util.xml,
  build-web.xml,

It would be very easy for us to add new build files if the "Names:" input field allows a pattern:

   build-*.xml

This would identify all our build files as Ant Files.
Comment 1 Michael Rumpf CLA 2008-05-18 06:24:37 EDT
And variable support would also be great.

The build files I mentioned above are maintained by a central instance. Each developer can have his own targets and therefore we provide a developer specific file:

build-michael.rumpf.xml

In the Ant script we import it like this:

<import file="config/build-${user.name}.xml"/>

Therefore the "Names:" input field could also support system variables like this

build-${user.name}.xml

Comment 2 Eclipse Webmaster CLA 2019-09-06 16:12:11 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.