Uuups...
rather late :-(, anyway thanks for your help, but,
I just committed the first release of a custom plugin doing our jsdocs.
This had the advantage that I could leverage our structures regarding
assembly file positions, order of files to be processed, etc... If you
had written this mail
Hi
I'll take a look at this one. I don't think it could be hard to add some
goals for the report and jar generation. I'll try it and send a release vote
(beta) for this artifacts soon (this includes a snapshot dependency over
myfaces core, so we need to release this before the quick fix release).
Jakob Korherr jakob.korherr at gmail.com writes:
Hi,
IMO we can put this stuff into myfaces-builder-plugin (maybe re-use
some code from already existing open source plugins).
Hi,
I'm the maintainer of http://code.google.com/p/jsdoctk-plugin/
If it helps at all, I might be able to work
Ok guys after working until midnight yesterday and a few hours of work
today I have a preliminary version of our docs online
http://people.apache.org/~werpu/jsdoc/
(Note I only annotated classes which are in production as well, so no
ext classes and no debugging classes for now.
So far jsdoc
Hi,
IMO we can put this stuff into myfaces-builder-plugin (maybe re-use
some code from already existing open source plugins).
Furthermore, if packaging is a problem, we can use the assembly-plugin
to generate a jar file and attach it as a maven-artifact to the build
lifecycle!
Regards,
Jakob
Actually I am working on the impl classes so far it looks like I can
pull it off the _Runtime.js can definitely be documented via jsdoc.
The other classes which are more OO probably also can be mapped into our
jsdocs.
Am 25.07.11 15:35, schrieb Jakob Korherr:
Very nice. Great job, Werner!
Ok I have basically all patterns working, please revisit the link, you
can see now the api, the runtime class (basically a namespace with a set
of functions)
and the _Lang.js class, a singleton delegate which delegates the namespace.
The normal classes now should be no problem as well since
Hi Werner
Does this strategy generates a .jar?
regards,
Leonardo Uribe
2011/7/25 Werner Punz werner.p...@gmail.com:
Ok I have basically all patterns working, please revisit the link, you can
see now the api, the runtime class (basically a namespace with a set of
functions)
and the _Lang.js
Hi Leo no just the plain html docs.
I have to check if we can generate a jar out of it, if not we probably
have to jar the stuff ourselves.
Werner
Am 25.07.11 18:20, schrieb Leonardo Uribe:
Hi Werner
Does this strategy generates a .jar?
regards,
Leonardo Uribe
2011/7/25 Werner
Hi Werner
Yes, I was expecting that. The problem is how to generate an artifact
that should be attached to the pom.xml, so it is deployed on maven
repo when is generated, without write a custom plugin.
regards,
Leonardo
2011/7/25 Werner Punz werner.p...@gmail.com:
Hi Leo no just the plain
I only can guess here since I dont know if jsdoc can generate jars, but
my assumption is that we have to roll our own custom plugin.
This is still less work than to write our own javascript doc parser
or to adjust an existing codebase.
Werner
Am 25.07.11 18:26, schrieb Leonardo Uribe:
Hi
Hello Werner,
is the jsdoc produced by a maven plugin? Or is the output somewhere in
the target directory? If yes, it should be not a problem to use the
jar plugin to package the js docs.
Regards
Bernd
On Mon, Jul 25, 2011 at 7:00 PM, Werner Punz werner.p...@gmail.com wrote:
I only can guess
Hi the jsdoc is just more or less a command line tool (actually a jar)
I have yet to investigate the links to maven, Leo did some work there.
I am personally not very much in favor of running our own tool as long
as we can get away with jsdoc. This is another codebase to maintain
which I want
Hi
The problem to use jsdoc is there is no maven plugin that executes it.
For now we only have the ant task solution. Things are getting messy
when you try to setup other plugins like maven jar plugin, because
there is no way to define the ordering execution of the plugins
without create a custom
http://code.google.com/p/jsdoctk-plugin/
Am 26.07.11 00:29, schrieb Leonardo Uribe:
Hi
The problem to use jsdoc is there is no maven plugin that executes it.
For now we only have the ant task solution. Things are getting messy
when you try to setup other plugins like maven jar plugin, because
http://dev.abiss.gr/mvn-jstools/index.html
and a bunch of others :-)
Am 26.07.11 00:57, schrieb Werner Punz:
http://code.google.com/p/jsdoctk-plugin/
Am 26.07.11 00:29, schrieb Leonardo Uribe:
Hi
The problem to use jsdoc is there is no maven plugin that executes it.
For now we only have
Hi
The problem about use those plugins is they are not available on
apache maven repo, so we had to link to some unknown repo. I don't
know if this could be problematic, maybe in practice we have to
repackage some code there and put as a maven plugin, knowing that the
code is maintained somewhere
Improve the javascript docs in the function headers
---
Key: MYFACES-2212
URL: https://issues.apache.org/jira/browse/MYFACES-2212
Project: MyFaces Core
Issue Type: Sub-task
18 matches
Mail list logo
