WorldWind 2.1.0 Release to Maven Central

[mckelvym-usgs]

Hi @pdavidc,

I'm currently relying on WorldWindJava 2.0.0 from Maven Central. I see that the 2.1.0 release fixes problems with HTTP/HTTPS map services (Thank You!), which addresses the recent government mandate/switchover.

Is 2.1.0 available in Maven Central? If not, could it be published to Maven Central?

I'm using the following coordinates:

  <dependency>
      <groupId>gov.nasa</groupId>
      <artifactId>worldwind</artifactId>
      <version>2.0.0</version>
  </dependency>
  <dependency>
      <groupId>gov.nasa</groupId>
      <artifactId>worldwindx</artifactId>
      <version>2.0.0</version>
  </dependency>

Thanks,

• Mark

[vincent-bruel]

Hi, I agree there is a strong need for "pom" packaging, this helps integrating worldwind in just seconds. Worldwind is present here, but it is an "old" version: https://maven-repository.com/artifact/gov.nasa But maybe it's not the guys of worldwind that created this repo ?

Anyway, thanks for the great job.

[jakebeal]

Please do update the Maven release ASAP! This is a critical issue because the change on the server end breaks all existing WorldWind code deployed with the use of Maven or similar integration.

[pdavidc]

The artifacts in Maven Central aren't provided by the NASA World Wind team. We plan to publish official artifacts soon.

[jakebeal]

Glad to hear they will be updated soon. If NASA doesn't provide the Maven Central artifacts, who does?

[AlexFalappa]

The artifacts on Maven Central have been uploaded by some one other than NASA I believe. They are badly packaged and they lack proper dependencies in their pom (no jogl and gluegen).

While looking for exact coordinates I just found that there is also

<dependency>
    <groupId>com.github.pcmehlitz</groupId>
    <artifactId>worldwind-pcm</artifactId>
    <version>2.1.0.180</version>
</dependency>

coming from https://github.com/pcmehlitz/WorldWindJava-pcm that looks promising (it's a fork of this repository)

[jakebeal]

The updated version of the 3rd party release (worldwind-pcm) solves the problem.

@pdavidc Will NASA be releasing an official version on Maven, or should this bug be closed as now having a workaround solution?

[venabled]

Any progress here? The pcmehiltz versions on Maven don't include worldwindx , and I don't think have the native artifacts for gdal.

[AndrewTasso]

I'd also like to throw in a request for this. Our team is still using 2.0 since we can't resolve the proper dependencies in gradle.

[pdavidc]

Thanks for letting us know. The NASA team will be working to publish official NASA World Wind Java artifacts on JCenter and Maven Central in the next few weeks. As part of that work we're going to automate the publication process to ensure all future releases are available there.

[AndrewTasso]

@pdavidc Any word on this?

[pdavidc]

@AndrewTasso. We're committed to publishing all of our Java work on Maven Central and JCenter. My original estimate of a few weeks was overly optimistic. We'll update everyone watching this issue when we take on this work, hopefully soon.

[AndrewTasso]

@pdavidc Thanks for the update! We appreciate you teams' hard work.

[grammesm]

@pdavidc Any update on this? Trying to package worldwind into a maven jar and it's a real pain with manual dependencies.

[neogeogre]

it's a real pain with manual dependencies.

Yes

[jasonCodesAway]

@pdavidc Thank you for doing this much needed work! WorldWind has been a key enabling library for years now :)

[ajmcastro]

Hi @pdavidc thanks for the great job you are doing with Worldwind. Any news on the publishing on Maven Central? Thanks again for your team work. Cheers.

[henriquebferreira]

@pdavidc Hello. Any news?

[neogeogre]

After one year without commit or merge into master it's becoming obvious that the project has been shutted down...

[sparkyspider]

@pdavidc or anyone else? It's 8 months later. Pinging this again to see if there is any news.

[wcmatthysen]

@mckelvym-usgs, @vincent-bruel, @jakebeal, @AlexFalappa, @venabled, @AndrewTasso, @grammesm, @GeoffreyGamaya, @jasonCodesAway, @ajmcastro, @henriquebferreira, @sparkyspider, We are looking to address this issue in the community-edition fork of WorldWind. You can look at this issue for reference: https://github.com/WorldWindEarth/WorldWindJava/issues/36. Please feel free to come and help us with this.

[DJViking]

Is there any longer a need for the community fork WorldWindEarth? As NASA has recently recommitted to WorldWind.

Having NASA WorldWind in a maven repository would make it much easier to develop applications.

Currently I have referenced a 3party libs directory with all the necessary JARs within my Gradle dependency configuration. implementation fileTree(dir: '3party', include: '*.jar')

[mnk]

@AndrewTasso. We're committed to publishing all of our Java work on Maven Central and JCenter. My original estimate of a few weeks was overly optimistic. We'll update everyone watching this issue when we take on this work, hopefully soon.

Any news on this? Version v2.2.0 is now released, and it would be great to have that on Maven central.

[stephanheinemann]

Hi all, I have just released my NASA WorldWind 2.2.0 Maven project on oss.sonatype.org. It should be available on Maven Central pretty soon. Since I had to use my own repository target com.uvic-cfar.swim, you can find the artifacts under

com.uvic-cfar.swim.nasa.worldwind com.uvic-cfar.swim.nasa.worldwind.corex com.uvic-cfar.swim.nasa.worldwind.gdal com.uvic-cfar.swim.nasa.worldwind.milstd2525 com.uvic-cfar.swim.nasa.worldwind.vpf

Simply establish a dependency to com.uvic-cfar.swim.nasa.worldwind.corex version 2.2.0 and your project should find all required classes under gov.nasa.worldwind. and gov.nasa.worldwindx.

The project is aggregated in the parent pom of com.uvic-cfar.swim.nasa.worldwind. The corex artifact contains the WorldWind Java 2.2.0 core and extensions. The gdal artifact contains only the modified gdal library loader classes. Both, the milstd2525 and vpf artifacts contain the respective symbology resources. All artifacts are packaged to be OSGi compliant and can consequently also be used in Equinox or other OSGi frameworks.

Due to mutual dependencies between gov.nasa.worldwind. and gov.nasa.worldwindx., core and extensions had to be packaged in the same artifact corex. The corex artifact already establishes dependencies to the other artifacts.

None of the bundles contains any jar or zip resources and external dependencies have been established as can be seen from the respective pom files. It should be noted that I established dependencies to newer versions if available. In particular the old gdal version 1.7.4 was replaced with version 3.2.0. Since I did not have the modified gdal library loader sources, this was simply trial and work. Until now I did not see any issues with the established dependencies.

For your project you may want to keep your own /src/main/resources/config/worldwind.xml with an entry to find milstd2525 symbols in the classpath:

<Property name="gov.nasa.worldwind.avkey.MilStd2525IconRetrieverPath" value="classpath:"/>

Please let me know if you experience any problems. Thanks!