search

thombergs / docx-stamper

Easy-to-use template engine for creating docx documents in Java.
MIT License
213 stars 90 forks source link

Fork ? alternative ? #101

Closed bflorat closed 2 years ago

bflorat commented 2 years ago

This project seems abandoned by it original author still 2019.

I still thank him for his great piece of code and as an open source project admin myself, I understand very well that this he ows nothing to us.

However, it is paramount for some of my professional projects and I choosed it when very active back in 2018. I suppose I'm not the only one in this case.

Does somebody know an alternative ? think about a serious fork ?

crgardner commented 2 years ago

@bflorat - did you find alternatives after you posted?

bflorat commented 2 years ago

@crgardner No but I didn't actively searched.

Note that I had to fork this project to fix #32. I forked this project to fix this. It is available on Maven central at

  <dependency>
            <groupId>net.florat</groupId>
            <artifactId>docx-stamper</artifactId>
            <version>1.4.0~1</version>
        </dependency>

Let me know if you find an alternative.

dallanmc commented 2 years ago

I got rid of all that index stuff in the codebase. You can just delete the object by getting the parent and then calling remove on it and pass in the object you want to remove. It greatly simplified the codebase.

bflorat commented 2 years ago

Thanks. I don't remember well but it must be more or less what I did here

I also restored the maven packaging, I don't use gradle.

crgardner commented 2 years ago

My understanding is that newer java 11 docx4j rely on the jee jarkata packages but stamper expects javax objects. I was wanting to see if stamper could be updated to use the newer docx4j versions and hence be able to deal either Jakarta packages.

On Wed, Mar 23, 2022, 5:11 PM dallanmc @.***> wrote:

I got rid of all that index stuff in the codebase. You can just delete the object by getting the parent and then calling remove on it and pass in the object you want to remove. It greatly simplified the codebase.

— Reply to this email directly, view it on GitHub https://github.com/thombergs/docx-stamper/issues/101#issuecomment-1076824472, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAP3QSGK223QJVZA3G7BPJ3VBOCHZANCNFSM5NAA57NQ . You are receiving this because you were mentioned.Message ID: @.***>

caring-coder commented 2 years ago

I'm interested in an active fork as well, we are getting more and more invested in this piece of code at my workplace. If any of you want to start and maintain an open source fork, we could participate.

If not, i believe we will do it ourselves anyway.

bflorat commented 2 years ago

I'd like to but I for one have absolutely not the time to do it seriously.

Let us know if you start a fork, I may send MR.

caring-coder commented 2 years ago

We are starting to actively fork the repo You can find it here : https://github.com/verronpro/docx-stamper. We started find improving the repeatDocPart, and making it recursive, and learning the way to publish to maven central. Thanks for the inspiration! @AL1047088

dallanmc commented 2 years ago

This is great - I have a good few improvements that I have implemented (they are in the issues section) - but maybe you've implemented some of them already. A couple of useful ones would be the displayWordIf processor and the displaySectionIf processor. I also implemented the concept of preprocessors. I was facing an issue where spelling errors in the document would mess up the processing, so one preprocessor I made would remove all the spelling errors from the xml doc before then processing properly. I also implemented a replaceWordsWith for commenting around multiple words which works well.

I am sure there is other stuff, but it's probably in the issues section too.

bflorat commented 2 years ago

This is great ! I'll re-send you this PR https://github.com/thombergs/docx-stamper/pull/46 ASAP to fix the most important issue I have with this project.

caring-coder commented 2 years ago

This is great - I have a good few improvements that I have implemented (they are in the issues section) - but maybe you've implemented some of them already. A couple of useful ones would be the displayWordIf processor and the displaySectionIf processor. I also implemented the concept of preprocessors. I was facing an issue where spelling errors in the document would mess up the processing, so one preprocessor I made would remove all the spelling errors from the xml doc before then processing properly. I also implemented a replaceWordsWith for commenting around multiple words which works well.

I am sure there is other stuff, but it's probably in the issues section too.

Thanks @dallanmc, you can make the merge requests yourself on https://github.com/verronpro/docx-stamper with maybe a test case, and i'll include them. If not, then i might take them on myself during the coming month.

bflorat commented 2 years ago

Good work everybody ! Does the repeatDocPart() feature actually works now ? (even when elements are removed).

If it works now, I may try it again.

caring-coder commented 2 years ago

I did not try concurrently with the remove feature, but the repeatDocPart works and use only the given object as sub-context for the "doc part" covered by the comment.