Skip to content
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

Provide bndtools 7.1+ p2 release repositories so that oomph setups can refer to specific bndtools versions #6084

Open
scottslewis opened this issue Apr 12, 2024 · 1 comment

Comments

@scottslewis
Copy link
Contributor

As per discussion on #6046 and summarized by issue #6083 it would be desirable to have oomph setups contributed so that users could easily create and configure bndtools without having to separately install bndtools to Eclipse.

One requirement of using oomph setups is that there should be separate p2 repo urls for specific versions of bndtools, rather than simply the latest released version of bndtools by new versions. This need is summarized by this discussion:

https://bnd.discourse.group/t/specific-release-url-for-each-release-humble-request/289

This will require some changes to the bnd build and perhaps usage of p2 director (command line)? There is relevant work described by this comment #6046 (comment)

@chrisrueger
Copy link
Contributor

Just for further reference: The bnd release process (including the P2 repo stuff) seems to be described here:
https://github.com/bndtools/bnd/wiki/Release-Process

@pkriens pkriens assigned pkriens and unassigned pkriens Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants