Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.3.0.Beta2
-
Component/s: None
-
Labels:None
-
Last commented by a user?:true
Issue Links
- required for
-
HHH-8148
Create a 'regenerateSources' task that performs all generation tasks after invalidating the up-to-date checks for those tasks
-
- Closed
-
Activity
Correct.
Steve Ebersole
added a comment - Correct. +1 good idea, this way one can re-generate all the generated source with a single target. Might make the build also easier to understand.
Hardy Ferentschik
added a comment - +1 good idea, this way one can re-generate all the generated source with a single target. Might make the build also easier to understand. Well, regenerateSources is another idea altogether. generateSources would not "clean" first and given Gradle's up-to-date checking, would therefore probably not happen.
Steve Ebersole
added a comment - Well, regenerateSources is another idea altogether. generateSources would not "clean" first and given Gradle's up-to-date checking, would therefore probably not happen. Little nervous about generateSources and generateTestJpaMetamodelClasses. Most generateSources operate on production sources, whereas generateTestJpaMetamodelClasses operates on test classes.
Steve Ebersole
added a comment - Little nervous about generateSources and generateTestJpaMetamodelClasses . Most generateSources operate on production sources, whereas generateTestJpaMetamodelClasses operates on test classes. Little nervous about generateSources and generateTestJpaMetamodelClasses. Most generateSources operate on production sources, whereas generateTestJpaMetamodelClasses operates on test classes.
I think it is ok to combine them under generateSources. I guess the alternative is to have a generateTestSources as well.
Btw, I did not expect the generateSources would clean first by default.
Hardy Ferentschik
added a comment -
Little nervous about generateSources and generateTestJpaMetamodelClasses. Most generateSources operate on production sources, whereas generateTestJpaMetamodelClasses operates on test classes.
I think it is ok to combine them under generateSources . I guess the alternative is to have a generateTestSources as well.
Btw, I did not expect the generateSources would clean first by default. 
What does that really mean? I guess you are taking about jaxb, logging and antlr. Is generateSources just a task which depends on the tasks for these different source generations?