Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, I've just released apt-maven-plugin 1.0-alpha-2: http://repo1.maven.org/maven2/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2/ The documentation has been brought up-to-date: http://mojo.codehaus.org/apt-maven-plugin/ Feel free to move any apt-related issues from Tobago's JIRA to Mojo's: http://jira.codehaus.org/browse/MOJO/component/13192 I hope this allows you to migrate successfully to this plugin, let me know if you have any problems. Probably best to use the Mojo JIRA or [EMAIL PROTECTED] in future since I'll be unsubscribing from this list (too many mailing lists!). Thanks for all your feedback, Mark On 21/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Hi Bernd, Cool! I can start a vote to release 1.0-alpha-2 now that it's working fine for you guys and myself. I'll let you know how it goes. Cheers, Mark On 18/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build. When you will release the 1.0-alpha-2-SNAPSHOT version? Regards Bernd Bernd Bohmann schrieb: Hello Mark, I changed a local tobago version to use the apt-maven-plugin. I think everything is fine with the new plugin. In a few days I will commit the changed build to trunk. Regard Bernd Mark Hobson schrieb: Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
P.S. I meant to say that the only major change since 1.0-alpha-2-SNAPSHOT is that I've renamed the goals to align with apt itself: * apt:execute - apt:process * apt:test-execute - apt:test-process Cheers, Mark On 25/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Hi Bernd, I've just released apt-maven-plugin 1.0-alpha-2: http://repo1.maven.org/maven2/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2/ The documentation has been brought up-to-date: http://mojo.codehaus.org/apt-maven-plugin/ Feel free to move any apt-related issues from Tobago's JIRA to Mojo's: http://jira.codehaus.org/browse/MOJO/component/13192 I hope this allows you to migrate successfully to this plugin, let me know if you have any problems. Probably best to use the Mojo JIRA or [EMAIL PROTECTED] in future since I'll be unsubscribing from this list (too many mailing lists!). Thanks for all your feedback, Mark On 21/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Hi Bernd, Cool! I can start a vote to release 1.0-alpha-2 now that it's working fine for you guys and myself. I'll let you know how it goes. Cheers, Mark On 18/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build. When you will release the 1.0-alpha-2-SNAPSHOT version? Regards Bernd Bernd Bohmann schrieb: Hello Mark, I changed a local tobago version to use the apt-maven-plugin. I think everything is fine with the new plugin. In a few days I will commit the changed build to trunk. Regard Bernd Mark Hobson schrieb: Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, Cool! I can start a vote to release 1.0-alpha-2 now that it's working fine for you guys and myself. I'll let you know how it goes. Cheers, Mark On 18/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build. When you will release the 1.0-alpha-2-SNAPSHOT version? Regards Bernd Bernd Bohmann schrieb: Hello Mark, I changed a local tobago version to use the apt-maven-plugin. I think everything is fine with the new plugin. In a few days I will commit the changed build to trunk. Regard Bernd Mark Hobson schrieb: Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hello Mark, I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build. When you will release the 1.0-alpha-2-SNAPSHOT version? Regards Bernd Bernd Bohmann schrieb: Hello Mark, I changed a local tobago version to use the apt-maven-plugin. I think everything is fine with the new plugin. In a few days I will commit the changed build to trunk. Regard Bernd Mark Hobson schrieb: Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hello Mark, I changed a local tobago version to use the apt-maven-plugin. I think everything is fine with the new plugin. In a few days I will commit the changed build to trunk. Regard Bernd Mark Hobson schrieb: Just to let you know, the Codehaus apt-maven-plugin has graduated out of the sandbox and changed version. It is now located at: http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/ And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here: http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/ Did you have a chance to try the plugin with the Tobago build over ApacheCon? I'd be interested in any feedback before 1.0-alpha-2 is released. Cheers, Mark On 04/04/2008, Mark Hobson [EMAIL PROTECTED] wrote: Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, On 03/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: http://svn.apache.org/repos/asf/myfaces/tobago/trunk/sandbox/pom.xml http://svn.apache.org/repos/asf/myfaces/tobago/trunk/extension/facelets/pom.xml http://svn.apache.org/repos/asf/myfaces/tobago/trunk/extension/tobago-taglib-extension/pom.xml Okay, I won't argue with these pom.xmls :) I've kept this parameter as 'additionalSourceRoots'. Sorry, we are using this parameter. I think the apt plugin generates resources and with the parameter targetpath I can tell the resource plugin where the resouces should be copied. This parameter is used for generating the tlds in tobago. Without this parameter i need an extra resources section and I don't like to include the META-INF in the target. No worries, I've reinstated this parameter. No, but as far as I know some guys are using a one to many mapping. They are using the force parameter. An apt factory that creates multiple target files for each source file? Interesting, this may be supported by specifying multiple outputFileEnding parameters. Feel free to open a MOJO issue if this isn't supported. Okay, I think I'm done with the plugin now, aside from updating the documentation which I'll try to find time to do later. If you could give it a spin in Tobago then I'd be interested in how you get on: http://svn.codehaus.org/mojo/trunk/sandbox/apt-maven-plugin/ Let me know if you have any issues. Note that some parameters have been renamed for consistency with other plugins, but they should be pretty self-explanatory from the mojo javadoc. I can start a vote for an alpha release once we're both happy with it. Cheers, Mark
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Great, I'll looking forward to hearing back from you then. Cheers, Mark On 04/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, during the ApacheCon Europe next week I can spend some time to test the plugin with the tobago build. Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, Thanks for the reply, see below: On 02/04/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: I've also just removed any Java compliation support from the plugin since I couldn't see any advantage of duplicating this with the maven-compiler-plugin. Can you see any problems with that? I don't use this parameter, but this would break backwards compatibility. I'm not too concerned about backwards compatibility since the Codehaus plugin is currently in the sandbox and hence has no releases. If you're aware of any other users of the Tobago plugin then this may need considering if the Tobago version is removed for the Codehaus version. 1) Do you use extra source roots? I'm tempted to remove this parameter since it tends to go against the standard of using the project's current source roots. Yes, I need this parameter. We unpack a source artifact and process the containing source code too. But the extra source root should not included in the compile. Right, whereabouts is this in the build? Normally source roots are contributed to the build via plugins, for example the maven-compiler-plugin cannot be configured to use extra source roots but allows other plugins to add them during the lifecycle. 2) Do you use the resource target path parameter? I'd have thought that the apt factory should control this. Yes, I think the apt processor should only generate files and the resource plugin should copy the resources. Cool, I've removed this one. 3) Do you use the target files parameter? I wouldn't have thought you'd need such fine-grained control of source files to process when using Maven. Yes, we did see 4 4) Do you use staleness checking? I'm not too convinced by this implementation since it checks source files against class files to determine staleness. This is a problem when using -nocompile as the class file timestamp has no correlation with the staleness of generated resources. Auto-compiling IDEs then also pose a further problem since they never let a class file become stale, hence resources are never generated with apt. Yes, with the target file parameter the apt plugin is only called if the source code has changed. I see, I think misread the staleness implementation here. I've updated the Codehaus plugin to compute staleness using either: - suffixes of the processor-generated files (for one-to-one apt factories) - paths of the processor-generated files (for many-to-one apt factories) Your TLD factory falls into the latter category. This means that when at least one source file has a last modified timestamp beyond the generated file's last modified timestamp, then apt is run with *all* the source files. I believe this is the correct behaviour since with a many-to-one apt factory the generated resource is typically the amalgamation of all source files. Whereas for one-to-one apt factories, only stale source files are passed to apt. Can you see any problems with this logic? You can look at http://svn.apache.org/repos/asf/myfaces/tobago/trunk/core/pom.xml for some usages of the tobago apt plugin The old apt plugin from codehaus provides a 'generateToBuildDir' property. I think this parameter is useless. What do you think? I believe this placed the generated resources in the src directory or something daft? Nah, I don't think we need this either and it's gone in the current version. Cheers, Mark
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hello Mark, comments inline. Mark Hobson schrieb: Hi Bernd, 1) Do you use extra source roots? I'm tempted to remove this parameter since it tends to go against the standard of using the project's current source roots. Yes, I need this parameter. We unpack a source artifact and process the containing source code too. But the extra source root should not included in the compile. Right, whereabouts is this in the build? Normally source roots are contributed to the build via plugins, for example the maven-compiler-plugin cannot be configured to use extra source roots but allows other plugins to add them during the lifecycle. http://svn.apache.org/repos/asf/myfaces/tobago/trunk/sandbox/pom.xml http://svn.apache.org/repos/asf/myfaces/tobago/trunk/extension/facelets/pom.xml http://svn.apache.org/repos/asf/myfaces/tobago/trunk/extension/tobago-taglib-extension/pom.xml 2) Do you use the resource target path parameter? I'd have thought that the apt factory should control this. Yes, I think the apt processor should only generate files and the resource plugin should copy the resources. Cool, I've removed this one. Sorry, we are using this parameter. I think the apt plugin generates resources and with the parameter targetpath I can tell the resource plugin where the resouces should be copied. This parameter is used for generating the tlds in tobago. Without this parameter i need an extra resources section and I don't like to include the META-INF in the target. 3) Do you use the target files parameter? I wouldn't have thought you'd need such fine-grained control of source files to process when using Maven. Yes, we did see 4 4) Do you use staleness checking? I'm not too convinced by this implementation since it checks source files against class files to determine staleness. This is a problem when using -nocompile as the class file timestamp has no correlation with the staleness of generated resources. Auto-compiling IDEs then also pose a further problem since they never let a class file become stale, hence resources are never generated with apt. Yes, with the target file parameter the apt plugin is only called if the source code has changed. I see, I think misread the staleness implementation here. I've updated the Codehaus plugin to compute staleness using either: - suffixes of the processor-generated files (for one-to-one apt factories) - paths of the processor-generated files (for many-to-one apt factories) Your TLD factory falls into the latter category. This means that when at least one source file has a last modified timestamp beyond the generated file's last modified timestamp, then apt is run with *all* the source files. I believe this is the correct behaviour since with a many-to-one apt factory the generated resource is typically the amalgamation of all source files. Whereas for one-to-one apt factories, only stale source files are passed to apt. Can you see any problems with this logic? No, but as far as I know some guys are using a one to many mapping. They are using the force parameter. Thanks Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Thanks Mark, just some short notes inline Mark Hobson schrieb: Hi Bernd, I've finished with the major changes in tidying up the Codehaus apt-maven-plugin if you fancy taking a look: http://svn.codehaus.org/mojo/trunk/sandbox/apt-maven-plugin/ Major changes: - Manually merged in any exclusive features I could see in the Tobago version - Big refactor to simplify code - Added integration test intrastructure with a few tests to start with - Supported plugin dependencies (TOBAGO-130/MOJO-1072) I've also just removed any Java compliation support from the plugin since I couldn't see any advantage of duplicating this with the maven-compiler-plugin. Can you see any problems with that? I don't use this parameter, but this would break backwards compatibility. A few further points I'd like to ask you about: 1) Do you use extra source roots? I'm tempted to remove this parameter since it tends to go against the standard of using the project's current source roots. Yes, I need this parameter. We unpack a source artifact and process the containing source code too. But the extra source root should not included in the compile. 2) Do you use the resource target path parameter? I'd have thought that the apt factory should control this. Yes, I think the apt processor should only generate files and the resource plugin should copy the resources. 3) Do you use the target files parameter? I wouldn't have thought you'd need such fine-grained control of source files to process when using Maven. Yes, we did see 4 4) Do you use staleness checking? I'm not too convinced by this implementation since it checks source files against class files to determine staleness. This is a problem when using -nocompile as the class file timestamp has no correlation with the staleness of generated resources. Auto-compiling IDEs then also pose a further problem since they never let a class file become stale, hence resources are never generated with apt. Yes, with the target file parameter the apt plugin is only called if the source code has changed. I'd be interested in any feedback on using this plugin with Tobago. Feel free to move any existing JIRA issues across to the apt component in MOJO: http://jira.codehaus.org/browse/MOJO/component/13192 Cheers, Mark You can look at http://svn.apache.org/repos/asf/myfaces/tobago/trunk/core/pom.xml for some usages of the tobago apt plugin The old apt plugin from codehaus provides a 'generateToBuildDir' property. I think this parameter is useless. What do you think? Regards Bernd
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, I've finished with the major changes in tidying up the Codehaus apt-maven-plugin if you fancy taking a look: http://svn.codehaus.org/mojo/trunk/sandbox/apt-maven-plugin/ Major changes: - Manually merged in any exclusive features I could see in the Tobago version - Big refactor to simplify code - Added integration test intrastructure with a few tests to start with - Supported plugin dependencies (TOBAGO-130/MOJO-1072) I've also just removed any Java compliation support from the plugin since I couldn't see any advantage of duplicating this with the maven-compiler-plugin. Can you see any problems with that? A few further points I'd like to ask you about: 1) Do you use extra source roots? I'm tempted to remove this parameter since it tends to go against the standard of using the project's current source roots. 2) Do you use the resource target path parameter? I'd have thought that the apt factory should control this. 3) Do you use the target files parameter? I wouldn't have thought you'd need such fine-grained control of source files to process when using Maven. 4) Do you use staleness checking? I'm not too convinced by this implementation since it checks source files against class files to determine staleness. This is a problem when using -nocompile as the class file timestamp has no correlation with the staleness of generated resources. Auto-compiling IDEs then also pose a further problem since they never let a class file become stale, hence resources are never generated with apt. I'd be interested in any feedback on using this plugin with Tobago. Feel free to move any existing JIRA issues across to the apt component in MOJO: http://jira.codehaus.org/browse/MOJO/component/13192 Cheers, Mark On 27/03/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Ok, I'm waiting for your reply. Regards Bernd Mark Hobson schrieb: Hi Bernd, Thanks for the reply. I glad that you agree that merging the plugins is the way forward. I've started manually adding the features unique to the Tobago plugin to the Codehaus version and am currently tidying up the code. It's probably best to wait until I've finished doing that before submitting any patches; I'll let you know when it's ready for trialling with Tobago. Cheers, Mark On 27/03/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I think merging the plugin is a good idea. I hope I get enough time to prepare patches for the missing features in the codehaus apt plugin. The fist step would be using the apt-maven-plugin in the tobago build instead of the own plugin. Regards Bernd Mark Hobson schrieb: Hi there, I was looking for a Maven APT plugin and came across Tobago's and also one over at Codehaus [1]. I'm not aware of the history of these two plugins, but they both appear to be forked from the same codebase and been worked on over time. I'd like to see these plugins merged together to avoid duplicating efforts by both parties; if this of interest? I think the natural home for this plugin would be at Codehaus, which Tobago could easily use. I'm happy to help out merging the two codebases together since I have commit rights over at Codehaus. I've already fixed TOBAGO-130 as MOJO-1072 [2], so hopefully this merge will be beneficial to both parties. Let me know if you're interested and how you'd see the process moving forward. Cheers, Mark [1] http://mojo.codehaus.org/apt-maven-plugin/ [2] http://jira.codehaus.org/browse/MOJO-1072
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Hi Bernd, Thanks for the reply. I glad that you agree that merging the plugins is the way forward. I've started manually adding the features unique to the Tobago plugin to the Codehaus version and am currently tidying up the code. It's probably best to wait until I've finished doing that before submitting any patches; I'll let you know when it's ready for trialling with Tobago. Cheers, Mark On 27/03/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I think merging the plugin is a good idea. I hope I get enough time to prepare patches for the missing features in the codehaus apt plugin. The fist step would be using the apt-maven-plugin in the tobago build instead of the own plugin. Regards Bernd Mark Hobson schrieb: Hi there, I was looking for a Maven APT plugin and came across Tobago's and also one over at Codehaus [1]. I'm not aware of the history of these two plugins, but they both appear to be forked from the same codebase and been worked on over time. I'd like to see these plugins merged together to avoid duplicating efforts by both parties; if this of interest? I think the natural home for this plugin would be at Codehaus, which Tobago could easily use. I'm happy to help out merging the two codebases together since I have commit rights over at Codehaus. I've already fixed TOBAGO-130 as MOJO-1072 [2], so hopefully this merge will be beneficial to both parties. Let me know if you're interested and how you'd see the process moving forward. Cheers, Mark [1] http://mojo.codehaus.org/apt-maven-plugin/ [2] http://jira.codehaus.org/browse/MOJO-1072
Re: [Tobago] Merging maven-apt-plugin with Codehaus'
Ok, I'm waiting for your reply. Regards Bernd Mark Hobson schrieb: Hi Bernd, Thanks for the reply. I glad that you agree that merging the plugins is the way forward. I've started manually adding the features unique to the Tobago plugin to the Codehaus version and am currently tidying up the code. It's probably best to wait until I've finished doing that before submitting any patches; I'll let you know when it's ready for trialling with Tobago. Cheers, Mark On 27/03/2008, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Mark, I think merging the plugin is a good idea. I hope I get enough time to prepare patches for the missing features in the codehaus apt plugin. The fist step would be using the apt-maven-plugin in the tobago build instead of the own plugin. Regards Bernd Mark Hobson schrieb: Hi there, I was looking for a Maven APT plugin and came across Tobago's and also one over at Codehaus [1]. I'm not aware of the history of these two plugins, but they both appear to be forked from the same codebase and been worked on over time. I'd like to see these plugins merged together to avoid duplicating efforts by both parties; if this of interest? I think the natural home for this plugin would be at Codehaus, which Tobago could easily use. I'm happy to help out merging the two codebases together since I have commit rights over at Codehaus. I've already fixed TOBAGO-130 as MOJO-1072 [2], so hopefully this merge will be beneficial to both parties. Let me know if you're interested and how you'd see the process moving forward. Cheers, Mark [1] http://mojo.codehaus.org/apt-maven-plugin/ [2] http://jira.codehaus.org/browse/MOJO-1072
