So, you're running the commandline version or the ant task?
In both, there is a way to define multiple javadoc urls
like the example @
http://tacos.sourceforge.net/tacos4.1/tapdoc/tapdoc/ant.html
On Feb 11, 2008 5:40 PM, Tomek [EMAIL PROTECTED] wrote:
Hi,
a question again, di I understand it
Hi,
a question again, di I understand it correctly, that I need to write
tapestry-javadom.xml manually to get correct links to my javadoc files?
Thanks
Tomek
Tomek Sniadach schrieb:
Thanks Igor,
unfortunately I'm not using maven :( and this configuration doesn't
support code sample.
Hi,
a question again, di I understand it correctly, that I need to write
tapestry-javadom.xml manually to get correct links to my javadoc files?
Thanks
Tomek
Tomek Sniadach schrieb:
Thanks Igor,
unfortunately I'm not using maven :( and this configuration doesn't
support code sample.
If you want to generate it via maven you just need to add something like:
reporting
outputDirectory../outputDirectory
plugins
plugin
groupIdcom.erinors.tapestry/groupId
Thanks Igor,
unfortunately I'm not using maven :( and this configuration doesn't
support code sample.
Tomek
Igor Drobiazko schrieb:
If you want to generate it via maven you just need to add something like:
reporting
outputDirectory../outputDirectory
plugins
yes, but I have this message
/conf/tapdoc/build.xml:12: org.apache.hivemind.ApplicationRuntimeException:
Could not parse specification
classpath:/org/jfly/web/components/JFly.library
but src/main/java/org/jfly/web/components/JFly.library is present
the output message is:
this is a snippet of my pom:
executions
execution
idtapdoc/id
phasesite/phase
configuration
tasks
ant
antfile=src/main/conf/tapdoc/build.xml
I think it's not...
If I remember well then when the components of a library are enumerated,
only those components are listed which have an explicit component-type
/ declaration in the .library file. Pure Java components are not, so
they won't be included in the documentation by default. Pure
OK, I would.
andyhot wrote:
thx Norbert!
Just saw that we're not currently generating javadocs for contib (why???) at
http://tapestry.apache.org/tapestry4.1/tapestry-contrib/apidocs/index.html
but I guess you could already include this link in
TapDocTask.java (for the external javadoc
thx Norbert!
Just saw that we're not currently generating javadocs for contib (why???) at
http://tapestry.apache.org/tapestry4.1/tapestry-contrib/apidocs/index.html
but I guess you could already include this link in
TapDocTask.java (for the external javadoc references)
Norbert Sándor wrote:
Henri Dupre wrote:
Oh this looks very nice!
Does tapdoc take into account also components with annotations that
have no
.jwc?
It does... I think it uses a custom doclet to extract javadocs from
those 'annotation-only'
components
On 8/15/06, Norbert Sándor [EMAIL PROTECTED] wrote:
Hello,
Oh this looks very nice!
Does tapdoc take into account also components with annotations that have no
.jwc?
On 8/15/06, Norbert Sándor [EMAIL PROTECTED] wrote:
Hello,
I have converted Tapdoc to Maven2, so it now has a standard website at:
http://www.erinors.com/developer/project/tapdoc/
The
Hey, thanks. looks great. is there some docs on the ant plugin at all? i
want to use it to generate docs to include with the maven site.
On Tue, 2006-08-15 at 15:56 +0200, Norbert Sándor wrote:
Hello,
I have converted Tapdoc to Maven2, so it now has a standard website at:
Download the demo project, its pom.xml contains a sample configuration
of the ant task.
Regards,
Norbi
Dan Adams wrote:
Hey, thanks. looks great. is there some docs on the ant plugin at all? i
want to use it to generate docs to include with the maven site.
On Tue, 2006-08-15 at 15:56 +0200,
14 matches
Mail list logo
