Re: [VOTE] Release Maven 3.1.1
On 22/09/2013, at 9:28 AM, Jason van Zyl ja...@tesla.io wrote: A check is performed to ensure that each file in the source archive is present in the release revision Should that not be the other way around? That every file in the git clone should be in the source archive? Or vice versa, that should be neither more, or less files? Mark -- Mark Derricutt — twitter — podcast — blog — google+ signature.asc Description: Message signed with OpenPGP using GPGMail
rules for Apache release and tooling to help cheking compliance
Starting a separate thread to not pollute any vote. Isn't Apache Creadur the right place to: 1. discuss and refine Apache requirements 2. work on tooling Regards, Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: CMS + svnpubsub explanations
I will release the maven-deploy-plugin soon, so I can verify very well if that part is complete. Robert Op Sun, 22 Sep 2013 01:49:25 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: I just published a documentation about CMS + svnpubsub for Maven, with schema for global overview of the differences and synchronization points between Maven site and components reference documentations [1] The documentation about Maven website is expected to be complete, but components reference documentation still needs improvements for people to better understand how the configuration is done. It can even be subject to discussion, since not every component uses the same process for the moment: one of my intents by doing this documentation is to be able to discuss with Maven devs to define our target convention. But for the moment, it is not possible since I know a lot of people are lost in different cases (and no, there is no CMS when we publish component reference documentation). Please review and tell if anything is not clear Regards, Hervé [1] http://maven.apache.org/developers/website/deploy-maven-website.html - 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
JavaOne meetup
Morning/evening, all. In case there are more of us in JavaOne, feel free to send me an email so we can meet up for a chat, some drinks - or simply meeting and talking with one another. The more, the merrier, the meeting. -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid | EAI Architect Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype):jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==+
maven-scm pull request: Bugfixes to mercurial changelog
GitHub user hrmohr opened a pull request: https://github.com/apache/maven-scm/pull/6 Bugfixes to mercurial changelog This pull request includes several bugfixes to the mercurial changelog command: * Fixes date format by using a log template instead of log verbose * Fixes log template escaping by splitting the template parameter into two parts * New changelog parsing implementation to better detect new changesets and removes null changesets from result * Removes the branch name parsing warning You can merge this pull request into a Git repository by running: $ git pull https://github.com/hrmohr/maven-scm hgchangelogfix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-scm/pull/6.patch - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-plugins pull request: [MJAR-170] make the jar classifier customizable...
GitHub user ryenus opened a pull request: https://github.com/apache/maven-plugins/pull/13 [MJAR-170] make the jar classifier customizable via property maven.jar.classifier tested with the following snippet in my pom.xml and it works: ```xml properties maven.jar.classifierjdk6/maven.jar.classifier /properties build plugins plugin artifactIdmaven-jar-plugin/artifactId version2.5-SNAPSHOT/version !-- local patched snapshot version -- /plugin /plugins /build ``` You can merge this pull request into a Git repository by running: $ git pull https://github.com/ryenus/maven-plugins mjar-170 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-plugins/pull/13.patch - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-plugins pull request: [MJAVADOC-376] make the javadoc classifier cust...
GitHub user ryenus opened a pull request: https://github.com/apache/maven-plugins/pull/14 [MJAVADOC-376] make the javadoc classifier customizable via property maven.javadoc.classifier This should work just like my other PR #13 for, just there's unrelated test failures (might because it relies on certain settings). ```xml properties maven.javadoc.classifierjavadoc-jdk6/maven.javadoc.classifier /properties build plugins plugin artifactIdmaven-javadoc-plugin/artifactId version2.9.2-SNAPSHOT/version !-- local patched snapshot version -- /plugin /plugins /build ``` You can merge this pull request into a Git repository by running: $ git pull https://github.com/ryenus/maven-plugins mjavadoc-376 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-plugins/pull/14.patch - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Problem managing multiple versions of the same dependency via patient - child poms
Hi, I apologize in advance if this email contains sketchy / incomplete details. I'm not really a maven expert, and would love any advice that would be helpful. I'm a volunteer for a open source product which uses a modular architecture. We have a core project (supported by maven). Users can write their own modules (also supported by maven) to add the custom features that they require, and load them onto the OpenMRS core. Now in maven, if we declare multiple versions of the same dependency in the pom, maven automatically uses the very latest version of the given dependency. However, I am having trouble trying to replicate this by overriding a core dependency via a module. Assuming that the project trunk uses version 1.0 of jar A, and I want to write a module that requires version 2.0 of the same jar, how can I add this dependency to the pom file of a module, and make maven use the more recent dependency declared in the pom file of the module ? At the moment, what happens when I try this is both versions of the jar get loaded, and a casting error occurs. Any advice on how to manage this would be very much appreciated ! -- Best Regards, Suranga
Re: [VOTE] Release Maven 3.1.1
On 22 September 2013 08:13, Mark Derricutt m...@talios.com wrote: On 22/09/2013, at 9:28 AM, Jason van Zyl ja...@tesla.io wrote: A check is performed to ensure that each file in the source archive is present in the release revision Should that not be the other way around? That every file in the git clone should be in the source archive? Or vice versa, that should be neither more, or less files? The point of checking the source archive against the SCM tag is to ensure that all the files in the source release have got the correct license clearance. It is assumed that license conditions are checked when content is added to SCM, because that is in the CLA signed by committers. If there are files in the SCM tag that are not in the source release, that is generally not a problem as far as licensing is concerned (thought it's possible that the NOTICE/LICENSE files might need adjusting to take account of the missing files). Of course the missing files may be important for the functioning of the code - that is a separate matter. Ideally the two file sets agree, with the possible exception of some files that only belong in SCM, e.g. .gitignore is not needed in the source archive, and it does not make much sense to release a DOAP file. There may be some other SCM-only files. But I agree any discrepancies need to be investigated. Mark -- Mark Derricutt — twitter — podcast — blog — google+ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On 22 September 2013 05:03, Jason van Zyl ja...@tesla.io wrote: On Sep 21, 2013, at 7:44 PM, sebb seb...@gmail.com wrote: On 22 September 2013 03:09, Jason van Zyl ja...@tesla.io wrote: On Sep 21, 2013, at 6:16 PM, sebb seb...@gmail.com wrote: On 21 September 2013 23:09, Jason van Zyl ja...@tesla.io wrote: It would still be automated. However the source data would come form the vote e-mail, which makes more sense to me. If it were generated I would agree. Manually making an email is not automated or consistent. I don't care how the e-mail is created; it can be automated. What matters is that the content is understandable and complete. Ok, then we agree. We should try to keep the vote email threads for the votes. I think what you asked for was the impetus for the tool I made and it helped do a more complete audit than I've ever done manually. But the SCM coordinates are not a requirement for the release email currently and if we're going to discuss that then we probably shouldn't hijack the vote threads which we both just did. I don't believe it's hijacking the vote e-mail to point out that it is missing vital information. But the subsequent discussion has certainly veered off-topic. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: rules for Apache release and tooling to help cheking compliance
On 22 September 2013 09:49, Hervé BOUTEMY herve.bout...@free.fr wrote: Starting a separate thread to not pollute any vote. Isn't Apache Creadur the right place to: 1. discuss and refine Apache requirements No. 2. work on tooling Possibly. Regards, Hervé - 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] Release Maven 3.1.1
Sent from my iPad On Sep 22, 2013, at 4:41 PM, sebb seb...@gmail.com wrote: On 22 September 2013 05:03, Jason van Zyl ja...@tesla.io wrote: On Sep 21, 2013, at 7:44 PM, sebb seb...@gmail.com wrote: On 22 September 2013 03:09, Jason van Zyl ja...@tesla.io wrote: On Sep 21, 2013, at 6:16 PM, sebb seb...@gmail.com wrote: On 21 September 2013 23:09, Jason van Zyl ja...@tesla.io wrote: It would still be automated. However the source data would come form the vote e-mail, which makes more sense to me. If it were generated I would agree. Manually making an email is not automated or consistent. I don't care how the e-mail is created; it can be automated. What matters is that the content is understandable and complete. Ok, then we agree. We should try to keep the vote email threads for the votes. I think what you asked for was the impetus for the tool I made and it helped do a more complete audit than I've ever done manually. But the SCM coordinates are not a requirement for the release email currently and if we're going to discuss that then we probably shouldn't hijack the vote threads which we both just did. I don't believe it's hijacking the vote e-mail to point out that it is missing vital information. But the subsequent discussion has certainly veered off-topic. It is if the topic has been discussed before on other vote threads and/or the PMC has made a decision about what is required and it is not in conflict with any ASF published policy. If you believe the PMC is in error than as an ASF member you are free to bring that topic up on the PMC list or as a separate thread here. Bringing it up on every vote thread borders on trolling IMO, even if you are 100% correct in what you believe should be done. Ralph - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
pull requests on github?
Would anyone be taking care of the pull requests on github: https://github.com/apache/maven-plugins/pulls I just made 2 but saw there're pull requests open for years. Thanks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
