-
Notifications
You must be signed in to change notification settings - Fork 11
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
Maven Central Artifacts #9
Comments
@chlarsson But they have different osgi.ee requirements and have to have different versions. |
We have regarded this as compiling a C/C++ program for 32 or 64 bit, or ARM vs X86. The version is the same though. |
Cannot you use fragment bundles for native libs? |
I think you misunderstood. There's no native code / native libs, it was only a comparison. I.e. you normally don't change the version of a C-lib when you recompile it for X86_64. We have used the same philosophy in KF. I.e. we haven't changed the version of the bundle when changing JDK, it's just a recompilation. The distribution has then traditionally been as one complete versioned SDK with all bundles together. We have used this approach since 2003 (I don't think maven was around at that time). Anyway, this makes us not the ideal maven citizen and we are now looking at how to improve that. |
let me try to understand: you have bundles, for example, useradmin implementation that is compiled with JDK from 4 to 8 and all these artifacts have the same BSN and version, don't they? Only one difference from OSGi side - different osgi.ee requirement. |
Yes, that's correct. |
In this case, Maven classifier suits very well. e.g.
|
I would like to see the KF artifacts at maven central as well, and like to add the following aspect to the discussion: Even though it is often the case, there is no requirement for a maven artifact to match its bundle versions, so it would be perfectly fine to deploy the KF5 artifacts under the maven version 5.0.0 and the KF6 ones as maven version 6.0.0 even if their bundle versions are the same! |
I'd be great to see KF artifacts in Maven Central Repo. Discussion started in #6
The text was updated successfully, but these errors were encountered: