Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 82422

Summary: Automatically update @version Javadoc tags on resource modification
Product: [Eclipse Project] JDT Reporter: David Gates <gatesda>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 Keywords: helpwanted
Version: 3.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

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.