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

Make the snippetsupport.jar as part of the maven build #389

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

laeubi
Copy link
Contributor

@laeubi laeubi commented Feb 7, 2024

Currently snippetsupport.jar must be build in the ide using s ant script.

This changes the build to use maven only rebuilding the jar on each compile so class differences can be discovered automatically. The jar still needs to be checked in as it is used internally as a resource.

What it does

How to test

Author checklist

Currently snippetsupport.jar must be build in the ide using s ant
script.

This changes the build to use maven only rebuilding the jar on each
compile so class differences can be discovered automatically. The jar
still needs to be checked in as it is used internally  as a resource.
Copy link
Member

@iloveeclipse iloveeclipse left a comment

Choose a reason for hiding this comment

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

It is OK to build with maven, but why do we check in the jar to git? I would prefer not to do so, and instead keep the builder on project.

@laeubi
Copy link
Contributor Author

laeubi commented Feb 7, 2024

It is OK to build with maven, but why do we check in the jar to git? I would prefer not to do so, and instead keep the builder on project.

Yes this would be good, but if you look at

jarURL = JDIDebugUIPlugin.getDefault().getBundle().getEntry("snippetsupport.jar"); //$NON-NLS-1$

it wants this jar file, I could think of changing this part to look for the compiled classes via the classlaoder if it does not finds the jar and build one on-the-fly but that's a bit out of scope here, if you can help to resolve that issue the jar should not be required to checked in.

As an alternative one could want people to run the maven pom once before testing that feature in the IDE but I'm not sure its feasable.

@iloveeclipse
Copy link
Member

What is wrong with the external launcher that did this already but now removed?

@laeubi
Copy link
Contributor Author

laeubi commented Feb 11, 2024

What is wrong with the external launcher that did this already but now removed?

At least in my IDE these are very disruptive as they often run after each code changes open new consoles and take some time, but in general it would be of course also possible to run a maven command there.

@iloveeclipse
Copy link
Member

At least in my IDE these are very disruptive as they often run after each code changes open new consoles

One can setup them not to open a console.

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.

2 participants