OK - great :)
On Mon, 9 Nov 2009, Júlio Cesar Bueno Cotta wrote:
Sorry by the late anwser, I didn't see your reply.
I got create the javadoc as I wnated! :D
there are some warnings, but the javadoc it's almost the same of the javadoc
created by eclipse.
2009/10/29 Scot P. Floess
So, then
Sorry by the late anwser, I didn't see your reply.
I got create the javadoc as I wnated! :D
there are some warnings, but the javadoc it's almost the same of the javadoc
created by eclipse.
2009/10/29 Scot P. Floess
>
> So, then what happens? Those files don't have Javadoc generated and no
> err
So, then what happens? Those files don't have Javadoc generated and no
error message? But isn't that the same as it not finding those source
files? Were you after the error not being emitted?
On Wed, 28 Oct 2009, Júlio Cesar Bueno Cotta wrote:
I got a way..that is not so good..but works.
I got a way..that is not so good..but works..
I used the sourcepathref="the-path" and excludepackagenames="bla.*, bla1.*,
bla2.*" so the packages of the other project are in the path but the javadoc
of them is not generated. :D
That is not the best practice..but works. :D
Thanks for the help.
2009
Well the error you are getting is because it cannot find the source file
in order to actually do the Java documentation. Are you saying that you
do not want those file documented as well? If so, how will Javadoc handle
links to classes that your classes use?
Or am I missing something?
On
Thanks man, but
Using your last tip ..also build the javadoc of the sourcepathref..and that
is a problem to me.
:(
2009/10/28 Scot P. Floess
>
> Oops - may need to adjust the sourcepathref ;)
>
>
>
>
>
>
>
> Sorry about that :)
>
>
> On Wed, 28 Oct 2009, Júlio Cesar Bueno Cotta wrote:
>
>
Oops - may need to adjust the sourcepathref ;)
Thanks again Scot, but still the same.
:(
2009/10/28 Scot P. Floess
This may be your problem in your fileset...
Change:
To:
I note you list /src vs src
If that doesn't work, try:
On Wed, 28 Oct 2009, Júlio Cesar Bueno C
Thanks again Scot, but still the same.
:(
2009/10/28 Scot P. Floess
>
> This may be your problem in your fileset...
>
> Change:
>
>
>
> To:
>
>
>
> I note you list /src vs src
>
> If that doesn't work, try:
>
>
>
>
>
>
> On Wed, 28 Oct 2009, Júlio Cesar Bueno Cotta wrote:
>
> Thanks all
This may be your problem in your fileset...
Change:
To:
I note you list /src vs src
If that doesn't work, try:
On Wed, 28 Oct 2009, Júlio Cesar Bueno Cotta wrote:
Thanks all for the answers.
but I need more help
If I have just the .jar of the other project must to work in th
Thanks all for the answers.
but I need more help
If I have just the .jar of the other project must to work in the same way?
I had try using
>
> Hee - yep that is what I meant. Sorry I was sorta rushed in my response ;)
>
>
> On Wed, 28 Oct 2009, jan
Hee - yep that is what I meant. Sorry I was sorta rushed in my response
;)
On Wed, 28 Oct 2009, jan.mate...@rzf.fin-nrw.de wrote:
Ant with 'classpath' he meant the one for the task:
Because your source files depends on these libraries you should have
defined them somewhere before:
Ant with 'classpath' he meant the one for the task:
Because your source files depends on these libraries you should have
defined them somewhere before:
then reuse that
Jan
>-Ursprüngliche Nachricht-
>Von: Scot P. Floess [mailto:sflo...@nc.rr.com]
>Gesendet: Dienstag,
12 matches
Mail list logo
