Skip to content
This repository has been archived by the owner on Dec 18, 2021. It is now read-only.

Be defensive about creating directories for files #29

Merged
merged 1 commit into from
Apr 4, 2017

Conversation

dsyer
Copy link

@dsyer dsyer commented Nov 3, 2016

Maven 3.4 snapshots are now being published with invalid
zip files, where the entries are listed before their parent.
So the logic in the Installer is faulty: you have to mkdirs()
on all entries to be sure that the directory exists before you
write the file.

Maven 3.4 snapshots are now being published with invalid
zip files, where the entries are listed before their parent.
So the logic in the Installer is faulty: you have to mkdirs()
on all entries to be sure that the directory exists before you
write the file.
@dsyer
Copy link
Author

dsyer commented Nov 3, 2016

Arguably we should fix the zip files in 3.4 snapshots as well, but I figure it is better to be defensive here as well.

P.S. I didn't add a test because I don't understand well enough the way the Installer needs to be set up. I tested the jar file locally though and it works.

@dejan2609
Copy link

Kudos to to you @dsyer ! I was just about to create similar MR, but then I bumped into this one.

To whom it may concern: please consider to review and merge this change... Maven 3.4 is dropped, but Maven 3.5 is just around the corner (with same issues as described above, at lest in version 3.5.0-beta-1).

@dejan2609
Copy link

Update: it seems that issue will be solved on Maven side (version 3.5.0):

@jvanzyl
Copy link

jvanzyl commented Apr 3, 2017

@dsyer you just want commit access?

@dsyer
Copy link
Author

dsyer commented Apr 4, 2017

I don't think that's necessary, but go ahead if you think it's appropriate.

@jvanzyl
Copy link

jvanzyl commented Apr 4, 2017

It's more if you have fixes and then want to make releases to Maven Central, you'd be able to. Entirely up to you. Would be great to have others who can apply fixes and release.

@dsyer
Copy link
Author

dsyer commented Apr 4, 2017

I'm happy to be included I guess. What kind of process do you need to decide when to deploy a release? And you probably need to add me to the list of permitted deployers at sonatype for your groupid?

@jvanzyl
Copy link

jvanzyl commented Apr 4, 2017

If you feel like you want to do a release you can :-) Very simple.

@mosabua
Copy link
Member

mosabua commented Apr 4, 2017

@dsyer I can always do the release process for you. Also when we release this component we need to follow up with a release of the maven plugin. I think a good time to do a release would be soon after Maven 3.5.0 is shipped. Then we can also update that default version..

@mosabua
Copy link
Member

mosabua commented Apr 4, 2017

Also .. wdyt @dsyer .. this PR is still valuable and there is no harm .. so should we still merge? I tend to think yes..

@dsyer
Copy link
Author

dsyer commented Apr 4, 2017

Totally. Should be merged and released. I've been using a patched version for months now.

@mosabua mosabua merged commit 06e6db9 into takari:master Apr 4, 2017
@mosabua
Copy link
Member

mosabua commented Apr 4, 2017

Let me do that this week. Still have to check a couple of other PRs...

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

Successfully merging this pull request may close these issues.

4 participants