User JAR file path cannot be added to a custom classpath about capsule HOT 6 CLOSED

@pron I would like to point out that both paolo and myself have created custom capsules to add to the classpath after a capsule has been created via environment variables or system properties. We use ours to add logging dependencies after capsule creation, and I feel like this is a common enough use case to warrant including it in the core capsule functionality.

That said, would you rather this stay external as custom capsules? Or do you agree with me?

from capsule.

Well, I'm not 100% convinced, and when in doubt -- leave it out! (We can always add it later, but taking things out after a 1.0 release is not as simple).

In fact, as you can probably tell, the trend is to remove as much as possible from the core to caplets (I've removed all the Maven stuff). I even entertained the notion of moving all the JVM specific code (classpath etc.) to a caplet (so that core Capsule will just support attributes and buildProcess etc.), but thought that would be too much, as I don't expect people to use Caplet for non-JVM programs...

from capsule.

Sounds good to me 👍

from capsule.

Is there a release or a snapshot including this patch?

from capsule.

OK. I suppose it's included in the release 1.0-rc2-SNAPSHOT

from capsule.

Yep. Note that there will be no 1.0-rc1 release. We will release 1.0 in a couple of weeks.

from capsule.