would a patch to the maven-bundle-plugin be accepted?
Enrico
Am 28.09.2010 um 22:28 schrieb Justin Edelson:
If you want to write your own plugin, by all means go ahead. I was
trying to help you accomplish what I understood to be your goal
(adding
accurate metadata about one or more third party bundles into your own
OBR) with the existing plugin, but if that's not of interest to you, I
apologize for wasting your time.
Justin
On 9/28/10 1:48 AM, Enrico Schnepel wrote:
What I read from the documentation is that "bundle:deploy-file adds a
local bundle file to a remote OBR". but I need the opposite while
using
a maven dependency: "bundle:install-dependencies adds maven bundle
dependencies to a local OBR".
Furthermore I would depend on a specific maven repository with a
specific url. having a fallback-repository would not be possible
and the
through compile dependencies already installed maven bundle is
completely ignored.
Thanks
Enrico
Am 27.09.2010 um 17:03 schrieb Justin Edelson:
It sounds to me like you should use bundle:deploy-file. That goal
allows
you to specify the URL to the deployed bundle.
On 9/25/10 1:29 AM, Enrico Schnepel wrote:
Thanks for your answer.
I am rebundling to achive a higher goal ... I want to put a maven
bundle
dependency into the obr. install-file uses a file system path. I
have
only the maven dependency and I don't want to hard link into
local maven
repository or download it first from a url. a task install-
dependencies
would create the missing obr entry for the bundle without
touching the
bundle itself.
Thanks
Enrico
Am 24.09.2010 um 18:08 schrieb Justin Edelson:
If you have an OSGi bundle, why are you re-bundling it?
I don't have first-hand knowledge of this, but AFAIK,
bundle:install-file will use the MANIFEST.MF from the bundle being
installed. In point of fact, I don't see how it could work
otherwise.
Justin
On 9/24/10 12:24 AM, Enrico Schnepel wrote:
Does anyone have an idea?
Thanks
Enrico
Am 18.09.2010 um 06:52 schrieb Enrico Schnepel:
Hello Felix(-users),
I am currently using the maven bundle plugin to re-bundle an
existing
maven bundle in order to make it accessible in a obr
repository. The
problem I have... the exported package versions are not
correctly
exported to the manifest and repositoy.xml. There is no version
mentioned for the package export but the import package uses
versions.
This results in not resolved dependencies. In addition to
that ... I
think it is not the right way to go. What I really want to do
is a
"install-dependencies" goal. It should work like the
bundle:install-file goal but I want to simply specify the to be
exported bundles as dependencies in the pom.xml. The goal
should use
the metadata already in the MANIFEST.MF including the im- and
exported
packages with versions etc. and should put them into the local
repository.
Or is there a way to do this I have overseen?
Thanks
Enrico
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
