[
https://issues.apache.org/jira/browse/FELIX-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Wojtuniak updated FELIX-1891:
--
Attachment: org.apache.felix.io.test.zip
> IO Connector Service contribution
>
[
https://issues.apache.org/jira/browse/FELIX-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Wojtuniak updated FELIX-1891:
--
Attachment: io.zip
io.md5
io.test.md5
I would like to contribut
IO Connector Service contribution
-
Key: FELIX-1891
URL: https://issues.apache.org/jira/browse/FELIX-1891
Project: Felix
Issue Type: New Feature
Components: IO Connector Service
Reporter:
A very cheap + felix related solution would be: fileinstall + webconsole.
But also overpowered to some extend.
Best would be a platform optimized solution:
Mac users probably would like to have a Quck View Implementation for Bundles
that automatically show the manifest.mf . ;)
On Mon, Nov 23, 2009
Yeah, that's my understanding as well. I think that an visual
interactive tool would be handy.
On Nov 23, 2009, at 1:39 PM, Richard S. Hall wrote:
I think BND can be used as a viewer, but it is more of a command-
line thingy.
-> richard
On 11/23/09 15:29, Alan D. Cabrera wrote:
Sometimes
I think BND can be used as a viewer, but it is more of a command-line
thingy.
-> richard
On 11/23/09 15:29, Alan D. Cabrera wrote:
Sometimes it would just be plain handy to double click on a bundle
have have all sorts of information be displayed in a useful format.
Ideally, I could futz w/ i
I had to increase the memory using MAVEN_OPTS=-Xmx512m to make the build work
again. It was running out of memory without that on both the Bamboo server and
my machine. I'm sending this to the list to make sure everybody is aware of
this.
Greetings, Marcel
On Nov 23, 2009, at 21:50 , Atlassia
On Nov 23, 2009, at 10:23 AM, Stuart McCulloch wrote:
2009/11/24 Alan D. Cabrera
When converting 3rd party jars it's my understanding that it's a
good idea
that if it's a "leaf" jar, i.e. has no deps, then it should not
import what
it exports.
It's not clear to me how I should configure
[
https://issues.apache.org/jira/browse/FELIX-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781604#action_12781604
]
Fabrizio Giudici commented on FELIX-1890:
-
Quick correction. I wrote
"The curious
Sometimes it would just be plain handy to double click on a bundle
have have all sorts of information be displayed in a useful format.
Ideally, I could futz w/ imports/exports/etc and have the changes
saved in the proper manifest format.
Does such a tool exist?
Regards,
Alan
The maven-bundle-plugin doesn't work properly if spawned by release:perform
---
Key: FELIX-1890
URL: https://issues.apache.org/jira/browse/FELIX-1890
Project: Felix
Issu
Alan D. Cabrera wrote:
> When converting 3rd party jars it's my understanding that it's a good
> idea that if it's a "leaf" jar, i.e. has no deps, then it should not
> import what it exports.
IMHO Peter explained it well:
http://www.osgi.org/blog/2007/04/importance-of-exporting-nd-importing.ht
2009/11/24 Toni Menzel
> Why exactly do you want to do this ?
> It is common (and good) practice to import what you export to the framework
> more options for wiring. You don't lose anything. Its also known as
> "package
> substitution".
>
FYI, every rule or "best-practice" has exceptions ;) in
On Mon, Nov 23, 2009 at 7:23 PM, Stuart McCulloch wrote:
> 2009/11/24 Alan D. Cabrera
>
> > When converting 3rd party jars it's my understanding that it's a good
> idea
> > that if it's a "leaf" jar, i.e. has no deps, then it should not import
> what
> > it exports.
> >
> > It's not clear to me
2009/11/24 Alan D. Cabrera
> When converting 3rd party jars it's my understanding that it's a good idea
> that if it's a "leaf" jar, i.e. has no deps, then it should not import what
> it exports.
>
> It's not clear to me how I should configure the bundle plugin to do this.
>
the Bnd tool handles
Why exactly do you want to do this ?
It is common (and good) practice to import what you export to the framework
more options for wiring. You don't lose anything. Its also known as "package
substitution".
If you really want to do this, you try add a Import-Package:
!myexportpackage,*
But you usual
When converting 3rd party jars it's my understanding that it's a good
idea that if it's a "leaf" jar, i.e. has no deps, then it should not
import what it exports.
It's not clear to me how I should configure the bundle plugin to do
this.
Regards,
Alan
[
https://issues.apache.org/jira/browse/FELIX-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-1888.
Resolution: Fixed
Assignee: Guillaume Nodet
Committing to https://svn.apache.org/repo
The vote has passed with the following result :
+1 (binding): Guillaume Nodet, Marcel Offermans, Richard S. Hall
+1 (non binding): Chris Custine, Derek Baumm David Bosschaert, Freeman Fang,
I will copy this release to the Felix dist directory and
promote the artifacts to the central Maven rep
[
https://issues.apache.org/jira/browse/FELIX-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-1887.
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M
On Mon, Nov 23, 2009 at 16:59, Richard S. Hall wrote:
> +1
>
> Future releases should probably depend on the official OSGi JARs, not our
> deprecated JARs.
I've raised a jira for that.
>
> I also noticed some of the used vs. includes (e.g., commands launcher) in
> the NOTICE file were not comple
Gogo should depend on the official OSGi jars
Key: FELIX-1889
URL: https://issues.apache.org/jira/browse/FELIX-1889
Project: Felix
Issue Type: Task
Components: Gogo
Reporter:
+1
Future releases should probably depend on the official OSGi JARs, not
our deprecated JARs.
I also noticed some of the used vs. includes (e.g., commands launcher)
in the NOTICE file were not completely accurate, but apparently this is
unnecessary anyway...we still need to finalize how we a
The karaf client hangs if the authentication fails
--
Key: FELIX-1888
URL: https://issues.apache.org/jira/browse/FELIX-1888
Project: Felix
Issue Type: Bug
Components: Karaf
The stop script can't be used if the user or password has been changed
--
Key: FELIX-1887
URL: https://issues.apache.org/jira/browse/FELIX-1887
Project: Felix
Issue Type: Bu
On Nov 23, 2009, at 15:37 , Marcel Offermans wrote:
>> Did you update gpg to include my signing key ?
That was it, tnx!
+1
Btw, a bit more documentation for people to get started with gogo at
http://felix.apache.org/site/apache-felix-gogo.html would be helpful!
Greetings, Marcel
Hello Guillaume,
On Nov 23, 2009, at 14:23 , Guillaume Nodet wrote:
> Everything works on my side. Did you update gpg to include my signing
> key ? That would certainly explain the fact that all gpg signatures
> are wrong ...
I did not update anything, just ran the script, so probably that's w
I'm using 2.2 for this very reason and I uninstalled my 2.1 version a
long time ago to avoid such problems.
On Mon, Nov 23, 2009 at 14:18, Toni Menzel wrote:
> Guilaume, what maven do you use to produce+deploy the artifacts ? Just
> currious because gpg problems have been known with versions lik
Everything works on my side. Did you update gpg to include my signing
key ? That would certainly explain the fact that all gpg signatures
are wrong ...
On Mon, Nov 23, 2009 at 14:03, Marcel Offermans
wrote:
> On Nov 23, 2009, at 13:50 , Guillaume Nodet wrote:
>
>> I think we're missing q fez bi
Guilaume, what maven do you use to produce+deploy the artifacts ? Just
currious because gpg problems have been known with versions like 2.1.x.
using a mallicious gpg plugin. Just currious.
On Mon, Nov 23, 2009 at 2:03 PM, Marcel Offermans <
marcel.offerm...@luminis.nl> wrote:
> On Nov 23, 2009, a
On Nov 23, 2009, at 13:50 , Guillaume Nodet wrote:
> I think we're missing q fez binding votes for this release of gogo ...
> On Tue, Nov 17, 2009 at 14:16, Guillaume Nodet wrote:
>>
>> Usage:
>> sh check_staged_release.sh 005 /tmp/felix-staging
I downloaded and ran this script. Is it suppose
+1
On Tue, Nov 17, 2009 at 21:30, Sten Roger Sandvik wrote:
> Hi,
>
> This is a vote for releasing Felix Http Service 2.0.4.
>
> We solved 7 issues in this release:
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12314280
>
> There is still outstanding issues:
> https://issues.apache.
I think we're missing q fez binding votes for this release of gogo ...
On Tue, Nov 17, 2009 at 14:16, Guillaume Nodet wrote:
> I've uploaded a release candidate for Gogo 0.2.2 which solves the
> following issues:
> http://issues.apache.org/jira/browse/FELIX-1671
> http://issues.apache.org/jira/
On Nov 23, 2009, at 11:00 , Toni Menzel wrote:
> On Mon, Nov 23, 2009 at 10:42 AM, Felix Meschberger wrote:
>> Point is that this is roughly the order of phases:
>>
>> process resources
>> compile
>> unit tests
>> package
>> integration-test
>> install
>> deploy
>>
>> So, the integration-
[
https://issues.apache.org/jira/browse/FELIX-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781362#action_12781362
]
Bertrand Delacretaz commented on FELIX-1886:
Thanks, makes perfect sense and th
[
https://issues.apache.org/jira/browse/FELIX-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch closed FELIX-1886.
---
Resolution: Not A Problem
Closing as the bundleplugin now follows the rules documented at
ht
[
https://issues.apache.org/jira/browse/FELIX-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781360#action_12781360
]
Stuart McCulloch commented on FELIX-1886:
-
The bundle symbolic name was always mean
Bundle-SymbolicName generated with maven-bundle-plugin 2.0.0 is not the same as
with 1.4.3
--
Key: FELIX-1886
URL: https://issues.apache.org/jira/browse/FELIX-1886
On Mon, Nov 23, 2009 at 10:42 AM, Felix Meschberger wrote:
> Hi,
>
> Toni Menzel schrieb:
> > On Mon, Nov 23, 2009 at 10:29 AM, Felix Meschberger >wrote:
> >
> >> Hi,
> >>
> >> Toni Menzel schrieb:
> >>> This is actually "home made" by placing integration tests in the
> >> component
> >>> under t
[
https://issues.apache.org/jira/browse/FELIX-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-1530:
Assignee: Felix Meschberger
> Extend the SCR introspection API to reflect the new D
Hi,
Toni Menzel schrieb:
> On Mon, Nov 23, 2009 at 10:29 AM, Felix Meschberger wrote:
>
>> Hi,
>>
>> Toni Menzel schrieb:
>>> This is actually "home made" by placing integration tests in the
>> component
>>> under test.
>>> This way you create a chicken egg problem. The tests (executed before
>>
Hi,
Gerry Woods schrieb:
> So it seems that we are the only ones facing this problem, although I have
> to believe that the Felix Web Console will suffer from it too if it is
> installed alongside FileInstall. I don't know my way around the Web console
> code very well, but I just has a quick loo
On Mon, Nov 23, 2009 at 10:29 AM, Felix Meschberger wrote:
> Hi,
>
> Toni Menzel schrieb:
> > This is actually "home made" by placing integration tests in the
> component
> > under test.
> > This way you create a chicken egg problem. The tests (executed before
> bundle
> > is being packaged, see m
Hi,
Toni Menzel schrieb:
> This is actually "home made" by placing integration tests in the component
> under test.
> This way you create a chicken egg problem. The tests (executed before bundle
> is being packaged, see maven lifecycle) grabs any older version of the
> component it finds (matching
44 matches
Mail list logo
