You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Martin Reurings <ma...@windgazer.nl> on 2011/09/01 01:27:33 UTC
Re: javascript docs
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 together with you to make
sure that jsdoctk-plugin repo gets synced to the maven repository?
My releases have been stable for over a year now and I'm making use
of maven deploy, updating my version numbers with grace and all
that jazz ;) Once upon a time I looked into getting into a genuine
repository but most of them required me to run my own stable
repository anyways, which sort of defeated my purpose at the time.
For now I'm using wagon-svn to deploy to the subversion hosted
environment on google-code, but I wouldn't mind deploying to
apache if it's not too much of an effort...
Anyways, I regularly check if my projects are worth keeping alive
and where possible like to offer my assistance in making my efforts
more usable...
>
> 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!
If there's any info/detail you need on the existing plugin, it should be
fairly painless to reuse within any other java-environment, although
to make it truly reusable some patching might be required...
> Regards,
> Jakob
>
Cheers,
Martin
Re: javascript docs
Posted by Leonardo Uribe <lu...@gmail.com>.
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).
regards,
Leonardo Uribe
2011/9/1 Werner Punz <we...@gmail.com>
> 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 two weeks ago I probably would have gone another way.
> Maybe I will come back to your proposal if we decide to drop our custom
> plugin.
>
> Either way you can now generate the jsdocs rather basically by
> mvn clean install -PgenerateJsDoc
>
> make sure you have the latest version of the myfaces build plugins checked
> out and committed.
>
> The final files then can be found under api/target/jsdoc/
> For now I do no packaging just the pure jsdoc generation.
>
> Werner
>
>
> Am 01.09.11 01:27, schrieb Martin Reurings:
>
> 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/<http://code.google.com/p/jsdoctk-plugin/>
>> If it helps at all, I might be able to work together with you to make
>> sure that jsdoctk-plugin repo gets synced to the maven repository?
>>
>> My releases have been stable for over a year now and I'm making use
>> of maven deploy, updating my version numbers with grace and all
>> that jazz ;) Once upon a time I looked into getting into a genuine
>> repository but most of them required me to run my own stable
>> repository anyways, which sort of defeated my purpose at the time.
>> For now I'm using wagon-svn to deploy to the subversion hosted
>> environment on google-code, but I wouldn't mind deploying to
>> apache if it's not too much of an effort...
>>
>> Anyways, I regularly check if my projects are worth keeping alive
>> and where possible like to offer my assistance in making my efforts
>> more usable...
>>
>>
>>> 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!
>>>
>>
>> If there's any info/detail you need on the existing plugin, it should be
>> fairly painless to reuse within any other java-environment, although
>> to make it truly reusable some patching might be required...
>>
>>
>> Regards,
>>> Jakob
>>>
>>>
>> Cheers,
>>
>> Martin
>>
>>
>>
>>
>>
>
>
Re: javascript docs
Posted by Werner Punz <we...@gmail.com>.
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 two weeks ago I probably would have gone another
way. Maybe I will come back to your proposal if we decide to drop our
custom plugin.
Either way you can now generate the jsdocs rather basically by
mvn clean install -PgenerateJsDoc
make sure you have the latest version of the myfaces build plugins
checked out and committed.
The final files then can be found under api/target/jsdoc/
For now I do no packaging just the pure jsdoc generation.
Werner
Am 01.09.11 01:27, schrieb Martin Reurings:
> 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 together with you to make
> sure that jsdoctk-plugin repo gets synced to the maven repository?
>
> My releases have been stable for over a year now and I'm making use
> of maven deploy, updating my version numbers with grace and all
> that jazz ;) Once upon a time I looked into getting into a genuine
> repository but most of them required me to run my own stable
> repository anyways, which sort of defeated my purpose at the time.
> For now I'm using wagon-svn to deploy to the subversion hosted
> environment on google-code, but I wouldn't mind deploying to
> apache if it's not too much of an effort...
>
> Anyways, I regularly check if my projects are worth keeping alive
> and where possible like to offer my assistance in making my efforts
> more usable...
>
>>
>> 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!
>
> If there's any info/detail you need on the existing plugin, it should be
> fairly painless to reuse within any other java-environment, although
> to make it truly reusable some patching might be required...
>
>
>> Regards,
>> Jakob
>>
>
> Cheers,
>
> Martin
>
>
>
>