Re: [site] #evaluate Velocity macro ignored
Hi Lukas! thanks for the clarification, very appreciated! Are you aware of any turnaround? It would be really useful to let users use placeholders inside of $decoration.body.(head|foot)er elements. It is a requirement I have to satisfy in order to let other ASF communities adopt the fluido-skin, mainly because we have to fill trademarks... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 8:39 AM, Lukas Theussl ltheu...@apache.org wrote: Hi Simone, The evaluate directive was added in velocity 1.6 [1], doxia-site-renderer still uses velocity 1.5. HTH, -Lukas [1] https://issues.apache.org/jira/browse/VELOCITY-509 On 11/20/2011 04:45 PM, Simone Tripodi wrote: Hi all guys, is anyone aware about some Issue that prevents Velocity execute the #evaluate directive in the skins? It looks like it is just rendered as #evaluate(arg) string... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [site] #evaluate Velocity macro ignored
It's been a while for me but I remember I ran into several issues when trying to upgrade to a newer velocity version, see eg [1]. For the trademark, there has been an attempt to improve the footer customization [2], but I'm not sure how far this went. -Lukas [1] http://jira.codehaus.org/browse/DOXIASITETOOLS-39 [2] http://jira.codehaus.org/browse/MSITE-549 On 11/21/2011 09:03 AM, Simone Tripodi wrote: Hi Lukas! thanks for the clarification, very appreciated! Are you aware of any turnaround? It would be really useful to let users use placeholders inside of $decoration.body.(head|foot)er elements. It is a requirement I have to satisfy in order to let other ASF communities adopt the fluido-skin, mainly because we have to fill trademarks... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 8:39 AM, Lukas Theusslltheu...@apache.org wrote: Hi Simone, The evaluate directive was added in velocity 1.6 [1], doxia-site-renderer still uses velocity 1.5. HTH, -Lukas [1] https://issues.apache.org/jira/browse/VELOCITY-509 On 11/20/2011 04:45 PM, Simone Tripodi wrote: Hi all guys, is anyone aware about some Issue that prevents Velocity execute the #evaluate directive in the skins? It looks like it is just rendered as #evaluate(arg) string... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Jar Signer 1.0
+1 - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 16 Nov 2011 12:40, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release first version of Apache Maven Jar Signer. This shared library is an extraction of the code from maven-jarsigner-plugin to sign jars. The goal is to reuse this component in other mojos. Staging repository: https://repository.apache.org/content/repositories/maven-198/ Staging site: http://maven.apache.org/shared/maven-jarsigner/ Vote open for 72H. Here my +1. Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [site] #evaluate Velocity macro ignored
Hi Lukas, there are exactly the issues that would prevent the adoption in apache-commons... :( I need to study an alternative strategy, thanks for your help! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:58 AM, Lukas Theussl ltheu...@apache.org wrote: It's been a while for me but I remember I ran into several issues when trying to upgrade to a newer velocity version, see eg [1]. For the trademark, there has been an attempt to improve the footer customization [2], but I'm not sure how far this went. -Lukas [1] http://jira.codehaus.org/browse/DOXIASITETOOLS-39 [2] http://jira.codehaus.org/browse/MSITE-549 On 11/21/2011 09:03 AM, Simone Tripodi wrote: Hi Lukas! thanks for the clarification, very appreciated! Are you aware of any turnaround? It would be really useful to let users use placeholders inside of $decoration.body.(head|foot)er elements. It is a requirement I have to satisfy in order to let other ASF communities adopt the fluido-skin, mainly because we have to fill trademarks... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 8:39 AM, Lukas Theusslltheu...@apache.org wrote: Hi Simone, The evaluate directive was added in velocity 1.6 [1], doxia-site-renderer still uses velocity 1.5. HTH, -Lukas [1] https://issues.apache.org/jira/browse/VELOCITY-509 On 11/20/2011 04:45 PM, Simone Tripodi wrote: Hi all guys, is anyone aware about some Issue that prevents Velocity execute the #evaluate directive in the skins? It looks like it is just rendered as #evaluate(arg) string... Many thanks in advance, all the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT][VOTE] Apache Maven Jar Signer 1.0
Hello, The vote has passed with the following result: +1 (binding): Kristian, Stephen, Olivier +1 (non binding): Tony. I will continue the release process. Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Wagon 2.1
+1 On 11/18/11 12:03 PM, Olivier Lamy wrote: Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-219 Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Wagon 2.1
On 11/20/11 3:54 AM, Olivier Lamy wrote: Hello, I cancel this vote and will restart a new one on monday. As I'd like to include two more fixes. 2011/11/18 Olivier Lamy ol...@apache.org: Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-219 Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy argh, need to read the full thread before responding... -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Apache Maven Wagon 2.1 (take 2)
Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-228/ Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Wagon 2.1 (take 2)
On Mon, 21 Nov 2011 16:45:43 +0100 Olivier Lamy ol...@apache.org wrote: +1 (non binding) Viva core 3.0.4 :) Thanks. Tony Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-228/ Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Wagon 2.1 (take 2)
+1 On 11/21/11 10:45 AM, Olivier Lamy wrote: Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-228/ Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Wagon 2.1 (take 2)
tested with a local VM server without problems. +1 LieGrue, strub - Original Message - From: Olivier Lamy ol...@apache.org To: Maven Developers List dev@maven.apache.org Cc: Sent: Monday, November 21, 2011 4:45 PM Subject: [VOTE] Apache Maven Wagon 2.1 (take 2) Hello, I'd like to release Apache Maven Wagon 2.1. It looks to be the last step before being able to release core 3.0.4! We fixed 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17844styleName=TextprojectId=10335Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-228/ Staging site: http://maven.apache.org/wagon-2.1 (wait sync) [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
New plugin patch-tracker
Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin patch-tracker
Salut Olivier! in one word: GREAT :) I just have 2 minor suggestions: * name attachments as `*.patch` * I didn't have a look at the sourcecode already, but please design the plugin to easily plug other issue tracker (not like the changes plugin) well done, impressive work! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin patch-tracker
On 2011-11-21 21:55, Simone Tripodi wrote: Salut Olivier! in one word: GREAT :) I just have 2 minor suggestions: * name attachments as `*.patch` * I didn't have a look at the sourcecode already, but please design the plugin to easily plug other issue tracker (not like the changes plugin) I've worked quite a lot on the Changes Plugin, trying to move it towards using a high-level issue tracker API. It's far from finished, but if you are interested, we might put our minds together and sketch something up. well done, impressive work! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin patch-tracker
2011/11/21 Simone Tripodi simonetrip...@apache.org: Salut Olivier! in one word: GREAT :) I just have 2 minor suggestions: * name attachments as `*.patch` done :-) * I didn't have a look at the sourcecode already, but please design the plugin to easily plug other issue tracker (not like the changes plugin) Yup as easy as : * @plexus.component role=org.apache.maven.plugins.patchtracker.tracking.PatchTracker role-hint=foo */ public class FooPatchTracker implements PatchTracker and in cli -Dpatch.system=foo well done, impressive work! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin patch-tracker
Dennis - have you by chance modified the changes plugin so that there is a jar with most of the logic and the plugin? I recently wanted to create a new plugin that used logic from the changes plugin but couldn't see how to do it. Ralph On Nov 21, 2011, at 1:01 PM, Dennis Lundberg wrote: On 2011-11-21 21:55, Simone Tripodi wrote: Salut Olivier! in one word: GREAT :) I just have 2 minor suggestions: * name attachments as `*.patch` * I didn't have a look at the sourcecode already, but please design the plugin to easily plug other issue tracker (not like the changes plugin) I've worked quite a lot on the Changes Plugin, trying to move it towards using a high-level issue tracker API. It's far from finished, but if you are interested, we might put our minds together and sketch something up. well done, impressive work! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin patch-tracker
Could it be possible for the plugin to generate to automatically generate lines of code to fix bugs ?? :-D More seriously good job. A really useful service to ease contributions for ASF (and some others) projects. Arnaud On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven shade plugin question
Thanks for reviewing and committing the patch. Could you also deploy a new snapshot build to the apache snapshot repository? Thanks, Trask On Sun, Nov 20, 2011 at 10:12 AM, Trask Stalnaker trask.stalna...@gmail.com wrote: Thanks so much for the response. I look forward to your review of the patch. I'm happy to re-write it taking a different approach if you see fit, so just shoot me your feedback. Thanks again. Trask On Sun, Nov 20, 2011 at 5:00 AM, Benson Margulies bimargul...@gmail.comwrote: Trask, No problem, but in the future feel free to send such a thing to the maven dev list. I'll look at your patch. Honestly, there's no one who is very reliably looking for new patches across many of the plugins, so a ping is a good idea. We generally don't release for only one patch, and we released recently, but if it fixes a howler and it would help you I'll try to also turn the crank. --benson On Sun, Nov 20, 2011 at 4:41 AM, Trask Stalnaker trask.stalna...@gmail.com wrote: Hi Benson, I hope you don't mind me emailing you directly. I noticed that you have made the last few contributions to the maven shade plugin. I have submitted https://jira.codehaus.org/browse/MSHADE-104 a month or two ago. I just updated the jira ticket tonight with a second version of the patch. Is there anything I can do to help this patch get accepted into the maven shade plugin trunk? I'm happy to make any modifications to the patch that you would like to see, and I can provide more docs/examples/tests/explanations/etc if that will help. Thank you for your time. Sincerely, Trask Stalnaker
Re: New plugin patch-tracker
Hi Ralph I haven't gotten that far yet. There is one obstacle left to fix, before an api can be extracted, and that is full use of Java 5 generics. That in turn is currently blocked by an issue in Modello, that prevents upgrading to a version of Modello that can generate Java 5 code. Extracting an api is something I've wanted to do for some time. Looking ahead I will have time to work on it soon. As always with api design though, it help to be more than one person working on it. On Monday, November 21, 2011, Ralph Goers ralph.go...@dslextreme.com wrote: Dennis - have you by chance modified the changes plugin so that there is a jar with most of the logic and the plugin? I recently wanted to create a new plugin that used logic from the changes plugin but couldn't see how to do it. Ralph On Nov 21, 2011, at 1:01 PM, Dennis Lundberg wrote: On 2011-11-21 21:55, Simone Tripodi wrote: Salut Olivier! in one word: GREAT :) I just have 2 minor suggestions: * name attachments as `*.patch` * I didn't have a look at the sourcecode already, but please design the plugin to easily plug other issue tracker (not like the changes plugin) I've worked quite a lot on the Changes Plugin, trying to move it towards using a high-level issue tracker API. It's far from finished, but if you are interested, we might put our minds together and sketch something up. well done, impressive work! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Nov 21, 2011 at 9:33 PM, Olivier Lamy ol...@apache.org wrote: Hello, FYI, I have created a new plugin called maven-patch-tracker-plugin in sandbox. Basically, this plugin will generate a diff using the scm provider configured in your pom (note if the pom says svn but you use git svn, you can use -Dscm.providerType=git). Then will create an issue in your configured issue tracker (currently only jira is supported) and attach the patch. A typical cli is: mvn patch-tracker:create -e -X -Dpatch.summary=foo summary -Dpatch.serverUrl=http://localhost:8080/browse/MNG -B -Dpatch.user=uid -Dpatch.password=pwd Note you can add an entry in your settings and use it for authz with -Dpatch.serverId=serverIdFromYourSettings (and you can remove -Dpatch.user -Dpatch.pasword from your cli). The server url can come from the pom. (issueManagement/url). Urls with component id are supported too: https://jira.codehaus.org/browse/MSHARED/component/15255 (and issue is created in MSHARED and attach to the component with 15255) Note: there is a prompter use to setup values, BTW you can use -B and nothing will be asked if your configuration is correct. An other goal is to update an issue with an other patch: mvn patch-tracker:update -e -Dscm.providerType=git -Dpatch.description=update of the issue with an other patch -Dpatch.patchId=MNG-5203 -B The result is something like: https://jira.codehaus.org/browse/MNG-5203 Let me know if you see any other features (I think I will add support of loading patch in review board). Have fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org -- Dennis Lundberg
