Publish Fixy 2.1

Question

Publish Fixy 2.1

Opened this issue 11 years ago · 23 comments

eskatos commented 11 years ago

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.

elnur commented 9 years ago

😢

Answer 1 · 2013-10-16T09:14:35.000Z

Any chance to get feedback on this?

Do you plan to keep maintaining Fixy? or not?

Answer 2 · 2013-10-19T02:33:24.000Z

@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

Answer 3 · 2013-10-19T14:07:32.000Z

Excellent 👍

Answer 4 · 2013-10-21T18:56:51.000Z

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.

Answer 5 · 2013-11-04T16:15:22.000Z

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

Answer 6 · 2013-11-04T16:26:41.000Z

👍 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.

Answer 7 · 2013-11-04T17:02:47.000Z

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

Answer 8 · 2013-11-05T14:34:10.000Z

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?

Answer 9 · 2013-11-05T15:35:58.000Z

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

Answer 10 · 2013-11-11T15:33:46.000Z

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

Answer 11 · 2013-11-11T18:26:46.000Z

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

Answer 12 · 2013-11-25T10:48:31.000Z

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

Answer 13 · 2014-02-18T12:03:50.000Z

@sberan Any news?

Answer 14 · 2014-07-03T13:55:59.000Z

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

Answer 15 · 2014-07-18T11:34:03.000Z

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

Answer 16 · 2014-07-18T18:20:35.000Z

@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?

Answer 17 · 2016-03-17T21:42:12.000Z

Are you still looking for a maintainer?

Answer 18 · 2016-03-19T17:44:25.000Z

Yes. Interested?

On Thu, Mar 17, 2016 at 4:42 PM Fredrik Breivald notifications@github.com
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
#17 (comment)

Answer 19 · 2016-03-23T17:19:42.000Z

Yes, definitely.

Answer 20 · 2016-06-28T18:39:11.000Z

Ping. Still interested :)

Answer 21 · 2017-03-25T18:29:41.000Z

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

Answer 22 · 2017-06-27T07:59:12.000Z

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