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
0000000000002058 S _IS_JNI_1_2
0000000000000e30 T _JNI_OnLoad
0000000000002060 S _JVM
00000000000015b0 T _Java_org_fusesource_jansi_internal_CLibrary_00024Termios_init 0000000000001600 T _Java_org_fusesource_jansi_internal_CLibrary_00024WinSize_init
0000000000000e90 T _Java_org_fusesource_jansi_internal_CLibrary_init
0000000000001150 T _Java_org_fusesource_jansi_internal_CLibrary_ioctl__IJLorg_fusesource_jansi_internal_CLibrary_00024WinSize_2
00000000000011e0 T _Java_org_fusesource_jansi_internal_CLibrary_ioctl__IJ_3I
0000000000001280 T _Java_org_fusesource_jansi_internal_CLibrary_isatty
0000000000001290 T _Java_org_fusesource_jansi_internal_CLibrary_openpty
00000000000014b0 T _Java_org_fusesource_jansi_internal_CLibrary_tcgetattr
0000000000001520 T _Java_org_fusesource_jansi_internal_CLibrary_tcsetattr
0000000000001590 T _Java_org_fusesource_jansi_internal_CLibrary_ttyname
00000000000015a0 T _Java_org_fusesource_jansi_internal_CLibrary_ttyslot
0000000000001660 T _Java_org_fusesource_jansi_internal_Kernel32_00024CHAR_1INFO_init 0000000000001670 T _Java_org_fusesource_jansi_internal_Kernel32_00024CONSOLE_1SCREEN_1BUFFER_1INFO_init 0000000000001680 T _Java_org_fusesource_jansi_internal_Kernel32_00024COORD_init 0000000000001690 T _Java_org_fusesource_jansi_internal_Kernel32_00024INPUT_1RECORD_init 00000000000016a0 T _Java_org_fusesource_jansi_internal_Kernel32_00024KEY_1EVENT_1RECORD_init 00000000000016b0 T _Java_org_fusesource_jansi_internal_Kernel32_00024SMALL_1RECT_init
0000000000001650 T _Java_org_fusesource_jansi_internal_Kernel32_init
0000000000002068 S _TermiosFc
00000000000020b0 S _WinSizeFc
                 U ___stack_chk_fail
                 U ___stack_chk_guard
00000000000016c0 T _cacheTermiosFields
0000000000001a10 T _cacheWinSizeFields
0000000000001800 T _getTermiosFields
0000000000001ae0 T _getWinSizeFields
0000000000000dd0 T _hawtjni_attach_thread
0000000000000e10 T _hawtjni_detach_thread
                 U _ioctl
                 U _isatty
                 U _openpty
0000000000001910 T _setTermiosFields
0000000000001c30 T _setWinSizeFields
                 U _tcgetattr
                 U _tcsetattr
0000000000000e50 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 <rfscho...@apache.org> wrote:
Hi,

found a non-critical issue. It seems like with every Maven build, a new
lib/ext/jansi-64-1-xxxxxxxxxxxxxxx.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?projectId=12316922&version=12339664&styleName=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

Reply via email to