On 3/25/10 21:51, Felix Meschberger wrote:
Hi,
The NOTICE files of both the bundlerepository and the utils project
mention, that OSGi provided software is contained.
AFAICT for utils this has never been the case and for bundlerepository
this is not the case since the OBR API has been broken out
Guillaume,
Ok, indeed, it works if I manually do the following:
1) build utils
2) build bundlerepository
3) build bundleplugin
4) and then type "mvn -Dmaven.test.skip=true -Dpackaging=bundle install"
However, with your last commit, if I type directly "mvn
-Dmaven.test.skip=true -Dpackaging=bundl
The eventadmin doesn't need the logservice packages around to work --
hence, they are excluded. It can use a LogService however, assuming
one is around and the packages are around. The Import-Service is
deprecated but it never did anything in the first place. It is just
there to indicate that we ca
Folks,
is there a reason eventadmin excludes the Log Service from the
Import-Packages and instead uses the deprecated Import-Service header?
org.osgi.service.event.EventHandler,
org.osgi.service.log.LogService, org.osgi.service.log.LogReaderService
cheers
-thomas
--
xxx
[
https://issues.apache.org/jira/browse/FELIX-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-2235.
-
Resolution: Fixed
Fix Version/s: webconsole-3.0.0
Assignee: Valentin Valch
That one works for me. Make sure you svn up. The root pom may be missing
the utils subproject too and you actually need a freshly build copy of it,
so try building it manually first. I'll try to add it to the build in the
meantime.
On Thu, Mar 25, 2010 at 14:19, Pierre De Rop wrote:
> Guillau
I've just added support for the '<' operator this morning, so I think if you
rebuild the utils / bundlerepository / bundleplugin, you should get rid of
that one.
On Thu, Mar 25, 2010 at 13:51, Pierre De Rop wrote:
> Indeed, I get some exceptions while building the upnp subproject:
>
> [INFO] Sca
[
https://issues.apache.org/jira/browse/FELIX-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849706#action_12849706
]
Valentin Valchev commented on FELIX-2235:
-
Oops, it works correctly with SUN JDK bu
[
https://issues.apache.org/jira/browse/FELIX-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849701#action_12849701
]
Felix Meschberger commented on FELIX-2235:
--
Hmm, the deployment admin plugin is no
Hi,
The NOTICE files of both the bundlerepository and the utils project
mention, that OSGi provided software is contained.
AFAICT for utils this has never been the case and for bundlerepository
this is not the case since the OBR API has been broken out into a
separate bundle.
So, can we remove t
Deployment plugin fails with internal server error
--
Key: FELIX-2235
URL: https://issues.apache.org/jira/browse/FELIX-2235
Project: Felix
Issue Type: Bug
Components: Web Console
[
https://issues.apache.org/jira/browse/FELIX-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849697#action_12849697
]
Felix Meschberger commented on FELIX-2231:
--
Fixed the NullPointerException (and a
Hi,
Hmm, difficult question...
How about this: We leave it in for the 3.0 release and make upgrade from
previous releases as seemless as possible.
For the next release we scan all contained plugins and decide on which
plugins to keep in the core web console (I would assume the OSGi Core
Spec as
Guillaume,
The issue reported by Sahoo also takes place when just typing:
mvn -Dmaven.test.skip=true -Dpackaging=bundle install
(it's quicker than when typing "ant")
On Thu, Mar 25, 2010 at 1:51 PM, Pierre De Rop wrote:
> Indeed, I get some exceptions while building the upnp subprojec
Indeed, I get some exceptions while building the upnp subproject:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Apache Felix UPnP Extra
[INFO] Apache Felix UPnP Base Driver
[INFO] Apache Felix UPnP Tester
[INFO] Apache Felix UPnP Sample Binary-Light
[INFO] Apache Fel
Can you try building only the upnp subproject ?
I suspect a problem with maven mixing the versions of bundlerepository to
use.
On Thu, Mar 25, 2010 at 11:49, Pierre De Rop wrote:
> I just type "ant".
> Is this the correct way to compile the whole trunk ?
>
> /pierre
>
>
> On Thu, Mar 25, 2010 at
NO_LOCAL_RESOURCES does not take into account local resources (i.e.
resources created for bundles installed in your framework). This means
that any constraint will be solved by either the system bundle, or one of
the resource from the configured repositories. They will thus be listed in
the requ
Guillaume,
If you use the NO_LOCAL_RESOURCES flag, your resolution should not contain
any local resources,
What you describe here is the normal behaviour of the resolver without
any flag; and it was the whole point of JIRA:FELIX-692
What exact feature did you mean to implement with this flag?
I just type "ant".
Is this the correct way to compile the whole trunk ?
/pierre
On Thu, Mar 25, 2010 at 11:35 AM, Guillaume Nodet wrote:
> Btw, what command do you use the build the whole trunk ?
>
> On Thu, Mar 25, 2010 at 11:18, Pierre De Rop
> wrote:
>
> > Hello Guillaume;
> >
> > Just to
Btw, what command do you use the build the whole trunk ?
On Thu, Mar 25, 2010 at 11:18, Pierre De Rop wrote:
> Hello Guillaume;
>
> Just to confirm what Sahoo said: I also can't build the trunk, and get the
> same error: java.lang.NoClassDefFoundError:
> org/apache/felix/bundlerepository/Require
Hello Guillaume;
Just to confirm what Sahoo said: I also can't build the trunk, and get the
same error: java.lang.NoClassDefFoundError:
org/apache/felix/bundlerepository/Requirement ...
(I am using maven 2.2.1)
/pierre
On Thu, Mar 25, 2010 at 9:18 AM, Guillaume Nodet wrote:
> I don't see this
On 3/25/10 16:36, Guillaume Nodet wrote:
Yeah, I know. That was my idea originally. The problem is that some obr
repositories out there still use the '<' and'>' operator, so i'd like to
support those anyway.
I'll see if a better way would be to transform the filter expressions using
regexp befo
Hey guys,
I have been making some changes to the framework in trunk this week
which could result in behavioral differences. The changes will largely
impact querying services:
1. I have completely switched from the standard Filter implementation
to the one used by the framework's resolv
Hi:
camel-osgi component give another a spring osgi
namespace."http://camel.apache.org/schema/osgi";.
But if I use the normal
spring-namespace(http://camel.apache.org/schema/spring), it seems works too
in osgi environment.
So what's the real different for the osgi namespace?
Yeah, I know. That was my idea originally. The problem is that some obr
repositories out there still use the '<' and '>' operator, so i'd like to
support those anyway.
I'll see if a better way would be to transform the filter expressions using
regexp before parsing them and turn '(x=a))'
On Thu,
I'm not sure it's a great idea to continue to extend the Filter impl.
From my point of view it is better to stick to the standard filter
where possible...I understand that the subset operator is necessary for
time being to support mandatory attributes, but eventually we should be
able to avoid
I don't see this error.
Which version of maven do you use ? I use 2.2.0 and it seems to work for me.
On Thu, Mar 25, 2010 at 07:18, Sahoo wrote:
>[exec] [INFO]
>
>[exec] [INFO] Building Apache Felix UPnP Extra
>
27 matches
Mail list logo
