asfgit closed pull request #56:
URL: https://github.com/apache/maven-doxia/pull/56
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please
slachiewicz opened a new pull request #56:
URL: https://github.com/apache/maven-doxia/pull/56
…su.plexus
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Hello,
you need to escape : and \ in properties files:
org.slf4j.simpleLogger.logFile=E\:\\Mavenlogs\\Mavenlog.txt
BTW: this is a maven users question.
Gruss
Bernd
Am Thu, 20 Nov 2014 14:37:08 +
schrieb "Held, James E." :
> We'd like to log all maven activity to one common place by chan
We'd like to log all maven activity to one common place by changing the
logging.properties settings as shown below
org.slf4j.simpleLogger.showDateTime=false
org.slf4j.simpleLogger.showLogName=false
org.slf4j.simpleLogger.logFile=E:\Mavenlogs\Mavenlog.txt
Running under Win 7
Except it writes the
On Sun, Nov 2, 2014 at 10:41 AM, Hervé BOUTEMY wrote:
> Le dimanche 2 novembre 2014 09:51:14 Dennis Lundberg a écrit :
>> Looking into this I'm a bit puzzled. Version 1.1-SNAPSHOT of
>> maven-toolchains-plugin bind by default to the validate phase, but it
>> doesn't run unless I specify an executi
On Sat, Nov 1, 2014 at 10:41 AM, Dennis Lundberg wrote:
> Hi,
>
> I'm just starting to look at toolchains, with the goal of using Java 5 for
> jobs in latest Jenkins LTS version.
I have this working now.
> Here are a few reflections from what I've read so far.
>
> Great to have a toolchains refe
Le dimanche 2 novembre 2014 09:51:14 Dennis Lundberg a écrit :
> Looking into this I'm a bit puzzled. Version 1.1-SNAPSHOT of
> maven-toolchains-plugin bind by default to the validate phase, but it
> doesn't run unless I specify an execution for it. If I have it
> specified in build/plugins with co
Op Sat, 01 Nov 2014 14:56:56 +0100 schreef Hervé BOUTEMY
:
Le samedi 1 novembre 2014 23:45:32 Mark Derricutt a écrit :
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
> so that we can update it quickly when new plugins support it. The
others
> should just link to that page. The current inf
Le samedi 1 novembre 2014 10:41:40 Dennis Lundberg a écrit :
> The xsd used needs to be added
> to the main Maven site in the xsd directory.
+1 didn't see it wasn't there
I just did it: http://maven.apache.org/xsd/
>
> There are currently 3 wiki pages used or referenced. One Codehaus page [1]
> t
Le samedi 1 novembre 2014 23:45:32 Mark Derricutt a écrit :
> On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
> > so that we can update it quickly when new plugins support it. The others
> > should just link to that page. The current info on supporting
+1
this could be the mini guide, transforming
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
> so that we can update it quickly when new plugins support it. The others
> should just link to that page. The current info on supporting
For reference - my clojure-maven-plugin has supported it for ages now, and I
think I rolled that over onto m
Hi,
I'm just starting to look at toolchains, with the goal of using Java 5 for
jobs in latest Jenkins LTS version.
Here are a few reflections from what I've read so far.
Great to have a toolchains reference. It is in core site where it belongs.
It needs to be expanded with more explanations thou
I started improving documentation on toochains:
- in core [1]
- in m-toolchains-p [2]
feedback appreciated
next step is documenting how to create a custom toolchain: any pointer to some
working extra-toolchain (or even archetype, let's dream)?
Regards,
Hervé
[1] http://maven.apache.org/ref/3-
-1 on changing the JDK for M3.0.x
+1 for removal of the M3.1.x download from the mainpage
Op Thu, 30 Oct 2014 20:23:28 +0100 schreef Stephen Connolly
:
I am also -1 on changing the JDK for an existing line.
I seem to remember communicating that we would have at least a minor
version bump i
I am also -1 on changing the JDK for an existing line.
I seem to remember communicating that we would have at least a minor
version bump if we were upping the JVM requirement when communicating the
JVM version bump for 3.2.x
On Thursday, October 30, 2014, Dennis Lundberg wrote:
> I am -1 on c
I am -1 on changing JDK level in a patch version, either in core or another
one of our products. That is bad form, since the release is not backwards
compatible.
--
Dennis Lundberg
Den 29 okt 2014 08:04 skrev "Kristian Rosenvold" <
kristian.rosenv...@gmail.com>:
> Personally I think we could cons
+1 to switching to JDK 6 and for dropping the 3.1.x line.
Regards
Mirko
--
Sent from my mobile
On Oct 29, 2014 8:04 AM, "Kristian Rosenvold"
wrote:
> Personally I think we could consider releasing 3.0.6 with jdk6
> requirement and leave jdk5 altogether. And that's for plugins too :)
>
> Kristia
ding new features...which
> should be done in 3.2.X which is the recommended line for usage...
>
> Just removing the download i don't like it...better to make hint's on
> the pages to prefer 3.2.X....instead ...
>
>
> so my suggestion schedule:
>
> Make a final
Le jeudi 30 octobre 2014 10:08:19 Mark Derricutt a écrit :
> On 29 Oct 2014, at 19:33, Baptiste Mathus wrote:
> > Didn't double checked, but IIRC 3.1.1 still uses JDK5. 3.2.x uses JDK 6.
> > That may be a change you want to have in mind, though I personally don't
> > care about JDK 5.
>
> Another
On 29 Oct 2014, at 19:33, Baptiste Mathus wrote:
> Didn't double checked, but IIRC 3.1.1 still uses JDK5. 3.2.x uses JDK 6.
> That may be a change you want to have in mind, though I personally don't
> care about JDK 5.
Another +1 for promoting the use of toolchains.
--
Mark Derricutt
http://www
Am 2014-10-29 um 03:24 schrieb Hervé BOUTEMY:
we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
I see why we would release 3.0.6: Aether change force some users to stay to
3.0.x, and I started to define some backports I'd li
d ...
so my suggestion schedule:
Make a final release 3.0.6 JDK 5 based...
Define Maven 3.0.X line as only partially supported with security issues.
Define Maven 3.1.1. line as only partially supported with secority issues.
Define Maven 3.2.X line as supported line...
After 3 Months we could chnag
+1
On Wednesday, October 29, 2014, Hervé BOUTEMY wrote:
> we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
> which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
>
> I see why we would release 3.0.6: Aether change force some users to stay to
> 3.0.x, and I started to define s
+1
--
Olivier
On 29 Oct 2014 18:04, "Kristian Rosenvold"
wrote:
> Personally I think we could consider releasing 3.0.6 with jdk6
> requirement and leave jdk5 altogether. And that's for plugins too :)
>
> Kristian
>
>
> 2014-10-29 7:33 GMT+01:00 Baptiste Mathus :
> >> no outstanding change in 3.2
Personally I think we could consider releasing 3.0.6 with jdk6
requirement and leave jdk5 altogether. And that's for plugins too :)
Kristian
2014-10-29 7:33 GMT+01:00 Baptiste Mathus :
>> no outstanding change in 3.2.x that blocks 3.1.x users from upgrading to
> 3.2.x, isn't it?
>
> Didn't doubl
> no outstanding change in 3.2.x that blocks 3.1.x users from upgrading to
3.2.x, isn't it?
Didn't double checked, but IIRC 3.1.1 still uses JDK5. 3.2.x uses JDK 6.
That may be a change you want to have in mind, though I personally don't
care about JDK 5.
+1 indeed.
Cheers
Le mer. 29 oct. 2014
+1
29. Okt. 2014 03:24 skrev "Hervé BOUTEMY" følgende:
> we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
> which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
>
> I see why we would release 3.0.6: Aether change force some users to stay to
> 3.0.x, and I started to define som
+1 (non-binding)
Gary
On Tue, Oct 28, 2014 at 10:24 PM, Hervé BOUTEMY
wrote:
> we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
> which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
>
> I see why we would release 3.0.6: Aether change force some users to stay to
> 3.0.x, and
+1
On Wed, Oct 29, 2014 at 10:22 AM, Manfred Moser
wrote:
> +1 to that. Good idea imho..
>
> manfred
>
> Hervé BOUTEMY wrote on 28.10.2014 19:24:
>
> > we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
> > which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
> >
> > I see why
+1 to that. Good idea imho..
manfred
Hervé BOUTEMY wrote on 28.10.2014 19:24:
> we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
> which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
>
> I see why we would release 3.0.6: Aether change force some users to stay to
> 3.0.x,
we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
I see why we would release 3.0.6: Aether change force some users to stay to
3.0.x, and I started to define some backports I'd like to put in it [1]
But I don't see why we wou
How does 3.1.1 compare to 3.1.0 for your project ?
Kristian
11. Juni 2014 05:03 skrev "James Mao" følgende:
> Why Maven 3.1.1 is much faster than 3.0.X, what was the fix in the release?
>
>
>
> --
> View this message in context:
> http://maven.40175.n5
Why Maven 3.1.1 is much faster than 3.0.X, what was the fix in the release?
--
View this message in context:
http://maven.40175.n5.nabble.com/Release-Maven-3-1-1-tp5765942p5795322.html
Sent from the Maven Developers mailing list archive at Nabble.com
Hi,
I found that Maven 3.1.1 will try downloading the artifacts in parallel.
02:04:47 Downloading:
http://mycentral/content/repositories/central/javax/inject/javax.inject/1/javax.inject-1.pom
02:04:47 Downloaded:
http://mycentral/content/repositories/central/javax/inject/javax.inject/1
Sure, no problem.
On Oct 16, 2013, at 4:23 PM, Brett Porter wrote:
> Hi Jason,
>
> Would you mind sending this to annou...@maven.apache.org and
> annou...@apache.org? I didn't see it come through there.
>
> (Note that you have to send from jvan...@apache.org for those - they
> pre-filter to
Hi Jason,
Would you mind sending this to annou...@maven.apache.org and
annou...@apache.org? I didn't see it come through there.
(Note that you have to send from jvan...@apache.org for those - they pre-filter
to make life easier on the moderators)
Thanks,
Brett
On 05/10/2013, at 6:56 AM, Jason
fixed.
Sorry I don't have time to change the Jenkins script so use a lazy mode.
On 15 October 2013 07:34, Olivier Lamy wrote:
> For last release, I believe I used the easy/fast/lazy path to copy binaries
> in the layout Jenkins knows.
>
> --
> Olivier
>
> On Oct 15, 2013 7:31 AM, "jieryn" wrote:
For last release, I believe I used the easy/fast/lazy path to copy binaries
in the layout Jenkins knows.
--
Olivier
On Oct 15, 2013 7:31 AM, "jieryn" wrote:
> Greetings,
>
> On Mon, Oct 14, 2013 at 4:24 PM, Brett Porter wrote:
> > It's in the archive at the same location:
> https://archive.apac
Greetings,
On Mon, Oct 14, 2013 at 4:24 PM, Brett Porter wrote:
> It's in the archive at the same location:
> https://archive.apache.org/dist/maven/maven-3/3.1.1/binaries/
Thanks for that link.
> I thought Jenkins had been updated for the new layout.
As you can see from
https://github.com/jen
It's in the archive at the same location:
https://archive.apache.org/dist/maven/maven-3/3.1.1/binaries/
I thought Jenkins had been updated for the new layout.
- Brett
On 15/10/2013, at 7:05 AM, Jason van Zyl wrote:
> The standard download page?
>
> For example:
>
> http://apache.mirrors.pai
The standard download page?
For example:
http://apache.mirrors.pair.com/maven/maven-3/3.1.1/binaries/apache-maven-3.1.0-bin.tar.gz
or more generally:
http://apache.mirrors.pair.com/maven/maven-3/${version}/binaries/apache-maven-${version}-bin.tar.gz
Which would yield a more distributed load fr
Greetings,
On Mon, Oct 14, 2013 at 3:51 PM, Jason van Zyl wrote:
> Sorry, meant to say "why not use the standard download mechanism which is
> mirrored?"
> On Oct 14, 2013, at 12:50 PM, Jason van Zyl wrote:
>> Why use the standard download mechanism which is mirrored?
https://github.com/jenkin
Sorry, meant to say "why not use the standard download mechanism which is
mirrored?"
On Oct 14, 2013, at 12:50 PM, Jason van Zyl wrote:
> Someone else must have taken care of that for the 3.1.0 release as I don't
> recall doing anything specifically to populate that area.
>
> Why use the stan
Someone else must have taken care of that for the 3.1.0 release as I don't
recall doing anything specifically to populate that area.
Why use the standard download mechanism which is mirrored?
On Oct 14, 2013, at 12:02 PM, jieryn wrote:
> Greetings,
>
> On Fri, Oct 4, 2013 at 4:56 PM, Jason va
Greetings,
On Fri, Oct 4, 2013 at 4:56 PM, Jason van Zyl wrote:
> The Apache Maven Team is pleased to announce the release of 3.1.1
Why isn't it showing up like usual at
https://archive.apache.org/dist/maven/binaries/ ?
This affects Jenkins automatic tool installation.
On 5/10/2013, at 3:18 PM, Jason van Zyl wrote:
> Couldn't have done it without the Fredalizer.
+100. Good to see the release train rolling again.
Mark
signature.asc
Description: Message signed with OpenPGP using GPGMail
Couldn't have done it without the Fredalizer.
On Oct 4, 2013, at 8:40 PM, Fred Cooke wrote:
> Congratulations, Jason! :-)
>
>
> On Fri, Oct 4, 2013 at 10:56 PM, Jason van Zyl wrote:
>
>> Hi!
>>
>> The Apache Maven Team is pleased to announce the release of 3.1.1
>>
>> The release notes can
Congratulations, Jason! :-)
On Fri, Oct 4, 2013 at 10:56 PM, Jason van Zyl wrote:
> Hi!
>
> The Apache Maven Team is pleased to announce the release of 3.1.1
>
> The release notes can be found here:
> http://maven.apache.org/docs/3.1.1/release-notes.html
>
> The release can be downloaded from:
Hi!
The Apache Maven Team is pleased to announce the release of 3.1.1
The release notes can be found here:
http://maven.apache.org/docs/3.1.1/release-notes.html
The release can be downloaded from:
http://maven.apache.org/download.cgi
The changes in this release are as follows:
Bug:
[MNG-5459]
on=18968
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-065/
>
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
>
> Specifically the z
://repository.apache.org/content/repositories/maven-065/>
>>>
>>> The distributable binaries and sources for testing can be found here:
>>> https://repository.apache.org/**content/repositories/maven-**
>>> 065/org/apache/maven/apache-**maven/3.1.1/<https://r
All good, haven't released it yet.
On Oct 2, 2013, at 11:19 PM, Mark Derricutt wrote:
> So what happened in the end with the Maven 3.1.1 release? I saw lots of +1's
> but nothing to say it passed, or failed?
>
> -- Mark Derricutt ( m...@talios.com )
> — twitter: h
So what happened in the end with the Maven 3.1.1 release? I saw lots of +1's
but nothing to say it passed, or failed?
-- Mark Derricutt ( m...@talios.com )
— twitter: https://twitter.com/talios
— podcast: http://www.illegalargument.com
— blog: http://www.theoryinpractice.net
— google+:
g/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip
https://repository.apache.org/content/rep
/content/repositories/maven-065/
> >
> > The distributable binaries and sources for testing can be found here:
> > https://repository.apache.org/content/repositories/maven-065/org/apache/ma
> > ven/apache-maven/3.1.1/
> >
> > Specifically the zip, tarball, and s
Did you/can you check the contents of the bad jars ?
Kristian
2013/9/26 jieryn :
> Greetings,
>
> On Wed, Sep 25, 2013 at 11:05 PM, Jason van Zyl wrote:
>> Does 3.1.0 not display this behaviour?
>>
>> On Sep 25, 2013, at 6:41 PM, jieryn wrote:
>>> Archive for required library:
>>> '$HOME/.m2/re
Greetings,
On Wed, Sep 25, 2013 at 11:05 PM, Jason van Zyl wrote:
> Does 3.1.0 not display this behaviour?
>
> On Sep 25, 2013, at 6:41 PM, jieryn wrote:
>> Archive for required library:
>> '$HOME/.m2/repository/$GROUPID/$ARTIFACTID/$VERSION/$FINALNAME.jar' in
>> project 'test' cannot be read or
https://repository.apache.org/content/repositories/maven-065/
> >>
> >> The distributable binaries and sources for testing can be found here:
> >>
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
> >>
> >&g
sion=18968
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-065/
>>
>> The distributable binaries and sources for testing can be found here:
>> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apach
itories/maven-016/org/apache/maven/apache-maven/3.1.1/
>
> I can not definitively say that this is because of Apache Maven 3.1.1,
> but I'm seeing something strange with builds since using it widely.
> I'm seeing errors of the type:
>
> Archive for required library:
>
Greetings,
On Sun, Sep 8, 2013 at 9:07 AM, Jason van Zyl wrote:
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/
I can not definitively say that this is because of
For the record - +1 Non Binding after I fixed my broken .m2 :)
Lets roll this baby!
On 26/09/2013, at 3:22 AM, Jason van Zyl wrote:
> Anyone else going to give the release a whirl?
-- Mark Derricutt ( m...@talios.com )
— twitter: https://twitter.com/talios
— podcast: http://www.illegalargume
-065/
> >
> > The distributable binaries and sources for testing can be found here:
> > https://repository.apache.org/content/repositories/maven-065/org/apache/ma
> > ven/apache-maven/3.1.1/
> >
> > Specifically the zip, tarball, and source archives can be found here:
&g
ies/maven-065/
> >
> > The distributable binaries and sources for testing can be found here:
> >
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
> >
> > Specifically the zip, tarball, and source archives can be found her
sitories/maven-065/org/apache/maven/apache-maven/3.1.1/
>
> Specifically the zip, tarball, and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip
> https://repository.apach
Sent from my iPad
> On Sep 22, 2013, at 4:41 PM, sebb wrote:
>
>> On 22 September 2013 05:03, Jason van Zyl wrote:
>>
>>> On Sep 21, 2013, at 7:44 PM, sebb wrote:
>>>
On 22 September 2013 03:09, Jason van Zyl wrote:
> On Sep 21, 2013, at 6:16 PM, sebb wrote:
>
> On 21 S
On 22 September 2013 05:03, Jason van Zyl wrote:
>
> On Sep 21, 2013, at 7:44 PM, sebb wrote:
>
>> On 22 September 2013 03:09, Jason van Zyl wrote:
>>> On Sep 21, 2013, at 6:16 PM, sebb wrote:
>>>
On 21 September 2013 23:09, Jason van Zyl wrote:
It would still be automated.
On 22 September 2013 08:13, Mark Derricutt wrote:
> On 22/09/2013, at 9:28 AM, Jason van Zyl wrote:
>
> A check is performed to ensure that each file in the source archive is
> present in the release revision
>
>
> Should that not be the other way around? That every file in the git clone
> should
On 22/09/2013, at 9:28 AM, Jason van Zyl wrote:
> A check is performed to ensure that each file in the source archive is
> present in the release revision
Should that not be the other way around? That every file in the git clone
should be in the source archive? Or vice versa, that should be
On Sep 21, 2013, at 7:44 PM, sebb wrote:
> On 22 September 2013 03:09, Jason van Zyl wrote:
>> On Sep 21, 2013, at 6:16 PM, sebb wrote:
>>
>>> On 21 September 2013 23:09, Jason van Zyl wrote:
>>>
>>> It would still be automated.
>>> However the source data would come form the vote e-mail, w
release vote to the release artifacts.
>>>>
>>>>> On Sep 20, 2013, at 5:40 PM, sebb wrote:
>>>>>
>>>>>> On 17 September 2013 16:39, Jason van Zyl wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Mav
sue has been resolved
>>>>>> so I'm rolling 3.1.1 again.
>>>>>>
>>>>>> Here is a link to Jira with 6 issues resolved:
>>>>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968
>>>>>
core releases.
>>
>>> On Sep 20, 2013, at 5:40 PM, sebb wrote:
>>>
>>>> On 17 September 2013 16:39, Jason van Zyl wrote:
>>>>> Hi,
>>>>>
>>>>> Maven Core ITs are good, and the license/notice issue has been resolved
-maven/3.1.1/apache-maven-3.1.1-src.zip
Source ZIP SHA1 url exists.
https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip.sha1
Binary ZIP url exists.
https://repository.apache.org/content/repositories/maven-065/org/apache/maven
Ts are good, and the license/notice issue has been resolved so
>>>> I'm rolling 3.1.1 again.
>>>>
>>>> Here is a link to Jira with 6 issues resolved:
>>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968
>&g
; https://repository.apache.org/content/repositories/maven-065/
>>>
>>> The distributable binaries and sources for testing can be found here:
>>> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
>>>
>>> S
.jspa?projectId=10500&version=18968
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-065/
>>
>> The distributable binaries and sources for testing can be found here:
>> https://repository.apache.org/content/repositories/maven-
jectId=10500&version=18968
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-065/
>
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.
t;>>>> _
> >>>>> the_Latest_Documentation>
> >>>>>
> >>>>> Le mardi 17 septembre 2013 11:39:17 Jason van Zyl a écrit :
> >>>>>> Hi,
> >>>>>>
> >>>>>&g
gt;> [1]
>>>>> http://maven.apache.org/developers/release/maven-core-release.html#Stage
>>>>> _
>>>>> the_Latest_Documentation>
>>>>>
>>>>> Le mardi 17 septembre 2013 11:39:17 Jason van Zyl a écrit :
>>>>>> Hi,
>>&
e has been resolved
> >>>> so
> >>>> I'm rolling 3.1.1 again.
> >>>>
> >>>> Here is a link to Jira with 6 issues resolved:
> >>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&am
Sent from my HTC One™ X, an AT&T 4G LTE smartphone
- Reply message -
From: "Jason van Zyl"
To: "Maven Developers List"
Subject: [VOTE] Release Maven 3.1.1
Date: Thu, Sep 19, 2013 7:30 PM
Are you just manually copying that or is there an option on the CMS t
Sent from my HTC On kme™ X, an AT&T 4G LTE smartphone
- Reply message -
From: "Jason van Zyl"
To: "Maven Developers List"
Subject: [VOTE] Release Maven 3.1.1
Date: Thu, Sep 19, 2013 7:30 PM
Are you just manually copying that or is there an option on the CMS t
n=18968
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-065/
>>
>> The distributable binaries and sources for testing can be found here:
>>
>> https://repository.apache.org/content/repositories/maven-065/or
t; https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version
>>>> =18 968
>>>>
>>>> Staging repo:
>>>> https://repository.apache.org/content/repositories/maven-065/
>>>>
>>>> The distributable binaries and s
gt;> https://repository.apache.org/content/repositories/maven-065/
> >>
> >> The distributable binaries and sources for testing can be found here:
> >> https://repository.apache.org/content/repositories/maven-065/org/apache/m
> >> ave n/apache-maven/3.1.1/
>
t/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
>
> Specifically the zip, tarball, and source archives can be found here:
>
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip
>
> https://repo
> https://repository.apache.org/content/repositories/maven-065/
>>
>> The distributable binaries and sources for testing can be found here:
>> https://repository.apache.org/content/repositories/maven-065/org/apache/mave
>> n/apache-maven/3.1.1/
>>
>> Specific
After some experimentation I still couldn't detect any errors showing up,
however, I did remember I noticed some strange anomalies after using
dependency:purge-local-repository the other day - where that goal seems to
delete all the local artifacts, doesn't clean up any of the meta-data files in
ing repo:
> https://repository.apache.org/content/repositories/maven-065/
>
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/mave
> n/apache-maven/3.1.1/
>
> Specifi
On 19/09/2013, at 1:09 PM, Jason van Zyl wrote:
> If you can reproduce it in a stand-alone example I can track it down. Or if
> it's an OSS project I'll take a look.
Sadly not unfortunately - 3.1.1 seems to work flawlessly fine for our main
artefacts and any OSS projects I have, but something
gt; +1 (non-binding), installed this as default Maven 3 on a Jenkins
>> installation and after upping maven-site-plugin from 3.0 to 3.3 in
>> some projects, around 20 projects (Mostly maven and Jenkins plugin)
>> were successfully running "mvn clean install site" (@Stephen:
g can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
>
> Specifically the zip, tarball, and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/
g/content/repositories/maven-065/
The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/
Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.or
distributable binaries and sources for testing can be found here:
>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/
>>
>> Specifically the zip, tarball, and source archives can be found here:
>> https://repository.apache.org/con
/repository.apache.org/content/repositories/maven-016/
>
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/
>
> Specifically the zip, tarball, a
On 14 September 2013 11:19, Baptiste Mathus wrote:
> Le 13 sept. 2013 19:00, "sebb" a écrit :
>>
>> On 12 September 2013 21:52, Baptiste Mathus wrote:
>> > 2013/9/12 sebb
>> >
>> >> On 12 September 2013 14:52, Arnaud Héritier
> wrote:
>> >> > On Thu, Sep 12, 2013 at 3:44 PM, sebb wrote:
>> >>
Le 13 sept. 2013 19:00, "sebb" a écrit :
>
> On 12 September 2013 21:52, Baptiste Mathus wrote:
> > 2013/9/12 sebb
> >
> >> On 12 September 2013 14:52, Arnaud Héritier
wrote:
> >> > On Thu, Sep 12, 2013 at 3:44 PM, sebb wrote:
> >> >
> >> >> On 10 September 2013 16:33, Daniel Kulp wrote:
> >>
On 12 September 2013 21:52, Baptiste Mathus wrote:
> 2013/9/12 sebb
>
>> On 12 September 2013 14:52, Arnaud Héritier wrote:
>> > On Thu, Sep 12, 2013 at 3:44 PM, sebb wrote:
>> >
>> >> On 10 September 2013 16:33, Daniel Kulp wrote:
>> >> >
>> >> > -1
>> >> >
>> >> > The src.tar.gz and src.zip
spa?projectId=10500&version=18968
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-016/
>>>
>>> The distributable binaries and sources for testing can be found here:
>>> https://repository.apache.org/content/
1 - 100 of 189 matches
Mail list logo
