project.properties duplicate conflict b/w google-cloud-core & google-cloud-pubsub

[RaiYogesh]

I am using duplicate-finder-maven-plugin in my project which has started complaining for duplicate project.properties b/w google-cloud-core & google-cloud-pubsub

`[INFO] Checking test classpath

[WARNING] Found duplicate and different resources in [com.google.cloud:google-cloud-core:1.2.1, com.google.cloud:google-cloud-pubsub:0.20.1-beta]:
[WARNING] project.properties
[WARNING] Found duplicate classes/resources in compile classpath.
[WARNING] Found duplicate and different resources in [com.google.cloud:google-cloud-core:1.2.1, com.google.cloud:google-cloud-pubsub:0.20.1-beta]:
[WARNING] project.properties
[WARNING] Found duplicate classes/resources in runtime classpath.
[WARNING] Found duplicate and different resources in [com.google.cloud:google-cloud-core:1.2.1, com.google.cloud:google-cloud-pubsub:0.20.1-beta]:
[WARNING] project.properties
[WARNING] Found duplicate classes/resources in test classpath.`

Kindly help out

[jakub-bochenski]

I think better place for this project.properties would be under META-INF.

In fact version is stored there already in MANIFEST.MF and in Maven descriptor.

[michaelbausor]

I think this is something we should investigate - it may be that META-INF is better than what we do at the moment. I will file a separate issue to track that.

As a temporary workaround: I am not familiar with the plugin, but have you looked at using the ignoredResourcePatterns setting (seen on this page: https://github.com/basepom/duplicate-finder-maven-plugin/wiki). That might help unblock or resolve the warning in the short term.

[jakub-bochenski]

I am not familiar with the plugin, but have you looked at using the ignoredResourcePatterns setting

Yes, we have an even better solution, but it's bad practice to have conflicting entries on classpath anyway

                            <exception>
                                <conflictingDependencies>
                                    <dependency>
                                        <groupId>com.google.cloud</groupId>
                                        <artifactId>google-cloud-core</artifactId>
                                    </dependency>
                                    <dependency>
                                        <groupId>com.google.cloud</groupId>
                                        <artifactId>google-cloud-pubsub</artifactId>
                                    </dependency>
                                </conflictingDependencies>
                                <resources>
                                    <resource>project.properties</resource>
                                </resources>
                            </exception>

[danoscarmike]

Ping @michaelbausor - what are next steps here?

[michaelbausor]

@garrettjonesgoogle Are we planning on kicking off work to migrate from Maven to Gradle soon? (#1587) If so, this issue may be best handled as part of that transition.

[jakub-bochenski]

I just found this has been fixed in db0fdb1

I see it removed the offending sections from multiple poms, though the commit message makes no mention of it

PS. Maybe you could consider using https://github.com/dmurgala/gradle-duplicate-finder-plugin to prevent similiar problems in the future

[garrettjonesgoogle]

Correct, this is fixed now. Closing issue.