nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating marketplace package with variables in install.xml

patrek

Making a package for the marketplace, I'm trying the following syntax, with no success <update file="${package.root}/bundles/my-super-bundle-${property-from-pom.version}" todir="${env.bundles}" overwrite="true" />

But it works if I use <update file="${package.root}/bundles/my-super-bundle-1.0.0" todir="${env.bundles}" overwrite="true" />

As my bundle contains a few jar, I'd like to be able to define my version number in one place (the pom.xml file) and reuse it in assembly.xml and install.xml. Is there a way/syntax to do it or do I have to revert to replacement with the maven filtering mechanism?

Thanks

Find more posts tagged with

Accepted answers

Julien_Carsique

I recommend to assemble the Marketplace package using nuxeo-distribution-tools.

You can give a look at nuxeo-marketplace-dm to see how it's done for Nuxeo DM Marketplace package.

About your question, you could use Ant replacement with Maven variables (thanks to nuxeo-distribution-tools) but note the update command accepts a directory as input: you don't need to list each bundle with its precise name, simply provide the directory containing the bundles you want to be deployed by your package.

All comments

Julien_Carsique

I recommend to assemble the Marketplace package using nuxeo-distribution-tools.

You can give a look at nuxeo-marketplace-dm to see how it's done for Nuxeo DM Marketplace package.

patrek

We are using the nuxeo-distribution-tools.

Julien_Carsique

Note the Marketplace package build is using a comparison between the two EAR-like artifacts [nuxeo-distribution-cap][1] and [nuxeo-distribution-dm][2].