jira-importer commented on issue #198: URL: https://github.com/apache/maven-jar-plugin/issues/198#issuecomment-2956677833
**[Andy DePue](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=adepue)** commented It looks like this fix is scheduled for 2.1, but I'm curious if the fix addresses an issue I'm seeing? I'm currently using 2.0.5, and it looks like Maven is actually doing an "up to date" check between the .jar and the sources, but it always fails because pom.properties is a source file that gets included in the .jar, and since Maven always regenerates pom.properties with each build, it is always newer than the .jar. If I force maven NOT to include pom.properties in the resulting .jar, then Maven will actually work correctly: it won't rebuild the .jar until something changes. BTW, I'm turning off the inclusion of pom.properties via this config: ```xml <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <addMavenDescriptor>false</addMavenDescriptor> </archive> </configuration> </plugin> ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
