[CANCELLED] [VOTE] Release Apache Maven Archetype version 2.4
Ok, according to the -1 votes I'm cancelling the first vote. I'll start another one later on. -- Forwarded message -- From: Petar Tahchiev paranoia...@gmail.com Date: 2015-08-09 22:21 GMT+03:00 Subject: Re: [VOTE] Release Apache Maven Archetype version 2.4 To: Maven Developers List dev@maven.apache.org Ok, Let's close this vote. I will revert, fix it and perform a new release. Thank you. 2015-08-09 21:49 GMT+03:00 Karl Heinz Marbaise khmarba...@gmx.de: Hi Petar, checked SHA1 Ok.. unfortunately i have found an issue by running IT's etc. from the release zip archive...via: Maven 3.3.3, mvn -Prun-its clean verify So i have to give -1 here... The IT expected to have an empty folder which i assume should be already checked in, but that can't work with Git, cause in Git you can't checkin empty folders. You need to make setup.groovy etc. to create that empty folder before running the integration test. INFO] Post-archetype-generation invoker exit code: 0 [INFO] run script /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/verify.groovy [DEBUG] Running script with GroovyScriptInterpreter: /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/verify.groovy [INFO] Running post-build script: /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/verify.groovy [DEBUG] Error evaluating post-build script /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/verify.groovy, Assertion failed: assert new File(basedir,reference/src/main/resources/empty-directory).exists() || | || false | /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/reference/src/main/resources/empty-directory Assertion failed: assert new File(basedir,reference/src/main/resources/empty-directory).exists() || | || false | /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic /Users/kama/Downloads/maven-archetype-2.4/maven-archetype-plugin/target/it/build-archetype-ignore-eol-encoding/target/test-classes/projects/basic/reference/src/main/resources/empty-directory PS.: Can you please follow the full release procedure template which contains also the full path to the release.zip file...makes it easier to download instead of using the browser to find the zip file location so i can use curl instead On 8/9/15 8:18 PM, Petar Tahchiev wrote: Hi, We solved 9 issues: https://issues.apache.org/jira/browse/ARCHETYPE-483?jql=project%20%3D%20ARCHETYPE%20AND%20fixVersion%20%3D%202.4%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1203/ Staging site: http://maven.apache.org/archetype-archives/archetype-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Regards, Petar! Karlovo, Bulgaria. --- Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 -- Regards, Petar! Karlovo, Bulgaria. --- Public PGP Key at: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [VOTE] Release Apache Maven Archetype version 2.4 - TAKE 2
Hi, checked shasum Ok. tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.5, 3.3.3 via mvn -Prun-its clean verify without any issue. So +1 from me. Kind regards Karl Heinz Marbaise On 8/10/15 8:06 PM, Petar Tahchiev wrote: OK, here's the take two. Please pay extra attention as I haven't made a release for a long time now. We solved 10 issues: https://issues.apache.org/jira/browse/ARCHETYPE-483?jql=project%20%3D%20ARCHETYPE%20AND%20fixVersion%20%3D%202.4%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1204/ https://repository.apache.org/content/repositories/maven-1204/org/apache/maven/archetype/maven-archetype/2.4/maven-archetype-2.4-source-release.zip Source release checksum(s): maven-archetype-2.4-source-release.zip sha1: e0afe445f1bb7c9c8e557d59d035e5ae3854f7f1 Staging site: http://maven.apache.org/archetype-archives/archetype-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Archetype version 2.4
Hi Petar, If you need to cancel a VOTE please send an appropriate mail through the list for the record (and for further history)with the approriate Subject...[CANCELLED] [VOTE]... to make clear the VOTE has been cancelled. Furthermore the second VOTE try should be marked with something like ... - Take 2 to make it easy to see the difference... On 8/9/15 10:48 PM, Petar Tahchiev wrote: Sorry guys, gmail is absolutely stupid - I said new email but had this one opened to copy the url-s, and now it added it as a response :( .. I'll send one not as a response to this thread. 2015-08-09 23:46 GMT+03:00 Petar Tahchiev paranoia...@gmail.com: Hi, We solved 9 issues: https://issues.apache.org/jira/browse/ARCHETYPE-483?jql=project%20%3D%20ARCHETYPE%20AND%20fixVersion%20%3D%202.4%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1204/ https://repository.apache.org/content/repositories/maven-1204/org/apache/maven/archetype/maven-archetype/2.4/maven-archetype-2.4-source-release.zip Source release checksum(s): maven-archetype-2.4-source-release.zip sha1: e0afe445f1bb7c9c8e557d59d035e5ae3854f7f1 Staging site: http://maven.apache.org/archetype-archives/archetype-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Regards, Petar! Karlovo, Bulgaria. --- Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven Archetype version 2.4 - TAKE 2
OK, here's the take two. Please pay extra attention as I haven't made a release for a long time now. We solved 10 issues: https://issues.apache.org/jira/browse/ARCHETYPE-483?jql=project%20%3D%20ARCHETYPE%20AND%20fixVersion%20%3D%202.4%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1204/ https://repository.apache.org/content/repositories/maven-1204/org/apache/maven/archetype/maven-archetype/2.4/maven-archetype-2.4-source-release.zip Source release checksum(s): maven-archetype-2.4-source-release.zip sha1: e0afe445f1bb7c9c8e557d59d035e5ae3854f7f1 Staging site: http://maven.apache.org/archetype-archives/archetype-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Regards, Petar! Karlovo, Bulgaria. --- Public PGP Key at: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
How to determine which git repo MAven plugins reside in (was [ANN] 2015 Committer School for people who want to become Maven Committers)
This is a good question. Normally, I'd look at the jira project which would link back to the Maven project web pages. The summary jira page https://issues.apache.org/jira/browse/MNG?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel doesn't describe MNG components well enough to find them. The summary pages for each component doesn't link to a Maven project web page. If you select any issue, and then its Activity tab, you might get lucky and get a Hudson notification. And in the Hudson job you can find the git url in the Git Polling Log page. In this case https://git-wip-us.apache.org/repos/asf/maven.git which is all Maven Core. I'm behind an NTLM firewall at work so I've avoided working with git and Maven. Hopefully someone else can provide an answer, and then we can update the documentation to better reflect that. -- Forwarded message -- From: Benjamin Chylla ejbga...@gmail.com Date: 6 August 2015 at 00:53 Subject: Re: [ANN] 2015 Committer School for people who want to become Maven Committers To: Maven Developers List dev@maven.apache.org Hello, I have a question. I am trying to use Git in order to work with the source code in the Maven Respository. When I find a Maven project issue on JIRA, how do I determine which GitHub repository to make a fork of? From my understanding, https://git-wip-us.apache.org/repos/asf/maven.git is the location of the main git repository for Maven, but there is also a separate repository for the integration tests for the Maven core (https: //git-wip-us.apache.org/repos/asf/maven-integration-testing.git), as well as other components (Archetype, Indexer, Plugin Testing, SCM, Surefire, and Wagon). For example, one of the open JIRA issues that I am interested in working on has the following components listed: Embedding https://issues.apache.org/jira/browse/MNG/component/12325608, General https://issues.apache.org/jira/browse/MNG/component/12325623, Logging https://issues.apache.org/jira/browse/MNG/component/12325605,Performance https://issues.apache.org/jira/browse/MNG/component/12325616, Reactor and workspace https://issues.apache.org/jira/browse/MNG/component/12325615. There are two other issues that I am interested in; one displays Dependencies after Component/s, while the other displays None. I would also like to know whether the Affects Version/s section is important. I am using Maven 3.3.3 on my machine. Is it important to use a version of Maven that closely matches the affected version?
Working on MJAVADOC-400
I was looking at issue MJAVADOC-400 ( https://issues.apache.org/jira/browse/MJAVADOC-400). I have been working potential fix, I just want to check in before I put all the polish on it and submit it. The current behavior of the plugin is if one of the aggregate goals is targeted, javadoc is only generated if the project is the execution root. In that case, the javadoc for all the reactor projects are aggregated into the result. If the project in question is not the execution root (i.e. it is a module or grand-module (etc.) of the root project) then the javadoc is not generated and no error is reported. I have not been able to determine the reasoning behind the above behavior, except that if non-execution root projects were allowed to execute then as written the plugin would pull in all the javadoc from all the reactor projects, resulting in different results depending on what reactor projects were pulled in by different roots. But in my mind that is just a bug in the implementation, not a reason to prevent execution on module projects. So, with the goal of preserving the current behavior when javadoc was executed by the current code, and the goal of generating the same javadoc on a project whether it is the execution root, a module or a sub-sub-module, etc., I propose that instead of pulling in all reactor projects to generate javadoc, the plugin pulls in projects that are modules of the project and then recursively include the modules of those projects. I'll be working on implementing that fix and preparing a patch to submit. Thanks, Ray
