[
https://issues.apache.org/jira/browse/FELIX-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598162#action_12598162
]
Stuart McCulloch commented on FELIX-571:
----------------------------------------
FYI, there already is a property for the remote file, it's called remoteOBR -
from the online docs:
* deploy - adds the current bundle project to a remote OBR
configuration options:
o remoteOBR name of remote OBR, defaults to NONE (which means no
remote OBR deployment)
o obrRepository used when the remoteOBR name is blank, defaults to
repository.xml
o altDeploymentRepository alternative remote repository,
id::layout::url
o ignoreLock ignore remote locking when updating the OBR
So if remoteOBR is set to either the empty string or "true" (case-ignored) then
it will use the obrRepository value, otherwise it will take the remoteOBR value
as the remote filename. This lets you use different names for the local and
remote OBR files when installing and deploying in the same build.
> Remote OBR deployment does not support the obrRepository property
> -----------------------------------------------------------------
>
> Key: FELIX-571
> URL: https://issues.apache.org/jira/browse/FELIX-571
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.1
> Reporter: Clement Escoffier
> Priority: Minor
>
> The obrRepository property seems to not be supported when deploying on a
> remote repository.
> When specified, the local repository is correctly created in specified file
> but when deploying, the used file is always repository.xml.
> I wonder if two different properties could be useful to differentiate the
> local file and the remote file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
