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

Fix maven directories for publishing #1139

Closed

Conversation

r4stered
Copy link
Contributor

@r4stered r4stered commented Jan 8, 2024

This fixes the issue where new releases were going to a photonlib-* directory instead of PhotonLib-*

@@ -7,7 +7,7 @@ apply plugin: "edu.wpi.first.NativeUtils"
import java.nio.file.Path

ext {
nativeName = "photonlib"
Copy link
Member

@srimanachanta srimanachanta Jan 8, 2024

Choose a reason for hiding this comment

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

These really should be lowercase, this would also cause the vendordep to break which we want to avoid. Is there a specific reason why this change resolves the issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

def baseArtifactId = nativeName

This line makes the artifact id based on the nativename. Thats why this fixes the maven dir issue

Copy link
Contributor

Choose a reason for hiding this comment

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

Why would the vendor dep break?

Copy link
Member

Choose a reason for hiding this comment

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

Because the vendordep is looking for that, previously it was Title case but now it is all lowercase, old vendor deps are looking for Title case, whereas all beta vendordeps are looking for lowercase. Going back would break all beta vendordeps.

@mcm001
Copy link
Contributor

mcm001 commented Jan 8, 2024

Proposal: just change the artifact id of the json?

@mcm001
Copy link
Contributor

mcm001 commented Jan 8, 2024

Also keep in mind that windows is not case sensitive. If we change caps we should also change spelling

@srimanachanta
Copy link
Member

srimanachanta commented Jan 8, 2024

Also keep in mind that windows is not case sensitive. If we change caps we should also change spelling

Changes between years have only been in capitalization, not spelling, windows should be unaffected? I vote to just change the URL, especially if we are already fine with breaking the year to year, cause we did

@mcm001
Copy link
Contributor

mcm001 commented Jan 11, 2024

Let's change

artifactId = "${nativeName}-json"
to match the old name instead.

@mcm001
Copy link
Contributor

mcm001 commented Jan 21, 2024

Closing for now since it seems like we just stuck with the quietly breaking change

@mcm001 mcm001 closed this Jan 21, 2024
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

Successfully merging this pull request may close these issues.

3 participants