search

mryozo16 / jsdoc-toolkit

Automatically exported from code.google.com/p/jsdoc-toolkit
0 stars 0 forks source link

Need a way to define external plugins #268

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I'd like to use an svn:external for jsdoc-toolkit, but that means the plugins 
and templates can't be 
located in the jsdoc-toolkit folder. Templates are no problem, but plugins are 
another matter.

Original issue reported on code.google.com by jeff%met...@gtempaccount.com on 23 Nov 2009 at 12:44

GoogleCodeExporter commented 8 years ago 
Attached find a diff for main.js that adds a plugins option. The folder will be 
loaded just like the regular plugins 
folder.

Original comment by jeff%met...@gtempaccount.com on 23 Nov 2009 at 12:45

Attachments:

GoogleCodeExporter commented 8 years ago 
This patch is incomplete, adding a new commandline option requires a short and 
long name and this must listed 
in the help message. -p is already taken for "private". -t is for templates, 
maybe -g for plugins?

Original comment by micmath on 23 Nov 2009 at 9:49

GoogleCodeExporter commented 8 years ago 
I've updated the patch to include the command line options. I only ever run the 
tool using the -c option, so I 
didn't notice this issue. I also fixed the code that loads the plugins. It only 
worked when the plugin folder was 
relative to SYS.pwd (whatever that is).

Original comment by jeff%met...@gtempaccount.com on 24 Nov 2009 at 2:31

Attachments:

GoogleCodeExporter commented 8 years ago 
Committed revision 846. Thank you for contributing!

Original comment by micmath on 3 Jul 2010 at 7:55