possibility to set the repository name for the 'FeaturesAndBundlesPublisher'

Open

#212 opened on Sep 7, 2023 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 32/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: java
Domain: build-system

Research direction

Start by locating FeaturesAndBundlesPublisher and the p2.publish.featuresAndBundles Ant task integration, then trace how it generates artifacts.xml and content.xml. Check whether repositoryName, metadataRepositoryName, artifactRepositoryName, or the p2 repository-name properties are forwarded; done means a configurable name appears in both generated repository files, with the supported workaround documented if it cannot be added.

Written by the indexing model from the issue text.

Description

enhancement

It seems 'FeaturesAndBundlesPublisher' is missing a possibility to set the created repository name ('<repository name=...' in the generated 'artifacts.xml' and 'content.xml'). Repository names generated by default contain the repository disk path (i.e. one from the build server) which may be unacceptable.

I believe this may be done via 'repositoryName'/'metadataRepositoryName'/'artifactRepositoryName' attributes of the 'p2.publish.featuresAndBundles' Ant task (see https://wiki.eclipse.org/Equinox/p2/Publisher). Maybe (not sure) also somehow via 'p2.metadata.repo.name'/'p2.artifact.repo.name' properties.

Some general way of specifying some Ant task attribute would also be beneficial.

Is there any workaround way to specify the repository name for 'FeaturesAndBundlesPublisher' in the current Goomph version?

Dominant language: Java
Stars: 137
Forks: 33
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.