You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The simplest way to ensure that a javatools is used if it's already build, and ignoring its dependencies would be ignoring that as an @input to the XtcCompileTasks if we are explicitly told to no rebuild javatools when something has changed.
Verify that this is the case, and that it works to change javatools.jar without having the XTC modules of the XDK rebuilt as the next step.
(This also shows that it's a good idea to use more fine grained dependencies for javatools instead of the fatker, because incremental builds with the javatools dependency ENABLED (default) would likely resolve faster).
The text was updated successfully, but these errors were encountered:
I've read this through a few times, but I'm not sure what you're saying here.
Are you saying that currently we do not rebuild the javatools.jar if something it depends on changes? And if so, what dependency are we missing?
Or are you saying that currently we rebuild various .xtc files when javatools.jar changes, even if that is not necessary? And if so, could you give an example?
I’m saying that the best way to support Gene-mode, i.e. changing and rebuilding javatools jar, without rebuilding the XDK modules (as we technically should, because a dependency is a dependency), would be to remove the xtcJavaTools configuration from the @inputs to the compileXtc task, in that mode. Or even better, which should also work, changing the resolution logic for the xtcJavaTools configuration, so that it just goes to the latest javatools.jar on disk, hardcoded/hacked relative to the current repo root.
That would, I hope, be a very trivial fix and contained to one location in the code.
On 29 Mar 2024, at 17:34, Cameron Purdy ***@***.***> wrote:
I've read this through a few times, but I'm not sure what you're saying here.
Are you saying that currently we do not rebuild the javatools.jar if something it depends on changes? And if so, what dependency are we missing?
Or are you saying that currently we rebuild various .xtc files when javatools.jar changes, even if that is not necessary? And if so, could you give an example?
Or is it something else?
—
Reply to this email directly, view it on GitHub <#197 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIDMSITR6U57KEQOPAMTPLY2WJ27AVCNFSM6AAAAABFGQ3HASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXGQ3DENBTGQ>.
You are receiving this because you authored the thread.
The simplest way to ensure that a javatools is used if it's already build, and ignoring its dependencies would be ignoring that as an @input to the XtcCompileTasks if we are explicitly told to no rebuild javatools when something has changed.
Verify that this is the case, and that it works to change javatools.jar without having the XTC modules of the XDK rebuilt as the next step.
(This also shows that it's a good idea to use more fine grained dependencies for javatools instead of the fatker, because incremental builds with the javatools dependency ENABLED (default) would likely resolve faster).
The text was updated successfully, but these errors were encountered: