-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extraClasspath() method on WebAppContext dont support dir path #150
Labels
Comments
I am running into this same issue. Is this fixed yet or is there a workaround, instead of having to specify each jar file manually? |
@chinhodado we would be very happy to accept a pull request that implements this enhancement. |
@janbartel: I recently encountered this issue as well. Saw your comment -- please review my pull request! |
janbartel
pushed a commit
that referenced
this issue
Feb 6, 2019
* Issue #150: Ability to handle JAR directories in extraClasspath. In keeping with Java conventions[0], any directory paths ending in /* should be considered a JAR directory and all jars in that directory will be added (non recursively) to the classpath. [0] https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html Signed-off-by: Tushar Inamdar <[email protected]>
This feature was added to jetty-9.4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
migrated from Bugzilla #438482
status ASSIGNED severity enhancement in component server for 9.2.x
Reported in version 8.1.12 on platform PC
Assigned to: Jan Bartel
On 2014-06-29 06:33:09 -0400, Nir Barel wrote:
On 2014-06-30 20:19:44 -0400, Jan Bartel wrote:
On 2014-07-01 00:59:54 -0400, Nir Barel wrote:
On 2014-07-01 05:27:14 -0400, Jan Bartel wrote:
On 2014-07-01 05:34:04 -0400, Nir Barel wrote:
The text was updated successfully, but these errors were encountered: