Le mercredi 18 juin 2014 08:12:20 Michael Osipov a écrit :
> Am 2014-06-18 04:25, schrieb Paul Benedict:
> > Since 2.x is discontinued, this is our opportunity to rename the JIRA
> > project too. Right now it's "Maven 2 & 3". It can either be "Maven 3" or
> > simply "Maven". Thoughts?
>
> Good poi
Am 2014-06-18 04:25, schrieb Paul Benedict:
Since 2.x is discontinued, this is our opportunity to rename the JIRA
project too. Right now it's "Maven 2 & 3". It can either be "Maven 3" or
simply "Maven". Thoughts?
Good point, clean up the JIRA frontpage of MNG. Do you have the
permission to do
On 18 June 2014 13:48, Mark Derricutt wrote:
> You assume CI servers have intelligence and deep knowledge of Maven. Or
> that you have deep control over their configuration.
>
> You can't do that with Travis CI, nor with Code-review tools such as
> Gerrit ( not cleanly, not without doing evil thi
You assume CI servers have intelligence and deep knowledge of Maven. Or
that you have deep control over their configuration.
You can't do that with Travis CI, nor with Code-review tools such as
Gerrit ( not cleanly, not without doing evil things with maven configs
like I mention in [1] ).
St
On 18 June 2014 12:23, Mark Derricutt wrote:
> Interesting, I hadn't noticed this was only a warning.
>
> The main problem I have is the moment you start relying on these fake
> reactors you end up breaking C.I. builds with dependant changes.
>
Why?
Your CI should know that project B depends upo
Interesting, I hadn't noticed this was only a warning.
The main problem I have is the moment you start relying on these fake
reactors you end up breaking C.I. builds with dependant changes.
This is my main beef with multiple git repositories for projects - if
you have a pairing of dependant c
+1 non-binding here - so far looks good.
My work projects seem to build fine, as do my mojos.
On 18 Jun 2014, at 4:03, Jason van Zyl wrote:
Hi,
Time to release Maven 3.2.2!
Here is a link to Jira with 27 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versi
Since 2.x is discontinued, this is our opportunity to rename the JIRA
project too. Right now it's "Maven 2 & 3". It can either be "Maven 3" or
simply "Maven". Thoughts?
Cheers,
Paul
On Tue, Jun 17, 2014 at 3:03 PM, Michael Osipov wrote:
> Am 2014-06-17 21:57, schrieb Jason van Zyl:
>
>
>> On
I did "the work", ie I ran the classical commands:
mvn -Preporting site site:stage
mvn scm-publish:publish-scm
so the site is ready at http://maven.apache.org/ref/3-LATEST/
Notice:
1. it takes a little time because there are 142MB and ~4K files, but it works
like a charm with these commands
2.
Hi Hervè
I just published it
Thanks for finding and updating it...
Kind regards
Karl-Heinz Marbaise
Regards,
Hervé
Le mardi 17 juin 2014 22:45:39 Karl Heinz Marbaise a écrit :
Hi just a hint...
I've taken a look into the maven site and found out that there had not
been a release anno
I just published it
Regards,
Hervé
Le mardi 17 juin 2014 22:45:39 Karl Heinz Marbaise a écrit :
> Hi just a hint...
>
> I've taken a look into the maven site and found out that there had not
> been a release announcement of Maven 3.2.1 ...couldn't find a reference
> in the mailing list archives
Hi,
i just wan't to start release process for maven-jar-plugin within next
few days
Is there something which should be part of that release...
Current state of the release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=18297
Kind regards
Karl-Heinz Marbaise
-
Hi just a hint...
I've taken a look into the maven site and found out that there had not
been a release announcement of Maven 3.2.1 ...couldn't find a reference
in the mailing list archives...someone else? Did i missed something?
history.apt:
* <<2014-02-21 3.2.1
{{{http://mail-archives.a
+1
Regards,
Hervé
Le dimanche 15 juin 2014 16:23:51 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 2 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=187
> 76
>
> There are still 27 issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%20%3D%2
+1 (non-binding)
* SHA1 of src.zip OK
* Checked with invoker tests for our local company pom, two smaller
single module and one small multi-module projects.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbu
Am 2014-06-17 21:57, schrieb Jason van Zyl:
On Jun 17, 2014, at 3:47 PM, Michael Osipov
wrote:
Am 2014-06-17 21:14, schrieb Jason van Zyl:
Just start nuking/moving/cleaning if you think it makes sense.
Just did for 2.2.x. But are we going to relase 3.0.6 or 3.1.2? I
don't think so because
Hi,
first +1 (non binding) from me...
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T15:51:42+02:00)
Maven home: /usr/share/maven
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre
Defau
On Jun 17, 2014, at 3:47 PM, Michael Osipov wrote:
> Am 2014-06-17 21:14, schrieb Jason van Zyl:
>> Just start nuking/moving/cleaning if you think it makes sense.
>
> Just did for 2.2.x. But are we going to relase 3.0.6 or 3.1.2? I don't think
> so because all energy is being put into 3.2.x. I
Am 2014-06-17 21:14, schrieb Jason van Zyl:
Just start nuking/moving/cleaning if you think it makes sense.
Just did for 2.2.x. But are we going to relase 3.0.6 or 3.1.2? I don't
think so because all energy is being put into 3.2.x. If so, should we
declare at least 3.0.x as EOL? If not, people
Am 2014-06-17 21:17, schrieb Karl Heinz Marbaise:
Hi,
> has anyone of you ever check the roadmap in JIRA lately?>
There are several versions which will probably never be released.
Moveover, all tickets for 2.2.2 are fixed.
Can we clean up upcoming versions?
Are we going to release a EOL 2.2.2
Hi,
> has anyone of you ever check the roadmap in JIRA lately?>
There are several versions which will probably never be released.
Moveover, all tickets for 2.2.2 are fixed.
Can we clean up upcoming versions?
Are we going to release a EOL 2.2.2?
In february we had decided not to release any 2.
Just start nuking/moving/cleaning if you think it makes sense.
On Jun 17, 2014, at 3:05 PM, Michael Osipov wrote:
> Hi folks,
>
> has anyone of you ever check the roadmap in JIRA lately?
>
> There are several versions which will probably never be released. Moveover,
> all tickets for 2.2.2 ar
Hi folks,
has anyone of you ever check the roadmap in JIRA lately?
There are several versions which will probably never be released.
Moveover, all tickets for 2.2.2 are fixed.
Can we clean up upcoming versions?
Are we going to release a EOL 2.2.2?
Thanks,
Michael
--
Github user rfscholte commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46347052
Works fine on my system:
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: D:\apache-maven-3.2.1\bi
Done.
On Jun 17, 2014, at 1:58 PM, Michael Osipov wrote:
> Am 2014-06-17 18:03, schrieb Jason van Zyl:
>> Hi,
>>
>> Time to release Maven 3.2.2!
>
> I am confused?! There are nine unresolved issues for that release. If you are
> not going to fix, remove the 'Fix Version' please.
>
>
> -
Am 2014-06-17 18:03, schrieb Jason van Zyl:
Hi,
Time to release Maven 3.2.2!
I am confused?! There are nine unresolved issues for that release. If
you are not going to fix, remove the 'Fix Version' please.
-
To unsubscribe
We'll have to get the unresolved issues out of the release notes.
Cheers,
Paul
On Tue, Jun 17, 2014 at 11:03 AM, Jason van Zyl wrote:
> Hi,
>
> Time to release Maven 3.2.2!
>
> Here is a link to Jira with 27 issues resolved:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=1050
+1
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1025
groupId: org.apache.maven
artifactId: apache-maven
version: 3.2.2
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1025/org/apache/maven/apache-maven/3.2.2/apache-maven-3.2.2-s
Hi,
Time to release Maven 3.2.2!
Here is a link to Jira with 27 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20042
Staging repo:
https://repository.apache.org/content/repositories/maven-1025/
The distributable binaries and sources for testing can be
Can someone who runs on Windows take a look at:
https://github.com/apache/maven/pull/22#issuecomment-46325077
A user trying to contribute an IT and getting a failure on Windows. Looks like
he has a solution but I don't run anything on Windows so can't easily verify
without becoming very angry :
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46325077
I already got it running in Eclipse (pretty straight forward with m2e
etc.). Actually the failed test [MNG-4625]
(http://jira.codehaus.org/browse/MNG-4625) never seemed to
Can we discuss what kind of hardware Nexus is on? It's gone down again while
I'm trying to release and it's very annoying.
On Jun 17, 2014, at 9:46 AM, Jason van Zyl wrote:
> Thanks for bringing it back whoever kicked it.
>
> On Jun 17, 2014, at 9:39 AM, Jason van Zyl wrote:
>
>> Is Nexus do
Could someone possibly do the site related work? I write up the release notes.
But to update the site for the release and publish the reference site.
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://
Thanks for bringing it back whoever kicked it.
On Jun 17, 2014, at 9:39 AM, Jason van Zyl wrote:
> Is Nexus down for scheduled maintenance or did it just fall over?
>
> I'm trying to cut the 3.2.2 release and Nexus appears dead:
>
> https://repository.apache.org
>
> Thanks,
>
> Jason
>
> --
Is Nexus down for scheduled maintenance or did it just fall over?
I'm trying to cut the 3.2.2 release and Nexus appears dead:
https://repository.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
h
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46299917
They should all be passing. Happy to help you once I cut the 3.2.2 release.
Also, if you happen to use Eclipse I can show you how to do this all from
within Eclipse which i
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46291995
So, executing ITs with maven-3.2.1 also fails [MNG-4625]
(http://jira.codehaus.org/browse/MNG-4625). mng-5591-workspace-reader-module-a
also fails but I assume that's a di
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46286090
Ok, so I executed the ITs and faced two problems:
1. We use our own dedicated Nexus OSS and hence have custom user settings
(with mirror etc.). A lot of ITs fail be
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46279524
Just to get it right: for the ITs I have to clone
[https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git] and
then use my local SNAPSHOT build (maven-3.2.2-
+1
Thanks,
S.
On Mon, Jun 16, 2014 at 9:33 PM, Robert Scholte
wrote:
> +1
>
> * maven-ear-plugin-2.9.1-source-release.zip results in BUILD SUCCESS
> * [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated:
> 0 approved: 330 licence.
> * SHA1 correct
> * Site is ok
>
> Robert
>
40 matches
Mail list logo
