about MSITE-535
I just had a doubt regarding http://jira.codehaus.org/browse/MSITE-535. I came across a use case where implementing this would lead to different behavior. This case seems exotic to me but maybe it isn't. Assume: 1) a project inheriting the site descriptor from a parent 2) where the parent site.xml contains some relative links (for breadcrumbs, banners, links,...) 3) the child project gets deployed to a different site (ie the url has a different protocol://host:port). In this case, the parent's relative links will be resolved wrt the parent's base url, and with MSITE-535 implemented, the links will point to (typically) an scp (upload) url instead of the project.url. Note that there will be no problem if the parent only uses absolute links (because they won't be resolved), or if the child goes to the same site (because the same relative links will be used). So the question is: are there known instances of projects where the above assumptions hold? If this turns out to be a problem it can still be fixed (by resolving the parent links before inheritance, which IMO would be the proper procedure anyway), but that would necessitate an API change as the current InheritanceAssembler has no method for link resolution. Thanks, -Lukas - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven failsafe plugin
Hi, thanks for the answers... Please file a ticket and I'm sure Kristian will update this for the next release. /Anders Done. http://jira.codehaus.org/browse/SUREFIRE-692 Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
move MPOM in ASF jira (was Re: ASF pom release)
Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theusslltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: move MPOM in ASF jira (was Re: ASF pom release)
you can add me olivier (aheritier) On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote: Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theusslltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: move MPOM in ASF jira (was Re: ASF pom release)
I've added you. We should get a full list of the PMC's apache jira user id's and then any/all of the three of us can add the PMC to the project role 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: you can add me olivier (aheritier) On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote: Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theusslltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.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: move MPOM in ASF jira (was Re: ASF pom release)
ok, It's annoying to not have a mapping between LDAP/SVN groups and Jira. It could be easier to manage On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've added you. We should get a full list of the PMC's apache jira user id's and then any/all of the three of us can add the PMC to the project role 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: you can add me olivier (aheritier) On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote: Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theusslltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.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: move MPOM in ASF jira (was Re: ASF pom release)
aheritier baerrach bentmann brett brianf carlos dennisl dfabulich dkulp evenisse hboutemy jdcasey kenney krosenvold ltheussl mkleint oching olamy pgier rgoers snicoll stephenc vmassol vsiveton wfay 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: ok, It's annoying to not have a mapping between LDAP/SVN groups and Jira. It could be easier to manage On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've added you. We should get a full list of the PMC's apache jira user id's and then any/all of the three of us can add the PMC to the project role 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: you can add me olivier (aheritier) On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote: Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theusslltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: move MPOM in ASF jira (was Re: ASF pom release)
I tried :-) It's not working. Some users don't exist On Fri, Jan 28, 2011 at 3:34 PM, Brian Fox bri...@infinity.nu wrote: aheritier baerrach bentmann brett brianf carlos dennisl dfabulich dkulp evenisse hboutemy jdcasey kenney krosenvold ltheussl mkleint oching olamy pgier rgoers snicoll stephenc vmassol vsiveton wfay 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: ok, It's annoying to not have a mapping between LDAP/SVN groups and Jira. It could be easier to manage On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've added you. We should get a full list of the PMC's apache jira user id's and then any/all of the three of us can add the PMC to the project role 2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com: you can add me olivier (aheritier) On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote: Hello, I have changed the subject. As asked by Benson, it's probably better to move MPOM from codehaus jira to ASF jira. So I have created a jira entry : https://issues.apache.org/jira/browse/INFRA-3397 I'd like maven dev give me or add in the jira entry their id. Thanks ! -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/28 Olivier Lamy ol...@apache.org: 2011/1/28 John Casey jdca...@commonjava.org: On 1/27/11 4:22 PM, Benson Margulies wrote: I want to just put a bit of emphasis on the global impact of this POM. This POM gets advertised as the appropriate parent for \any/ Apache project building with Maven. As such, I submit to you, it should supply all of the necessary settings (e.g. repository locations, deployment) and no surprising extra behavior. If the Land Of Maven wants a policy of running a full build on prepare, I'd respectfully ask you to embody that policy in a POM that isn't the one advertised to the complete Apache community. ...which is why I said in another branch of this thread, that I'm okay with pulling this setting down into the maven parent POM(s). and document for others AFSERs having this in your pom is RECOMMENDED. http://www.apache.org/dev/publishing-maven-artifacts.html looks to be the appropriate place On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theussl ltheu...@apache.org wrote: Brian Fox wrote: FWIW, if the code-signing step fails due to some POM misconfiguration, and only runs in the perform step, then you've got to rollback the release and try it again...either that, or muck around with manually shifting the tag in the SCM, which is probably as ugly. I'm not as concerned about spending a little extra time to reduce the chances of things going wrong in the release process, since this seems to happen often enough already...and causes a HUGE waste of time in some cases. If we were releasing a 100+ module project structure, then I'd be willing enough to give on this point and say that accepting a little extra risk in the 'perform' phase isn't that big of a deal. But, at least in Maven, the releases aren't that big. For Lukas: I agree with John here. For everyone else: +1 For everyone: I agree too. Especially with the part about things going wrong often enough. -Lukas ;p - 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 -- John Casey Developer, PMC Member - 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 -- Olivier Lamy http://twitter.com/olamy http://www.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:
Questions about surefire site
Surefire and failsafe today contain two different sites that are near-identical copies, because the current plugin is a merge of two forks. My main problem is that there is a fair amount of hand-written apt documents that are common between these two projects, and at the moment they are forked. I want to end this duplication. How should I do it ? So either I'm thinking something symlink like or just merge these two into one site, and since I am a total mess when it comes to all things gui related I need to ask these n00bish questions: Is there another multi-module plugin project that has a common site for two different plugin sub-projects that I can look at ? (I didn't say copy but you bet I was tempted) Does merging sites mean the url's for the top-level entry points change ? http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html I seem to be unable to find coherent documentation on how to do things like this, so tips in that area are also welcome ;) Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Questions about surefire site
Does this have to happen right now I am distracted with some stuff... but RSN (4-6 weeks) I will be able to lend a hand and sort something out -Stephen On 28 January 2011 15:33, Kristian Rosenvold krist...@rosenvold.com wrote: Surefire and failsafe today contain two different sites that are near-identical copies, because the current plugin is a merge of two forks. My main problem is that there is a fair amount of hand-written apt documents that are common between these two projects, and at the moment they are forked. I want to end this duplication. How should I do it ? So either I'm thinking something symlink like or just merge these two into one site, and since I am a total mess when it comes to all things gui related I need to ask these n00bish questions: Is there another multi-module plugin project that has a common site for two different plugin sub-projects that I can look at ? (I didn't say copy but you bet I was tempted) Does merging sites mean the url's for the top-level entry points change ? http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html I seem to be unable to find coherent documentation on how to do things like this, so tips in that area are also welcome ;) Kristian - 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: Questions about surefire site
Ok. There's still enough bugs to roll 2.7.3 in the meantime. Since I know how to send email *and* create appointments from my phone, I will put you up in 6 weeks from now ;) Kristian fr., 28.01.2011 kl. 15.44 +, skrev Stephen Connolly: Does this have to happen right now I am distracted with some stuff... but RSN (4-6 weeks) I will be able to lend a hand and sort something out -Stephen On 28 January 2011 15:33, Kristian Rosenvold krist...@rosenvold.com wrote: Surefire and failsafe today contain two different sites that are near-identical copies, because the current plugin is a merge of two forks. My main problem is that there is a fair amount of hand-written apt documents that are common between these two projects, and at the moment they are forked. I want to end this duplication. How should I do it ? So either I'm thinking something symlink like or just merge these two into one site, and since I am a total mess when it comes to all things gui related I need to ask these n00bish questions: Is there another multi-module plugin project that has a common site for two different plugin sub-projects that I can look at ? (I didn't say copy but you bet I was tempted) Does merging sites mean the url's for the top-level entry points change ? http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html I seem to be unable to find coherent documentation on how to do things like this, so tips in that area are also welcome ;) Kristian - 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: Questions about surefire site
quit boasting On 28 January 2011 16:02, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Ok. There's still enough bugs to roll 2.7.3 in the meantime. Since I know how to send email *and* create appointments from my phone, I will put you up in 6 weeks from now ;) Kristian fr., 28.01.2011 kl. 15.44 +, skrev Stephen Connolly: Does this have to happen right now I am distracted with some stuff... but RSN (4-6 weeks) I will be able to lend a hand and sort something out -Stephen On 28 January 2011 15:33, Kristian Rosenvold krist...@rosenvold.com wrote: Surefire and failsafe today contain two different sites that are near-identical copies, because the current plugin is a merge of two forks. My main problem is that there is a fair amount of hand-written apt documents that are common between these two projects, and at the moment they are forked. I want to end this duplication. How should I do it ? So either I'm thinking something symlink like or just merge these two into one site, and since I am a total mess when it comes to all things gui related I need to ask these n00bish questions: Is there another multi-module plugin project that has a common site for two different plugin sub-projects that I can look at ? (I didn't say copy but you bet I was tempted) Does merging sites mean the url's for the top-level entry points change ? http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html I seem to be unable to find coherent documentation on how to do things like this, so tips in that area are also welcome ;) Kristian - 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: Frequently Asked Technical Questions translation
Sounds fine, in general you can ask questions to the list dev@maven.apache.org (cc'd) On Fri, Jan 28, 2011 at 12:12 PM, Amanda Lynn amnda.l...@gmail.com wrote: Hello, I want to translate 'Frequently Asked Technical Questions' (http://maven.apache.org/general.html) to Belorussian language, which is my mother tongue. When Ill be done I'm gonna send to you a link to the article. Is it ok with you, don't you mind? Do you prefer email or IM for contact (if any questions regarding the translation arise)? What instant messaging client (if any) do you use? AIM, MSN, Skype? -- Regards, Amanda Lynn - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Frequently Asked Technical Questions translation
This is a good question. We had a similar question come into Struts. A community member wanted to translate the user documentation into Chinese. We were debating accept it as a patch or does it require a CLA form? Does the answer depend on the amount of work being submitted? We decided on a patch but I don't have any clear-cut guidance. What are your opinions? Paul On Fri, Jan 28, 2011 at 3:56 PM, Brian Fox bri...@infinity.nu wrote: Sounds fine, in general you can ask questions to the list dev@maven.apache.org (cc'd) On Fri, Jan 28, 2011 at 12:12 PM, Amanda Lynn amnda.l...@gmail.com wrote: Hello, I want to translate 'Frequently Asked Technical Questions' (http://maven.apache.org/general.html) to Belorussian language, which is my mother tongue. When Ill be done I'm gonna send to you a link to the article. Is it ok with you, don't you mind? Do you prefer email or IM for contact (if any questions regarding the translation arise)? What instant messaging client (if any) do you use? AIM, MSN, Skype? -- Regards, Amanda Lynn - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Frequently Asked Technical Questions translation
I would accept a patch On Fri, Jan 28, 2011 at 5:03 PM, Paul Benedict pbened...@apache.org wrote: This is a good question. We had a similar question come into Struts. A community member wanted to translate the user documentation into Chinese. We were debating accept it as a patch or does it require a CLA form? Does the answer depend on the amount of work being submitted? We decided on a patch but I don't have any clear-cut guidance. What are your opinions? Paul On Fri, Jan 28, 2011 at 3:56 PM, Brian Fox bri...@infinity.nu wrote: Sounds fine, in general you can ask questions to the list dev@maven.apache.org (cc'd) On Fri, Jan 28, 2011 at 12:12 PM, Amanda Lynn amnda.l...@gmail.com wrote: Hello, I want to translate 'Frequently Asked Technical Questions' (http://maven.apache.org/general.html) to Belorussian language, which is my mother tongue. When Ill be done I'm gonna send to you a link to the article. Is it ok with you, don't you mind? Do you prefer email or IM for contact (if any questions regarding the translation arise)? What instant messaging client (if any) do you use? AIM, MSN, Skype? -- Regards, Amanda Lynn - 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: Regarding MNG-3321 - Support for Skipping Plugin Execution
Hi, Thank you for the comments. I updated the issue, http://jira.codehaus.org/browse/MNG-3321 with the modified patches. Regarding your point about documentation, will you please point me to the exact location where I should include the usage instructions for this feature and other info (perhaps a wiki ?). Sincere Regards, Kalyan C. Akella On Fri, Jan 28, 2011 at 12:55 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Thanks for the patch, which looks good. I added some comments to the issue, http://jira.codehaus.org/browse/MNG-3321 Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
