Development status of BIRT reporting Framework?












0














Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?










share|improve this question



























    0














    Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?










    share|improve this question

























      0












      0








      0







      Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?










      share|improve this question













      Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?







      eclipse birt status






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 18 '18 at 15:22









      achnichtsowichtig

      52




      52
























          2 Answers
          2






          active

          oldest

          votes


















          0














          We decided to use BIRT instead of Jasper 8 years ago.
          We are still using 4.2.1 for development and 4.3.0 for production runtime.



          I reported several bugs since then and only very few of them got fixed.



          Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.



          I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.



          I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.



          My conclusion with 8 years experience of using BIRT for production:



          PROS:




          • BIRT is very powerful and flexible, you can achieve some very cool results.

          • The quality of the resulting PDFs.

          • There are only very few things I miss and cannot work around.

          • The runtime engine is very stable and fast enough, very few problems.

          • The community is helpful.


          CONS:



          From an open-source perspective, it is one of the weakest projects I know of.




          • New versions tend to introduce more bugs than they fix.

          • Bugs, ideas and patches from the community seem to be ignored most of the time.

          • Lack of internal code quality and documentation.






          share|improve this answer





























            0














            Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:



            The Birt project is still alive, but not as active as before:





            • there has been only one release per year since 2016 and


            • in the last three months there have been more than 20 commits from 11 contributors.


            Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.






            share|improve this answer





















            • I am still using BIRT 4.2.1 for development and 4.3.0 for production.
              – hvb
              Nov 23 '18 at 9:06











            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53362448%2fdevelopment-status-of-birt-reporting-framework%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            We decided to use BIRT instead of Jasper 8 years ago.
            We are still using 4.2.1 for development and 4.3.0 for production runtime.



            I reported several bugs since then and only very few of them got fixed.



            Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.



            I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.



            I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.



            My conclusion with 8 years experience of using BIRT for production:



            PROS:




            • BIRT is very powerful and flexible, you can achieve some very cool results.

            • The quality of the resulting PDFs.

            • There are only very few things I miss and cannot work around.

            • The runtime engine is very stable and fast enough, very few problems.

            • The community is helpful.


            CONS:



            From an open-source perspective, it is one of the weakest projects I know of.




            • New versions tend to introduce more bugs than they fix.

            • Bugs, ideas and patches from the community seem to be ignored most of the time.

            • Lack of internal code quality and documentation.






            share|improve this answer


























              0














              We decided to use BIRT instead of Jasper 8 years ago.
              We are still using 4.2.1 for development and 4.3.0 for production runtime.



              I reported several bugs since then and only very few of them got fixed.



              Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.



              I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.



              I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.



              My conclusion with 8 years experience of using BIRT for production:



              PROS:




              • BIRT is very powerful and flexible, you can achieve some very cool results.

              • The quality of the resulting PDFs.

              • There are only very few things I miss and cannot work around.

              • The runtime engine is very stable and fast enough, very few problems.

              • The community is helpful.


              CONS:



              From an open-source perspective, it is one of the weakest projects I know of.




              • New versions tend to introduce more bugs than they fix.

              • Bugs, ideas and patches from the community seem to be ignored most of the time.

              • Lack of internal code quality and documentation.






              share|improve this answer
























                0












                0








                0






                We decided to use BIRT instead of Jasper 8 years ago.
                We are still using 4.2.1 for development and 4.3.0 for production runtime.



                I reported several bugs since then and only very few of them got fixed.



                Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.



                I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.



                I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.



                My conclusion with 8 years experience of using BIRT for production:



                PROS:




                • BIRT is very powerful and flexible, you can achieve some very cool results.

                • The quality of the resulting PDFs.

                • There are only very few things I miss and cannot work around.

                • The runtime engine is very stable and fast enough, very few problems.

                • The community is helpful.


                CONS:



                From an open-source perspective, it is one of the weakest projects I know of.




                • New versions tend to introduce more bugs than they fix.

                • Bugs, ideas and patches from the community seem to be ignored most of the time.

                • Lack of internal code quality and documentation.






                share|improve this answer












                We decided to use BIRT instead of Jasper 8 years ago.
                We are still using 4.2.1 for development and 4.3.0 for production runtime.



                I reported several bugs since then and only very few of them got fixed.



                Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.



                I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.



                I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.



                My conclusion with 8 years experience of using BIRT for production:



                PROS:




                • BIRT is very powerful and flexible, you can achieve some very cool results.

                • The quality of the resulting PDFs.

                • There are only very few things I miss and cannot work around.

                • The runtime engine is very stable and fast enough, very few problems.

                • The community is helpful.


                CONS:



                From an open-source perspective, it is one of the weakest projects I know of.




                • New versions tend to introduce more bugs than they fix.

                • Bugs, ideas and patches from the community seem to be ignored most of the time.

                • Lack of internal code quality and documentation.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 '18 at 9:34









                hvb

                1,6511610




                1,6511610

























                    0














                    Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:



                    The Birt project is still alive, but not as active as before:





                    • there has been only one release per year since 2016 and


                    • in the last three months there have been more than 20 commits from 11 contributors.


                    Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.






                    share|improve this answer





















                    • I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                      – hvb
                      Nov 23 '18 at 9:06
















                    0














                    Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:



                    The Birt project is still alive, but not as active as before:





                    • there has been only one release per year since 2016 and


                    • in the last three months there have been more than 20 commits from 11 contributors.


                    Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.






                    share|improve this answer





















                    • I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                      – hvb
                      Nov 23 '18 at 9:06














                    0












                    0








                    0






                    Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:



                    The Birt project is still alive, but not as active as before:





                    • there has been only one release per year since 2016 and


                    • in the last three months there have been more than 20 commits from 11 contributors.


                    Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.






                    share|improve this answer












                    Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:



                    The Birt project is still alive, but not as active as before:





                    • there has been only one release per year since 2016 and


                    • in the last three months there have been more than 20 commits from 11 contributors.


                    Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 18 '18 at 16:08









                    howlger

                    10.4k51737




                    10.4k51737












                    • I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                      – hvb
                      Nov 23 '18 at 9:06


















                    • I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                      – hvb
                      Nov 23 '18 at 9:06
















                    I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                    – hvb
                    Nov 23 '18 at 9:06




                    I am still using BIRT 4.2.1 for development and 4.3.0 for production.
                    – hvb
                    Nov 23 '18 at 9:06


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53362448%2fdevelopment-status-of-birt-reporting-framework%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Trompette piccolo

                    Slow SSRS Report in dynamic grouping and multiple parameters

                    Simon Yates (cyclisme)