[
https://issues.apache.org/jira/browse/FELIX-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-580.
------------------------------------
Resolution: Fixed
Ok, I've committed a variation of this patch:
the deploy goal now supports prefixUrl (to force absolute locations) and
bundleUrl (to force an explicit location)
it also supports obrDeploymentRepository, which will override the standard
altDeploymentRepository setting.
this allows much more flexibility when deploying OBR metadata - I've also
updated the remote-clean goal to match.
I've left the deploy-file goal alone for the moment, because imho it should be
kept purely as a command-line variant
that doesn't read in the current pom.xml - this is what maven users typically
expect, and changing it to do otherwise
is potentially confusing. (if users want to use the current pom.xml they should
use the deploy goal instead)
> Allows maven-bunde-plugin to generate a repository file outide a maven
> repository with absolute url
> ---------------------------------------------------------------------------------------------------
>
> Key: FELIX-580
> URL: https://issues.apache.org/jira/browse/FELIX-580
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Reporter: Clement Escoffier
> Assignee: Stuart McCulloch
> Fix For: maven-bundle-plugin-1.4.2
>
> Attachments: obr-patch.patch
>
>
> The actual maven-bunde-plugin:deploy goal generates OBR repository files but
> this file is necessary at the root of a maven repository where the artifacts
> are deployed. So, creating a new OBR often requires to duplicate bundle
> files. The deploy-file goal can generate this kind of OBR (with absolute URL
> and no duplication) but does not support multi-module project and is a pain
> to configure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
