Re: modernizing the build process: github/actions, maven central, etc.

Hi all,

I agree that there are many questions here (Git, Github, github actions)
and would strongly argue in favor of all of them, in particular the move to
github.
i do suppose a read-only GitHub mirror accomplishes a lot of what you get
out of github anyways.

if the "git" direction is decided on, i can volunteer to help work on that
- but would not want to decide for the group about other hosting.
Björn: ultimately sounds like you have a handle on things but I'm available
to tinker/iterate on things - if it helps, lmk

best,
David

On Mon, Jun 12, 2023 at 5:45 AM Vampire <[email protected]> wrote:

> Hi again
>
> Forgot to say, whether we "move" to GitHub or just mirror the code is a
> completely different discussion.
> While many projects went away from SourceForge, this is not really
> mandatory.
> SourceForge is not dead to my knowledge and also provides much more
> possibilities and flexibility.
> For example, for the things already in Git repositories we have our own
> Git hooks running on the SourceForge repos that are not possible on GitHub
> and so on.
>
> Regards
> Björn
>
> Am Mo., 12. Juni 2023 um 11:41 Uhr schrieb Vampire <[email protected]>:
>
>> Hi David
>>
>> I know I horribly failed in doing the Git-migration in a timely manner,
>> but I'm going to soon pick up where I left off and finally finish the Git
>> migration of the source code,
>> I was just unfortunately interrupted again by some paid work. :-(
>>
>> There is no need for the `jedit-project` org on GitHub you just invited
>> me to though.
>> We already have `jedit-editor` on GitHub, `jedit` group on GitLab, and
>> the `jEdit` workspace on Bitbucket,
>> and I'm still hoping to get contact to the seemingly unused `jedit`
>> account on GitHub to also there get the name.
>>
>> Once I finished the Git-migration of the main repo and also the plugins,
>> I would at least put some mirroring up to have the code also on GitHub and
>> maybe the others.
>> And I'm also planning to then use GitHub actions for building, especially
>> as you can build on macOS for free which we need for building the macOS
>> distributable.
>> Actually I'm already "abusing" one of my other GitHub projects' GitHub
>> actions to do the macOS build on releases, so I know it works as intended.
>>
>> Best regards
>> Björn
>>
>>
>> Am Mo., 12. Juni 2023 um 11:07 Uhr schrieb David Ankin <
>> [email protected]>:
>>
>>> Hi folks,
>>>
>>> I would like to create an official home for this project on github,
>>> resume publishing versions of the library (or reusable pieces?) to maven
>>> central - i believe this would be beneficial to both users and developers
>>> as it would encourage people to view the project as living rather than dead
>>> and unmaintained. its sort of an inevitable association with source forge.
>>>
>>> if anyone is interested in making this a reality, let me know.
>>>
>>> best,
>>> David
>>> --
>>> -----------------------------------------------
>>> jEdit Users' List
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/jedit-users
>>>
>>

-- 
-----------------------------------------------
jEdit Users' List
[email protected]
https://lists.sourceforge.net/lists/listinfo/jedit-users