Remove gdx-ai from core repo

[Tom-Ski]

• Remove from parent pom.
• Remove from build
• Removed tests
• Removed code

[badlogic]

Hi guys, could you not remove modules without telling me about it? This influences the build among other things. Thanks.

[MobiDevelop]

In his defense, I told him he could merge if his new repo was ready because
people are/were having problems finding the right snapshots.

Blame me if it messed something up.

[NathanSweet]

I blame Nex.

On Sun, Sep 21, 2014 at 7:45 PM, Justin Shapcott notifications@github.com
wrote:

In his defense, I told him he could merge if his new repo was ready because
people are/were having problems finding the right snapshots.

Blame me if it messed something up.

—
Reply to this email directly or view it on GitHub
#2312 (comment).

[badlogic]

We had a plan to push out 1.3.2 with the old gdx-ai, then switch over to the new repo.

[badlogic]

The reason there'sno release yet is related to RoboVM which has issues on iOS 8. Once that's fixed i can do a release.

[MobiDevelop]

Ah, I guess that plan was not shared with everyone as I had no clue that
was the plan. For what it's worth, gdx-ai was never in the setup so I guess
the impact is somewhat low.

[Tom-Ski]

Shouldn't our next release be 1.4.0 due to API breakages? Given the circumstances, the least painful route could be to release 1.4.0 without ai in the core repo, bump the ai repo to 1.4.0 and release ai. From then on the release cycles can be completely independent.

[badlogic]

Right, communication. We do what Tomski does as soon as the RoboVM issues
are resolved.
On Sep 21, 2014 8:42 PM, "Tomski" notifications@github.com wrote:

Shouldn't our next release be 1.4.0 due to API breakages? Given the
circumstances, the least painful route could be to release 1.4.0 without ai
in the core repo, bump the ai repo to 1.4.0 and release ai. From then on
the release cycles can be completely independent.

—
Reply to this email directly or view it on GitHub
#2312 (comment).

[davebaol]

We had a plan to push out 1.3.2 with the old gdx-ai, then switch over to the new repo.

Sorry for the mess, I think I got confused by your comments below where you wrote that the next libgdx release will not include steering:

• libgdx/gdx-ai#1 (comment)
• libgdx/gdx-ai#1 (comment)

My bad :(