New/beta releases ?

[joerg....@gmail.com]

Hey,

I've been excitedly waiting for https://github.com/jacoco/jacoco/pull/495 but it seems there haven't been any releases in a while, and I was wondering if there was a way to get beta releases or something of that sort, short of building my own jacoco (which since it is used as part of the build process is a bit annoying, since I'd have to locally install it on all dev machines + the CI servers to the local Maven repo).

Toodles

[Evgeny Mandrikov]

Hi,

In addition to primary job and personal lives, we are currently in a process of making sure that EclEmma will be released as part of upcoming Eclipse Oxygen, which is a top priority right now over finalization of work on next JaCoCo version. Also any publicly available release (alpha/beta/normal) of this feature will raise questions why this is not available in SonarQube/Jenkins/EclEmma/etc (actually already raises - see https://github.com/jacoco/jacoco/pull/513#issuecomment-293176354 and https://groups.google.com/d/msg/jacoco/GF-YJIPUuOg/ifkBWLXfAAAJ , but will become more frequent). So we prefer to really finalize version and contribute an update to SonarQube/Jenkins/EclEmma. Please be a bit more patient. Or use a snapshot - http://www.jacoco.org/jacoco/trunk/doc/repo.html Also if there is no centralized Maven repository/proxy in your organization, then I would advice to invest into this, which will allow to use private/custom/etc artifacts without headaches of distribution to CI servers and developer machines.

Thank you for your understanding.

Regards,

Evgeny

[joerg....@gmail.com]

Thank you very much! I appreciate your work and that you are doing it after work for free, and I didn't mean to come over as critical. I merely meant that since this is a project with a slow release cycle, I was looking for a way to play with the new features already.

Your solution to that is perfect for us, as we can just add the snapshot repo to our pom for the time being.

[cho...@elementum.com]

Any update on an expected release date for 0.7.10? How can we help you?

[Matt Nelson]

Bouncing this as another eager consumer waiting on 0.8.0. I've been monitoring the milestone release date, which recently changed to no due date. Is there another place that shows the projected release date and/or the other blockers that are preventing the release?

[1] https://github.com/jacoco/jacoco/milestone/23

[Marc Hoffmann]

Hi Matt,

there is no release date as we cannot promise capacity to work on the
remaining issues. Basically the two missing filters is what we consider
as a blocker (incomplete features are killing us with questions on the
mailing list and invalid bug reports).

Thanks for your understanding.

Regards,
-marc

[thef...@gmail.com]

Bouncing again since it has been a while. Do the remaining filters have to be shipped with 0.8? I imagine there are a lot of users who would benefit from the exIsting filters and would be open to only using what is currently implemented and welcome the idea of additional future releases as more filters are added. Since the byte code filtering is a new feature with 0.8, it would seem reasonable that this release doesn't have to include all filters. Every subsequent release could introduce more filters that would continue to report higher percentages of coverage.

I have been using the latest snapshots for several months now. We are switching from clover to jacoco and the improvements in build times are dramatic. Unfortunately without the byte code filters the lower coverage percentage reported by jacoco would be a blocker to migrating. We have discussed forking an internal release until 0.8 is released, since we feel that the code in its current state is sufficient for our immediate needs.

[Chas Honton]

We're also considering an internal release. 

On Tue, Nov 21, 2017 at 3:21 PM, <thef...@gmail.com> wrote:

Bouncing again since it has been a while. Do the remaining filters have to be shipped with 0.8? I imagine there are a lot of users who would benefit from the exIsting filters and would be open to only using what is currently implemented and welcome the idea of additional future releases as more filters are added. Since the byte code filtering is a new feature with 0.8, it would seem reasonable that this release doesn't have to include all filters. Every subsequent release could introduce more filters that would continue to report higher percentages of coverage.

I have been using the latest snapshots for several months now. We are switching from clover to jacoco and the improvements in build times are dramatic. Unfortunately without the byte code filters the lower coverage percentage reported by jacoco would be a blocker to migrating. We have discussed forking an internal release until 0.8 is released, since we feel that the code in its current state is sufficient for our immediate needs.

--
You received this message because you are subscribed to a topic in the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jacoco/gd8xD30TDNo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jacoco+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/82a18495-59f1-4faa-8d95-8f8b28ba3db8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Chas Honton

Architect - CI/CD

ch...@elementum.com

www.elementum.com

Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message