You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/09/08 09:30:23 UTC
[jira] Commented: (CAMEL-11) maven plugin to generate a report per
maven module of all the Type Converter methods available in each module
(preferably with a way to aggregate them) so folks can easily see what
conversions are possible
[ https://issues.apache.org/activemq/browse/CAMEL-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40111 ]
James Strachan commented on CAMEL-11:
-------------------------------------
Patch applied with huge thanks Hadrian!
I'm wondering; should we move this code into the camel-maven-plugin as another goal/report? Also making it a real maven report, so it gets its own page in the maven generated site; like the 'mvn camel:dot' plugin does?
http://activemq.apache.org/camel/camel-maven-plugin.html
we could use one of those Sink classes, like the DotMojo does to generate HTML nicely for the report.
BTW when I did a build, I found the converters.txt only had the stuff from camel-core in there? Am thinking, we might wanna use a similar trick to the DotMojo (maybe even combine the two) - we basically boot up the camel context in a new class loader so that all the jars are available, then generate the EIP diagrams.
Maybe we just need to do like the EmbeddedMojo does and just create a new classloader; then in that class loader we run the actual generation of the report via reflection?
> maven plugin to generate a report per maven module of all the Type Converter methods available in each module (preferably with a way to aggregate them) so folks can easily see what conversions are possible
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-11
> URL: https://issues.apache.org/activemq/browse/CAMEL-11
> Project: Apache Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: James Strachan
> Fix For: 1.2.0
>
> Attachments: camel-11.patch
>
>
> e.g. be able to look in camel-core or camel-jms or whatever and see what types from -> to etc
> e.g.
> Document -> String, Source, byte[], Stax ....
> etc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (CAMEL-11) maven plugin to generate a report per maven module of all the Type Converter methods available in each module (preferably with a way to aggregate them) so folks can easily see what conversions are possible
Posted by James Strachan <ja...@gmail.com>.
On 9/8/07, Hadrian Zbarcea <hz...@gmail.com> wrote:
> All valid points. Now that you said it, I am surprised I didn't add it
> as a new goal in the camel plugin in the first place :(.
>
> With the reporting I was not sure how it would be more convenient for
> the users to look at the results. I could picture them willing to see
> the results ordered alphabetically (like now) or per package/class and
> links to javadocs wouldn't hurt either.
>
> I'll look at all the improvements you suggested,
Great, thanks!
BTW if you take a looksie at the source of the camel:dot plugin, I
figured out how to make a plugin work in the reports - or being
callable whenever you like.
I take your point on HTML v text too - maybe we should generate all
possible output formats at the same time? e.g. the camel:dot generates
dot, png, svg and html.
--
James
-------
http://macstrac.blogspot.com/
Re: [jira] Commented: (CAMEL-11) maven plugin to generate a report
per maven module of all the Type Converter methods available in each module
(preferably with a way to aggregate them) so folks can easily see what conversions
are possible
Posted by Hadrian Zbarcea <hz...@gmail.com>.
All valid points. Now that you said it, I am surprised I didn't add it
as a new goal in the camel plugin in the first place :(.
With the reporting I was not sure how it would be more convenient for
the users to look at the results. I could picture them willing to see
the results ordered alphabetically (like now) or per package/class and
links to javadocs wouldn't hurt either.
I'll look at all the improvements you suggested,
Thanks a bunch,
Hadrian
James Strachan (JIRA) wrote:
> [ https://issues.apache.org/activemq/browse/CAMEL-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40111 ]
>
> James Strachan commented on CAMEL-11:
> -------------------------------------
>
> Patch applied with huge thanks Hadrian!
>
> I'm wondering; should we move this code into the camel-maven-plugin as another goal/report? Also making it a real maven report, so it gets its own page in the maven generated site; like the 'mvn camel:dot' plugin does?
>
> http://activemq.apache.org/camel/camel-maven-plugin.html
>
> we could use one of those Sink classes, like the DotMojo does to generate HTML nicely for the report.
>
> BTW when I did a build, I found the converters.txt only had the stuff from camel-core in there? Am thinking, we might wanna use a similar trick to the DotMojo (maybe even combine the two) - we basically boot up the camel context in a new class loader so that all the jars are available, then generate the EIP diagrams.
>
> Maybe we just need to do like the EmbeddedMojo does and just create a new classloader; then in that class loader we run the actual generation of the report via reflection?
>
>
>
>
>
>
>> maven plugin to generate a report per maven module of all the Type Converter methods available in each module (preferably with a way to aggregate them) so folks can easily see what conversions are possible
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Key: CAMEL-11
>> URL: https://issues.apache.org/activemq/browse/CAMEL-11
>> Project: Apache Camel
>> Issue Type: New Feature
>> Components: tooling
>> Reporter: James Strachan
>> Fix For: 1.2.0
>>
>> Attachments: camel-11.patch
>>
>>
>> e.g. be able to look in camel-core or camel-jms or whatever and see what types from -> to etc
>> e.g.
>> Document -> String, Source, byte[], Stax ....
>> etc
>>
>
>