Why do you need it there?
The way binaries are kept at Apache is inconsistent. How it evolved over time
where things disappear from one place to another (official distribution to
archives) I don't find makes much sense but that's the way it is. If you
require a distribution in a standard place
we generally switched Maven release canonical download area to
https://dist.apache.org/repos/dist/release/maven/maven-3/
IIRC, http://archive.apache.org/dist/maven/binaries/ was used by Jenkins folks
for automatic Maven version discovery and download, before the change
seems like we didn't took
yes, that's one of the first git trick to learn: git rebase [1] :)
perhaps real git gurus here have better links to explain.
Regards,
Hervé
[1] https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase
Le dimanche 28 décembre 2014 16:09:31 Dan Tran a écrit :
> Obviously, I am Git n
Le dimanche 28 décembre 2014 21:18:18 David Nalley a écrit :
> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
>
> wrote:
> > Dear Infra,
> >
> > For historical reasons, the Maven project has a host of JIRA projects
> > at codehaus. This is not an ideal situation for many reasons.
> >
> > In
Hello,
for some reason 3.2.3 is not available in the archives, is that intentional
or something went wrong with the 3.2.5 release?
Thanks
Milos
> -Original Message-
> From: Benson Margulies
> Sent: Sunday, December 28, 2014 21:52
>
> On Sun, Dec 28, 2014 at 9:18 PM, David Nalley wrote:
> > On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
> > wrote:
> >> Dear Infra,
> >>
> >> For historical reasons, the Maven project has a ho
On Sun, Dec 28, 2014 at 9:18 PM, David Nalley wrote:
> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
> wrote:
>> Dear Infra,
>>
>> For historical reasons, the Maven project has a host of JIRA projects
>> at codehaus. This is not an ideal situation for many reasons.
>>
>> In the past, discuss
Obviously, I am Git newbie, not sure if this causes problem?
-D
On Sun, Dec 28, 2014 at 3:55 PM, wrote:
> Merge branch 'master' of
> https://git-wip-us.apache.org/repos/asf/maven-wagon
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven-wagon/repo
> Commit: http://git-wip-us.apache.org/
> -Original Message-
> From: Hervé BOUTEMY
> Sent: Sunday, December 28, 2014 18:27
>
> if I count from
> http://jira.codehaus.org/secure/BrowseProjects.jspa#all
> taking relevant projects from "Maven 2 Plugins", "Maven
> Admin" and "Maven
> Technologies" categories, I get 61 projects
A more patient counter than I reports:
if I count from http://jira.codehaus.org/secure/BrowseProjects.jspa#all
taking relevant projects from "Maven 2 Plugins", "Maven Admin" and "Maven
Technologies" categories, I get 61 projects
On Sun, Dec 28, 2014 at 6:20 PM, Benson Margulies wrote:
> On Sun
if I count from http://jira.codehaus.org/secure/BrowseProjects.jspa#all
taking relevant projects from "Maven 2 Plugins", "Maven Admin" and "Maven
Technologies" categories, I get 61 projects
Hope this helps :)
Regards,
Hervé
Le dimanche 28 décembre 2014 18:13:45 Benson Margulies a écrit :
> inf
On Sun, Dec 28, 2014 at 6:07 PM, Jake Farrell wrote:
> Hey Benson
> What is the exact number and would an import of existing issues be needed or
> will the project be taking care of that migration?
I did a count and came up with 46. I've asked for help in rendering
that number precise.
The Maven
infra@ asks: _exactly_ how many projects. Does anyone know off hand?
On Sun, Dec 28, 2014 at 1:13 AM, Barrie Treloar wrote:
> On 28 December 2014 at 08:46, Jason van Zyl wrote:
>
>> Would certainly be easier to have it at Apache at this point. I don't
>> think it's particularly hard, just time
Le dimanche 28 décembre 2014 21:04:50 Robert Scholte a écrit :
> Op Sun, 28 Dec 2014 19:37:47 +0100 schreef Kristian Rosenvold
>
> :
> > I'll sumarize what appears to be our consensus so far.
> >
> > Update to jdk 6.0 "at will", but please be sure that we're not leaving
> > the last 1.5 version i
> On Dec 14, 2014, at 8:29 PM, Jason van Zyl wrote:
>
> What we want is a form of continuous delivery where a version like 3.2.4 is
> the version that we call it to the outside world (some refer to it as the
> marketing version) and the qualifier changes from build to build so we have:
>
> 3
Op Sun, 28 Dec 2014 19:37:47 +0100 schreef Kristian Rosenvold
:
I'll sumarize what appears to be our consensus so far.
Update to jdk 6.0 "at will", but please be sure that we're not leaving
the last 1.5 version in a regressed state.
Version number indicates minimum maven version, so a simple
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 2.18.1
The release contains a number of bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
http://maven.apache.org
I'll sumarize what appears to be our consensus so far.
Update to jdk 6.0 "at will", but please be sure that we're not leaving
the last 1.5 version in a regressed state.
Version number indicates minimum maven version, so a simple JDK
upgrade only mandates a minor version update.
We are also in a si
+1
Regards,
Hervé
Le mercredi 17 décembre 2014 20:40:59 Igor Fedorenko a écrit :
> Hi,
>
> We solved 1 issue:
> https://jira.codehaus.org/browse/MPLUGINTESTING-44
>
> There are no issues left in JIRA
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1106/
>
> http:
+1
2014-12-28 15:06 GMT+01:00 Karl Heinz Marbaise :
> Hi,
>
> here is only one vote missing ;-)...
>
> Kind regards
> Karl Heinz Marbaise
> On 12/18/14 2:40 AM, Igor Fedorenko wrote:
>>
>> Hi,
>>
>> We solved 1 issue:
>> https://jira.codehaus.org/browse/MPLUGINTESTING-44
>>
>> There are no issues
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/78
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=20436
http://jira.codehaus.org/issues/?jql=project%20%3D%20MEAR%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
https://repository.apache.org/content/reposi
Hi,
here is only one vote missing ;-)...
Kind regards
Karl Heinz Marbaise
On 12/18/14 2:40 AM, Igor Fedorenko wrote:
Hi,
We solved 1 issue:
https://jira.codehaus.org/browse/MPLUGINTESTING-44
There are no issues left in JIRA
Staging repo:
https://repository.apache.org/content/repositories/mav
Swizzle sounds a good solution. I remember using it to migrate a mojo
project to ASF instance.
--
Olivier
On 28 Dec 2014 17:14, "Barrie Treloar" wrote:
> On 28 December 2014 at 08:46, Jason van Zyl wrote:
>
> > Would certainly be easier to have it at Apache at this point. I don't
> > think it's
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Hervé Boutemy, Olivier Lamy, Kristian
Rosenvold
+1 (non binding): Andreas Gudian
I will promote the artifacts to the central repo.
Cheers
Tibor
-
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/78
[SUREFIRE-1131] Remove obsolete maven profiles
Remove maven profiles jdk1.3 and jdk 1.4.
Inline testng dependency into ordinal dependencies from profile jdk15.
You can merge this pull req
26 matches
Mail list logo
