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

Classpath not resolved when it's in a Maven container #1964

Closed
ghost opened this issue Jul 27, 2016 · 0 comments
Closed

Classpath not resolved when it's in a Maven container #1964

ghost opened this issue Jul 27, 2016 · 0 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Milestone

Comments

@ghost
Copy link

ghost commented Jul 27, 2016

Reproduction Steps:

  1. Import a Maven project
  2. Use ${project.java.classpath} in a command
  3. Run a command with this macro

Expected behavior:

${project.java.classpatgh} is translated into the actual classpath

Observed behavior:
${project.java.classpath} is translated into an absolute path to project root.

@ghost ghost added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 27, 2016
@svor svor added this to the 4.7.0 milestone Aug 4, 2016
@svor svor closed this as completed Aug 4, 2016
@bmicklea bmicklea mentioned this issue Aug 9, 2016
89 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants