Deploy on maven central?

[victornoel]

Hi,

There seems to be only old versions available on maven central, is this intended?

See: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.jidesoft%22%20AND%20a%3A%22jide-oss%22

[jidesoft]

Not intended but we have trouble uploading the releases. Tried a few times but couldn't do it. Seems to be something wrong with the gradle script. Not sure if there is a way to manually upload the files.

[akazancev]

This is kind of important issue. Do you have any ETA for this?
Thanks,
-Alex

[jidesoft]

We tried but couldn't get it working. So no ETA for now. Please import the jars manually.

[akazancev]

Thank you!
Very sad :(( We cannot do manual import due to our company policies. Only open source projects published in maven central can be used.

[victornoel]

@jidesoft could you share with us what you tried to do and what failed? maybe someone can help :)

[lambdas]

Hi, guys! Any success with this? It's really inconvenient to be unable to grab the library from maven.

[swimmesberger]

Would appreciate a maven central deployment of the current version.

[bourgesl]

I fixed the maven build in PR:
#32

[illumi]

@jidesoft can you merge #32 and perform a deploy?

[jidesoft]

Just did

[illumi]

@jidesoft 3.7.x still not available on central. Any chance..?

[bourgesl]

As @jidesoft is not making any progress on publishing binary artifacts on maven central, I will release my own build (jar files) on github.
It is FOSS, do what you want with good source code...

[bourgesl]

Here is my unofficial build:
https://github.com/bourgesl/jide-oss/releases/tag/3.7.4-b20181214

[lambdas]

@bourgesl Maybe you can publish your fork to maven and update it with every release.. That would be awesome.

[bourgesl]

Even if jide-oss is free code, I can not publish on maven central instead.
Sorry, I just published 1 binary release to let you enjoy it, I will not release jide-oss releases myself, it is their project & releaseq.

[jidesoft]

Even if jide-oss is free code, I can not publish on maven central instead.
Sorry, I just published 1 binary release to let you enjoy it, I will not release jide-oss releases myself, it is their project & releaseq.
Hi Bourgesl,

Do you think you can publish it on the maven repository if I made you an admin for this project?

-David

[illumi]

Hi David,

GitHub and maven central are two different systems. Making someone an admin on GitHub doesn't mean they can deploy in the name of jidesoft.

Are you saying Jidesoft cannot or has lost the ability or knowledge to deploy artifacts?

[jidesoft]

We couldn't get it working.

[bourgesl]

Sorry, I do not understand.

@jidesoft you are not able to publish on maven central (nexus account) ?
I do have an account (for the marlin renderer) but never pushed (properly) artifacts on nexus, lack of time.

If you want me to help you, I could but please contact me directly via twitter DM (see https://github.com/bourgesl)

[Joerg-Schoemer]

Hi all,

you use gradle to publish to a nexus on a maven project? This sounds strange to me!

Maven supplies a release-plugin to publish to maven repositories.
I've build a pull request to migrate completely to the maven structure. Now it should be easy to publish with maven. For the first time the maven project supports only java8.

Kind regards
Jörg

[mokun]

Hi David,

Could you configure this fine library as a maven artifact using jitpack in GitHub?

That way, we can use the latest version with bugs fixed.

Thanks!

[mokun]

Anyone is working on deploying the latest jide-oss to a repo ?

[akazancev]

@mokun I doubt:((
I think most people are working on getting rid of jide-oss dependency completely, especially due to Java 11 incompatibility of published versions.

[apjanke]

Hi folks,

I think I have Maven Central publishing working under the net.janklab.opp group. (I'm doing this as part of the Janklab-OPP project, which aims to make Maven Central builds of libraries used by Matlab but which don't do their own Maven Central publishing.) I've published a SNAPSHOT of jide-oss 3.7.4. Anyone want to test it out? It'd be nice to have confirmation this is working for other users before I publish the non-snapshot release.

To pull it in, you need to enable the snapshot repo in your project's POM:

  <repositories>
    <repository>
      <id>oss.sonatype.org-snapshot</id>
      <url>http://oss.sonatype.org/content/repositories/snapshots</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </repository>
  </repositories>

Then reference the net.janklab.opp:jide-oss artifact:

  <dependencies>
    <dependency>
      <groupId>net.janklab.opp</groupId>
      <artifactId>jide-oss</artifactId>
      <version>3.7.4-SNAPSHOT</version>
    </dependency>
  </dependencies>

You can see the tweaks I made to the jide-oss pom.xml here:

New pom.xml state:

• https://github.com/apjanke/janklab-opp/blob/bd7de70c39e3d980ea4c7a4c37eab039c796371d/jide-oss/jide-oss-3.7.4/project/jide-oss-3.7.4/pom.xml

How I got there:

• janklab/janklab-opp@2446b03
• janklab/janklab-opp@59341f9
• janklab/janklab-opp@74acde8
• janklab/janklab-opp@bd7de70

[mokun]

@apjanke ,

So, for 3.7.4, use <version>3.7.4</version> (without the word -SNAPSHOT), right ? since I saw janklab/janklab-opp@c5e1c3f

But for 3.7.6, use <version>3.7.6-SNAPSHOT</version> (with the word -SNAPSHOT), right ?

I saw https://github.com/apjanke/janklab-opp/blob/master/jide-oss/jide-oss-3.7.6/project/jide-oss-3.7.6/pom.xml

Q: does it work on beyond Java 9, such as Java 14 ?

[mokun]

@apjanke ,

How come your 3.7.4 has a lot of files missing ?

For instance, when I try to look for LookAndFeelFactory.java as in Eclipse IDE, it won't let me.

It turns out that this java class and a lot of other class files are not in this jide-oss-3.7.4.jar jarfile that you distributed in maven.

https://github.com/jidesoft/jide-oss/blob/master/src/com/jidesoft/plaf/LookAndFeelFactory.java

When I use 3.6.18 and downloaded those files locally to my machines, note their sizes are big.

When I switch to your distribution and use 3.7.4 and downloaded them locally, note their sizes are much smaller.

So, did jide stripped off those size intentionally in newer versions ?

[apjanke]

So, did jide stripped off those size intentionally in newer versions ?

Well, uh-oh: I have no idea! I'll look in to this.

[tferr]

@apjanke, sincere thank you for working on this! I can confirm the jar contains no compiled classes, just resource files, such as icons and such. Did you manage to find out what the issue is?

[apjanke]

No, sorry! I've gotten really busy at the day job.

I'll try to get to this soon since I know people are waiting on it.

Cheers,
Andrew

[mokun]

@apjanke

Well obviously it doesn't compile correctly as you know.

But since now you're the one who knows how to post it in maven repo, we're hoping you can figure it out.

Best regards !

[sfuerte]

as it's been dragging already for almost 3 years, is it possible to be released via Github packages at least?

https://docs.github.com/en/free-pro-team@latest/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages#installing-a-package

Thank you!

[mokun]

@sfuerte

It'll be awesome if someone who are familiar with the process of releasing it as a github packages can spearhead this.

[sfuerte]

@mokun
I believe the documentation is rather explanatory and clear. But if need any hand, sure thing, send me a PM.

On the another hand, it looks like there is a problem with 3.7.x release builds in general, logged it in a separate issue - #48

[jidesoft]

The compilation error is one of the reason we gave up deploying on maven. From: sfuerte <[email protected]> Sent: Monday, November 30, 2020 7:43 PM To: jidesoft/jide-oss <[email protected]> Cc: jidesoft <[email protected]>; Mention <[email protected]> Subject: Re: [jidesoft/jide-oss] Deploy on maven central? (#27) @mokun <https://github.com/mokun> I believe the documentation is rather explanatory and clear. But if need any hand, sure thing, send me a PM. On the another hand, it looks like there is a problem with 3.7.x release builds in general, logged it in a separate issue - #48 <#48> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALKLGJOKXOP5BE4KFWABU3SSRQ3LANCNFSM4EPTDXPQ> . <https://github.com/notifications/beacon/AALKLGMODQXKYKRCFAVE5CTSSRQ3LA5CNFSM4EPTDXP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFPQXZ4A.gif>

[sfuerte]

The compilation error is one of the reason we gave up deploying on maven.

@jidesoft , does it mean that jide-oss is simply an abandoned project?

Your Maven POM is a bit outdated and hence doesn't compile properly. And can be fixed quite easily.

But the source of the problem isn't that (as Ant build produces errors as well) but rather project's dependency on the Windows LAF which is not included anymore in non-Windows JDK releases, see more at https://bugs.openjdk.java.net/browse/JDK-6461834

#48 is pretty much a blocker for Maven builds and releases.

[jidesoft]

@sfuerte Swing is dying so we are not very actively working on this project except for bug fixes.

[sfuerte]

@jidesoft , will #48 be considered as a bug that requires a fix?

[DevCharly]

I've built and published latest jide-oss version to Maven Central:
https://search.maven.org/artifact/com.formdev/jide-oss

<dependency>
  <groupId>com.formdev</groupId>
  <artifactId>jide-oss</artifactId>
  <version>3.7.11.1</version>
</dependency>

This was built on GitHub Actions using Gradle.
Project is here: https://github.com/JFormDesigner/jide-oss