Re: [hibernate-dev] Jira - edit comments
I think this happens when a Jira is closed. On Wed, 17 Oct 2018 at 17:27, Steve Ebersole wrote: > The elipse is there but the only option is Permalink > > > On Wed, Oct 17, 2018, 9:53 AM Chris Cranford wrote: > > > Steve - > > > > I have the option for my user. Is the ellipsis button not showing up > > for you on the comment? > > > > On 10/17/18 9:12 AM, Steve Ebersole wrote: > > > Did someone remove the ability to edit one's comments? I added a > > comment I > > > would like to adjust syntax (code fragment), but Jira will not let me > > ___ > > hibernate-dev mailing list > > hibernate-dev@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Jira - edit comments
The elipse is there but the only option is Permalink On Wed, Oct 17, 2018, 9:53 AM Chris Cranford wrote: > Steve - > > I have the option for my user. Is the ellipsis button not showing up > for you on the comment? > > On 10/17/18 9:12 AM, Steve Ebersole wrote: > > Did someone remove the ability to edit one's comments? I added a > comment I > > would like to adjust syntax (code fragment), but Jira will not let me > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Deprecating Environment#verifyProperties
Currently this method is used but not doing much at all, as maps OBSOLETE_PROPERTIES and RENAMED_PROPERTIES are constant and empty. I'm wondering if this is because it's just a coincidence at this point in time we have nothing registered in those maps, or if this strategy is just no longer the preferred choice to handle "out of date configuration properties". I'm guessing that going forward we all rather implement such logic using ad-hoc logic and more specific error messages? In that case I'd want to deprecate this code and remove those maps. Objections? Thanks, Sanne ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Introducing a "none" BytecodeProvider
After some experimentation I figured out that the BytecodeProvider is not really necessary, if you are happy to use the tools we have to enhance the entities upfront. In some environments such as on GraalVM I need to pre-enhance the entities (need as in "not optional"), but some further things would be really much simpler if I then could exclude Byte Buddy from runtime dependencies. As the code stands today, the Byte Buddy engine is loaded very early during bootstrap (even if the entities are already enhanced, as we didn't test for that yet at this point) and can't be disabled. I have a successful experiment which introduces a "none" configuration value for the "hibernate.bytecode.provider" property which allows me to fully disable the need to have ByteBuddy on classpath at runtime. I would not generally recommend this as there is no safety net: if you set this property AND did not enhance your entities, I expect trouble. Also there's a strong limitation: I could not implement the `BasicProxyFactory`, which is probably making this unfit for general purpose; I could use some help to nail down why exactly we need this and see if we can actually implement an alternative - possibly having the build time entity enhancement tools generate the necessary bytecode upfront? Still, I'd propose to merge this feature as an advanced feature that some power users will need when making progress on support for new platforms. Because of this experimental aspect, I'm not bothering to mention it on the user guide :) Ok? Thanks, Sanne ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Jira - edit comments
Steve - I have the option for my user. Is the ellipsis button not showing up for you on the comment? On 10/17/18 9:12 AM, Steve Ebersole wrote: > Did someone remove the ability to edit one's comments? I added a comment I > would like to adjust syntax (code fragment), but Jira will not let me ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Jira - edit comments
Did someone remove the ability to edit one's comments? I added a comment I would like to adjust syntax (code fragment), but Jira will not let me ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
