[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MBUILDCACHE-16:
-------------------------------------
    Description: 
reported to me by someone trying to test:
I've noticed that all the docs state a file named maven-cache-config.xml but 
the source suggests it should be called maven-build-cache-config.xml:
https://github.com/apache/maven-build-cache-extension/blob/c92e48ef924e0f67a0e1299[…]/main/java/org/apache/maven/buildcache/xml/CacheConfigImpl.java

Also maybe worth stating that the XXMM (memory mapped files) hash algorithm 
seems to require JDK9+ as it uses ByteBuffer.clear() somewhere - or at least, 
when I tried to use it, I saw a stacktrace with that - maybe some other 
extension/plugin interacting badly. It only seemed to happen with XXMM.


  was:
reported to me by someone trying to test:
I've noticed that all the docs state a file named maven-cache-config.xml but 
the source suggests it should be called maven-build-cache-config.xml:
https://github.com/apache/maven-build-cache-extension/blob/c92e48ef924e0f67a0e1299[…]/main/java/org/apache/maven/buildcache/xml/CacheConfigImpl.java


> config file name
> ----------------
>
>                 Key: MBUILDCACHE-16
>                 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-16
>             Project: Maven Build Cache Extension
>          Issue Type: Bug
>            Reporter: Herve Boutemy
>            Priority: Major
>
> reported to me by someone trying to test:
> I've noticed that all the docs state a file named maven-cache-config.xml but 
> the source suggests it should be called maven-build-cache-config.xml:
> https://github.com/apache/maven-build-cache-extension/blob/c92e48ef924e0f67a0e1299[…]/main/java/org/apache/maven/buildcache/xml/CacheConfigImpl.java
> Also maybe worth stating that the XXMM (memory mapped files) hash algorithm 
> seems to require JDK9+ as it uses ByteBuffer.clear() somewhere - or at least, 
> when I tried to use it, I saw a stacktrace with that - maybe some other 
> extension/plugin interacting badly. It only seemed to happen with XXMM.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to