Create Maven Snapshots about richtextfx

[TomasMikula]

Hi Michael,

thanks for your interest. It has been on my to-do list for a while, together with changing the package name to match the standard reversed domain name. At this occasion, I may as well change the name of the project, since CodeAreaFX is no longer just for writing code, but also has some rich-text support.

Stay tuned.

[miho]

Have you thought about adding it to JFXtras? We just moved from a monolithic project to a modular one. In my opinion CodeAreaFX would perfectly fit into it. And @tbee already did the Maven upload configuration etc. So you wouldn't have to start from scratch.

Here's the link to the mailing list: https://groups.google.com/forum/#!forum/jfxtras-dev

Anyway, keep up the good work!

[TomasMikula]

I have thought about it. I also had a discussion with @JonathanGiles about contributing it to OpenJFX or ControlsFX. We have come to the conclusion that for now it's probably best to keep CodeArea as a separate project. The reasons are mainly twofold:

1. CodeAreaFX is (still) licensed under GPLv2 with Classpath exception (not a problem for OpenJFX).
2. CodeAreaFX has dependencies on ReactFX and UndoFX.

My other worry with going right to OpenJFX would be that if we don't get the API right the first time, we won't ever be able to fix it.

Anyway, what is the JFXtras policy towards having third-party dependencies?
What exactly does modular mean? Especially

1. Can modules have separate repositories?
2. Can modules use a different license?

My personal plan for now is to first get ReactFX and UndoFX to Sonatype, then get CodeAreaFX to Sonatype. In the long term, I am still open to contributing to another open-source project.

[tbee]

In light of IoT we have separated the official release which was extracted from JFXtras-labs (aka incubator) into individual jars; things like common, controls, windows, agenda. This will give each module the freedom to bloat or not (and also use any external dependencies) as it pleases without influencing other jars.
https://github.com/JFXtras/jfxtras

Now, I do not know if Jonathan wants a subproject or add to controlsFX, but for JFXtras you most definitely will be a subproject on your own and there are no problems on dependencies to 3rd party components. The advantage of joining up with a project like ControlFX or JFXtras are that you can spent your time better; the automated nightly builds with pushing into Maven are already setup, and hopefully soon also running the tests (JFX has problems there on a headless server).

A separate license is a bit of a challenge, it can be done of course, but different licenses in a single project would be confusing. We use the new BSD (http://en.wikipedia.org/wiki/BSD_licenses)

I'm unclear why you would want to release to a different repository than Sonatype for snapshots and Maven central for releases.

I think you are wise not to contribute to OpenJFX.

On 2014-2-28 12:45, TomasMikula wrote:

I have thought about it. I also had a discussion with @JonathanGiles https://github.com/JonathanGiles about contributing it to OpenJFX or ControlsFX. We have come to the conclusion that for now it's probably best to keep CodeArea as a separate project. The reasons are mainly twofold:

1. CodeAreaFX is (still) licensed under GPLv2 with Classpath exception (not a problem for OpenJFX).
2. CodeAreaFX has dependencies on ReactFX https://github.com/TomasMikula/ReactFX and UndoFX https://github.com/TomasMikula/UndoFX. My other worry with going right to OpenJFX would be that if we don't get the API right the first time, we won't ever be able to fix it.

Anyway, what is the JFXtras policy towards having third-party dependencies?
What exactly does /modular/ mean? Especially

1. Can modules have separate repositories?
2. Can modules use a different license?

My personal plan for now is to first get ReactFX and UndoFX to Sonatype, then get CodeAreaFX to Sonatype. In the long term, I am still open to contributing to another open-source project.

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

[TomasMikula]

Thanks for your input, Tom.

The freedom of external dependencies sounds good to me.

Regarding a different repository, I meant source code repository, not maven repository. I asked mainly because of the (now) different license.

[tbee]

A different source repository would be very unpractical for a nightly build.

Tom

On 2014-2-28 15:47, TomasMikula wrote:

Thanks for your input, Tom.

The freedom of external dependencies sounds good to me.

Regarding a /different repository/, I meant source code repository, not maven repository. I asked mainly because of the (now) different license.

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

[TomasMikula]

Snapshots are now in Sonatype.

groupId: 'org.fxmisc.richtext'
artifactId: 'richtextfx'
version: '1.0.0-SNAPSHOT'

[miho]

Good news!