You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a POM module called wicketstuff-bom containing only managed dependencies for the wicketstuff core modules. This way downstream users can import the BOM and do not need to specify versions for all the owlapi modules (not even via a version property). The module should only define versions of wicketstuff core modules, not of third-party dependencies.
The text was updated successfully, but these errors were encountered:
I doubt it would be possible to provide the single bom for all projects
I would create *-bom subproject for the module of your interest for ex. wicketstuff-jquery-ui-parent\wicketstuff-jquery-ui-bom :)
@solomax why do you believe it would not be possible to provide a single BOM? As I said, the BOM is for downstream consumption and only manages the wicketstuff module versions and not any third-party versions. Thus, IMHO it should not be any problem at all.
Provide a POM module called
wicketstuff-bom
containing only managed dependencies for the wicketstuff core modules. This way downstream users can import the BOM and do not need to specify versions for all the owlapi modules (not even via a version property). The module should only define versions of wicketstuff core modules, not of third-party dependencies.The text was updated successfully, but these errors were encountered: