Skip to content

Conversation

@steelswing
Copy link

Fixed Compile On Save in Java SE Project on application running or debugging
Fixed Java Debugger did not apply the code change in Java SE Project if the project is Java source version 8
Fixed JSP Java Code analyzer in Java SE Project
Improved JSP Hyperlink provider


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

@matthiasblaesing matthiasblaesing self-requested a review November 13, 2025 18:46
@matthiasblaesing
Copy link
Contributor

I'm willing to have a look at this. But these are three totally unrelated changes, that should not be in the same PR. Please split them.

When creating the new PRs, please keep unrelated changes to a minimum. Whitespace without relation to the changed code should not be changed (there are exceptions to the rule, but it would be good not to go down that route), debugging only changes should be removed (there is no need to mess with log levels), commented out code should not be part of additions.

Please also ensure that there is full author information available, currently there is a nickname instead of the author information.

Copy link

@donphelix donphelix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can drop these comments. With clear naming and proper spacing, the code should be self-explanatory.

Comment on lines +351 to +358

// private void checkPreprocessors(FileObject fileObject) {
// CssPreprocessors.getDefault().process(p, fileObject);
// }
//
// private void checkPreprocessors(FileObject fileObject, String originalName, String originalExtension) {
// CssPreprocessors.getDefault().process(p, fileObject, originalName, originalExtension);
// }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steelswing would it make sense to remove this entirely rather than commenting it out? Might keep things cleaner.

FileObject root = group.getRootFolder();
objects.add(root);
}
objects.add(project.getProjectDirectory());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: blank line before the return?


@Override
public void fileRenamed(FileRenameEvent fe) {
// XXX: notify BrowserReload about filename change

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: no need of this comment

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

Successfully merging this pull request may close these issues.

3 participants