Publish Fixy 2.1

[eskatos]

Fixy 2.0 is the last published version and is now 2 years old.

The master branch has many interesting changes such as field access support.

It would be great to get Fixy 2.1 published.

[eskatos]

Any chance to get feedback on this?

Do you plan to keep maintaining Fixy? or not?

[sberan]

@eskatos sorry for the delay on this, and thanks for following up. I've created an account with Sonatype OSS, and will be publishing there soon. My current setup of self-hosted repository is far from ideal and I'll be moving away from it as soon as my OSS project is created.

-Sam

[eskatos]

Excellent :+1:

[sberan]

Well, it looks like using com.fixy for my package name was a mistake. Sonatype OSS requires that I own the fixy.com domain in order to register the group ID of com.fixy. If I change the group ID of the project, I'd probably want to move the packages as well, since traditionally they should match up.

I'm thinking of buying fixy.io and using that, since I don't really like the idea of having the package tied to my github username. Ugh.

[eskatos]

I wonder how to help on this. Would you accept a PR for the package name change ?

[sberan]

:+1: sure would. io.fixy will run me $80 a year, which will probably get annoying after a couple of years. in.fixy is not quite as good, but at $15 a years is definitely tempting.

[eskatos]

Good. State on the package name and I'll go for the PR.

[sberan]

I already own samb.in, which I use for any personal projects, so I could go with in.samb.fixy for the package name - sound ok?

[eskatos]

Sure, it should make things much easier for you regarding Sonatype OSS policy. I'll do the PR during the week.

[sberan]

@eskatos Hope you haven't started yet, let's just use 'fixy' for the package, and decouple it from the domain name altogether.

[eskatos]

@sberan Was about to do it tomorrow so, right on time! I'll use "fixy" for package in the PR.

[eskatos]

Now that the code is ready, when do you plan to publish 2.1 to maven central ? Cheers

[eskatos]

@sberan Any news?

[mikehaas763]

Just discovered this package and saw this issue and am now wondering if this package is basically abandoned?

[eskatos]

@mikehaas763 looks like it is ... @sberan could you make a statement about this?

[sberan]

@mikehaas763 @eskatos sorry to be such a terrible maintainer here, guys. I'm not writing server-side Java anymore so I have very little motivation to keep working on Fixy. I can publish 2.1, but I would love it if someone more motivated wanted to become maintainer of this project. Does anybody want to take over?

[elnur]

:cry:

[fbreivald]

Are you still looking for a maintainer?

[sberan]

Yes. Interested?

On Thu, Mar 17, 2016 at 4:42 PM Fredrik Breivald [email protected] wrote:

Are you still looking for a maintainer?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/sberan/Fixy/issues/17#issuecomment-198095174

[fbreivald]

Yes, definitely.

[fbreivald]

Ping. Still interested :)

[sberan]

@fbreivald if you want to create a repository or organization i will redirect this one to it.

[ghost]

For the time being until release 2.1, one could use JitPack to use the latest commit in master: https://jitpack.io/#sberan/Fixy