Is this project still alive? Thank you. about ashley HOT 7 CLOSED

Hi, I am not actively maintaining it. Someone else in the libgdx contributors team could pick it up if they so desired.

from ashley.

But why? Any technical disadvantage? LidGDX app really needs this.
I know a js version of ECS framework, and they are getting a little bit thriving after years of nobody caring. That's how opens source really is.
People can fork it. What you mean "pick it up"?

from ashley.

Why: because, unfortunately, I don't have the time to work on it anymore.

I mean that any of the developers who currently manage libgdx are equipped to continue work on this project if they deem it important.

Due to its open source nature anyone can fork it or work from source as well.

from ashley.

I vote for having someone continue to work on.

from ashley.

I am happy to maintain this repo. it seems a robust ecs impl in java world. when I saw a concept of familiy, I can say this repo was written by people who really unsersatnd and practise ecs. codes are really clean and elegant to follow.

from ashley.

Hi @Kiddinglife do you think it's possible to publish a new Ashley release (1.7.4) soon? Ashley 1.7.3 is no longer compatible for a while with libgdx because of GWT upgrade. Precisely this fix. Devs have hard time with this bug.

We can discuss about it on libgdx discord server if you want :-)

Sorry i maybe misunderstood who is maintaining the repo now @dsaltares

from ashley.

If I understand it correctly, the problem (#279) can be fixed with uploading jar to maven central repository.
I have a maven (nexus) user id but not sure if I can upload to a different artifact group ID other than the group ID I had got by opening an issue there.
And I think it's important been authorized by the author.

Edit: Sorry guys, Ashley should also use gradle. Forgot It!

from ashley.