-
Notifications
You must be signed in to change notification settings - Fork 27
Skip file overwrite if output is identical #1
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
Comments
I think it is possible to implement such feature |
"maven-source-plugin" Invokes the execution of the lifecycle phase generate-sources prior to executing itself, thus if using maven-source-plugin and java-comment-preprocessor at the same time it forces maven to recompile the project twice. |
By the way: I like how smooth JCP integration is. I use it to support multiple JDK versions for PostgreSQL JDBC driver: pgjdbc/pgjdbc#435. |
I have added --z parameter into CLI and compareDestination into MAVEN and ANT f63d1ad |
Do you mean snapshot version is deployed somewhere? |
you can build from sources or use brebuilt version https://drive.google.com/file/d/0BxHnNp97IgMRX05LZXNtbEVhZEE/view?usp=sharing |
Thanks for the quick fix.
FYI: build without
|
the plug-in has a bit bizarre build process and you should have maven distributive on your machine and the way to the distributive should be directly placed into maven.home property in the pom.xml, it starts maven during integration tests |
I see. I just did a test via jitpack.io just for fun and it does not work:
|
Hi @vlsi Probably the issue is that JitPack rewrites groupId/artifactId to match the GitHub repository. Guessing that the original groupId is specified in the plugin descriptor. |
@raydac , would you mind releasing 6.0.1? |
@vlsi it works well? |
it does as in log above: #1 (comment) |
I have moved integration tests into special profile and at present anyone should not have problems to build version locally |
JFY: that solves
|
@vlsi so how is your opinion? is it ready to be released as 6.0.1 in current state? |
@raydac , it looks like it does not work. Here's what i get with Just "Content was not saved " with no explanation.
|
I believe, the fix is #5 |
@vlsi I have merged the fix and also I have improved logging for debugging, now it will be written into debug log if the file content was not rewritten because its content was not changed, also verbose level is activated automatically if maven debug level is active |
@raydac , it works fine for me |
Currently java-comment-preprocessor always overwrites files, so java compiler always recompiles all the files.
Can JCP doublecheck if output is good enough and avoid file overwrites?
The text was updated successfully, but these errors were encountered: