Skip to content
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

Unable to use clients repository proxy for the 'hardcoded' specs path #239

Open
Robin-Bezuijen opened this issue Jan 30, 2022 · 0 comments

Comments

@Robin-Bezuijen
Copy link

When using a client repo proxy (which is normal on customer projects not sharing the master credentials) the wagon urls will not work:

                    <configuration>
                        <url>https://repo.backbase.com/specs/accessgroup-integration-service</url>
                        <fromFile>accessgroup-integration-inbound-api-v2.2.0.yaml</fromFile>
                    </configuration>

the /specs path is not a repository (under /repo/specs)

Possible fixes:

  1. Add the specs to the repo to make https://repo.backbase.com/repo/specs/accessgroup-integration-service/accessgroup-integration-inbound-api-v2.2.0.yaml work.

  2. Use the bom and uzip all specs from a bom version to the downloaded-api folder:

                             <artifactItem>
                                 <groupId>com.backbase.dbs</groupId>
                                 <artifactId>banking-services-bom</artifactId>
                                 <version>${dbs-bom.version}</version>
                                 <classifier>api</classifier>
                                 <type>zip</type>
                                 <outputDirectory>${project.build.directory}/specs</outputDirectory>
                             </artifactItem>
    

Option 2 makes way more sense because then fuel is in sync with a BB release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant