-
Notifications
You must be signed in to change notification settings - Fork 3
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
Using org.eclipse.orbit:ant:1.10.14
for the latest ant version causes problems
#17
Comments
org.eclipse.orbit:ant:1.10.14
for the latest ant version causes problems
Tycho 2.x is EOL
Tycho 3.x is EOL
If you see issues with current released latest Tycho version please provide an integration-test to demonstrate the issue.
This is the recommended approach prior Tycho 4...
The best would be to simply deploy it to maven central, there is already an orbit group id: |
I don't think this is the right solution - as when we rewrap things we are often changing the dependency information. I think instead of trying to make it look like The supposed reason to map to maven coordinates is so things like |
With both Tycho 2.7.5, 3.0.5, and probably 4.0.3, a build against the Platform's 4.30 version fails because of ant dependency checking.
Update: No it does not fail for Tycho 4.0.3. So using the latest Tycho is definitely the best step forward.
Firstly one sees this in the log:
But then the build fails completely like this:
The problems are highlighted here:
It appears that the following functions well as a workaround:
So the open question for Orbit is, should I change the coordinates used to publish the transformed ant downloads from this location
to use coordinates that will exactly match this:
keeping in mind that these are NOT THE SAME ARTIFACTS so there seems some risk in conflating the two.
In other words, should I replace the org.eclipse.obit prefix/groupId with org.apache for the following build process:
https://github.com/eclipse-orbit/orbit-simrel/tree/main/maven-ant
Everyone having broken Tycho builds is also extremely unpleasant so I'm not sure how best to balance risk against unpleasantness...
The text was updated successfully, but these errors were encountered: