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
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 o
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 st
done: http://maven.apache.org/scm-archives/scm-LATEST/
On 7 January 2014 15:52, Dominik Bartholdi 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 a
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.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 wrote:
> My next problem…
> does any one have any idea?
> Pu
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
:
My next problem…
does any one have any idea?
Publishing the page always hangs here (more then 30 Mi
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
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
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
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 proje
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 un
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 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.
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..
Did you log into repository.apache.org?
On Mon, Jan 6, 2014 at 1:44 PM, Dominik Bartholdi 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-sta
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/C
Is this the correct commit message?
On 6 January 2014 16:57, 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
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 wrote:
In this particular case
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 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 Con
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
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 so
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):
...
Last Published: 2013-12-27
| Version:
${project.version}
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"...
Othe
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 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 wrote:
>
> On Jan 6, 2014, at 9:07 AM, Stephen Connolly <
> stephen.alan.conno...@gm
Yup, I agree.
On Jan 6, 2014, at 10:39 AM, Stephen Connolly
wrote:
> yes but keep the dash between the mng and the mng number
>
>
> On 6 January 2014 15:24, Jason van Zyl wrote:
>
>> +1 On the original name
>>
>> I just made another IT and it's definitely much clearer with the JIRA id
>> a
yes but keep the dash between the mng and the mng number
On 6 January 2014 15:24, Jason van Zyl 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 F
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
On Jan 6, 2014, at 9:07 AM, Stephen Connolly
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
+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 wrote:
> Stephen,
>
> I would prefer to keep the original test name, i.e.
> mng5530-mojo-execution-scope
+1 (binding)
On 4 January 2014 14:54, Karl Heinz Marbaise 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.
>
On Sun, 05 Jan 2014 22:33:28 +0100
Hervé BOUTEMY 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:
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
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 ex
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 th
34 matches
Mail list logo
