HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277872654
My question was actually: "is there a way to export/store the JIT and plugin
classloaders cache, so we can override and reuse in a new daemon, just like the
registry file."
ppalaga commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277767328
> start a container with a deamon already running, and with a JIT cache
already warmed up and the plugin classloaders already loaded
JIT and classloader caching will only kick
HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277729537
My use case is the same as @dcaillia and @chicobento.
I am running the same maven project with same set of plugins over and over,
from a new container everytime.
Th
ppalaga commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277662865
Actually, if your goal is just to invoke the client inside the running
container, then you may start the daemon by simply `mvnd -v` - its starts it
and leaved it in idle state.
-
ppalaga commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277648019
Yeah, the daemon starts in busy state so that the client that initiates its
start can grab it by daemonId.
I think currently, there is no way to instruct the client on the CLI to
HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277602583
@ppalaga Thanks for pointing out. It is in "Busy" status. probably the
reason why I can't reuse it.
I copy pasted the command run by `mvnd -v` as you recommended.
I now
ppalaga commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277493411
@HomeOfTheWizard what is `docker exec mvnd --status` showing
after you start the container? Is the daemon up and running and is it in the
IDLE state?
--
This is an automated
HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2276266613
> > (1) make sure it never shuts down, because it's a daemon
>
> There is currently no easy way to start the daemon process directly. But
it is not that hard to put to
HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2270771295
@wallentx I think it is possible this cache extension with mvnd
```
mvnd.coreExtensions: internal option to specify the list of maven extension
to register
F
HomeOfTheWizard commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2270735882
This would open doors for a lot of new use cases.
Especially for using plugins that help for configuring an application
running on K8s/Docker.
For example I have a plug
wallentx commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2265607381
Yo I literally just stumbled upon this
https://github.com/fbricon/mvn-cache-test
https://maven.apache.org/extensions/maven-build-cache-extension/getting-started.html
cstamas commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2264121697
Interesting ideas in this discussion...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
wallentx commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2263745033
This would be extremely useful for us in the context of running this in k8s.
Our monorepo CI has hit the limits. We are pulling down 1TB of dependencies
and plugins per day, and
13 matches
Mail list logo
