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

List maven repositories that were used when resolution of artifact fails #89

Closed
markpollack opened this issue Jul 5, 2016 · 2 comments
Assignees
Labels
type/backport Is a issue to track backport, use with branch/xxx
Milestone

Comments

@markpollack
Copy link
Contributor

markpollack commented Jul 5, 2016

the error message

dataflow:>stream create --name http2file --definition "http | mytransformer | log" --deploy
Command failed org.springframework.cloud.dataflow.rest.client.DataFlowClientException: failed to resolve MavenResource: org.springframework.cloud.stream.app:log-sink-rabbit:jar:1.0.0.BUILD-SNAPSHOT

failed to resolve MavenResource: org.springframework.cloud.stream.app:log-sink-rabbit:jar:1.0.0.BUILD-SNAPSHOT

org.springframework.cloud.dataflow.rest.client.DataFlowClientException: failed to resolve MavenResource: org.springframework.cloud.stream.app:log-sink-rabbit:jar:1.0.0.BUILD-SNAPSHOT

should have more info on remote repo locations.

@markfisher
Copy link
Contributor

Do you have the full trace? As far as I know the repository URL is listed in the trace, but not exactly where you would expect.

@sabbyanandan sabbyanandan added this to the 1.0.4.RELEASE milestone Oct 3, 2016
@trisberg trisberg modified the milestones: 1.1.0.M2, 1.0.4.RELEASE Oct 14, 2016
@sabbyanandan sabbyanandan assigned ghillert and unassigned markpollack Nov 3, 2016
@ghillert ghillert added in progress and removed ready labels Nov 5, 2016
ghillert added a commit to ghillert/spring-cloud-deployer that referenced this issue Nov 8, 2016
@ghillert ghillert added in pr and removed in progress labels Nov 8, 2016
@ghillert
Copy link
Contributor

ghillert commented Nov 8, 2016

Some discussion points:

The PR is at best a work-around. Ideally the deployer's resource resolution should have proper (abstracted) exception handling defined.

At present the Deployer SPI does not define exception handling well. We use the super generic org.springframework.core.io.Resource class backed by the generic ResourceLoader so that everything is abstracted away. Unfortunately, those classes don't define exception handling.

ghillert pushed a commit to ghillert/spring-cloud-deployer that referenced this issue Nov 8, 2016
…ion of artifact fails

- Add `ResourceNotResolvedException` to `DelegatingResourceLoader`
@sabbyanandan sabbyanandan removed the in pr label Nov 8, 2016
donovanmuller pushed a commit to donovanmuller/spring-cloud-deployer that referenced this issue Nov 12, 2016
…ion of artifact fails

- Add `ResourceNotResolvedException` to `DelegatingResourceLoader`
@cppwfs cppwfs added type/backport Is a issue to track backport, use with branch/xxx and removed for/backport labels Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/backport Is a issue to track backport, use with branch/xxx
Projects
None yet
Development

No branches or pull requests

6 participants