[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-ant-dev] ant editor enhancements -- new bug ids
|
Darins,
I have started work on the formatting action but would be happy to pass off
a patch of work-to-date if someone else is particularly interested in taking
it up.
I will make the templating a personal priority. I want to see this in 3.0
and will do my best to put in the work to make it happen. The same sort of
issue exists here as with refactoring--good code already exists in JDT. Do
we refactor JDT to expose this functionality or get it working in ant first?
Sorry for presumptive use of bugzilla--thanks for the guidelines.
Let's talk more about what is going into M7. I'd like to help however I can
with the time I have.
John-Mason Shackelford
Software Developer
Pearson Educational Measurement - eMeasurement Group
2510 North Dodge St.
Iowa City, IA 52245
ph. 319-354-9200x6214
john-mason.shackelford@xxxxxxxxxxx
http://etest.ncspearson.com
-----Original Message-----
From: Darin Swanson [mailto:Darin_Swanson@xxxxxxxxxx]
Sent: Monday, January 05, 2004 5:25 PM
To: platform-ant-dev@xxxxxxxxxxx
Subject: Re: [platform-ant-dev] ant editor enhancements -- new bug ids
I neglected to check this mailing list over the Christmas break so sorry for
the delay in a public response.
We appreciate you interest in helping us out. We will be working on the Ant
plan for M7 (Feb 13th, 2004) in the next couple of days.
For M7, it is likely we will want to work on the formatting action.
Better support for the Ant 1.6 enhancements will likely be addressed in M7
as well.
The code generation / template stuff is not likely to happen for 3.0 unless
you do most of the work in this area (limited resources :-) )
Improvements in code assist we could investigate.
The other bugs seem relatively small enhancements that could happen (and
some you have submitted patches for already, thanks).
Some general guidelines for Ant bug reports:
we generally leave bug milestone assignment to the committers.
no need to preface with [ant editor]
assigning to yourself is fine if you feel you can finish a bug
report in a relatively short period of time (say before the next integration
build).
Otherwise indicate that you are willing to help out on the bug /
enhancement and the indicate the approximate amount of time/support you can
allocate to that bug report and or when you feel you could implement
the fix/feature. This can be done within the bug report comments and will
greatly help us out in our planning for the Ant component
We look forward to continuing to work with you
Darins
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
