Hi, I'm trying to figure out if there is concensus at Eclipse regarding the versioning of bundles in a Maven repository.
OSGi/Eclipse requires <major>.<minor>.<service>.<qualifier> where the qualifier is some string designation for the build. However, Maven users utilizing "version ranges" would require usage of the Maven standard of <major>.<minor>.<revision>-[qualifier/buildno]. Some experimentation on my part shows that Maven renames objects based upon the artifactId and versionId when publishing. I haven't confirmed whether they are renamed back when retrieved for a build. However, to be compatible with Eclipse they will need to retain the <bundle_name>_<M>.<m>.<s>.<qualifier>.jar naming. Do they? Am I wrong? Since I don't use Maven for building I cannot test it easily. Now Tycho utilizes P2 repositories, so the question is mostly sidestepped, but not all projects use Tycho to generate their bundles, not all projects generate only eclipse plugins, and not all teams publish only to P2. I'm wondering how other teams deal with the disparity between versioning schemes. I don't want to accommodate Maven publishing standards only to break the artifacts published (Publishing to Maven shouldn't preclude the bundles use in Eclipse). However, given the growing number of bugs I'm receiving regarding Maven support, I believe that ignoring Maven methodology isn't in the best interest of the project as a whole. Any comments/suggestions? Thanks. -Eric _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
