Publish Maven Build To Central

[pipebaum]

Currently, there is no automated feature to publish the BIRT-Runtime to Maven. Wouldn't it be nice to fix this.

[pipebaum]

@wimjongman Do you or anyone you know have experiencing setting this up? What we would like is to be able to automatically deploy/publish the Runtime to Maven Central. To date, we have been doing this by hand, it would be great if we could do this in the easiest way possible. @SteveSchafer-Innovent

[wimjongman]

I have tried once and failed...

However, it seems doable with some focus.

https://docs.github.com/en/actions/guides/publishing-java-packages-with-maven
https://dzone.com/articles/publish-your-artifacts-to-maven-central

[pipebaum]

Thanks Wim, We will take a look in the upcoming days using those links. Scott

…

On Thu, Apr 29, 2021 at 1:46 PM Wim Jongman ***@***.***> wrote: I have tried once and failed... However, it seems doable with some focus. https://docs.github.com/en/actions/guides/publishing-java-packages-with-maven https://dzone.com/articles/publish-your-artifacts-to-maven-central — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#625 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKF2BOJ6UWXBORNJMMBOLLTLGSO5ANCNFSM4ZYBQNVA> .

-- Scott Rosenbaum Innovent Solutions, Inc. 612 220 6006 cell

[martins-1992]

Hello there,
we are currently working on integrating BIRT into a private service for report generation.
We noticed that there is currently no public build release of the BIRT runtime.

We were able to build the BIRT runtime locally and will probably integrate the runtime by using the build jars
as dependencies.

Can we help you, in order to get a public build release on Maven Central?

[wimjongman]

Can we help you, in order to get a public build release on Maven Central?

Yes, that would be great. You can create PR's referencing this issue.

[martins-1992]

What are the release problems?

[martins-1992]

We could setup a release workflow, where a release is uploaded to Github first
and find issues with the build process that way.

We have done it for our project as well: https://github.com/minova-afis/aero.minova.core.application.system/blob/master/.github/workflows/release.yml

The only thing needed to my knowledge are a username and an access token for Github,
as a secret in the project.

[wimjongman]

@splitcells, @pipebaum can we re-start working on this?

[martins-1992]

@wimjongman It is not known, what is needed or if a Maven Central release is desired.

[JacquesLeRoux]

Hi,

I'm not sure what your problem is, but for sure a Maven Central release is desired by us, see #863

[wimjongman]

This is what is currently inside the maven repo [1]. Our official build is in Jenkins [2].

[1] https://mvnrepository.com/artifact/org.eclipse.birt
[2] https://ci.eclipse.org/birt/

[martins-1992]

Which one is the release workflow or what are the commands used for release?
Is it this one? https://ci.eclipse.org/birt/job/populate-build-lists/

[wimjongman]

The birt-master job creates all the artifacts. The artifacts are then uploaded here [1]

We used to have a process to make milestones and release candidates but we are going to skip that for now.

Finally, there will be a job that will move the artifacts from the downloads/snapshots and update-site/snapshots to a final release location.

Then there could be another job that uploads these artifacts to maven central. I guess the artifacts to upload are the bundles in update-site/snapshots/plugins

[1] https://download.eclipse.org/birt/

[martins-1992]

You mentioned earlier, that you tried something?
What are the commands executed for the release?
What were the errors?

That way, we have a common process to start from.