Bug 82422 - Automatically update @version Javadoc tags on resource modification
Summary: Automatically update @version Javadoc tags on resource modification
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-01-08 12:26 EST by David Gates CLA
Modified: 2005-02-16 09:18 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Gates CLA 2005-01-08 12:26:56 EST
 
Comment 1 Frederic Fusier CLA 2005-02-15 11:34:35 EST
Seems to be a JDT/UI feature
Comment 2 Martin Aeschlimann CLA 2005-02-15 11:43:26 EST
What version would that be, just an increment? On any resource modification.

Comment 3 David Gates CLA 2005-02-16 06:30:55 EST
Perhaps you could add automatic updating for the current whatever variables
(e.g. current time, current file, current package) in the code templates?  That
would handle date-time versioning and keep javadoc correct across refactorings.
 It would be a separate RFE, but might do enough to cover this one too.

With the above, you could make a build count variable available to the code
templates, which would handle the incremented number versioning style.
Comment 4 Martin Aeschlimann CLA 2005-02-16 09:18:41 EST
I don't think we should go into this. There has to be some standard for that
otherwise we do something that most other users don't like.
I guess version numbers should also be in sync with version numbers from your
repository.

This feature is a good idea for an extra, additional plugin, that could be
pioneered by somebody in the comunity.