Agree with David, the "legacy" is "important" IMHO.
Regards
JB
On 11/10/2015 08:27 AM, David Bosschaert wrote:
Hi Benson,
Personally I wouldn't rename the plugin. Whether or not it's following
naming guidelines, it's known as the 'maven-bundle-plugin' and
renaming it will cause confusion.
I h
Hi Benson,
Personally I wouldn't rename the plugin. Whether or not it's following
naming guidelines, it's known as the 'maven-bundle-plugin' and
renaming it will cause confusion.
I have no problem with bumping the version. I personally don't think
it has to follow the bnd versioning - it would be
My 2 cents as a non developer for felix or karaf
I have made the switch for my core packages to the bnd-maven-plugin and
like that I can copy things between my bnd.bnd file and my bndrun file
that I use for testing in eclipse. I am looking forward to when they get
launcher and test support for
Thanks for the suggestions Christian. I may indeed write a blog post. In the
meantime, you can place this in the bnd.bnd of your parent project:
-exportcontents:
${packages;ANNOTATED;org.osgi.annotation.versioning.Version}
This exports any packages that have the @Version annotation on t
Thanks for the clarifications.
I personally like the external bnd.bnd files. They are more concise than
xml configs.
You should maybe write a blog entry about the annotations and also the
parent configs. I liked the way you generically set up the exports based
on the version annotations but fo
I am preparing, at least mentally, to do to [1] to the
maven-bundle-plugin -- to make it require Maven 3.x.
So, you might think that I need to change the major version number.
This, of course, would have the effect of de-syncing the versions from
bnd versions. Maybe this doesn't bother anyone.
On
Just addressing a couple of points made on this list.
Yes, we support only instructions in the separate bnd.bnd file (currently).
However with judicious use of Java annotations, we find that you very rarely
need bnd instructions at all! However I don’t agree that this is the "biggest
difference
Is there an Embed-Dependency analog?
On Nov 9, 2015 12:07 PM, "Konrad Windszus" wrote:
> The biggest difference is that currently the bnd-maven-plugin does not
> support instructions within pom files (
> https://github.com/bndtools/bnd/issues/952) but rather only in dedicated
> bnd files.
> There
The biggest difference is that currently the bnd-maven-plugin does not support
instructions within pom files (https://github.com/bndtools/bnd/issues/952) but
rather only in dedicated bnd files.
Therefore for existing users of maven-bundle-plugin it is not so easy to
migrate.
Konrad
> On 09 Nov
Hi Christian,
it sounds promising, but maybe a bit early to have a strong opinion.
From a technology standpoint, it's good to converge.
However, we talk about two different community there, and maybe license.
As a tooling, it's not a big deal.
Regards
JB
On 11/09/2015 11:02 AM, Christian Schn
+1
2015-11-02 13:24 GMT+01:00 Marcel Offermans :
> I would be more comfortable if we first had someone volunteer to adapt all
> (Maven and Ant/Gradle based builds) to work with Git and otherwise ensure
> that all projects keep working. Then demonstrate all of that (with a copy
> of our repositor
Here's my +1
David
On 9 November 2015 at 09:47, wrote:
> Hi all,
>
> I'd like to call a vote on a 0.1.0 (beta) release of the subsystems
> plugin for the Felix Webconsole.
> This plugin adds support for managing OSGi subsystems to the Felix
> Webconsole. While this plugin is not completely matu
Here's my +1
David
On 9 November 2015 at 09:28, wrote:
> Hi all,
>
> I'm calling a vote on the Felix OSGi Coordinator version 1.0.2. The
> coordinator implements chapter 130 of the OSGi Enterprise specs.
>
> The following issues were fixed since 1.0.0:
> FELIX-5086 Coordinator.begin can return
[
https://issues.apache.org/jira/browse/FELIX-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996524#comment-14996524
]
Przemek Wesolek commented on FELIX-5058:
I can also confirm that this bug is also
[
https://issues.apache.org/jira/browse/FELIX-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Vodicka closed FELIX-5086.
-
> Coordinator.begin can return null
> -
>
> Key: FELIX
+1
David
On 9 November 2015 at 11:44, Benson Margulies wrote:
> Hi,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333631&styleName=Text&projectId=12310100&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C0a2bd62f03263e903089dc8019574717effb605c%7Clin
>
>
+1 (non binding)
Regards
JB
On 11/09/2015 10:28 AM, dav...@apache.org wrote:
Hi all,
I'm calling a vote on the Felix OSGi Coordinator version 1.0.2. The
coordinator implements chapter 130 of the OSGi Enterprise specs.
The following issues were fixed since 1.0.0:
FELIX-5086 Coordinator.begin c
+1 (non binding)
Regards
JB
On 11/09/2015 10:47 AM, dav...@apache.org wrote:
Hi all,
I'd like to call a vote on a 0.1.0 (beta) release of the subsystems
plugin for the Felix Webconsole.
This plugin adds support for managing OSGi subsystems to the Felix
Webconsole. While this plugin is not comp
+1 (non binding)
Regards
JB
On 11/09/2015 12:44 PM, Benson Margulies wrote:
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333631&styleName=Text&projectId=12310100&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C0a2bd62f03263e903089dc8019574717effb605c%7
[
https://issues.apache.org/jira/browse/FELIX-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996420#comment-14996420
]
Przemek Wesolek commented on FELIX-5058:
Can confirm this happen. The usage of old
+1 (non-binding)
Is this the one that is 'owned' by the bndlib people, or are there
more than one?
The 'bnd' mailing list told me that it had less capability than the
maven-bundle-plugin, so that would be a reason not to retire.
I'll take on the lifecycle, but I'll make it a plugin that requires
maven 3, first. T
I recently looked into the bnd-maven-plugin from paremus. It features a
better maven lifecycle integration than the felix one.
So for example you do not need the packaging "bundle" anymore which is a
big obstacle for some projects.
It also will probably be part of the maven support for bdntools.
This thread has again quiesced. I respectfully submit that it's time
for a PMC member to start a [VOTE] thread to see whether there is a
decision to proceed.
On Sat, Oct 24, 2015 at 2:51 PM, Benson Margulies wrote:
> Greeting, Marcel,
>
> It's not my intention to try to talk anyone into changing
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333631&styleName=Text&projectId=12310100&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C0a2bd62f03263e903089dc8019574717effb605c%7Clin
There are still a couple of issues left in JIRA:
https://issues.apache.org
I don't seem to have access to manage versions, and people have been
marking JIRAs as fixed for 3.0.2 instead of 3.0.1. I am going to cheat
to send out a vote, but I will fix up JIRA as soon as I have access.
Hi all,
I'd like to call a vote on a 0.1.0 (beta) release of the subsystems
plugin for the Felix Webconsole.
This plugin adds support for managing OSGi subsystems to the Felix
Webconsole. While this plugin is not completely mature yet, this 0.1.0
release will make it easier for other communities t
Very nice, Benson!
David
On 9 November 2015 at 07:01, Hervé BOUTEMY wrote:
> great
>
> Warning: you should add a "/extpaths.txt" file containing "components" ASAP,
> because if you don't do this, the next time you'll use the CMS to push content
> from staging area to production area, the content
Hi all,
I'm calling a vote on the Felix OSGi Coordinator version 1.0.2. The
coordinator implements chapter 130 of the OSGi Enterprise specs.
The following issues were fixed since 1.0.0:
FELIX-5086 Coordinator.begin can return null
FELIX-5065 Coordinator should provide osgi.service capability
Sta
[
https://issues.apache.org/jira/browse/FELIX-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert resolved FELIX-5086.
-
Resolution: Fixed
> Coordinator.begin can return null
> -
Konrad Windszus created FELIX-5095:
--
Summary: Extend javadoc for instructions parameter of
maven-bundle-plugin
Key: FELIX-5095
URL: https://issues.apache.org/jira/browse/FELIX-5095
Project: Felix
31 matches
Mail list logo
