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.

Sign up for GitHub

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

Jump to bottom

Could not find :unspecified: when importing transitive dependencies #294

Open
rm3l opened this issue Apr 22, 2022 · 3 comments
Open

Could not find :unspecified: when importing transitive dependencies #294

rm3l opened this issue Apr 22, 2022 · 3 comments
Labels
bug lifecycle/frozen

Comments

@rm3l
Copy link
Owner

rm3l commented Apr 22, 2022 •
edited
Loading

Looks like the generated POMs published to Maven Central contain a weird unspecified dependency:

<dependency>
   <groupId/>
    <artifactId>unspecified</artifactId>
    <version/>
</dependency>

This seems to affect maoni, maoni-common as well as all other callback libraries.

We need to understand where this comes from and fix it.
@rm3l rm3l mentioned this issue Apr 22, 2022
Closed
rm3l added a commit that referenced this issue Apr 22, 2022
@rm3l
Document temporary workaround when importing transitively
547ced7 
Importing each dependency non-transitively (as suggested in #253)
might require users to specify each dependency
indivifually, which might quickly feel cumbersome.

ref #253
ref #294
@rm3l rm3l added the bug label Apr 22, 2022
@rm3l rm3l changed the title Could not find :unspecified:. when importing transitive dependencies Could not find :unspecified: when importing transitive dependencies May 7, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jul 3, 2023 •
edited by rm3l
Loading

A friendly reminder that this issue had no activity for at least 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 7, 2023

A friendly reminder that this issue had no activity for at least 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 6, 2023

This issue was closed because it has been inactive for 90 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023
@rm3l rm3l reopened this May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug lifecycle/frozen
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rm3l