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
Currently, reckon doesn't allow me to rebuild historic snapshots from old commits (with clean repo) if the subsequent normal version has already been released. Let's assume the following project setup:
Plugin settings:
reckon {
normal = scopeFromProp()
preRelease = snapshotFromProp()
}
Now I want to rebuild X from a clean repo state, but reckon complains, saying:
* What went wrong:
Could not determine the dependencies of task ':compileJava'.
> Could not resolve all dependencies for configuration ':compileClasspath'.
> Reckoned target normal version 0.1.0 has already been released.
In my opinion it should be possible to rebuild 0.1.0-SNAPSHOT from X when there are no local changes present and the 0.0.1 Tag is the lowest normal version within the successor commits reachable from X.
Of course I can still use -Preckon.scope=major or -Preckon.scope=patch to build 1.0.0-SNAPSHOT or 0.0.1-SNAPSHOT in this example, if the subsequent normals have not been claimed yet.
But the behavior above can be particularly painful, since I am not able to import old revisions (e.g. when im git bisecting) of my project into Eclipse using buildship with the build failing.
I wrote a small (failing) test, illustrating the expected behavior:
esz/reckon@dbe10e34ac53a514cb6b6b750e9209c6673c4d01
What do you think about that? Am I just overlooking some valid reason for this restrictive behavior? If you think this would be a useful addition, I'd contribute happily!
The text was updated successfully, but these errors were encountered:
Currently, reckon doesn't allow me to rebuild historic snapshots from old commits (with clean repo) if the subsequent normal version has already been released. Let's assume the following project setup:
Plugin settings:
Repo:
Now I want to rebuild
X
from a clean repo state, but reckon complains, saying:In my opinion it should be possible to rebuild
0.1.0-SNAPSHOT
fromX
when there are no local changes present and the0.0.1
Tag is the lowest normal version within the successor commits reachable fromX
.Of course I can still use
-Preckon.scope=major
or-Preckon.scope=patch
to build1.0.0-SNAPSHOT
or0.0.1-SNAPSHOT
in this example, if the subsequent normals have not been claimed yet.But the behavior above can be particularly painful, since I am not able to import old revisions (e.g. when im
git bisect
ing) of my project into Eclipse using buildship with the build failing.I wrote a small (failing) test, illustrating the expected behavior:
esz/reckon@dbe10e34ac53a514cb6b6b750e9209c6673c4d01
What do you think about that? Am I just overlooking some valid reason for this restrictive behavior? If you think this would be a useful addition, I'd contribute happily!
The text was updated successfully, but these errors were encountered: