Bug 46053

Summary:	Generation of Project API Documentation stopped when I place my classes in there own namespace
Product:	[Developer tools] kdevplatform	Reporter:	dragon
Component:	classbrowser	Assignee:	KDevelop-Devel List <kdevelop-devel>
Status:	RESOLVED INTENTIONAL
Severity:	normal
Priority:	NOR
Version:	git master
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description dragon 2002-08-02 06:16:48 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.1 (using KDE 3.0.0 )
Severity:          normal
Installed from:    Red Hat Linux 7.2.93
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)
OS:                Linux (i686) release 2.4.18-5
OS/Compiler notes: 

I decided to place all classes that I write into there own namespace. As soon as I did that and my hard work in writing documentation nolonger appears in the Projects API-DOC




(Submitted via bugs.kde.org)
(Called from KBugReport dialog)

Comment 1 Amilcar do Carmo Lucas 2003-03-20 20:23:52 UTC

This is/was probably a Doxygen bug. This is KDevelop independent. 
But if you ment ClassView instead of API-DOC, then you're probably right.

Comment 2 Amilcar do Carmo Lucas 2003-06-24 09:07:43 UTC

I asked for more details 3 months ago. You didn't answer :( 
I can not reproduce/understand the bug. Closing. And besides that: 
 
KDevelop 2.x is no longer under development. 
 
You are strongly advised to update to the latest CVS version of KDevelop3 code 
name gideon, take a look at: 
http://www.kdevelop.org/index.html?filename=branches_compiling.html 
for all the details you need. If you find a problem or need help please send a 
mail to the mailing list: 
http://www.kdevelop.org/index.html?filename=mailinglist.html 
or drop us a line at the channel #kdevelop on the server irc.kde.org using 
ksirc, for example. 
Please use the CVS version and compile it yourself because that way you can 
easily patch it if a bug is found. 
 
KDevelop3 can import KDevelop2 projects. To do so, run the kdevprj2kdevelop 
script. 
You can have and run KDevelop3 and KDevelop2 at the same time on the same 
computer without any problems. 
So migrating is a breeze. :) 
 
Closing. Please feel free to reopen if the bug presists in KDevelop3 
 
P.S. : The KDevelop team closed 390 bugs since the release of the last 
KDevelop2.x

Comment 3 Aleix Pol 2013-03-31 01:31:03 UTC

moving to kdevplatform's classbrowser