Keeping selected versions of bundles from "Central" JPM4J repo between updates

[Przemysław Wesołek]

I'm using "Central" JPM4J repo, as created in enRoute workspace:

-plugin.4.Central:  \
\
        aQute.bnd.deployer.repository.wrapper.Plugin; \
            location            =    "${build}/cache/wrapper"; \
            reindex                =    true, \
\
        aQute.bnd.jpm.Repository; \
            includeStaged       =       true; \
            name                =       Central; \
            location            =       ~/.bnd/shacache; \
            index               =       ${build}/central.json

Once in a while I right-click on the repo in Bndtools and select "Update all" — really nice feature in itself! However, not having a control over the process is troublesome. Despite "updating all" I don't want to update all bundles: some bundles have to kept in the specific version. Is there a way to "tag" or "hold" a bundle in a repository and not updating?

A problem in itself, and possibly additional rational, assuming I want to have "bleeding edge" versions, is that such a process leads to "semantic downgrade". Many Maven packages are semantically versioned, but older releases of them are not. E.g. the newest commons-lang [1] is 2.6.0, but after "Update all" an ancient version 20030203.129.0 replaces 2.6.0. Is there a way to circumvent this?

[1] http://jpm4j.org/#!/p/commons-lang/commons-lang

[Peter Kriens]

Unless you provide PRs there is not a lot of stuff going to happen (by me at least) on the JPM user interface due to lack of time.

Kind regards,

Peter Kriens

--
You received this message because you are subscribed to the Google Groups "bndtools-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bndtools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Przemysław Wesołek]

And without UI? Is there any way to lock a bundle version?

Przemek

[Peter Kriens]

There is an API on JPM, look at the biz.aQute.bnd.repository project in bnd. The JPM Repository class actually provide the menu entries so you could create a menu command. The repository can get even the most minute detail of a revision or program.

Kind regards,

Peter Kriens

[Marc Schlegel]

I was actually planning to enhance the UI support with some PRs, but did not have the time to do so yet.

There are a couple of issues that needs to be adressed

• Multiple selections do not work -> https://github.com/bndtools/bndtools/issues/1427
• Update will get you the latest version, which might involve a major version bump. You might also get a beta/snapshot version -> a dialog with available updates to select from should also fix your problem

Let me know if you are working on a PR as well. It would be a waste of time for at least one of us ;-)

regards

Marc

[Peter Kriens]

I absolutely have no time so please go ahead … 

For any work, create a PR and keep updating it so we can track progress and know what is being worked upon. When you’re done, send a mail so we can review and merge it.

Kind regards,

Peter Kriens