4 Jul 2013 7:33 AM #251
JSDuck 5.0 beta 5 released
Some more serious problems did pop up with the previous beta caused by problematic Unicode handling in RKelly. So I patched up RKelly and did another release with a bunch of other little fixes.
4 Jul 2013 12:59 PM #252
In shell script (without any ant tasks), you can use $0 - $x for arguments. Also $@ works too. But you need to have Bash interpreter.
That mean shell script must start with:
Depends on host OS, starting line:
maybe will not work, but with bash will work for sure. Of course you need to check where is located your bash executable.
All bash scripts (shell scripts) you can use that in Jenkins/Hudson post-build-tasks. With ant you can build project, but as post build task you can use pure shell scripting to invoke jsduck. Any shell script can be used, and I am sure that env vars are passed to jenkins but as user's env jenkins running.
For example my Jenkins running as unix user 'build' and if that user have exported env vars then jenkins have them too.
Otherwise you can add exports and declare all env vars in shell script and everything will work same as it working when you run manually jsduck commands in command line.
18 Jul 2013 5:32 AM #253
JSDuck 5.0 Final released
As announced on SenchaCon, JSDuck 5 is now finally out of beta. The major changes since JSDuck 4 include:
- New custom tags system
- New flat export format
- Improved warnings system
- New tags @localdoc @fires
For more info, read the detailed overview of the changes..
2 Aug 2013 12:56 AM #254
JSDuck 5.0.1 released
Thanks to everybody who has tried out the new JSDuck 5 and reported bugs. The more urgent ones are now fixed with this patch-release, plus a bunch of old bugs.
For more see the changelog..
11 Aug 2013 11:09 PM #255
6 Sep 2013 3:33 AM #256
JSDuck 5.2.0 released
This version brings an improved way of toggling warnings for missing documentation.
Previously there were three warnings types: no_doc, no_doc_member, no_doc_param. This version deprecated them all in favor of a new nodoc warning type, which accepts parameters in the form of:
[+/-] nodoc(<TYPE>, <VISIBILITY>)
Other little changes listed in the changelog..
11 Sep 2013 11:22 PM #257
i have error on cmd while setting up the jsduck
i am using jsduck 5.2.0 ,
ruby version is 2.0.0
Temporarily enhancing PATH to include DevKit...Building native extensions. This could take a while... ERROR: Error installing jsduck: ERROR: Failed to build gem native extension.
12 Sep 2013 12:12 AM #258
Looks like it fails when compiling a native extension. So it's likely problem with the rdiscount dependency not with JSDuck itself. Try installing rdiscount separately:
gem install rdiscount
12 Sep 2013 1:27 AM #259
13 Sep 2013 1:02 PM #260
Using JSDuck for the first time. It is fantastic. My only issue is the extjs-build directory in the output dir. It gets blown away every time docs are regenerated. Is there a way to specify a path in the jsduck.config instead of putting the extjs-build directory in there? I see --extjs-path in the --help, but it looks like this is the path that the documentation uses.