-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
review feat: API for incremental build #2051
Conversation
@Egor18 WDYT about this API? It's not polished yet: I'm thinking about removing the new fields from Launcher that seem unecessary and to put them as local variable, do you agree? |
This API looks good, thanks. Yes, unecessary fields can be removed. |
ok I'll try first to improve it without changing the way it works. We'll be able to improve the way we detect changes later: for now modification time can already be used in several cases. |
API changes: 4 (Detected by Revapi) Old API: fr.inria.gforge.spoon:spoon-core:jar:6.3.0-20180611.225429-136 / New API: fr.inria.gforge.spoon:spoon-core:jar:6.3.0-SNAPSHOT
|
/** | ||
* This class store information for incremental build. | ||
*/ | ||
public class IncrementalBuildInformation { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
put @Internal
or in package called something.internal (eg spoon.launcher.internal)
Incremental launcher is a different responsibility. What about having an IncrementalLauncher for this? (which would delegate to Launcher) |
Why was #1905 still marked as WIP? |
I suppose because I asked for changes regarding the API... |
:-) did you add new tests here? |
No |
Thanks a lot @surli to have revived this topic! |
That will be a great release! |
This PR aims at finishing the incremental build mechanism proposed by @Egor18 in #1905 with an API well integrated with Spoon Environment and standard launcher.