Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds, Rory O'Donnell Senior Quality Engineering Manager Java Platform Group Oracle EMEA , Block P5, East Point Business Park, Dublin 3 Phone: +353 (0)1 8033887
mng-5530 vs mng5530-mojo-execution-scope
Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: mng-5530 vs mng5530-mojo-execution-scope
The test name was not the issue, though not keeping with the pattern is, e.g. `mng-5530-blah-blah-blah` if you must but not `mng5530-blah-blah-blah` as all the other tests start with `mng-` so they are sorted consistently The real issue was that the test case itself broke when I switched the Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests run in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to resolve for the plugin side of the test case On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration- testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven JarSigner 1.3.1 and Apache Maven Jarsigner plugin 1.3.1
On Sun, 05 Jan 2014 22:33:28 +0100 Hervé BOUTEMY herve.bout...@free.fr wrote: I updated unit tests to avoid future regressions thanks. I also update the site to include the Karl doc typo fix ;) I miss a last binding vote, any PCM aroud ? tony. +1 Regards, Hervé Le vendredi 3 janvier 2014 21:42:14 Tony Chemit a écrit : Hi, Shame on me, I copy-paste a code and add a typo just after it :(. Maven shared JarSigner 1.3.1 The version 1.3.1 just fix an important bug while unsigning jar (ok it was exactly the goal of version 1.3...) We solved 1 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=19 867styleName=Html There is no more issues in JIRA left :) Staging repo: https://repository.apache.org/content/repositories/maven-001 https://repository.apache.org/content/repositories/maven-001/org/apache/mave n/shared/maven-jarsigner/1.3.1/maven-jarsigner-1.3.1-source-release.zip Source release checksum(s): maven-jarsigner-1.3.1-source-release.zip sha1: 6404f86d081b8edb3b3f8679eaec0a6c8730c5ce Staging site: http://maven.apache.org/shared-archives/maven-jarsigner-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 my +1 Apache Maven Jarsigner plugin 1.3.1 --- Follow maven-jarsigner shared component + add an IT that prove this time it will work! We solved 1 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990version=198 68styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=MJARSIGNE Rstatus=1 Staging repo: https://repository.apache.org/content/repositories/maven-001 https://repository.apache.org/content/repositories/maven-001/org/apache/mave n/plugins/maven-jarsigner-plugin/1.3.1/maven-jarsigner-plugin-1.3.1-source-r elease.zip Source release checksum(s): maven-jarsigner-plugin-1.3.1-source-release.zip sha1: 2e9d2a9a3ac55e7ee1cbaa63029389af1fec2da1 Staging site: http://maven.apache.org/plugins-archives/maven-jarsigner-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 my +1 tony. - 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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven JarSigner 1.3.1 and Apache Maven Jarsigner plugin 1.3.1
+1 (binding) On 4 January 2014 14:54, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, maven-jarsigner 1.3.1: * Checked the sha1 sum: Ok. * Unpacked source package and tried the following: * mvn verify * Maven 2.2.1 Ok. * Maven 3.0.5 Ok. * Maven 3.1 Ok. * Maven 3.1.1 Ok. Environment: Java version: 1.7.0_21, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_ 21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.8.5, arch: x86_64, family: mac So +1 from me for maven-jarsigner. Found only a small typo on the index.html page: At the end of the page it is mentioned: Now you can use the component to verify your signe jar: which in my opinion should be: Now you can use the component to verify your signed jar: Maven Jarsigner Plugin 1.3.1: * Checked the sha1 sum: Ok. * Unpacked source package and tried the following: * mvn -Prun-its clean verify * Maven 2.2.1 Ok. * Maven 3.0.5 Ok. * Maven 3.1 Ok. * Maven 3.1.1 Ok. Environment the same as above. +1 from me for maven-jarsigner-plugin 1.3.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
Re: mng-5530 vs mng5530-mojo-execution-scope
+1 On the original name I just made another IT and it's definitely much clearer with the JIRA id and a short blurb. I see this as an improvement. On Jan 6, 2014, at 7:51 AM, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: mng-5530 vs mng5530-mojo-execution-scope
On Jan 6, 2014, at 9:07 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The test name was not the issue, though not keeping with the pattern is, e.g. `mng-5530-blah-blah-blah` if you must but not `mng5530-blah-blah-blah` as all the other tests start with `mng-` so they are sorted consistently Sure, that's a valid point. But I think the extra information is good. I don't see anything wrong with mng--short-description as a pattern. The real issue was that the test case itself broke when I switched the Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests run in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to resolve for the plugin side of the test case The version of Maven you are running needs to be installed in the local repo you are running the ITs against, but I ran them all day yesterday without issue. I'll fetch and give it a whirl. On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration- testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: mng-5530 vs mng5530-mojo-execution-scope
yes but keep the dash between the mng and the mng number On 6 January 2014 15:24, Jason van Zyl ja...@tesla.io wrote: +1 On the original name I just made another IT and it's definitely much clearer with the JIRA id and a short blurb. I see this as an improvement. On Jan 6, 2014, at 7:51 AM, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
maven pull request: [MNG-5075] MavenProject.getParent throws undocumented I...
Github user jglick closed the pull request at: https://github.com/apache/maven/pull/8 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: mng-5530 vs mng5530-mojo-execution-scope
The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for now... but is still hacky... On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote: On Jan 6, 2014, at 9:07 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The test name was not the issue, though not keeping with the pattern is, e.g. `mng-5530-blah-blah-blah` if you must but not `mng5530-blah-blah-blah` as all the other tests start with `mng-` so they are sorted consistently Sure, that's a valid point. But I think the extra information is good. I don't see anything wrong with mng--short-description as a pattern. The real issue was that the test case itself broke when I switched the Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests run in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to resolve for the plugin side of the test case The version of Maven you are running needs to be installed in the local repo you are running the ITs against, but I ran them all day yesterday without issue. I'll fetch and give it a whirl. On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration- testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: mng-5530 vs mng5530-mojo-execution-scope
Yup, I agree. On Jan 6, 2014, at 10:39 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: yes but keep the dash between the mng and the mng number On 6 January 2014 15:24, Jason van Zyl ja...@tesla.io wrote: +1 On the original name I just made another IT and it's definitely much clearer with the JIRA id and a short blurb. I see this as an improvement. On Jan 6, 2014, at 7:51 AM, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: mng-5530 vs mng5530-mojo-execution-scope
We don't really have an easy way to specify an interim version that needs to be tested. Once 3.2 is release it can be updated and locked down. If we always want to test the version exercised by the ITs we'll have to figure that out. Maybe as simple as exposing a property we can interpolate into the POM. On Jan 6, 2014, at 10:40 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for now... but is still hacky... On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote: On Jan 6, 2014, at 9:07 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The test name was not the issue, though not keeping with the pattern is, e.g. `mng-5530-blah-blah-blah` if you must but not `mng5530-blah-blah-blah` as all the other tests start with `mng-` so they are sorted consistently Sure, that's a valid point. But I think the extra information is good. I don't see anything wrong with mng--short-description as a pattern. The real issue was that the test case itself broke when I switched the Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests run in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to resolve for the plugin side of the test case The version of Maven you are running needs to be installed in the local repo you are running the ITs against, but I ran them all day yesterday without issue. I'll fetch and give it a whirl. On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote: Stephen, I would prefer to keep the original test name, i.e. mng5530-mojo-execution-scope. Having both the JIRA issue id and short description of the test makes it much easier to understand what the test is supposed to do and still be able to find any additional information if needed. Can you explain what problems you see with the original test name? https://git-wip-us.apache.org/repos/asf?p=maven-integration- testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: mng-5530 vs mng5530-mojo-execution-scope
I looked into that... the issue here is that the code does not promise to
be able to give you a version of Maven, IOW there are some cases where the
test harness will just give up and say Oh the maven version is null
because I can't figure it out... I'll ignore all skips now... good luck...
Otherwise the way is to mage getMavenVersion() protected and then you can
do verifier.setSystemProperty(foo,getMavenVersion()); and then use ${foo}
and rely on it being expanded at run time from the system properties...
nastyish but will work... we cannot use filtering as the target maven
version is not available until the test suite starts running...
On 6 January 2014 15:46, Jason van Zyl ja...@tesla.io wrote:
We don't really have an easy way to specify an interim version that needs
to be tested. Once 3.2 is release it can be updated and locked down. If we
always want to test the version exercised by the ITs we'll have to figure
that out. Maybe as simple as exposing a property we can interpolate into
the POM.
On Jan 6, 2014, at 10:40 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I
changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for
now... but is still hacky...
On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote:
On Jan 6, 2014, at 9:07 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The test name was not the issue, though not keeping with the pattern
is,
e.g. `mng-5530-blah-blah-blah` if you must but not
`mng5530-blah-blah-blah`
as all the other tests start with `mng-` so they are sorted
consistently
Sure, that's a valid point. But I think the extra information is good. I
don't see anything wrong with mng--short-description as a pattern.
The real issue was that the test case itself broke when I switched the
Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests
run
in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to
resolve for the plugin side of the test case
The version of Maven you are running needs to be installed in the local
repo you are running the ITs against, but I ran them all day yesterday
without issue. I'll fetch and give it a whirl.
On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote:
Stephen,
I would prefer to keep the original test name, i.e.
mng5530-mojo-execution-scope. Having both the JIRA issue id and short
description of the test makes it much easier to understand what the
test
is supposed to do and still be able to find any additional information
if needed.
Can you explain what problems you see with the original test name?
https://git-wip-us.apache.org/repos/asf?p=maven-integration-
testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47
--
Regards,
Igor
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Problem with maven changes plugin Jira report
The Jira report (and maybe others) is failing to substitute the project.version
into the title line of the generated report.
It produces (here's the html source listing):
...
div class=xleft
span id=publishDateLast Published: 2013-12-27/span
nbsp;| span id=projectVersionVersion:
${project.version}/span
/div
div class=xright
The ** ${project.version} ** I think is supposed be substituted, somewhere
along the way, with a maven project version, but it's instead showing up as
the literal characters ${project.version} in the browser.
I took a look, but lost my way in some common Maven reporting code.
Should I file a Jira? Any hints on where to look to see how to fix?
-Marshall Schor
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: mng-5530 vs mng5530-mojo-execution-scope
In this particular case once we release 3.2.0 then [3.2.0,) will be sufficient
and not need to be changed.
On Jan 6, 2014, at 10:51 AM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
I looked into that... the issue here is that the code does not promise to
be able to give you a version of Maven, IOW there are some cases where the
test harness will just give up and say Oh the maven version is null
because I can't figure it out... I'll ignore all skips now... good luck...
Otherwise the way is to mage getMavenVersion() protected and then you can
do verifier.setSystemProperty(foo,getMavenVersion()); and then use ${foo}
and rely on it being expanded at run time from the system properties...
nastyish but will work... we cannot use filtering as the target maven
version is not available until the test suite starts running...
On 6 January 2014 15:46, Jason van Zyl ja...@tesla.io wrote:
We don't really have an easy way to specify an interim version that needs
to be tested. Once 3.2 is release it can be updated and locked down. If we
always want to test the version exercised by the ITs we'll have to figure
that out. Maybe as simple as exposing a property we can interpolate into
the POM.
On Jan 6, 2014, at 10:40 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I
changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for
now... but is still hacky...
On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote:
On Jan 6, 2014, at 9:07 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The test name was not the issue, though not keeping with the pattern
is,
e.g. `mng-5530-blah-blah-blah` if you must but not
`mng5530-blah-blah-blah`
as all the other tests start with `mng-` so they are sorted
consistently
Sure, that's a valid point. But I think the extra information is good. I
don't see anything wrong with mng--short-description as a pattern.
The real issue was that the test case itself broke when I switched the
Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests
run
in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to
resolve for the plugin side of the test case
The version of Maven you are running needs to be installed in the local
repo you are running the ITs against, but I ran them all day yesterday
without issue. I'll fetch and give it a whirl.
On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote:
Stephen,
I would prefer to keep the original test name, i.e.
mng5530-mojo-execution-scope. Having both the JIRA issue id and short
description of the test makes it much easier to understand what the
test
is supposed to do and still be able to find any additional information
if needed.
Can you explain what problems you see with the original test name?
https://git-wip-us.apache.org/repos/asf?p=maven-integration-
testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47
--
Regards,
Igor
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Re: mng-5530 vs mng5530-mojo-execution-scope
I think once we release 3.2.0 then we can revert back to just 3.2.0 and not
the version range
On 6 January 2014 16:16, Jason van Zyl ja...@tesla.io wrote:
In this particular case once we release 3.2.0 then [3.2.0,) will be
sufficient and not need to be changed.
On Jan 6, 2014, at 10:51 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I looked into that... the issue here is that the code does not promise to
be able to give you a version of Maven, IOW there are some cases where
the
test harness will just give up and say Oh the maven version is null
because I can't figure it out... I'll ignore all skips now... good
luck...
Otherwise the way is to mage getMavenVersion() protected and then you can
do verifier.setSystemProperty(foo,getMavenVersion()); and then use
${foo}
and rely on it being expanded at run time from the system properties...
nastyish but will work... we cannot use filtering as the target maven
version is not available until the test suite starts running...
On 6 January 2014 15:46, Jason van Zyl ja...@tesla.io wrote:
We don't really have an easy way to specify an interim version that
needs
to be tested. Once 3.2 is release it can be updated and locked down. If
we
always want to test the version exercised by the ITs we'll have to
figure
that out. Maybe as simple as exposing a property we can interpolate into
the POM.
On Jan 6, 2014, at 10:40 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I
changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for
now... but is still hacky...
On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote:
On Jan 6, 2014, at 9:07 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The test name was not the issue, though not keeping with the pattern
is,
e.g. `mng-5530-blah-blah-blah` if you must but not
`mng5530-blah-blah-blah`
as all the other tests start with `mng-` so they are sorted
consistently
Sure, that's a valid point. But I think the extra information is
good. I
don't see anything wrong with mng--short-description as a pattern.
The real issue was that the test case itself broke when I switched
the
Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests
run
in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts
to
resolve for the plugin side of the test case
The version of Maven you are running needs to be installed in the
local
repo you are running the ITs against, but I ran them all day yesterday
without issue. I'll fetch and give it a whirl.
On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote:
Stephen,
I would prefer to keep the original test name, i.e.
mng5530-mojo-execution-scope. Having both the JIRA issue id and
short
description of the test makes it much easier to understand what the
test
is supposed to do and still be able to find any additional
information
if needed.
Can you explain what problems you see with the original test name?
https://git-wip-us.apache.org/repos/asf?p=maven-integration-
testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47
--
Regards,
Igor
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Re: mng-5530 vs mng5530-mojo-execution-scope
On 1/6/2014, 11:35, Stephen Connolly wrote:
I think once we release 3.2.0 then we can revert back to just 3.2.0 and not
the version range
This was my plan. Sorry I didn't communicate this better.
--
Regards,
Igor
On 6 January 2014 16:16, Jason van Zyl ja...@tesla.io wrote:
In this particular case once we release 3.2.0 then [3.2.0,) will be
sufficient and not need to be changed.
On Jan 6, 2014, at 10:51 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I looked into that... the issue here is that the code does not promise to
be able to give you a version of Maven, IOW there are some cases where
the
test harness will just give up and say Oh the maven version is null
because I can't figure it out... I'll ignore all skips now... good
luck...
Otherwise the way is to mage getMavenVersion() protected and then you can
do verifier.setSystemProperty(foo,getMavenVersion()); and then use
${foo}
and rely on it being expanded at run time from the system properties...
nastyish but will work... we cannot use filtering as the target maven
version is not available until the test suite starts running...
On 6 January 2014 15:46, Jason van Zyl ja...@tesla.io wrote:
We don't really have an easy way to specify an interim version that
needs
to be tested. Once 3.2 is release it can be updated and locked down. If
we
always want to test the version exercised by the ITs we'll have to
figure
that out. Maybe as simple as exposing a property we can interpolate into
the POM.
On Jan 6, 2014, at 10:40 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The issue was he had hard-coded 3.1.2-SNAPSHOT in the test resource. I
changed that to [3.1.2-SNAPSHOT,) which gets 3.2.0-SNAPSHOT working for
now... but is still hacky...
On 6 January 2014 15:36, Jason van Zyl ja...@tesla.io wrote:
On Jan 6, 2014, at 9:07 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The test name was not the issue, though not keeping with the pattern
is,
e.g. `mng-5530-blah-blah-blah` if you must but not
`mng5530-blah-blah-blah`
as all the other tests start with `mng-` so they are sorted
consistently
Sure, that's a valid point. But I think the extra information is
good. I
don't see anything wrong with mng--short-description as a pattern.
The real issue was that the test case itself broke when I switched
the
Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests
run
in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts
to
resolve for the plugin side of the test case
The version of Maven you are running needs to be installed in the
local
repo you are running the ITs against, but I ran them all day yesterday
without issue. I'll fetch and give it a whirl.
On 6 January 2014 12:51, Igor Fedorenko i...@ifedorenko.com wrote:
Stephen,
I would prefer to keep the original test name, i.e.
mng5530-mojo-execution-scope. Having both the JIRA issue id and
short
description of the test makes it much easier to understand what the
test
is supposed to do and still be able to find any additional
information
if needed.
Can you explain what problems you see with the original test name?
https://git-wip-us.apache.org/repos/asf?p=maven-integration-
testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47
--
Regards,
Igor
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
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: git commit: MNG-5557: IT to test the constraining of the reactor with --projects - rename the mojo execution scope directory to have a small description
Is this the correct commit message?
On 6 January 2014 16:57, jvan...@apache.org wrote:
Updated Branches:
refs/heads/master fa0f5050b - c01884d6d
MNG-5557: IT to test the constraining of the reactor with --projects
- rename the mojo execution scope directory to have a small description
Project:
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/repo
Commit:
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/c01884d6
Tree:
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/tree/c01884d6
Diff:
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/diff/c01884d6
Branch: refs/heads/master
Commit: c01884d6d4dbaca328edf6d8e238e6959449f25b
Parents: fa0f505
Author: Jason van Zyl ja...@tesla.io
Authored: Mon Jan 6 11:55:57 2014 -0500
Committer: Jason van Zyl ja...@tesla.io
Committed: Mon Jan 6 11:55:57 2014 -0500
--
.../MavenITmng5530MojoExecutionScopeTest.java | 2 +-
...MavenITmng5557ProperlyRestrictedReactor.java | 65 ++
.../mng-5530-mojo-execution-scope/basic/pom.xml | 51 +++
.../plugin/pom.xml | 95
.../TestExecutionScopeMojo.java | 40 +
.../TestExecutionScopedComponent.java | 90 +++
.../src/test/resources/mng-5530/basic/pom.xml | 51 ---
.../src/test/resources/mng-5530/plugin/pom.xml | 95
.../TestExecutionScopeMojo.java | 40 -
.../TestExecutionScopedComponent.java | 90 ---
.../pom.xml | 15
.../project-0/pom.xml | 31 +++
.../java/org/apache/maven/its/mng5557/App.java | 13 +++
.../org/apache/maven/its/mng5557/AppTest.java | 38
.../project-1/pom.xml | 26 ++
.../java/org/apache/maven/its/mng5557/App.java | 13 +++
.../org/apache/maven/its/mng5557/AppTest.java | 38
.../project-2/pom.xml | 26 ++
.../java/org/apache/maven/its/mng5557/App.java | 13 +++
.../org/apache/maven/its/mng5557/AppTest.java | 38
.../project-3/pom.xml | 26 ++
.../java/org/apache/maven/its/mng5557/App.java | 13 +++
.../org/apache/maven/its/mng5557/AppTest.java | 38
.../project-4/pom.xml | 26 ++
.../java/org/apache/maven/its/mng5557/App.java | 13 +++
.../org/apache/maven/its/mng5557/AppTest.java | 38
26 files changed, 747 insertions(+), 277 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/blob/c01884d6/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5530MojoExecutionScopeTest.java
--
diff --git
a/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5530MojoExecutionScopeTest.java
b/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5530MojoExecutionScopeTest.java
index 6cac091..f9b45be 100644
---
a/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5530MojoExecutionScopeTest.java
+++
b/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5530MojoExecutionScopeTest.java
@@ -34,7 +34,7 @@ public class MavenITmng5530MojoExecutionScopeTest
public void test_copyfiles()
throws Exception
{
-File testDir = ResourceExtractor.simpleExtractResources(
getClass(), /mng-5530);
+File testDir = ResourceExtractor.simpleExtractResources(
getClass(), /mng-5530-mojo-execution-scope);
File pluginDir = new File( testDir, plugin );
File projectDir = new File( testDir, basic );
http://git-wip-us.apache.org/repos/asf/maven-integration-testing/blob/c01884d6/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5557ProperlyRestrictedReactor.java
--
diff --git
a/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5557ProperlyRestrictedReactor.java
b/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5557ProperlyRestrictedReactor.java
new file mode 100644
index 000..2d2ce05
--- /dev/null
+++
b/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5557ProperlyRestrictedReactor.java
@@ -0,0 +1,65 @@
+package org.apache.maven.it;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy
Re: [VOTE] Apache Maven SCM 1.9 (take 2)
Hey guys, I finally started the release of scm-1.9 - I was able to stage the artifacts, but now , following this process http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage I would have to close the staging repo (as described here https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository), but I do not see the repo I expected. My guess is, that I just don’t have the permission to see it - who might be able to grant me the correct perissions? thanks Domi On 03.01.2014, at 14:51, Dominik Bartholdi d...@fortysix.ch wrote: I was hopping for a drysuite :) On 03.01.2014, at 11:49, Stephen Connolly stephen.alan.conno...@gmail.com wrote: And better to get your feet wet early after all ;-) On 3 January 2014 10:43, Robert Scholte rfscho...@apache.org wrote: Domi, you knew that day would come sooner or later, right? ;) Op Fri, 03 Jan 2014 08:58:59 +0100 schreef Dominik Bartholdi d...@fortysix.ch: Thanks Robert, I’ll give it a go, but its gona be my first “official maven plugin release”, so please be patient :) /Domi On 30.12.2013, at 13:07, Robert Scholte rfscho...@apache.org wrote: Personally I think it is important that the source-releases.zip can at least be built somewhere. The more the better of course. If Windows isn't the right OS, then that's fine for me. @Domi, if nobody sees any blockers, could you start a take 3? thanks, Robert Op Fri, 27 Dec 2013 10:00:07 +0100 schreef Dominik Bartholdi d...@fortysix.ch: Hi Robert, I had a go too, on Mac everything is OK - but on Win with SVN 1.8.5 the maven-scm-plugin failed to create the repository :( regards Domi On 24.12.2013, at 22:26, Robert Scholte rfscho...@apache.org wrote: Hi, I've fixed SCM-737, which means that the source-releases.zip should match all the files project files again. If I'm correct this means that the reason for the -1 vote has been solved. However, on my Windows machine I don't get the test for the maven-scm-plugin to succeed. The svnadmin fails to create/load a repository. I've tried svn 1.6, 1.7 and 1.8, all failing with equivalent failures. Could somebody else verify the current trunk? thanks, Robert Op Tue, 03 Dec 2013 03:10:39 +0100 schreef Hervé BOUTEMY herve.bout...@free.fr: http://jira.codehaus.org/browse/SCM-737 created Le mardi 3 décembre 2013 03:05:17 Hervé BOUTEMY a écrit : +1 need to find a workaround for CVS provider unit tests later Regards, Hervé Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit : Hi, We fixed 11 issues. The new feature is the jgit provider (based on jgit). Details: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10527version=1 87 83 Staging repository: https://repository.apache.org/content/repositories/maven-002/ Staged site: http://maven.apache.org/scm-archives/scm-LATEST/ Sources release: https://repository.apache.org/content/repositories/maven- 002/org/apache/ma ve n/scm/maven-scm/1.9/maven-scm-1.9-source-release.zip Vote open for 72H [+1] [0] [-1] Thanks - 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 - 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 SCM 1.9 (take 2)
Did you log into repository.apache.org? On Mon, Jan 6, 2014 at 1:44 PM, Dominik Bartholdi d...@fortysix.ch wrote: Hey guys, I finally started the release of scm-1.9 - I was able to stage the artifacts, but now , following this process http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage I would have to close the staging repo (as described here https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository), but I do not see the repo I expected. My guess is, that I just don’t have the permission to see it - who might be able to grant me the correct perissions? thanks Domi On 03.01.2014, at 14:51, Dominik Bartholdi d...@fortysix.ch wrote: I was hopping for a drysuite :) On 03.01.2014, at 11:49, Stephen Connolly stephen.alan.conno...@gmail.com wrote: And better to get your feet wet early after all ;-) On 3 January 2014 10:43, Robert Scholte rfscho...@apache.org wrote: Domi, you knew that day would come sooner or later, right? ;) Op Fri, 03 Jan 2014 08:58:59 +0100 schreef Dominik Bartholdi d...@fortysix.ch: Thanks Robert, I’ll give it a go, but its gona be my first “official maven plugin release”, so please be patient :) /Domi On 30.12.2013, at 13:07, Robert Scholte rfscho...@apache.org wrote: Personally I think it is important that the source-releases.zip can at least be built somewhere. The more the better of course. If Windows isn't the right OS, then that's fine for me. @Domi, if nobody sees any blockers, could you start a take 3? thanks, Robert Op Fri, 27 Dec 2013 10:00:07 +0100 schreef Dominik Bartholdi d...@fortysix.ch: Hi Robert, I had a go too, on Mac everything is OK - but on Win with SVN 1.8.5 the maven-scm-plugin failed to create the repository :( regards Domi On 24.12.2013, at 22:26, Robert Scholte rfscho...@apache.org wrote: Hi, I've fixed SCM-737, which means that the source-releases.zip should match all the files project files again. If I'm correct this means that the reason for the -1 vote has been solved. However, on my Windows machine I don't get the test for the maven-scm-plugin to succeed. The svnadmin fails to create/load a repository. I've tried svn 1.6, 1.7 and 1.8, all failing with equivalent failures. Could somebody else verify the current trunk? thanks, Robert Op Tue, 03 Dec 2013 03:10:39 +0100 schreef Hervé BOUTEMY herve.bout...@free.fr: http://jira.codehaus.org/browse/SCM-737 created Le mardi 3 décembre 2013 03:05:17 Hervé BOUTEMY a écrit : +1 need to find a workaround for CVS provider unit tests later Regards, Hervé Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit : Hi, We fixed 11 issues. The new feature is the jgit provider (based on jgit). Details: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10527version=1 87 83 Staging repository: https://repository.apache.org/content/repositories/maven-002/ Staged site: http://maven.apache.org/scm-archives/scm-LATEST/ Sources release: https://repository.apache.org/content/repositories/maven- 002/org/apache/ma ve n/scm/maven-scm/1.9/maven-scm-1.9-source-release.zip Vote open for 72H [+1] [0] [-1] Thanks - 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 - 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 SCM 1.9 (take 2)
Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven SCM 1.9 (take 2)
Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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] Release Maven JarSigner 1.3.1 and Apache Maven Jarsigner plugin 1.3.1
Hi, The vote has passed with the following result: +1 (binding): Hervé BOUTEMY, Olivier Lamy, Stephen Connolly +1 (non binding): Karl Heinz Marbaise, Tony CHEMIT I will promote the artifacts to the central repo. tony. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Shared Jarsigner 1.3.1 Released
The Maven team is pleased to announce the release of the Apache Maven Jarsigner, version 1.3.1 This component provides some utilities to sign/verify jars/files in your Mojos. http://maven.apache.org/shared/maven-jarsigner/ To use the Maven Jarsigner, add the following dependency to your project: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-jarsigner/artifactId version1.3.1/version /dependency Release Notes - Maven Shared Components - Version maven-jarsigner-1.3.1 ** Bug * [MSHARED-315] - Unsign jars are still not ok Enjoy, -The Maven team tony. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Jarsigner Plugin 1.3.1 Released
The Maven team is pleased to announce the release of the Maven Jarsigner Plugin, version 1.3.1. This plugin signs and verifies the project artifacts using the jarsigner tool. See the plugin's site for more details: http://maven.apache.org/plugins/maven-jarsigner-plugin/ This plugin is meant to supercede the existing jar:sign and jar:verify goals from the Maven Jar Plugin which will be deprecated in a future release. To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jarsigner-plugin/artifactId version1.3.1/version executions ... /executions /plugin Release Notes - Maven Jar Signer Plugin - Version 1.3.1 ** Bug * [MJARSIGNER-33] - Sign already signed jar still does not work Enjoy, The Maven team. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Jarsigner Plugin 1.3.1 Released
The Maven team is pleased to announce the release of the Maven Jarsigner Plugin, version 1.3.1. This plugin signs and verifies the project artifacts using the jarsigner tool. See the plugin's site for more details: http://maven.apache.org/plugins/maven-jarsigner-plugin/ This plugin is meant to supercede the existing jar:sign and jar:verify goals from the Maven Jar Plugin which will be deprecated in a future release. To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jarsigner-plugin/artifactId version1.3.1/version executions ... /executions /plugin Release Notes - Maven Jar Signer Plugin - Version 1.3.1 ** Bug * [MJARSIGNER-33] - Sign already signed jar still does not work Enjoy, The Maven team. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven SCM 1.9 (take 2)
My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 SCM 1.9 (take 2)
Just be patient, it is a huge commit. All changes to the documentation of the whole(!) SCM site are committed at once. Robert Op Mon, 06 Jan 2014 22:23:59 +0100 schreef Dominik Bartholdi d...@fortysix.ch: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 SCM 1.9 (take 2)
I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 Ecetera: http://ecetera.com.au 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 SCM 1.9 (take 2)
Hi Oliver, I tried over and over again - it just does not work out on my Mac - I’m not able to publish the Documentation. Would be great if you could do it - everything else (the artifacts) are already done (https://repository.apache.org/content/repositories/maven-009/). thanks Domi On 07.01.2014, at 01:52, Olivier Lamy ol...@apache.org wrote: I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 Ecetera: http://ecetera.com.au 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: [VOTE] Apache Maven SCM 1.9 (take 2)
done: http://maven.apache.org/scm-archives/scm-LATEST/ On 7 January 2014 15:52, Dominik Bartholdi d...@fortysix.ch wrote: Hi Oliver, I tried over and over again - it just does not work out on my Mac - I’m not able to publish the Documentation. Would be great if you could do it - everything else (the artifacts) are already done (https://repository.apache.org/content/repositories/maven-009/). thanks Domi On 07.01.2014, at 01:52, Olivier Lamy ol...@apache.org wrote: I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 Ecetera: http://ecetera.com.au 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 Ecetera: http://ecetera.com.au 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 SCM 1.9 (take 2)
If you're in europe you should probably set the us svn server in your hosts file; someone here will give you the magic settings :) I tend to cross my fingers and let site publication run overnight. All the different site publication strategies have been flawed in one way or another, this latest strategy is perhaps the most flawed of them all. Kristian 2014/1/7 Dominik Bartholdi d...@fortysix.ch Hi Oliver, I tried over and over again - it just does not work out on my Mac - I’m not able to publish the Documentation. Would be great if you could do it - everything else (the artifacts) are already done ( https://repository.apache.org/content/repositories/maven-009/). thanks Domi On 07.01.2014, at 01:52, Olivier Lamy ol...@apache.org wrote: I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn: https://svn.apache.org/repos/infra/websites/production/maven/content/scm-archives/scm-LATEST... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.commit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 Ecetera: http://ecetera.com.au 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: [VOTE] Apache Maven SCM 1.9 (take 2)
in the short term, Olivier did the publication: job done but let's understand what does not work: did you get a failure? Or only you stopped the publication process after some (long) time? Regards, Hervé Le mardi 7 janvier 2014 05:52:16 Dominik Bartholdi a écrit : Hi Oliver, I tried over and over again - it just does not work out on my Mac - I’m not able to publish the Documentation. Would be great if you could do it - everything else (the artifacts) are already done (https://repository.apache.org/content/repositories/maven-009/). thanks Domi On 07.01.2014, at 01:52, Olivier Lamy ol...@apache.org wrote: I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/con tent/scm-archives/scm-LATEST ... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.co mmit [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 SCM 1.9 (take 2)
IMHO the latest strategy is good for main site content: ie we can now publish a modification in plugins list, for example, in a few minutes, with a site being build in a consistent manner (no more anybody frightened to break the site because something in his conf is different) but for component reference documentation, yes, the actual solution is really unfriendly: large multi-modules take hours to publish from local machine, and network performance to svn is a key factor If anybody has an idea on how to improve this second scenario... Regards, Hervé Le mardi 7 janvier 2014 07:51:57 Kristian Rosenvold a écrit : If you're in europe you should probably set the us svn server in your hosts file; someone here will give you the magic settings :) I tend to cross my fingers and let site publication run overnight. All the different site publication strategies have been flawed in one way or another, this latest strategy is perhaps the most flawed of them all. Kristian 2014/1/7 Dominik Bartholdi d...@fortysix.ch Hi Oliver, I tried over and over again - it just does not work out on my Mac - I’m not able to publish the Documentation. Would be great if you could do it - everything else (the artifacts) are already done ( https://repository.apache.org/content/repositories/maven-009/). thanks Domi On 07.01.2014, at 01:52, Olivier Lamy ol...@apache.org wrote: I don't know if you stop trying this but if needed I can do it for you, I use an external ci server to not block my laptop and be able to continue various music, videos etc... Just let me know. On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote: My next problem… does any one have any idea? Publishing the page always hangs here (more then 30 Minutes, actually never ends...): mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x …. [INFO] [INFO] Building Maven SCM 1.9 [INFO] [INFO] [INFO] --- maven-scm-publish-plugin:1.0-beta-2:publish-scm (default-cli) @ maven-scm --- [WARNING] No output encoding, defaulting to UTF-8. [INFO] Updating the pub tree from scm:svn: https://svn.apache.org/repos/infra/websites/production/maven/content/scm-a rchives/scm-LATEST... [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive update /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST [INFO] changeSets [ null null Updating '.':, 0 null ] [INFO] Updating content... [INFO] Publish files: 0 addition(s), 1815 update(s), 0 delete(s) [INFO] Checking in SCM... [INFO] Checking in to the scm [INFO] Executing: /bin/sh -c cd /Users/domi/maven-sites/scm-archives/scm-LATEST svn --username imod --password '*' --no-auth-cache --non-interactive commit --file /var/folders/rz/649mxsf10xvc64sc078ll0nhgn/T/maven-scm-1622187473.comm it [INFO] Working directory: /Users/domi/maven-sites/scm-archives/scm-LATEST ….HANGS HERE…. On 06.01.2014, at 19:59, Dominik Bartholdi d...@fortysix.ch wrote: Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it! Lets see how far I get now :) Domi On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote: Are you imod? If so, the repo is sitting there. I can close it for you, but you should try logging in and closing it for yourself. - 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 Ecetera: http://ecetera.com.au 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
