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

RFE: Extra build customisation #1986

Open
ThrawnCA opened this issue Oct 31, 2018 · 1 comment
Open

RFE: Extra build customisation #1986

ThrawnCA opened this issue Oct 31, 2018 · 1 comment

Comments

@ThrawnCA
Copy link

ThrawnCA commented Oct 31, 2018

I'd like to be able to set up a build that would run a single Java (JUnit) test. I've been able to set up a build that will run all tests from the current class (via Maven, in this case):

CLASSNAME=$(echo %f |sed 's|[\].java||'); mvn -Dtest=${CLASSNAME} test
(feedback on better approaches is welcome)

But there just aren't any string substitutions that will allow me to specify parts of a class.

Some options for how this could be achieved:

  • Provide a build placeholder representing the current text selection, eg %s
  • Allow more than one build entry to have the custom input dialog that "Make Custom Target..." gets. I already use that one to build arbitrary Maven targets, but it would be nice to have a second, more specialised one where I could just paste in a test name and run that.
  • Ideally, I'd love to have a placeholder that would substitute the current function name (determined in the same way as the Symbols sidebar), but that's probably more complicated.
@elextr
Copy link
Member

elextr commented Jan 27, 2019

@ThrawnCA sorry for the delay responding, missed this issue.

Provide a build placeholder representing the current text selection, eg %s

Would be possible

Allow more than one build entry to have the custom input dialog that "Make Custom Target..." gets.

Allowing this was suggested when the current build system was in development and was vetoed as the system was already "too complex". Maybe it can be added now that everybody has gotten used to the system being "normal". Probably a few semantics to define first though.

Ideally, I'd love to have a placeholder that would substitute the current function name (determined in the same way as the Symbols sidebar), but that's probably more complicated.

Yes, because its filetype dependent, but maybe it could use the scope shown on the status bar (note that isn't foolproof though, and can be fully qualified, not just the function name).

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

No branches or pull requests

2 participants