Raised PR #456

Hi @sdehors-ibm, thank you for raising this issue and opening a PR to address it. Given the time of the year, we will have someone on our team take a closer look next week.

Based on your description of the issue, we may consider a solution beyond providing an option to users to disable the refresh. We may need to update our default behaviour.

@TrevCraw , sure I proposed this to unlock our adoption of VScode + liberty tools but ideally the refresh should only be triggered when appropriate.

Hi @sdehors-ibm , when i tried the build i was not able to see any pom files getting generated in the target folder , also checked if refresh is getting invoked during the build but seems like it isn't . Not sure what i'm missing here. Can you share the steps you tried for which you got this issue?

Initially made a few changes to avoid looking into target and build directories for wherever there is a reference for pom.xml or build.gradle in the extension which didn't seem to fix the issue .
Was able to recreate the issue by copying the pom into the target folder during the build by modifying the pom file in the project used for testing and refresh is getting invoked directly at this point . Trying to prevent this refresh invocation when pom/build files are generated in the target folders can be the possible solution

hi @sdehors-ibm , can you give few details about the bug

1. where is the projects target directory ?

2. We are currently checking if the pom.xml file resides in a subdirectory within the project's target or build directory (located at the root of the project). If it does, we skip the refresh process. If it doesn't, we proceed with the refresh. Can you confirm if this behaviour aligns with your project structure?

3. Is there a possibility that your build process is causing pom.xml files to be created repeatedly, potentially in a loop?

4. Do these pom.xml files only appear inside the target folder / sub directories of the target folder after generation, or could they be located elsewhere in your project?

5. We tested this by adding a config to the project’s pom.xml to copy it into the target directory and other locations during the build. Does this test cover the issue you're facing?

Hi,

1. the target directories are at the standard location provided by maven under each module folder.
2. the project is composed of several modules, each have a target folder. The test poms are present in subdirectories in those target folders.
3. the build process copies the pom files from the src/test/resources folder to target/test-classes. I don't think there is any loop, unless the build is retriggered and re-copies those resources
4. see 3.
5. I think you can just put the pom files in the src/test/resources, we also have a zip dependency that gets unzipped to target/test-classes but this goal does not seem to be executed by vs code during its build.