jarpacker packages javadoc html files instead of class files

I'm not sure about how to reproduce it, but i'll try to explain the

situation. I have a tree of my classes com.* and another tree of web

applications. For each of the web applications i have a project in which it

gets mounted as web module and so on. Inside there WEB-INF/lib folders are

jar packagers which include some of the classes that are needed by each web

module. All works fine, BUT i have one project (and to be more funny, it is

my documentation project), within which i cannot compile the jars

correctly: the jar packager puts the javadoc html files of the classes in

the source tree into the jar rather than the class files. Only thing i

changed in the configuration was setting a different target destination for

the javadoc and some other javadoc flags, but why should this influence my

jar packager? What's more, if i kill the packager and make a new one, all

works as it should until i reload the project. It is not difficult to avoid

the problem, but i was just curious to know what is happening.

Regards, Jens Stutte

[1150 byte] By [JensStutte] at [2007-11-25 16:50:56]
# 1

Forgot to mention: this happens with Forte 4, updated with some netbeans

modules.

JensStutte@qu

idinfo.itTo:nbusers@netbeans.org

cc:

02/08/2002Subject:jarpacker packages javadoc html files instead of

15.37class files

Please

respond to

nbusers

I'm not sure about how to reproduce it, but i'll try to explain the

situation. I have a tree of my classes com.* and another tree of web

applications. For each of the web applications i have a project in which it

gets mounted as web module and so on. Inside there WEB-INF/lib folders are

jar packagers which include some of the classes that are needed by each web

module. All works fine, BUT i have one project (and to be more funny, it is

my documentation project), within which i cannot compile the jars

correctly: the jar packager puts the javadoc html files of the classes in

the source tree into the jar rather than the class files. Only thing i

changed in the configuration was setting a different target destination for

the javadoc and some other javadoc flags, but why should this influence my

jar packager? What's more, if i kill the packager and make a new one, all

works as it should until i reload the project. It is not difficult to avoid

the problem, but i was just curious to know what is happening.

Regards, Jens Stutte

JensStutte at 2007-7-2 23:49:44 > top of Java-index,Archived Forums,Sun ONE Studio 4...