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

jspc-maven-plugin does not release usage of scanned logfiles files. #87

Open
hofmanndavid opened this issue Nov 22, 2021 · 2 comments
Open

Comments

@hofmanndavid
Copy link

I am trying to wrap my head around the next. I think there is some classpath issues here.

  • When I execute a mvn clean package build with the jspc-maven-plugin on prepare-package phase the plugin runs fine, but then when maven-war-plugin is trying to move stuff it fails the build saying that log4j-api-2.14.1.jar: The process cannot access the file because it is being used by another process.
  • When I comment out the jspc-maven-plugin the maven war plugin has no problem moving things around to make the war.

This behaviour is repeatable.

I am running jspc-maven-plugin in prepare-package phase since my project uses overlays and I don't what this plugin to only compile jsps from my project, but also the overlayed projects so I point it to the target/ folder.

I am using version 2.4.6 compiling for tomcat 8.5 running on jvm version 8.

@hofmanndavid
Copy link
Author

here the SO question Any maven jspc plugin will block some scanned jar file?

@leonardehrenfried
Copy link
Owner

I've never heard about this but I'm happy to merge a PR if you find out what the cause is.

2.4.6 and Java 8 are both very old versions though.

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

No branches or pull requests

2 participants