Help with maintainance #18

mischah · 2016-02-21T12:55:58Z

Micromata can’t maintain the project actively. But we would love to find someone who is willing to take that over even if this person is only reviewing and merging PRs.

Please ping @micromata/developers in case your are interested.

Thanks in advance 😘

ZiglioUK · 2016-03-01T21:56:32Z

Hi @mischah

it would be nice to have someone to be in charge. I'm not sure if I can be that person, I don't want to take a responsibility I won't be able to fulfill. I'd be happy to help and fix a few bugs as a simple committer.
So, if you want to give me (and anybody who's sent pull requests) committer rights, I'm up for it.

Is anyone out there with a vision of where this project should be?
Should we aim just to fix the remaining bugs and produce a final release?
I can't see the KML standard moving too fast, which is a good thing.
Google Earth is in a state of abandonment unless Google decides to donate it to something like the Apache Foundation (it worked well AFAIK for projects such as SkyMap, MyTracks etc).
So once a new release is ready, would anybody from Micromata be able to push it to the Maven repository?

Pinging @maniksurtani, @SriramMLN, @SriramMLN

mischah · 2016-10-01T10:12:59Z

Hi @ZiglioNZ,

thanks for your feedback.

This would be one possible approach:

So, if you want to give me (and anybody who's sent pull requests) committer rights, I'm up for it.
So once a new release is ready, would anybody from Micromata be able to push it to the Maven repository?

But the initial idea I discussed with some workmates back February was to »transfer« the whole thing from micromata/javaapiforkml to yourname/javaapiforkml.

The other option needs to be discussed by @micromata/developers and @hthole. Someone will report back into this issue.

dgcooke · 2017-02-09T22:49:47Z

Could we get a gradle repository for it also?

Damien

mischah · 2017-02-10T07:48:20Z

@micromata/jak-dev @mcahornsirup fyi ⬆️

mcahornsirup · 2017-02-10T13:46:35Z

@mischah There are a lot of things to keep in mind... maybe we need to update the foundation itself and start using the official OGC-Dependencies (https://github.com/highsource/ogc-schemas/tree/master/kml) ... As a result, YAK would only be a small wrapper with a nicer syntax due to the builder pattern ...

SecuritasMachina · 2017-06-17T11:05:22Z

HI, I'm an experienced java team lead, I can manage this project here: https://github.com/ackdev/javaapiforkml

mischah · 2017-06-19T09:33:56Z

Hej @ackDev,

thanks for your offer 👌

There is no need to fork the repo. We could either add you as contributor to this repo or transfer the Repo with al its stars, open issues and PRs to your account.

It’s up to @micromata/jak-dev to decide how to proceed.

laubfall · 2017-06-19T10:03:50Z

Hi,

we planed to support this project in the future. But any help is welcome. So, as mischah mentioned you are welcome as a contributor. I'll do a review of the open issues to get an idea about the todos.

Greetings,
Daniel

SecuritasMachina · 2017-06-19T10:05:06Z

Hi Michael, I'm okay with transferring the repo and have renamed my existing one. Doesn't seem right to publish to maven under your domain, so I was planning to publish under my domain. I expect it'll be a minor dependency change for users of the library. I don't think transferring the repo will impact your current distributables in the maven repositories, so no existing usages will break. As there a lot of links to your github project, once the transfer is complete, can you setup a stub project to point to the new url? If not, it's not that big a deal. Let me know if you have any concerns or suggestions with this approach. Side note - not sure if intentional or not, however the following receives a 404, do you plan to maintain that or would you like to transfer that to me as well? <groupId>de.micromata.jak</groupId> <artifactId>XJCPluginJavaApiforKml</artifactId> <version>1.0.1-SNAPSHOT</version> Thanks, Charles

…

On Mon, Jun 19, 2017 at 5:33 AM, Michael Kühnel ***@***.***> wrote: Hej @ackDev <https://github.com/ackdev>, thanks for your offer 👌 There is no need to fork the repo. We could either add you as contributor to this repo or transfer the Repo with al its stars, open issues and PRs to your account. It’s up to @micromata/jak-dev <https://github.com/orgs/micromata/teams/jak-dev> to decide how to proceed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVZijBYCVeo6JhSfKOJWzncq7AVYNEFks5sFkCFgaJpZM4He8eB> .

mcahornsirup · 2017-06-19T10:56:23Z

Hej @ackDev,

just some additional thoughts about the current state of the project and its foundation.

The Java API for KML relies on XML-Schemas used to generate Java-Code... there are official Specifications, XML-Schemas and there are "official" Java-Libs available, too.
OGC-Standards: http://www.opengeospatial.org/standards
Java-Libs: https://github.com/highsource/ogc-schemas.

Maybe it is more suitable to use these, already generated, Java-Libs as a foundation and wrap them with syntactic sugar (builder pattern etc.) => Java API for KML

Happy Coding!

SecuritasMachina · 2017-06-19T22:53:43Z

Thanks for the pointer, applying same builder constructs you used on 2.2 is a great way to go for 2.3 using ogc's implementation.

…

On Mon, Jun 19, 2017 at 6:56 AM, Steffen Schuler ***@***.***> wrote: Hej @ackDev <https://github.com/ackdev>, just some additional thoughts about the current state of the project and its foundation. The *Java API for KML* relies on *XML-Schemas* used to generate Java-Code... there are official XML-Schemas and there are "official" Java-Libs available, too. https://github.com/highsource/ogc-schemas. Maybe it is more suitable to use these, already generated, Java-Libs as a foundation and wrap them with syntactic sugar (builder pattern etc.) => *Java API for KML* — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVZihbZvKGS2MFB65D8aVY2eYi7aLKzks5sFlPZgaJpZM4He8eB> .

Palmeta · 2020-04-26T01:47:39Z

Hi, I think this is a great project and it breaks my heart to see it abandoned. Is it possible just to get its dependencies updated as it is throwing illegal reflective access exceptions with the latest releases of java.

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 (file:/C:/Users/arlin.DESKTOP-AN92BDB/.m2/repository/com/sun/xml/bind/jaxb-impl/2.2/jaxb-impl-2.2.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

quilkin · 2020-12-29T09:43:43Z

Check out the KmlDocument class in https://github.com/MKergall/osmbonuspack for a better solution. See my answer at https://stackoverflow.com/questions/15636303/ for more details.

urbancamo · 2022-03-30T11:25:31Z

I have a port at https://github.com/urbancamo/javaapiforkml which has been updated to compile and run with Java 11 - Java 17. Regards, Mark.

It is available on mavencentral:

<dependency>
  <groupId>uk.m0nom</groupId>
  <artifactId>JavaAPIforKml</artifactId>
  <version>3.0.1</version>
</dependency>

danshome · 2023-05-29T03:43:56Z

@urbancamo @tuxBurner @mischah Are there any updates on getting a release done?

urbancamo · 2023-05-29T13:34:50Z

Unfortunately I don't have a way to release new versions at the moment. I am hoping that this part of the process will be handed over to me.

mischah · 2023-05-30T13:20:49Z

I have to admit that I don't have a plan about getting stuff released in the Java Eco system.

A colleague said that it is not necessary to publish that via Maven Central.

I will check again in our company chat who can help out here.

kristofdho · 2023-05-30T15:27:41Z

A colleague said that it is not necessary to publish that via Maven Central.

Could you elaborate on what your colleague ment by that and how we're supposed to consume this then?

mischah · 2023-05-31T07:26:51Z

Could you elaborate on what your colleague ment by that and how we're supposed to consume this then?

I guess a kinda misunderstood what he meant 🙈

Anyway, I’m taking care of this by myself.

According to https://central.sonatype.org/publish/manage-permissions/ permissions to publish to Maven Central are handled by Jira Tickets.

@urbancamo Therefore I need your Username of this Jira instance: https://issues.sonatype.org/
You can create a user if you don't have one yet.

urbancamo · 2023-05-31T08:45:05Z

Good morning @mischah Michael.
My username is the same on that site, @urbancamo

I do releases of my own software, so should be able to work this out once I have permissions.

Regards, Mark

urbancamo · 2023-06-13T08:10:55Z

Any progress @mischah Michael?

urbancamo · 2023-08-02T16:54:37Z

Checking in again, Any progress @mischah Michael?

urbancamo · 2023-11-20T21:58:03Z

I've had several emails about maintenance, and as we've had issues getting maintenance going for the main repo I've decided to move to my fork at https://github.com/urbancamo/javaapiforkml and bring that up to date with all the PRs and bug fix requests. As it stands now the latest version 3.0.2 supports Java 11 although it does need several pull requests to be applied moving forward. You will need to change the name of the package in your pom file, but there should be no compatibility issues, obviously raise any issues on the fork itself. Thanks to the folk at Micromata for open sourcing this library.

mischah · 2023-11-21T07:26:27Z

Hej @urbancamo, Thanks for your efforts 🙏🏻

Guess that’s the best way to handle it without further frustrations 😔

Another option to avoid confusion would be to transfer this repo micromata/javaapiforkml to urbancmo/javaapiforkml.
This way your repo wouldn’t not only contain the Git history, but also the history of issues and PRs. Plus your repo would be the single source oof truth.

Let me know what you are thinking about this.

urbancamo · 2023-11-21T09:22:00Z

Hi @mischah, thanks for the reply. If we can still get access for me to publish from this repo then I'm happy to proceed on that basis, otherwise I'm not sure what the process is for getting the entire repo moved, but I have been able to publish from my fork so at least we have a way forward. Cheers, Mark.

mischah · 2023-11-21T10:53:51Z

Hej @urbancamo,

otherwise I'm not sure what the process is for getting the entire repo moved

the process ist pretty much straight forward.

Thanks for your patience. As it's not my project, I'm not that committed to taking care of moving things forward. I'm really sorry about that and totally understand the way you handle it. But I’m also happy that you are willig to take care about it 💖

I’m willing to try to get you publish Access. Moving this up on my TODO List. Maybe we should revisited this in 1 Month and decide about the transfer.

Thanks again ❤️ 💯

Cheers, Michael

urbancamo · 2023-11-21T13:01:09Z

Hi Michael

Transfer ownership is the way to go I think Michael, if you want to give that a go? Then I don't have to bother you if there are any issues further down the line.

Regards, Mark.

mischah · 2023-11-21T13:04:46Z

Let’s do it 🥳

Guess you have to (temporarly) rename you existing repo (the fork) to avoid naming conflicts.
Ping me if you’ve done this.

danshome · 2023-11-21T13:09:52Z

BTW... Please consider #35. I did most of the work for you to modernize the build months ago. Thanks, Dan McLaughlin

mischah · 2023-11-21T13:13:02Z

@danshome

Hope @urbancamo will take care of it and your efforts will be pulled in 👀

urbancamo · 2023-11-21T13:30:18Z

OK @mischah I've renamed my fork... thanks.

urbancamo · 2023-11-21T13:30:59Z

BTW... Please consider #35. I did most of the work for you to modernize the build months ago. Thanks, Dan McLaughlin

Hi Dan - noted as I've looked through all the potential PRs, and plan to merge everything sensible in when the repo has stabilized, thanks.

Mark.

mischah · 2023-11-21T13:39:39Z

Weird 🤪

I’m going to try to transfer it via my userpace to your 🧐

mischah · 2023-11-21T13:42:54Z

Okay. Guess you have to delete your fork (on github.com)

Ping if this it done. I can transfer the repo afterwards.

urbancamo · 2023-11-21T13:47:25Z

OK @mischah the fork has been deleted.

mischah · 2023-11-21T13:49:00Z

👍🏻

It’s on its way

urbancamo · 2023-11-21T13:50:23Z

That's been successful @mischah - thanks very much for your time today.

mischah · 2023-11-21T13:50:29Z

It’s done:
https://github.com/urbancamo/javaapiforkml

Congrats 🎉

mischah · 2023-11-21T13:50:52Z

Thanks for taking care of it 🥇

urbancamo · 2023-11-21T18:06:12Z

All sorted now! Closing issue

stundzig mentioned this issue Aug 4, 2016

[Import] KML Polymap4/polymap4-p4#38

Closed

laubfall self-assigned this Dec 27, 2017

urbancamo closed this as completed Nov 20, 2023

urbancamo reopened this Nov 21, 2023

urbancamo closed this as completed Nov 21, 2023

urbancamo unpinned this issue Nov 21, 2023

Help with maintainance #18

Help with maintainance #18

Comments

mischah commented Feb 21, 2016

ZiglioUK commented Mar 1, 2016

mischah commented Oct 1, 2016

dgcooke commented Feb 9, 2017

mischah commented Feb 10, 2017

mcahornsirup commented Feb 10, 2017 • edited Loading

SecuritasMachina commented Jun 17, 2017 • edited Loading

mischah commented Jun 19, 2017

laubfall commented Jun 19, 2017

SecuritasMachina commented Jun 19, 2017 via email

mcahornsirup commented Jun 19, 2017 • edited Loading

SecuritasMachina commented Jun 19, 2017 via email

Palmeta commented Apr 26, 2020 • edited Loading

quilkin commented Dec 29, 2020

urbancamo commented Mar 30, 2022 • edited Loading

danshome commented May 29, 2023

urbancamo commented May 29, 2023

mischah commented May 30, 2023

kristofdho commented May 30, 2023 • edited Loading

mischah commented May 31, 2023

urbancamo commented May 31, 2023

urbancamo commented Jun 13, 2023

urbancamo commented Aug 2, 2023

urbancamo commented Nov 20, 2023

mischah commented Nov 21, 2023

urbancamo commented Nov 21, 2023

mischah commented Nov 21, 2023

urbancamo commented Nov 21, 2023

mischah commented Nov 21, 2023

danshome commented Nov 21, 2023 via email • edited by mischah Loading

mischah commented Nov 21, 2023

urbancamo commented Nov 21, 2023

urbancamo commented Nov 21, 2023

mischah commented Nov 21, 2023

mischah commented Nov 21, 2023 • edited Loading

urbancamo commented Nov 21, 2023

mischah commented Nov 21, 2023

urbancamo commented Nov 21, 2023

mischah commented Nov 21, 2023

mischah commented Nov 21, 2023

urbancamo commented Nov 21, 2023

mcahornsirup commented Feb 10, 2017 •

edited

Loading

SecuritasMachina commented Jun 17, 2017 •

edited

Loading

mcahornsirup commented Jun 19, 2017 •

edited

Loading

Palmeta commented Apr 26, 2020 •

edited

Loading

urbancamo commented Mar 30, 2022 •

edited

Loading

kristofdho commented May 30, 2023 •

edited

Loading

danshome commented Nov 21, 2023 via email •

edited by mischah

Loading

mischah commented Nov 21, 2023 •

edited

Loading