Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of sethfromaustria@gmail.com
 designates 209.85.220.181 as permitted sender)
MIME-Version: 1.0
Sender: sethfromaustria@gmail.com
In-Reply-To: <j23a5u$i5g$1@dough.gmane.org>
References: <j23a5u$i5g$1@dough.gmane.org>
Date: Fri, 12 Aug 2011 15:43:13 +0200
Message-ID: 
 <CAP9Xh4SP1bYH4Nxsh8S343piFnSEDLtsYejDH4jbH269baPeSQ@mail.gmail.com>
Subject: Re: jsdocs + build tools
From: Jakob Korherr <jakob.korherr@gmail.com>
To: MyFaces Development <dev@myfaces.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi Werner,

Great!!

Frankly, I'd prefer a).

Regards,
Jakob

2011/8/12 Werner Punz <werner.punz@gmail.com>:
> Hi Everyone
>
> Status update: I have a preliminary maven plugin up and running which
> triggers jsdoc upon our javascript assembly.xml information.
> I will refine the plugin and once good enough I will merge it as preliminary
> version into our build tools in a few weeks.
>
> I started basically from scratch because I wanted it to use our assembly
> information which we also use for compression.
>
> The question now is more along the lines since I start the refinement phase.
>
> What do we want to do with the plugin. There are several options:
>
> a) provide a separate jsdoc goal which generates the jsdocs
>
> or
>
> b) generate the jsdocs in the same phase as our javadocs and bundle the
> generated jsdocs along the javadocs.
>
> Werner
>
>
>


-- 
Jakob Korherr

blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at