This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 56559 - Javadoc -overview parameter deserves its oen UI field
Summary: Javadoc -overview parameter deserves its oen UI field
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-16 17:08 UTC by levmatta
Modified: 2009-11-02 11:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description levmatta 2005-03-16 17:08:13 UTC
Javadoc addicional options is designed to allow such things as defining the
overview file parameter. It is pretty broken for this and many other
funcionalities because it can not access important properties.

It is extremelly important to define the adicional parameters using Ant
properties. The correct way to define the overview parameter is:

${src.dir}\overview.html

The only way it works today is:

${basedir)\src\overview.html //This is a BUG

I have explored somewhat and found that src.dir is in project.properties and is
loaded after javadoc.additionalparam which is in private.properties. My overview
property is a property of the project and not at all a private one.

PS: What about giving overview a first class configuration
Comment 1 Jan Pokorsky 2005-03-16 17:43:27 UTC
wrong component, reassining to java/project
Comment 2 Tomas Zezula 2005-03-21 12:36:33 UTC
Reassigning to Javadoc expert :-)
Comment 3 Petr Hrebejk 2005-03-29 10:33:17 UTC
After some investigation:

1) Yes the additional javadoc options are stored in the private.properties. It
is a question if these should be stored in the project.properties. (Perhaps not
as some of the Javadoc parameters may require absolute paths)
2) Using ANT properties in the UI. Currently possible as side efect. (Of course
not true for private.proerties) However they will be fully resolved after next
open of the project customizer. Not sure if we should add any extra support, I
would vote NO.
3) The -overview deserves its own UI field. Definitely yes. a) It should be
stored in project.properties not private. b) there is extra parameter for
overview in the ANT Javadoc task, which handles relative paths correctly. c) It
is frequently used parameter

Propose to fix this by adding extra UI field for the overview parameter and
store it in project.properties.

Jano: if you agree please just say yes and reassign to me.

Too late to put it into 4.1 thus marking as future, but definitely desirable for F.
Comment 4 jrojcek 2007-07-19 15:26:41 UTC
I agree with adding a field for -overview parameter.
Comment 5 Jan Becicka 2008-11-13 14:00:36 UTC
Will resolve later
Comment 6 Quality Engineering 2009-11-02 11:00:04 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX