Code Monkey home page Code Monkey logo

Comments (8)

takezoe avatar takezoe commented on July 2, 2024

@aadrian package name hasn't been updated to com.miragesql.

from mirage.

aadrian avatar aadrian commented on July 2, 2024

package name hasn't been updated to com.miragesql.

Not in the sources, only in the mvn descriptor for now.

Since changing the sources would break existing software, there should be a major not minor version update for this, and I would like to write a Migration Guide first.

from mirage.

aadrian avatar aadrian commented on July 2, 2024

@takezoe a first version of the Migration Guide: https://github.com/mirage-sql/mirage/wiki/Migration-Guide

from mirage.

takezoe avatar takezoe commented on July 2, 2024

@aadrian Thanks. I felt 2 step migration might be redundant. How about updating to 2.0.0 directly, not through 1.3.x?

from mirage.

aadrian avatar aadrian commented on July 2, 2024

Well, I already updated libraries and Java to 8 for 1.3.0 (so it's not just a version bump) and I'm in the process of aquiring a Nexus ORG for com.sqlmirage (since it can't publish to the old one): https://issues.sonatype.org/browse/OSSRH-30759

The 1.3.0 might redundant but it's a simple drop in replacement as opposed to 2.0.0 that requires user code changes since imports must be updated too.

from mirage.

takezoe avatar takezoe commented on July 2, 2024

Well, I already updated libraries and Java to 8 for 1.3.0 (so it's not just a version bump) and I'm in the process of aquiring a Nexus ORG for com.sqlmirage (since it can't publish to the old one): https://issues.sonatype.org/browse/OSSRH-30759

Thanks. Do you mean we will continue to maintain 1.3.x for existing users who can't move to 2.0.0? That's reasonable. I will update the subject of this issue to just "Update group id" and close again.

and naming of 1.x branch may be confusing a little, because 1.3.0 is not on 1.x branch despite it's matching 1.x.

from mirage.

aadrian avatar aadrian commented on July 2, 2024

Do you mean we will continue to maintain 1.3.x for existing users who can't move to 2.0.0?

Yes, for a while. There are many extensions (priavate) that depend on the old package naming so keeping that for a while (until the project is split in modules at least) makes sense IMHO.

and naming of 1.x branch may be confusing a little

Indeed. I'll delete it and when 2.0.0 will be out, I'll make a new branch: 1.3.x

from mirage.

takezoe avatar takezoe commented on July 2, 2024

Thanks. All became clear.

from mirage.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.