byte-code-enhancement

How to copy resource files in classes folder with gradle?

烂漫一生 提交于 2019-12-22 06:56:55
问题 Enviroment I am using a third party lib which requires bytecode instrumentation. The tool which does the bytecode instrumentation requires some description files and those files have to be in the same folder structure like the compiled .class files. Those files are only necessary at compiletime. Problem I thought gradle would place all files (resource and class) temporarily within the same folder and then create a jar from that folder. But it seems that gradle have two different places for

Hibernate 4 bytecode enhancement not working for dirty checking optimization

爱⌒轻易说出口 提交于 2019-12-09 04:12:33
问题 I am using the Hibernate 4.3.6 and I made use of the latest Maven bytecode enhancement to instrument all entities for self dirtiness awareness. I added the maven plugin: <build> <plugins> <plugin> <groupId>org.hibernate.orm.tooling</groupId> <artifactId>hibernate-enhance-maven-plugin</artifactId> <executions> <execution> <phase>process-test-resources</phase> <goals> <goal>enhance</goal> </goals> </execution> </executions> </plugin> </plugins> </build> and I see my entities are being enhanced:

How to copy resource files in classes folder with gradle?

守給你的承諾、 提交于 2019-12-05 11:46:23
Enviroment I am using a third party lib which requires bytecode instrumentation. The tool which does the bytecode instrumentation requires some description files and those files have to be in the same folder structure like the compiled .class files. Those files are only necessary at compiletime. Problem I thought gradle would place all files (resource and class) temporarily within the same folder and then create a jar from that folder. But it seems that gradle have two different places for resources and class files before assembling a jar. Like mentioned before the third party tool for code

Hibernate 4 bytecode enhancement not working for dirty checking optimization

谁说我不能喝 提交于 2019-12-02 20:12:00
I am using the Hibernate 4.3.6 and I made use of the latest Maven bytecode enhancement to instrument all entities for self dirtiness awareness. I added the maven plugin: <build> <plugins> <plugin> <groupId>org.hibernate.orm.tooling</groupId> <artifactId>hibernate-enhance-maven-plugin</artifactId> <executions> <execution> <phase>process-test-resources</phase> <goals> <goal>enhance</goal> </goals> </execution> </executions> </plugin> </plugins> </build> and I see my entities are being enhanced: @Entity public class EnhancedOrderLine implements ManagedEntity, PersistentAttributeInterceptable,