[
https://issues.apache.org/jira/browse/MRM-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574716#comment-17574716
]
David Newcomb commented on MRM-2031:
------------------------------------
Well I decided to give you another half day. Managed to setup a remote repo and
link it into a managed repo. So I can request a specific artefact and it talks
to the remote to deliver the jar/pom. My remote does not produce
maven-meta?.xml file (because it is a jfrog virtual repo) so I have to rely on
directory scanning. However it appears Archiva can only download index's from a
remote repo ("Download Remote Index") and does not do directory scanning so
local repo can't be browsed. I was expecting to scan the remote into the
managed local so that it is browseable. Maybe this is my misunderstanding, so I
tried to switch on DEBUG in the wrapper.conf. This gives me loads of messages
from the wrapper but not from the application itself so it was largely useless.
Couldn't find any other options for log levels.
I really have run out of time now, it's a shame because your product is pretty
clean and simple compared to others in this market space.
> Switch to JDK 11
> ----------------
>
> Key: MRM-2031
> URL: https://issues.apache.org/jira/browse/MRM-2031
> Project: Archiva
> Issue Type: Improvement
> Reporter: Martin Schreier
> Assignee: Martin Schreier
> Priority: Major
> Fix For: 3.0.0
>
>
> We should use JDK 11 as baseline, if the libraries and build process work.
> This is possible only after switching to Jakarta EE 9.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
