Convert to SpringBoot?

[cstroe]

It seems that VRaptor is no longer maintained and this project integrates many disparate Java libraries that are hard to get working together.

Would it be valuable to convert this project to use the SpringBoot framework?

[steimntz]

Sad, but true. I agree because I think more people can get involved on a more maintained stack. VRaptor is great it has awesome features as injecting in a constructor but Spring is always on the pulse of the industry.

[icemagno]

Learn with it! This is the price you'll pay for reinvent the weel. Don't ever create a tool for YOU when there is a good tool in the market that do the same.

[vicenthy]

great idea

[vicenthy]

let's start?

[cstroe]

How do we want to start? Do we make incremental PRs to master?

[vicenthy]

no member is present, better create another repository

[cstroe]

I created an organization and forked this repo there: https://github.com/mamutehq/mamute

I will add you @vicenthy and we can start with that. Anyone else can join if they're interested.

[vicenthy]

cool, the issues will continue here and the commits will go there and what's the next step?

let's continue with the same architecture and just migrate to spring MVC?

[icemagno]

I'm in. But for now I'm in a huge project. @vicenthy I think we must keep the interface and the business rules, but change the code to Spring Boot + WEB + Security + JPA + PostgreSQL. In short, we must keep WHAT it does but change HOW it does.

[vicenthy]

Great! I understand

[cstroe]

Work has begun here: https://github.com/mamutehq/mamute/milestone/1

[icemagno]

Is that repository up to date? I see 7 releases and very old files..

[cstroe]

That repository is a fork of this one, so it kept the releases. It is not a rewrite from scratch, but an in-place conversion to Spring Boot (for example, see the current PR that's converting the database migrations to Liquibase: mamutehq#6)

[marikth]

Do you have any knowledge in java, if you are willing to help, We can start a new forum and do a migration, I can do all the integrations including elastic search and spring and I have a friend that are willing to code all the UI using rest. Any one is up for the challenge?

…

On Thu, Jul 12, 2018 at 12:43 PM Cosmin Stroe ***@***.***> wrote: That repository is a fork of this one, so it kept the releases. It is not a rewrite from scratch, but an in-place migration (for example, see the current PR that's converting the database migrations to Liquibase: mamutehq#6 <mamutehq#6> [image: screenshot from 2018-07-12 04-37-13] <https://user-images.githubusercontent.com/1182093/42625738-217682c4-858e-11e8-9e33-e4287d3ac15c.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#303 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADAv-9m9yDMKhm5-NUV0GVO3xdvPWfxWks5uFxpLgaJpZM4TPS3C> .

[cstroe]

@marikth Are you proposing a complete rewrite of Mamute? In that case, please see #299, which created https://github.com/JamesSullivan/manmosu

If you have a specific feature in mind (you mention ElasticSearch and adopting a UI framework/exposing a RESTful API), feel free to document your idea as an issue on https://github.com/mamutehq/mamute and open PRs against that repo.

[icemagno]

Yeah. I'm a Java developer. But for now I'm in a very big military project and have no time left to another mission.