Skip to content

[CAMEL-18156] Add support for hyperledger-aries #7973

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

Merged
merged 2 commits into from
Jul 15, 2022

Conversation

tdiesler
Copy link
Contributor

@tdiesler tdiesler commented Jul 5, 2022

No description provided.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 5, 2022

⚠️ This PR changes Camel components and will be tested automatically.

@tdiesler tdiesler changed the title Camel 18156 [CAMEL-18156] Add support for hyperledger-aries Jul 5, 2022
Copy link
Contributor

@oscerd oscerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems good, only minor findings related to ASF headers and version

"title": "Aries",
"description": "Access market data and trade on Bitcoin and Altcoin exchanges.",
"deprecated": false,
"firstVersion": "3.17.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First version should be 3.19.0 I suppose, because 3.18.0 is on vote already

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@@ -0,0 +1,44 @@
/*-
* #%L
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section should be removed from the license header.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These headers are generated with the maven plugin. I suppose you don't manually maintain license headers across all files. I can remove all headers with plugin and perhaps then regenerate in the way you want it, but how would I do that?

@@ -0,0 +1,152 @@
/*-
* #%L
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

@@ -0,0 +1,101 @@
/*-
* #%L
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

@@ -0,0 +1,101 @@
/*-
* #%L
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

@@ -0,0 +1,112 @@
/*-
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

@github-actions
Copy link
Contributor

github-actions bot commented Jul 5, 2022

❌ Finished component verification: 1 component(s) test failed out of 2 component(s) tested

@tdiesler
Copy link
Contributor Author

These headers are generated with the maven plugin. I suppose you don't manually maintain license headers across all files. I can remove all headers with plugin and perhaps then regenerate in the way you want it, but how would I do that?

Anything I can do to unlock this?

@zhfeng
Copy link
Contributor

zhfeng commented Jul 12, 2022

@tdiesler maybe you can run mvn -Plicense license:format on the hyperledger-aries component?

@tdiesler tdiesler force-pushed the CAMEL-18156 branch 2 times, most recently from 370cf0f to 1d43092 Compare July 12, 2022 08:36
@tdiesler
Copy link
Contributor Author

@zhfeng Merci, that seems to have worked

@oscerd
Copy link
Contributor

oscerd commented Jul 12, 2022

We need to check how the plugin manages the license. But not your fault, so you could ignore my comment.

@tdiesler
Copy link
Contributor Author

checkstyle passes for me locally

mvn -Dcheckstyle.failOnViolation=true checkstyle:checkstyle
...
[INFO] --- maven-checkstyle-plugin:3.1.2:checkstyle (default-cli) @ camel-hyperledger-aries ---
[INFO] Starting audit...
Audit done.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

@zhfeng
Copy link
Contributor

zhfeng commented Jul 12, 2022

The CI failure looks like not related to code styles. I think it should be good.

ERROR] Failed to execute goal on project camel-allcomponents: Could not resolve dependencies for project org.apache.camel:camel-allcomponents:pom:3.19.0-SNAPSHOT: Could not find artifact org.apache.camel:camel-hyperledger-aries:jar:3.19.0-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots/) -> [Help 1]

@tdiesler can you check the build.log on https://github.com/apache/camel/actions/runs/2655649560? The compilation error is

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project camel-hyperledger-aries: Compilation failure
[ERROR] /home/runner/work/camel/camel/components/camel-hyperledger-aries/src/main/java/org/apache/camel/component/aries/HyperledgerAriesEndpoint.java:[49,76] error: cannot find symbol
[ERROR]   symbol:   variable IDENTITY
[ERROR]   location: class Category
[ERROR] -> [Help 1]

@tdiesler
Copy link
Contributor Author

tdiesler commented Jul 12, 2022

@zhfeng It's here https://github.com/tdiesler/camel/blob/CAMEL-18156/core/camel-api/src/generated/java/org/apache/camel/Category.java#L55

Perhaps that file is indeed generated and I should define that new category elsewhere?

@zhfeng
Copy link
Contributor

zhfeng commented Jul 12, 2022

@github-actions
Copy link
Contributor

❌ Finished component verification: 3 component(s) test failed out of 5 component(s) tested

1 similar comment
@github-actions
Copy link
Contributor

❌ Finished component verification: 3 component(s) test failed out of 5 component(s) tested

@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 2 component(s) tested

@tdiesler
Copy link
Contributor Author

This is now failing for some unknown reason

[INFO] Running org.apache.camel.converter.aries.ConnectionReceiveInvitationFilterConverterTest
[WARNING] Tests run: 8, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.523 s - in org.apache.camel.converter.aries.ConnectionReceiveInvitationFilterConverterTest
[INFO] Running org.apache.camel.converter.aries.SchemaSendRequestConverterTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 s - in org.apache.camel.converter.aries.SchemaSendRequestConverterTest
[INFO] Running org.apache.camel.converter.aries.V1CredentialFreeOfferRequestConverterTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s - in org.apache.camel.converter.aries.V1CredentialFreeOfferRequestConverterTest
[INFO] 
[INFO] Results:
[INFO] 
[WARNING] Tests run: 10, Failures: 0, Errors: 0, Skipped: 6

@oscerd
Copy link
Contributor

oscerd commented Jul 13, 2022

I just noticed that the library is not on Maven central. Is that for a particular reason? We already had a lot of troubles with 3rd party Maven repositories like Atlassian.. So I'd really prefer to have the lib on Maven central.

@tdiesler
Copy link
Contributor Author

Do you mean the nessus-aries component? Like nessus-ipfs, nessus-xchange, they are published to the redhat 3rd party repository, for which I have access. I've never published anything on central, so far.

@oscerd
Copy link
Contributor

oscerd commented Jul 13, 2022

Yes, I mean 3rd party repositories in general. All of them are less reliable than central. It's not really a problem, but at some point I'd move the libraries there

@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 2 component(s) tested

@tdiesler
Copy link
Contributor Author

sure, we can do that when needed

@github-actions
Copy link
Contributor

✔️ Finished component verification: 0 component(s) test failed out of 2 component(s) tested

@github-actions
Copy link
Contributor

✔️ Finished component verification: 0 component(s) test failed out of 3 component(s) tested

@oscerd
Copy link
Contributor

oscerd commented Jul 13, 2022

I'll try to merge this week.

@tdiesler
Copy link
Contributor Author

This is now failing for some unknown checkstyle issue

@oscerd
Copy link
Contributor

oscerd commented Jul 14, 2022

Maybe try to rebase on main

@github-actions
Copy link
Contributor

✔️ Finished component verification: 0 component(s) test failed out of 3 component(s) tested

@oscerd oscerd merged commit aa7549b into apache:main Jul 15, 2022
@tdiesler tdiesler deleted the CAMEL-18156 branch July 15, 2022 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants