Re: [DISCUSS] 3.5.0 alpha/beta's on Central

[Christian Schulte]

Am 02/25/17 um 22:55 schrieb Karl Heinz Marbaise:
> Hi,
> 
> based on the started discussion about either to bring 3.5.0-alpha-1 to 
> Central or not I would suggest to discuss in a separate thread and 
> prevent using the VOTE's threads for that (as Stephen already mentioned).
> 
> Using Central:
>   o Everybody can use it and make tests on it.
> 
> Using an other repository:
>   o Which one?
> 
> Using only dist area? Or something different?
> 
> WDY?
> 
> Based on earlier releases which had been in Central with alpha's:
> 
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22
> 

It's just a matter of naming, IMHO.

3.5.0-RC1
  Should not be deployed to central - just made available for testing.

3.5.0-alpha-1
  A complete release which happens to be classified "alpha".

Back when Maven 2 got released, almost all plugins were classified alpha
or beta.

If we want to ensure no one is embedding an alpha release and then not
upgrade to the non-alpha release, we maybe should log a warning upon
execution (This is an alpha release bla bla bla) and remove that warning
before releasing 3.5.0.

Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Christian Schulte]

Am 02/25/17 um 17:25 schrieb Tibor Digana:
>>> There are two commits for MNG-6078 part of -alpha-1.
> 
> This was caused by system property duplicates in surefire ITs.
> It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES.

If something works with 3.3.9 but not 3.5.0, we need to fix it in Maven.
I think this is what Stephen did. No need to "fix" surefire ITs, if they
were working with 3.3.9 before. 3.5.0 would not be a drop in replacement
anymore that way.

Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

[Manfred Moser]

Imho it should go to Central just like any other release. All components and 
everything. The version clearly tells thats its alpha and this allows for clean 
testing, embedding and so on. 

We have done it in the past and I dont see any reason for changing this. 

Manfred

Stephen Connolly wrote on 2017-02-25 16:05:

> So if I am embedding Maven, how do I embed Maven 3.5.0-alpha-1?
> 
> (I know it should not be a big issue as we should have the release soon
> anyway, but more from the principal POV)
> 
> Consider the Jenkins "evil" job type plugin that has dependencies on some
> of the artifacts that are in the staging repository? If there is a need to
> update the adapter libs for that to work with alpha-1, how would that be
> possible if we don't publish the artifacts at least somewhere?
> On Sat 25 Feb 2017 at 23:23, Robert Scholte  wrote:
> 
>> It depends on what the task of Central is. If it for *dependencies*,
>> there's no need to publish pre-final versions; don't think we should
>> motive plugins to depend on alphas.
>>
>> AFAIK the common way to get a new version of Maven is via
>> http://maven.apache.org/download.cgi and not via Central.
>>
>> This is also about hygiene. Not every artifact belongs in Central (we've
>> seen continuous deployment-like releases), and pre-releases could belong
>> to that group.
>>
>> Funny, just like Jigsaw there's a clear difference between libraries and
>> applications; I don't mind treating them differently, especially in these
>> unofficial release stages.
>>
>> Robert
>>
>> On Sat, 25 Feb 2017 22:55:55 +0100, Karl Heinz Marbaise
>>  wrote:
>>
>> > Hi,
>> >
>> > based on the started discussion about either to bring 3.5.0-alpha-1 to
>> > Central or not I would suggest to discuss in a separate thread and
>> > prevent using the VOTE's threads for that (as Stephen already mentioned).
>> >
>> > Using Central:
>> >   o Everybody can use it and make tests on it.
>> >
>> > Using an other repository:
>> >   o Which one?
>> >
>> > Using only dist area? Or something different?
>> >
>> > WDY?
>> >
>> > Based on earlier releases which had been in Central with alpha's:
>> >
>> >
>> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22
>> >
>> > Kind regards
>> > Karl Heinz Marbaise
>> >
>> > -
>> > 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
>>
>> --
> Sent from my phone
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

[Stephen Connolly]

So if I am embedding Maven, how do I embed Maven 3.5.0-alpha-1?

(I know it should not be a big issue as we should have the release soon
anyway, but more from the principal POV)

Consider the Jenkins "evil" job type plugin that has dependencies on some
of the artifacts that are in the staging repository? If there is a need to
update the adapter libs for that to work with alpha-1, how would that be
possible if we don't publish the artifacts at least somewhere?
On Sat 25 Feb 2017 at 23:23, Robert Scholte  wrote:

> It depends on what the task of Central is. If it for *dependencies*,
> there's no need to publish pre-final versions; don't think we should
> motive plugins to depend on alphas.
>
> AFAIK the common way to get a new version of Maven is via
> http://maven.apache.org/download.cgi and not via Central.
>
> This is also about hygiene. Not every artifact belongs in Central (we've
> seen continuous deployment-like releases), and pre-releases could belong
> to that group.
>
> Funny, just like Jigsaw there's a clear difference between libraries and
> applications; I don't mind treating them differently, especially in these
> unofficial release stages.
>
> Robert
>
> On Sat, 25 Feb 2017 22:55:55 +0100, Karl Heinz Marbaise
>  wrote:
>
> > Hi,
> >
> > based on the started discussion about either to bring 3.5.0-alpha-1 to
> > Central or not I would suggest to discuss in a separate thread and
> > prevent using the VOTE's threads for that (as Stephen already mentioned).
> >
> > Using Central:
> >   o Everybody can use it and make tests on it.
> >
> > Using an other repository:
> >   o Which one?
> >
> > Using only dist area? Or something different?
> >
> > WDY?
> >
> > Based on earlier releases which had been in Central with alpha's:
> >
> >
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > -
> > 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
>
> --
Sent from my phone

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

[Robert Scholte]

It depends on what the task of Central is. If it for *dependencies*,  
there's no need to publish pre-final versions; don't think we should  
motive plugins to depend on alphas.


AFAIK the common way to get a new version of Maven is via  
http://maven.apache.org/download.cgi and not via Central.


This is also about hygiene. Not every artifact belongs in Central (we've  
seen continuous deployment-like releases), and pre-releases could belong  
to that group.


Funny, just like Jigsaw there's a clear difference between libraries and  
applications; I don't mind treating them differently, especially in these  
unofficial release stages.


Robert

On Sat, 25 Feb 2017 22:55:55 +0100, Karl Heinz Marbaise  
 wrote:



Hi,

based on the started discussion about either to bring 3.5.0-alpha-1 to  
Central or not I would suggest to discuss in a separate thread and  
prevent using the VOTE's threads for that (as Stephen already mentioned).


Using Central:
  o Everybody can use it and make tests on it.

Using an other repository:
  o Which one?

Using only dist area? Or something different?

WDY?

Based on earlier releases which had been in Central with alpha's:

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22

Kind regards
Karl Heinz Marbaise

-
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: [DISCUSS] 3.5.0 alpha/beta's on Central

[Guillaume Boué]

I don't see a reason not to push 3.5.0-alpha-1 to Central. It has been 
done this way for previous versions, and makes it more broadly 
applicable for all users.


Guillaume


Le 25/02/2017 à 22:55, Karl Heinz Marbaise a écrit :

Hi,

based on the started discussion about either to bring 3.5.0-alpha-1 to 
Central or not I would suggest to discuss in a separate thread and 
prevent using the VOTE's threads for that (as Stephen already mentioned).


Using Central:
 o Everybody can use it and make tests on it.

Using an other repository:
 o Which one?

Using only dist area? Or something different?

WDY?

Based on earlier releases which had been in Central with alpha's:

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22 



Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] 3.5.0 alpha/beta's on Central

[Stephen Connolly]

My view is we should release to central.

I am not so strongly held of this view that I would object to
alternatives... but I do think just dropping the staging repo and pushing
the src to dist would be a bad plan

On Sat 25 Feb 2017 at 21:56, Karl Heinz Marbaise  wrote:

> Hi,
>
> based on the started discussion about either to bring 3.5.0-alpha-1 to
> Central or not I would suggest to discuss in a separate thread and
> prevent using the VOTE's threads for that (as Stephen already mentioned).
>
> Using Central:
>   o Everybody can use it and make tests on it.
>
> Using an other repository:
>   o Which one?
>
> Using only dist area? Or something different?
>
> WDY?
>
> Based on earlier releases which had been in Central with alpha's:
>
>
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

[DISCUSS] 3.5.0 alpha/beta's on Central

[Karl Heinz Marbaise]

Hi,

based on the started discussion about either to bring 3.5.0-alpha-1 to 
Central or not I would suggest to discuss in a separate thread and 
prevent using the VOTE's threads for that (as Stephen already mentioned).


Using Central:
 o Everybody can use it and make tests on it.

Using an other repository:
 o Which one?

Using only dist area? Or something different?

WDY?

Based on earlier releases which had been in Central with alpha's:

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22

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: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Stephen Connolly]

I think it might be better if we could release them into a different repo
so that the artifacts are available - just not synced to central.

Either that or we say screw it sync to central... al least if we make them
available via dist.

If we don't make available via dist, then yes we should just drop... but
then we cannot have non-engaged users contribute to testing as if we are
not supposed to make generally available non-voted artifacts... and voted
artifacts are supposed to be on dist.

(Perhaps we need to move this portion of debate to a separate thread)

On Sat 25 Feb 2017 at 21:00, Robert Scholte  wrote:

> I would say: all pre-final should be dropped, i.e. should not up in
> Central.
> However, we could make the distributions available for download.
> If this is done via the staged repository or via our dist folder[1], I
> don't mind; whatever fits best.
>
> Robert
>
> [1] https://archive.apache.org/dist/maven/maven-3/
>
> On Sat, 25 Feb 2017 19:56:16 +0100, Stephen Connolly
>  wrote:
>
> > We need to start thinking whether any of the issues so far are enough to
> > drop alpha-1 and run with alpha-2
> >
> > IMHO we would gain more information from users if we release alpha-1 with
> > and ACK for the known issues and say that alpha-2 is 1-2 weeks away
> > rather
> > than drop alpha-1 and wait that time for alpha-2. These are alpha
> > versions,
> > as long as we are thorough with our known issues, I would expect users
> > will
> > forgive us WDYT?
> >
> > On 25 February 2017 at 16:50, Michael Osipov 
> wrote:
> >
> >> Am 2017-02-25 um 17:07 schrieb Robert Scholte:
> >>
> >>> Hi,
> >>>
> >>> found a non-critical issue. It seems like with every Maven build, a new
> >>> lib/ext/jansi-64-1-xxx.13 is generated.
> >>> If this is a temp-file, I'd rather write it to the OS temp folder
> >>> instead of the Maven distribution.
> >>>
> >>
> >> This is horribly ugly by Jansi and Hawt JNI.
> >> This has been introduced in b80915b8822b51aafa962a9ef53a61c0ac59033d.
> >> Before reset, I had a separate ticket for that and performed a single
> >> commit. After reset Hervé and me agreed to merge this into MNG-3507. The
> >> issue is MNG-6115. See also the reasoning. It was intented to avoid the
> >> constant extraction from JAR to {java.io.tmpdir}.
> >>
> >> I expected library.jansi.path to be read-only. Alternatively, we should
> >> expand all native libraries to {maven.home}/lib/ext/jansi and see if
> >> this
> >> works. {maven.home} must be remain read-only.
> >>
> >> Michael
> >>
> >>
> >> On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
> >>>  wrote:
> >>>
> >>> Hi,
> 
>  We solved 65 issues:
>  https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>  ctId=12316922=12339664=Text
> 
> 
>  There are still a couple of issues left in JIRA for 3.5.0, but I do
>  not
>  think any of those are blocking an alpha release:
>  https://issues.apache.org/jira/issues/?jql=project%20%3D%
>  20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVer
>  sion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%
>  20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
> 
>  In addition there are 315 issues left in JIRA for Maven core:
>  https://issues.apache.org/jira/issues/?jql=project%20%3D%
>  20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>  20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
> 
>  Staging repo:
>  https://repository.apache.org/content/repositories/maven-1324
> 
>  The distributable binaries and sources for testing can be found here:
>  https://repository.apache.org/content/repositories/maven-132
>  4/org/apache/maven/apache-maven/3.5.0-alpha-1/
> 
> 
>  Specifically the zip, tarball, and source archives can be found here:
>  https://repository.apache.org/content/repositories/maven-132
>  4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>  3.5.0-alpha-1-bin.zip
> 
>  https://repository.apache.org/content/repositories/maven-132
>  4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>  3.5.0-alpha-1-bin.tar.gz
> 
>  https://repository.apache.org/content/repositories/maven-132
>  4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>  3.5.0-alpha-1-src.zip
> 
>  https://repository.apache.org/content/repositories/maven-132
>  4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>  3.5.0-alpha-1-src.tar.gz
> 
> 
>  Source release checksum(s):
>  apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
>  6055696aece5b0bfdd0308dae60838b37e218aba
>  apache-maven-3.5.0-alpha-1-src.zip sha1:
>  7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
> 
>  Git tag:
>  https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
>  

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Robert Scholte]

I would say: all pre-final should be dropped, i.e. should not up in  
Central.

However, we could make the distributions available for download.
If this is done via the staged repository or via our dist folder[1], I  
don't mind; whatever fits best.


Robert

[1] https://archive.apache.org/dist/maven/maven-3/

On Sat, 25 Feb 2017 19:56:16 +0100, Stephen Connolly  
 wrote:



We need to start thinking whether any of the issues so far are enough to
drop alpha-1 and run with alpha-2

IMHO we would gain more information from users if we release alpha-1 with
and ACK for the known issues and say that alpha-2 is 1-2 weeks away  
rather
than drop alpha-1 and wait that time for alpha-2. These are alpha  
versions,
as long as we are thorough with our known issues, I would expect users  
will

forgive us WDYT?

On 25 February 2017 at 16:50, Michael Osipov  wrote:


Am 2017-02-25 um 17:07 schrieb Robert Scholte:


Hi,

found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder
instead of the Maven distribution.



This is horribly ugly by Jansi and Hawt JNI.
This has been introduced in b80915b8822b51aafa962a9ef53a61c0ac59033d.
Before reset, I had a separate ticket for that and performed a single
commit. After reset Hervé and me agreed to merge this into MNG-3507. The
issue is MNG-6115. See also the reasoning. It was intented to avoid the
constant extraction from JAR to {java.io.tmpdir}.

I expected library.jansi.path to be read-only. Alternatively, we should
expand all native libraries to {maven.home}/lib/ext/jansi and see if  
this

works. {maven.home} must be remain read-only.

Michael


On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly

 wrote:

Hi,


We solved 65 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
ctId=12316922=12339664=Text


There are still a couple of issues left in JIRA for 3.5.0, but I do  
not

think any of those are blocking an alpha release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%
20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVer
sion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%
20ASC%2C%20priority%20DESC%2C%20created%20ASC


In addition there are 315 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%
20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC


Staging repo:
https://repository.apache.org/content/repositories/maven-1324

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-132
4/org/apache/maven/apache-maven/3.5.0-alpha-1/


Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-132
4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
3.5.0-alpha-1-bin.zip

https://repository.apache.org/content/repositories/maven-132
4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
3.5.0-alpha-1-bin.tar.gz

https://repository.apache.org/content/repositories/maven-132
4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
3.5.0-alpha-1-src.zip

https://repository.apache.org/content/repositories/maven-132
4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
3.5.0-alpha-1-src.tar.gz


Source release checksum(s):
apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
6055696aece5b0bfdd0308dae60838b37e218aba
apache-maven-3.5.0-alpha-1-src.zip sha1:
7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698


Staging site:
https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
-Stephen



-
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] Release Apache Maven 3.5.0-alpha-1

[Karl Heinz Marbaise]

Hi,

the last two days I'm running the 3.5.0-alpha-1 here on my mac with 
system installation and doing my work under usual user...not any problem 
so far...


I have taken a look into the lib/ext folder where I can't find a file 
similar to that which could only be there if the process has system 
access permission which is not the case...so I don't see it as critical...



Apart from that we should take a more deeper look into it:

Furthermore I've checked if I run Maven 3.5.0 (current master) under 
user space so I can acknowledge the things Robert has written...it looks 
like a temp file which generated from native code (taken a look into 
it...). It could be dumped via nm...


$ nm 
~/tools/maven-test/apache-maven-3.5.0-SNAPSHOT/lib/ext/libjansi-64-1-7745124109922235605.13

2058 S _IS_JNI_1_2
0e30 T _JNI_OnLoad
2060 S _JVM
15b0 T 
_Java_org_fusesource_jansi_internal_CLibrary_00024Termios_init
1600 T 
_Java_org_fusesource_jansi_internal_CLibrary_00024WinSize_init

0e90 T _Java_org_fusesource_jansi_internal_CLibrary_init
1150 T 
_Java_org_fusesource_jansi_internal_CLibrary_ioctl__IJLorg_fusesource_jansi_internal_CLibrary_00024WinSize_2

11e0 T _Java_org_fusesource_jansi_internal_CLibrary_ioctl__IJ_3I
1280 T _Java_org_fusesource_jansi_internal_CLibrary_isatty
1290 T _Java_org_fusesource_jansi_internal_CLibrary_openpty
14b0 T _Java_org_fusesource_jansi_internal_CLibrary_tcgetattr
1520 T _Java_org_fusesource_jansi_internal_CLibrary_tcsetattr
1590 T _Java_org_fusesource_jansi_internal_CLibrary_ttyname
15a0 T _Java_org_fusesource_jansi_internal_CLibrary_ttyslot
1660 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024CHAR_1INFO_init
1670 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024CONSOLE_1SCREEN_1BUFFER_1INFO_init
1680 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024COORD_init
1690 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024INPUT_1RECORD_init
16a0 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024KEY_1EVENT_1RECORD_init
16b0 T 
_Java_org_fusesource_jansi_internal_Kernel32_00024SMALL_1RECT_init

1650 T _Java_org_fusesource_jansi_internal_Kernel32_init
2068 S _TermiosFc
20b0 S _WinSizeFc
 U ___stack_chk_fail
 U ___stack_chk_guard
16c0 T _cacheTermiosFields
1a10 T _cacheWinSizeFields
1800 T _getTermiosFields
1ae0 T _getWinSizeFields
0dd0 T _hawtjni_attach_thread
0e10 T _hawtjni_detach_thread
 U _ioctl
 U _isatty
 U _openpty
1910 T _setTermiosFields
1c30 T _setWinSizeFields
 U _tcgetattr
 U _tcsetattr
0e50 T _throwOutOfMemory
 U _ttyname
 U _ttyslot
 U dyld_stub_binder



Kind regards
Karl Heinz Marbaise



On 25/02/17 18:01, Benson Margulies wrote:

Is it still non-critical if the user lacks write access to that directory?

On Sat, Feb 25, 2017 at 8:07 AM, Robert Scholte  wrote:

Hi,

found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder instead of
the Maven distribution.

Robert

On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
 wrote:


Hi,

We solved 65 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text

There are still a couple of issues left in JIRA for 3.5.0, but I do not
think any of those are blocking an alpha release:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

In addition there are 315 issues left in JIRA for Maven core:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

Staging repo:
https://repository.apache.org/content/repositories/maven-1324

The distributable binaries and sources for testing can be found here:

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/

Specifically the zip, tarball, and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Stephen Connolly]

We need to start thinking whether any of the issues so far are enough to
drop alpha-1 and run with alpha-2

IMHO we would gain more information from users if we release alpha-1 with
and ACK for the known issues and say that alpha-2 is 1-2 weeks away rather
than drop alpha-1 and wait that time for alpha-2. These are alpha versions,
as long as we are thorough with our known issues, I would expect users will
forgive us WDYT?

On 25 February 2017 at 16:50, Michael Osipov  wrote:

> Am 2017-02-25 um 17:07 schrieb Robert Scholte:
>
>> Hi,
>>
>> found a non-critical issue. It seems like with every Maven build, a new
>> lib/ext/jansi-64-1-xxx.13 is generated.
>> If this is a temp-file, I'd rather write it to the OS temp folder
>> instead of the Maven distribution.
>>
>
> This is horribly ugly by Jansi and Hawt JNI.
> This has been introduced in b80915b8822b51aafa962a9ef53a61c0ac59033d.
> Before reset, I had a separate ticket for that and performed a single
> commit. After reset Hervé and me agreed to merge this into MNG-3507. The
> issue is MNG-6115. See also the reasoning. It was intented to avoid the
> constant extraction from JAR to {java.io.tmpdir}.
>
> I expected library.jansi.path to be read-only. Alternatively, we should
> expand all native libraries to {maven.home}/lib/ext/jansi and see if this
> works. {maven.home} must be remain read-only.
>
> Michael
>
>
> On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
>>  wrote:
>>
>> Hi,
>>>
>>> We solved 65 issues:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12316922=12339664=Text
>>>
>>>
>>> There are still a couple of issues left in JIRA for 3.5.0, but I do not
>>> think any of those are blocking an alpha release:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVer
>>> sion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%
>>> 20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>>
>>>
>>> In addition there are 315 issues left in JIRA for Maven core:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>>> 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>>
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-1324
>>>
>>> The distributable binaries and sources for testing can be found here:
>>> https://repository.apache.org/content/repositories/maven-132
>>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/
>>>
>>>
>>> Specifically the zip, tarball, and source archives can be found here:
>>> https://repository.apache.org/content/repositories/maven-132
>>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>>> 3.5.0-alpha-1-bin.zip
>>>
>>> https://repository.apache.org/content/repositories/maven-132
>>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>>> 3.5.0-alpha-1-bin.tar.gz
>>>
>>> https://repository.apache.org/content/repositories/maven-132
>>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>>> 3.5.0-alpha-1-src.zip
>>>
>>> https://repository.apache.org/content/repositories/maven-132
>>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>>> 3.5.0-alpha-1-src.tar.gz
>>>
>>>
>>> Source release checksum(s):
>>> apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
>>> 6055696aece5b0bfdd0308dae60838b37e218aba
>>> apache-maven-3.5.0-alpha-1-src.zip sha1:
>>> 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
>>>
>>> Git tag:
>>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
>>> ;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698
>>>
>>>
>>> Staging site:
>>> https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>>
>>> Thanks,
>>> -Stephen
>>>
>>
>> -
>> 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] Release Apache Maven 3.5.0-alpha-1

[Benson Margulies]

Is it still non-critical if the user lacks write access to that directory?

On Sat, Feb 25, 2017 at 8:07 AM, Robert Scholte  wrote:
> Hi,
>
> found a non-critical issue. It seems like with every Maven build, a new
> lib/ext/jansi-64-1-xxx.13 is generated.
> If this is a temp-file, I'd rather write it to the OS temp folder instead of
> the Maven distribution.
>
> Robert
>
> On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
>  wrote:
>
>> Hi,
>>
>> We solved 65 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text
>>
>> There are still a couple of issues left in JIRA for 3.5.0, but I do not
>> think any of those are blocking an alpha release:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> In addition there are 315 issues left in JIRA for Maven core:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1324
>>
>> The distributable binaries and sources for testing can be found here:
>>
>> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/
>>
>> Specifically the zip, tarball, and source archives can be found here:
>>
>> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip
>>
>> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz
>>
>> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip
>>
>> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz
>>
>> Source release checksum(s):
>> apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
>> 6055696aece5b0bfdd0308dae60838b37e218aba
>> apache-maven-3.5.0-alpha-1-src.zip sha1:
>> 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
>>
>> Git tag:
>>
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698
>>
>> Staging site:
>> https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> Thanks,
>> -Stephen
>
>
> -
> 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] Release Apache Maven 3.5.0-alpha-1

[Michael Osipov]

Am 2017-02-25 um 17:07 schrieb Robert Scholte:

Hi,

found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder
instead of the Maven distribution.


This is horribly ugly by Jansi and Hawt JNI.
This has been introduced in b80915b8822b51aafa962a9ef53a61c0ac59033d.
Before reset, I had a separate ticket for that and performed a single 
commit. After reset Hervé and me agreed to merge this into MNG-3507. The 
issue is MNG-6115. See also the reasoning. It was intented to avoid the 
constant extraction from JAR to {java.io.tmpdir}.


I expected library.jansi.path to be read-only. Alternatively, we should 
expand all native libraries to {maven.home}/lib/ext/jansi and see if 
this works. {maven.home} must be remain read-only.


Michael


On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly
 wrote:


Hi,

We solved 65 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text


There are still a couple of issues left in JIRA for 3.5.0, but I do not
think any of those are blocking an alpha release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC


In addition there are 315 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC


Staging repo:
https://repository.apache.org/content/repositories/maven-1324

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/


Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip

https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz


Source release checksum(s):
apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
6055696aece5b0bfdd0308dae60838b37e218aba
apache-maven-3.5.0-alpha-1-src.zip sha1:
7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698


Staging site:
https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
-Stephen


-
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] Release Apache Maven 3.5.0-alpha-1

[Tibor Digana]

The SNAPSHOT is therefore getting quite big 70 MB.

On Sat, Feb 25, 2017 at 5:07 PM, Robert Scholte 
wrote:

> Hi,
>
> found a non-critical issue. It seems like with every Maven build, a new
> lib/ext/jansi-64-1-xxx.13 is generated.
> If this is a temp-file, I'd rather write it to the OS temp folder instead
> of the Maven distribution.
>
> Robert
>
>
> On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> Hi,
>>
>> We solved 65 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12316922=12339664=Text
>>
>> There are still a couple of issues left in JIRA for 3.5.0, but I do not
>> think any of those are blocking an alpha release:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVer
>> sion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%
>> 20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> In addition there are 315 issues left in JIRA for Maven core:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>> 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1324
>>
>> The distributable binaries and sources for testing can be found here:
>> https://repository.apache.org/content/repositories/maven-132
>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/
>>
>> Specifically the zip, tarball, and source archives can be found here:
>> https://repository.apache.org/content/repositories/maven-132
>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>> 3.5.0-alpha-1-bin.zip
>> https://repository.apache.org/content/repositories/maven-132
>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>> 3.5.0-alpha-1-bin.tar.gz
>> https://repository.apache.org/content/repositories/maven-132
>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>> 3.5.0-alpha-1-src.zip
>> https://repository.apache.org/content/repositories/maven-132
>> 4/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-
>> 3.5.0-alpha-1-src.tar.gz
>>
>> Source release checksum(s):
>> apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
>> 6055696aece5b0bfdd0308dae60838b37e218aba
>> apache-maven-3.5.0-alpha-1-src.zip sha1:
>> 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
>>
>> Git tag:
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
>> ;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698
>>
>> Staging site:
>> https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> Thanks,
>> -Stephen
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Cheers
Tibor

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Tibor Digana]

>>There are two commits for MNG-6078 part of -alpha-1.

This was caused by system property duplicates in surefire ITs.
It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES.
System props duplicates: -DreuseForks=false -DreuseForks=true
I am sure the ITs now pass because of Stepen's commit with better
resolution of system properties.
More info in mailing list apart.



On Sat, Feb 25, 2017 at 4:34 PM, Christian Schulte [via Maven] <
ml-node+s40175n5900050...@n5.nabble.com> wrote:

> Am 02/25/17 um 14:40 schrieb Tibor Digana:
>
> > @Stephen
> > @Michael-O
> > What changed in Maven after Michael used his snapshot version of
> > Maven-3.5.0-SNAPSHOT?
> > Michael said that surefire failed with ForkModeIT and he tested
> Surefire's
> > commits from HEAD to 502d18442113b4c6c72630dca5842e1eb287b8b0.
> > I followed more deeply in the commits of Surefire project but my
> snapshot
> > version of Maven-3.5.0-SNAPSHOT still failed till January 16th, 2015.
> > Then I decided to use this Maven release of Alpha-1 and ForkModeIT
> passed.
> >
>
> There are two commits for MNG-6078 part of -alpha-1.
>
> Regards,
> --
> Christian
>
>
> -
> To unsubscribe, e-mail: [hidden email]
> 
> For additional commands, e-mail: [hidden email]
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-3-5-0-alpha-1-
> tp5899775p5900050.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-3-5-0-alpha-1-tp5899775p5900059.html
Sent from the Maven Developers mailing list archive at Nabble.com.

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

[Tibor Digana]

@Michael-O
The issue(two errors in ForkModeIT)  with commit
e0bcffd05bb04001f97bf752de56bca7137da3e2 is caused by duplicate properties
but it is not cause of that commit.
I have found the root cause (reuseForks duplicates):
-DforkMode=perthread *-DreuseForks=false -DreuseForks=true* -DthreadCount=1
I have the same tests failed as you had:

Failed tests:
testForkModeOncePerThreadSingleThread(org.apache.maven.surefire.its.ForkModeIT):
pid 1 didn't match pid 2 expected:<[19220]@SK-ZA-04278 testVal...> but
was:<[23028]@SK-ZA-04278 testVal...>

testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT):
number of different pids is not as expected expected:<2> but was:<3>

We already prevented from this issue in the branch
https://github.com/apache/maven-surefire/commits/SUREFIRE_SYSPROP_DUPLICATES
but of course the old commits, like e0bcffd05, do not have this fix and
therefore this issue come up.

I will remove duplicates with system property "testNgVersion" in 17 POMs of
our tests in the branch.


On Thu, Feb 23, 2017 at 7:20 PM, Michael Osipov  wrote:

> So guys,
>
> I took a different approach to provide Tibor more information about the
> failures. First of all, I added another platform for the test which is
> exotic: HP-UX 11.31. The VM comes directly from HPE which is a repackaged
> Oracle JVM.
>
> I started Git bisect and discovered some broken commits, e.g.,
> 9dd4074e83c0edae5e2050f66e9cadfdba40fe01 where less tests previously
> fail, but doing a git revert of the offending commit does not resolve the
> issue. After that I started a manual bisect going binary through commits
> where I found that last known good commit 
> 502d18442113b4c6c72630dca5842e1eb287b8b0
> has a lower number of failures while the next commit
> e0bcffd05bb04001f97bf752de56bca7137da3e2 introduced a regression from my
> point of view, Tibor has a different opinion.
> Going deeper I have compared the same debug logs between FreeBSD and HP-UX
> and noticed that the consumer from the plugin is too greedy and declares
> the forked VM as dead. I consider this as race conditions as well as stdio
> issues not solvable w/o native code (I might be wrong).
>
> For those who would like to take a closer look at the results, see again
> here:
>
> http://home.apache.org/~michaelo/
>
>> maven-surefire-2.19.2-experimental.tar.gz
>> maven-surefire-308d941c9b6ebb695aba9630f81fc5b400f21322-all-ITs.tar.gz
>> maven-surefire-502d18442113b4c6c72630dca5842e1eb287b8b0.tar.gz
>> maven-surefire-502d18442113b4c6c72630dca5842e1eb287b8b0-all-ITs.tar.gz
>> maven-surefire-502d18442113b4c6c72630dca5842e1eb287b8b0-all-
>> ITs-hp-ux.tar.gz
>> maven-surefire-e0bcffd05bb04001f97bf752de56bca7137da3e2.tar.gz
>> maven-surefire-e0bcffd05bb04001f97bf752de56bca7137da3e2-all-ITs.tar.gz
>> maven-surefire-e0bcffd05bb04001f97bf752de56bca7137da3e2-all-
>> ITs-hp-ux.tar.gz
>>
>
> I consider several commits between Surefire 2.19.1 and master
> broken/regressions.
>
> Tibor, feel free to add your comments and findings for everyone. Your
> analysis is better than mine since your know the code better than I do.
>
> Michael
>
> PS: All build done with Maven master. I will switch to 3.5.0-alpha-1.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Cheers
Tibor

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Robert Scholte]

Hi,

found a non-critical issue. It seems like with every Maven build, a new  
lib/ext/jansi-64-1-xxx.13 is generated.
If this is a temp-file, I'd rather write it to the OS temp folder instead  
of the Maven distribution.


Robert

On Thu, 23 Feb 2017 17:10:18 +0100, Stephen Connolly  
 wrote:



Hi,

We solved 65 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text

There are still a couple of issues left in JIRA for 3.5.0, but I do not
think any of those are blocking an alpha release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

In addition there are 315 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

Staging repo:
https://repository.apache.org/content/repositories/maven-1324

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/

Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz

Source release checksum(s):
apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
6055696aece5b0bfdd0308dae60838b37e218aba
apache-maven-3.5.0-alpha-1-src.zip sha1:
7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698

Staging site:
https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
-Stephen


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Christian Schulte]

Am 02/25/17 um 14:40 schrieb Tibor Digana:
> @Stephen
> @Michael-O
> What changed in Maven after Michael used his snapshot version of
> Maven-3.5.0-SNAPSHOT?
> Michael said that surefire failed with ForkModeIT and he tested Surefire's
> commits from HEAD to 502d18442113b4c6c72630dca5842e1eb287b8b0.
> I followed more deeply in the commits of Surefire project but my snapshot
> version of Maven-3.5.0-SNAPSHOT still failed till January 16th, 2015.
> Then I decided to use this Maven release of Alpha-1 and ForkModeIT passed.
> 

There are two commits for MNG-6078 part of -alpha-1.

Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Tibor Digana]

@Stephen
@Michael-O
What changed in Maven after Michael used his snapshot version of
Maven-3.5.0-SNAPSHOT?
Michael said that surefire failed with ForkModeIT and he tested Surefire's
commits from HEAD to 502d18442113b4c6c72630dca5842e1eb287b8b0.
I followed more deeply in the commits of Surefire project but my snapshot
version of Maven-3.5.0-SNAPSHOT still failed till January 16th, 2015.
Then I decided to use this Maven release of Alpha-1 and ForkModeIT passed.




On Sat, Feb 25, 2017 at 12:44 PM, stephenconnolly [via Maven] <
ml-node+s40175n5900039...@n5.nabble.com> wrote:

> We should also tip our hat to what happened to 3.4.x
>
> On Sat 25 Feb 2017 at 11:41, Stephen Connolly <
> [hidden email] >
> wrote:
>
> > I think we can do alpha release notes. It maybe on a sub page
> >
> > Thanks for picking this up (I was going to start it later today subject
> to
> > family approval ;-) )
> >
> > On Sat 25 Feb 2017 at 11:34, Karl Heinz Marbaise <[hidden email]
> >
> > wrote:
> >
> > Hi,
> >
> > I have started to summarize the changes we had in 3.5.0-alpha-1..
> >
> >
> > https://github.com/khmarbaise/maven-release-notes/blob/
> master/content/markdown/docs/3.5.0/release-notes.md
> >
> > If there are any supplementals/changes/fixes etc. Please make an issue
> > or a pull request to it...or write here...
> >
> > (Should we do a release notes for 3.5.0-alpha-1 alone or should we
> > summarize that for 3.5.0 ?)
> >
> > Kind regards
> > Karl Heinz Marbaise
> > On 23/02/17 17:10, Stephen Connolly wrote:
> > > Hi,
> > >
> > > We solved 65 issues:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316922=12339664=Text
> > >
> > > There are still a couple of issues left in JIRA for 3.5.0, but I do
> not
> > > think any of those are blocking an alpha release:
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%
> 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > >
> > > In addition there are 315 issues left in JIRA for Maven core:
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1324
> > >
> > > The distributable binaries and sources for testing can be found here:
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1324/org/apache/maven/apache-maven/3.5.0-alpha-1/
> > >
> > > Specifically the zip, tarball, and source archives can be found here:
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-
> maven-3.5.0-alpha-1-bin.zip
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-
> maven-3.5.0-alpha-1-bin.tar.gz
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-
> maven-3.5.0-alpha-1-src.zip
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-
> maven-3.5.0-alpha-1-src.tar.gz
> > >
> > > Source release checksum(s):
> > > apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
> > > 6055696aece5b0bfdd0308dae60838b37e218aba
> > > apache-maven-3.5.0-alpha-1-src.zip sha1:
> > > 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
> > >
> > > Git tag:
> > >
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> 8e6bbc4d4aa7cdc837625a05358c98ca15f72698
> > >
> > > Staging site:
> > > https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
> > >
> > > Vote open for 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > >
> > > Thanks,
> > > -Stephen
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: [hidden email]
> 
> > For additional commands, e-mail: [hidden email]
> 
> >
> > --
> > Sent from my phone
> >
> --
> Sent from my phone
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-3-5-0-alpha-1-
> tp5899775p5900039.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Stephen Connolly]

We should also tip our hat to what happened to 3.4.x

On Sat 25 Feb 2017 at 11:41, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I think we can do alpha release notes. It maybe on a sub page
>
> Thanks for picking this up (I was going to start it later today subject to
> family approval ;-) )
>
> On Sat 25 Feb 2017 at 11:34, Karl Heinz Marbaise 
> wrote:
>
> Hi,
>
> I have started to summarize the changes we had in 3.5.0-alpha-1..
>
>
> https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.0/release-notes.md
>
> If there are any supplementals/changes/fixes etc. Please make an issue
> or a pull request to it...or write here...
>
> (Should we do a release notes for 3.5.0-alpha-1 alone or should we
> summarize that for 3.5.0 ?)
>
> Kind regards
> Karl Heinz Marbaise
> On 23/02/17 17:10, Stephen Connolly wrote:
> > Hi,
> >
> > We solved 65 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text
> >
> > There are still a couple of issues left in JIRA for 3.5.0, but I do not
> > think any of those are blocking an alpha release:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > In addition there are 315 issues left in JIRA for Maven core:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1324
> >
> > The distributable binaries and sources for testing can be found here:
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/
> >
> > Specifically the zip, tarball, and source archives can be found here:
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
> > 6055696aece5b0bfdd0308dae60838b37e218aba
> > apache-maven-3.5.0-alpha-1-src.zip sha1:
> > 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
> >
> > Git tag:
> >
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698
> >
> > Staging site:
> > https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> >
> > Thanks,
> > -Stephen
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
> Sent from my phone
>
-- 
Sent from my phone

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Stephen Connolly]

I think we can do alpha release notes. It maybe on a sub page

Thanks for picking this up (I was going to start it later today subject to
family approval ;-) )
On Sat 25 Feb 2017 at 11:34, Karl Heinz Marbaise  wrote:

> Hi,
>
> I have started to summarize the changes we had in 3.5.0-alpha-1..
>
>
> https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.0/release-notes.md
>
> If there are any supplementals/changes/fixes etc. Please make an issue
> or a pull request to it...or write here...
>
> (Should we do a release notes for 3.5.0-alpha-1 alone or should we
> summarize that for 3.5.0 ?)
>
> Kind regards
> Karl Heinz Marbaise
> On 23/02/17 17:10, Stephen Connolly wrote:
> > Hi,
> >
> > We solved 65 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text
> >
> > There are still a couple of issues left in JIRA for 3.5.0, but I do not
> > think any of those are blocking an alpha release:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > In addition there are 315 issues left in JIRA for Maven core:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1324
> >
> > The distributable binaries and sources for testing can be found here:
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/
> >
> > Specifically the zip, tarball, and source archives can be found here:
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip
> >
> https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
> > 6055696aece5b0bfdd0308dae60838b37e218aba
> > apache-maven-3.5.0-alpha-1-src.zip sha1:
> > 7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd
> >
> > Git tag:
> >
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698
> >
> > Staging site:
> > https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> >
> > Thanks,
> > -Stephen
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

[Karl Heinz Marbaise]

Hi,

I have started to summarize the changes we had in 3.5.0-alpha-1..

https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.0/release-notes.md

If there are any supplementals/changes/fixes etc. Please make an issue 
or a pull request to it...or write here...


(Should we do a release notes for 3.5.0-alpha-1 alone or should we 
summarize that for 3.5.0 ?)


Kind regards
Karl Heinz Marbaise
On 23/02/17 17:10, Stephen Connolly wrote:

Hi,

We solved 65 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text

There are still a couple of issues left in JIRA for 3.5.0, but I do not
think any of those are blocking an alpha release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(3.5.0%2C%203.5.0-candidate)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

In addition there are 315 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

Staging repo:
https://repository.apache.org/content/repositories/maven-1324

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/

Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.zip
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-bin.tar.gz
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.zip
https://repository.apache.org/content/repositories/maven-1324/org/apache/maven/apache-maven/3.5.0-alpha-1/apache-maven-3.5.0-alpha-1-src.tar.gz

Source release checksum(s):
apache-maven-3.5.0-alpha-1-src.tar.gz sha1:
6055696aece5b0bfdd0308dae60838b37e218aba
apache-maven-3.5.0-alpha-1-src.zip sha1:
7d6adcdf8929205bf20399c71c6a2bdb9ee4f6dd

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8e6bbc4d4aa7cdc837625a05358c98ca15f72698

Staging site:
https://people.apache.org/~stephenc/maven-3.5.0-alpha-1/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
-Stephen




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org