egeria: Debugging Egeria client code - sources not found
In order to reproduce a reported problem I created a new IntelliJ project just containing my test code.
I had previously built egeria from source (master) which populated maven artifacts into my ~/.m2, as well as specified our snapshot repo within the test project’s maven pom.xml via
<version>1.0-SNAPSHOT</version>
<repositories>
<repository>
<id>egeriasnap</id>
<name>Egeria Snapshot Repo</name>
<url>https://odpi.jfrog.io/odpi/egeria-snapshot</url>
</repository>
<repository>
<id>central</id>
<name>Maven Central</name>
<url>https://repo1.maven.org/maven2/</url>
</repository>
</repositories>
When debugging in the test project, and dropping into the egeria client code, IntelliJ was able to decompose the class files fairly well … however it was not picking up the actual source.
The option to ‘download sources’ resulted in an error
Sources not found for: org.odpi.egeria:ocf-metadata-client:1.1-20191004.123226-31
In my local ~/.m2 I had the following from my master build:
➜ egeria cd ocf-metadata-client
➜ ocf-metadata-client ls
1.1-SNAPSHOT maven-metadata-local.xml
➜ ocf-metadata-client cd 1.1-SNAPSHOT
➜ 1.1-SNAPSHOT ls
_remote.repositories
maven-metadata-egeriasnap.xml
maven-metadata-egeriasnap.xml.sha1
maven-metadata-local.xml
ocf-metadata-client-1.1-20190927.155640-22.jar
ocf-metadata-client-1.1-20190927.155640-22.jar.sha1
ocf-metadata-client-1.1-20190927.155640-22.pom
ocf-metadata-client-1.1-20190927.155640-22.pom.sha1
ocf-metadata-client-1.1-20191004.123226-31-sources.jar.lastUpdated
ocf-metadata-client-1.1-20191004.123226-31.jar
ocf-metadata-client-1.1-20191004.123226-31.jar.sha1
ocf-metadata-client-1.1-20191004.123226-31.pom
ocf-metadata-client-1.1-20191004.123226-31.pom.sha1
ocf-metadata-client-1.1-SNAPSHOT-javadoc.jar
ocf-metadata-client-1.1-SNAPSHOT-sources.jar
ocf-metadata-client-1.1-SNAPSHOT.jar
ocf-metadata-client-1.1-SNAPSHOT.pom
resolver-status.properties
➜ 1.1-SNAPSHOT
whilst jfrog has
ocf-metadata-client-1.1-20190930.122708-28.pom 30-Sep-2019 12:27 1.39 KB
ocf-metadata-client-1.1-20191001.092428-29-javadoc.jar 04-Oct-2019 07:29 154.03 KB
ocf-metadata-client-1.1-20191001.092428-29-sources.jar 04-Oct-2019 07:29 54.83 KB
ocf-metadata-client-1.1-20191001.092428-29.jar 01-Oct-2019 09:24 59.44 KB
ocf-metadata-client-1.1-20191001.092428-29.pom 01-Oct-2019 09:24 1.39 KB
ocf-metadata-client-1.1-20191004.072919-30-javadoc.jar 04-Oct-2019 12:32 154.01 KB
ocf-metadata-client-1.1-20191004.072919-30-sources.jar 04-Oct-2019 12:32 54.83 KB
ocf-metadata-client-1.1-20191004.072919-30.jar 04-Oct-2019 07:29 59.44 KB
ocf-metadata-client-1.1-20191004.072919-30.pom 04-Oct-2019 07:29 1.39 KB
ocf-metadata-client-1.1-20191004.123226-31.jar 04-Oct-2019 12:32 59.44 KB
ocf-metadata-client-1.1-20191004.123226-31.pom 04-Oct-2019 12:32 1.39 KB
As can be seen from this, some builds do include the sources (-sources.jar), others dont.
Debugging java software with maven nicely requires these sources are available to 3rd parties (for open source it’s no concern sharing), indeed upload to maven central MANDATES source.
So there is something wrong in the build/upload - profiles perhaps, which needs investigating to better support consumers of Egeria.
Investigating …
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 22 (22 by maintainers)
This is the update I received this morning.
@planetf1 Here’s the gist for reproducing the issue.
Interestingly it appears the Artifactory “Builds” system is not involved - Though it might be able to help, we’ll see.
Responding to the issue I raised with JFrog, and will let you know when they’ve gotten back to me and hopefully directed us in the right direction - Or identified the bug that might exist in Artifactory. 🤞