Skip to content
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

projectArtifactFirstInClassPath and useWildcardClassPath are incompatible #121

Open
FrigoCoder opened this issue May 11, 2021 · 0 comments

Comments

@FrigoCoder
Copy link

I want to get CDI/Weld working on a command line application. Weld is finicky, the project artifact has to be the first on the classpath, and its manifest has to contain the entire classpath. The projectArtifactFirstInClassPath parameter is fine for small projects, but once I have too many dependencies the startup script crashes. I have to add useWildcardClassPath, which completely negates the former parameter.

Classpath with projectArtifactFirstInClassPath:
set CLASSPATH="%BASEDIR%"\conf;"%REPO%"\recovery-tools-1.2.1-SNAPSHOT.jar;"%REPO%"\weld-se-core-3.1.4.Final.jar;"%REPO%"\weld-environment-common-3.1.4.Final.jar;...

Classpath with useWildcardClassPath:
set CLASSPATH="%BASEDIR%"\conf;"%REPO%"\*

What I want:
set CLASSPATH="%BASEDIR%"\conf;"%REPO%"\recovery-tools-1.2.1-SNAPSHOT.jar;"%REPO%"\*

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant