I'll recut a release to fix the legal stuff.
On Mon, Jan 31, 2011 at 17:45, Guillaume Nodet wrote:
> I would like to call a vote on the maven-bundle-plugin 2.3.0 release:
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-020/
>
> Changelog:
> https://is
File Install does not support empty configuration when no configuration already
exists
--
Key: FELIX-2818
URL: https://issues.apache.org/jira/browse/FELIX-2818
Projec
I would like to call another vote on the maven-bundle-plugin 2.3.0 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-025/
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8d589633a054278ec7f36db6fcb02560518a1b8f&version=12
+1
I've updated the copyright in NOTICE and DEPENDENCIES files.
On Tue, Feb 1, 2011 at 20:28, Richard S. Hall wrote:
> On 2/1/11 13:58, Carsten Ziegeler wrote:
>>
>> Richard S. Hall wrote
>>>
>>> The copyright year wasn't updated...I can't remember, do we consider
>>> this a big deal or not?
>>
[
https://issues.apache.org/jira/browse/FELIX-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-2818.
--
Resolution: Fixed
Fixed in trunk.
> File Install does not support empty configuration
[
https://issues.apache.org/jira/browse/FELIX-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier updated FELIX-2818:
-
Fix Version/s: fileinstall-3.1.10
Just update the fix version.
> File Install does not s
+1
Regards
JB
On 02/02/2011 10:41 AM, Guillaume Nodet wrote:
I would like to call another vote on the maven-bundle-plugin 2.3.0 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-025/
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.
Hi,
-1
Sorry to veto this vote. AFAICT you cannot try again with the same
version number.
Regards
Felix
Am Mittwoch, den 02.02.2011, 09:41 + schrieb Guillaume Nodet:
> I would like to call another vote on the maven-bundle-plugin 2.3.0 release:
>
> Staging repositories:
> https://repositor
Hi
-1
Sorry to veto the vote. AFAICT you cannot retry with the same version
number.
Regards
Felix
Am Montag, den 31.01.2011, 08:34 + schrieb Guillaume Nodet:
> Same as before, but the release actually contains both fixes and an
> updated changelog
>
> This release fixes two issues
> https
Over the past two years, I've been doing several releases in Felix and
i've re-rolled some with the same version without any problems.
I don't see any mention about not reusing the same number twice in the
release process:
http://felix.apache.org/site/release-management-nexus.html
What's the driver
Hi,
My vetoes (actually there is no veto in a release vote since this is a
majority vote) are grounded on a message Roy Fielding once sent to the
Jackrabbit list [1]:
> The problem with doing all of our laundry in public is that the public
> often download our unreleased packages even when we tel
On Wed, Feb 2, 2011 at 14:18, Felix Meschberger wrote:
> Hi,
>
> My vetoes (actually there is no veto in a release vote since this is a
> majority vote)
I know there's no vetoes in releases, but the goal is usually to
gather a consensus.
The fact you voted -1 puts a lot of pressure on me if I wan
Last, remember each PMC decides on its own rules to govern its project.
So the fact Roy sent an email on Jackrabbit doesn't make it an
official policy for the ASF (and the ASF itself doesn't care about
such technical details).
I'll re-roll those releases, but I'd like things to be agreed upon
*and
I cancel this release and will re-spin a 2.3.2 asap.
On Wed, Feb 2, 2011 at 11:19, Felix Meschberger wrote:
> Hi,
>
> -1
>
> Sorry to veto this vote. AFAICT you cannot try again with the same
> version number.
>
> Regards
> Felix
>
> Am Mittwoch, den 02.02.2011, 09:41 + schrieb Guillaume Node
I cancel this release and will re-spin a 3.1.10 now.
On Wed, Feb 2, 2011 at 11:21, Felix Meschberger wrote:
> Hi
>
> -1
>
> Sorry to veto the vote. AFAICT you cannot retry with the same version
> number.
>
> Regards
> Felix
>
> Am Montag, den 31.01.2011, 08:34 + schrieb Guillaume Nodet:
>> Sa
Hi,
Does this release will contain the fixed I committed this morning
(FELIX-2818) ?
Regards,
Clement
On 02.02.11 15:06, "Guillaume Nodet" wrote:
>I cancel this release and will re-spin a 3.1.10 now.
>
>On Wed, Feb 2, 2011 at 11:21, Felix Meschberger
>wrote:
>> Hi
>>
>> -1
>>
>> Sorry to vet
Vote on fileinstall .3.1.10
This release fixes three issues
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8159ff149eb3d70fdca9490b559e5269f0ea79d8&version=12316134&styleName=Text&projectId=12310100&Create=Create
* [FELIX-2798] - ArtifactListener services are not ordered
acco
Yes.
On Wed, Feb 2, 2011 at 15:20, Clement Escoffier
wrote:
> Hi,
>
> Does this release will contain the fixed I committed this morning
> (FELIX-2818) ?
>
> Regards,
>
> Clement
>
> On 02.02.11 15:06, "Guillaume Nodet" wrote:
>
>>I cancel this release and will re-spin a 3.1.10 now.
>>
>>On Wed,
Hi,
Am Mittwoch, den 02.02.2011, 14:01 + schrieb Guillaume Nodet:
> The fact you voted -1 puts a lot of pressure on me if I want to go to
> the majority in order to have those released ;-)
Probably yes. So I have to apologize to have rushed in with a
would-be-veto. I should rather only have r
I would like to call another vote on the maven-bundle-plugin 2.3.2 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-027/
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8159ff149eb3d70fdca9490b559e5269f0ea79d8&version=123
+1
Regards
Felix
Am Dienstag, den 01.02.2011, 08:16 + schrieb Guillaume Nodet:
> This release fixes several issues
> * [FELIX-2713] - Problem in HtmlConfigurationWriter
> * [FELIX-2729] - Webconsole - Configuration fails to print
> configuration for bundles without MetatypeService co
I think originally we were more strict on changing the version number
after failed votes, but we've since backed off. The reason for not being
as strict, if I recall, is that people can still download the failed
version while it's available with the signatures and put them up on some
web site a
+1
Regards
Felix
Am Mittwoch, den 02.02.2011, 14:37 + schrieb Guillaume Nodet:
> Vote on fileinstall .3.1.10
>
> This release fixes three issues
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8159ff149eb3d70fdca9490b559e5269f0ea79d8&version=12316134&styleName=Text&proje
+1
Regards
JB
On 02/02/2011 03:37 PM, Guillaume Nodet wrote:
Vote on fileinstall .3.1.10
This release fixes three issues
https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8159ff149eb3d70fdca9490b559e5269f0ea79d8&version=12316134&styleName=Text&projectId=12310100&Create=Create
Hi,
Am Mittwoch, den 02.02.2011, 14:42 + schrieb Richard S. Hall:
> I think originally we were more strict on changing the version number
> after failed votes, but we've since backed off. The reason for not being
> as strict, if I recall, is that people can still download the failed
> vers
I haven't fully looked at the release yet, but I was looking in my trunk
build...
The NOTICE file is for required notices for included software. It lists
(besides Apache) OSGi and aQute. The DEPENDENCIES files says we include
these too. But I don't see them in the generated JAR file. Are these
You're way too quick on your releases...I don't even get a chance to
look... :-)
On 2/2/11 9:39, Guillaume Nodet wrote:
I would like to call another vote on the maven-bundle-plugin 2.3.2 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-027/
Chan
I think since issue has been solved a while ago by mandating all
artifacts have pgp / md5 signatures to identify if those are valid or
not. That's the whole (and only afaik) point of those additional
required files.
On Wed, Feb 2, 2011 at 15:49, Felix Meschberger wrote:
> Hi,
>
> Am Mittwoch,
On 2/2/11 9:49, Felix Meschberger wrote:
Hi,
Am Mittwoch, den 02.02.2011, 14:42 + schrieb Richard S. Hall:
I think originally we were more strict on changing the version number
after failed votes, but we've since backed off. The reason for not being
as strict, if I recall, is that people ca
They should not have valid signatures. Signatures are supposed to be
always provided by the ASF infrastructure, else anybody can claim
being a valid release.
On Wed, Feb 2, 2011 at 16:00, Richard S. Hall wrote:
> On 2/2/11 9:49, Felix Meschberger wrote:
>>
>> Hi,
>>
>> Am Mittwoch, den 02.02.201
I think they're left over from when we used to embed BND. I can't
find any source file that doesn't seem to come from the ASF. Do you
want me to recut a 2.3.4 ?
On Wed, Feb 2, 2011 at 15:55, Richard S. Hall wrote:
> I haven't fully looked at the release yet, but I was looking in my trunk
> buil
On 2/2/11 10:07, Guillaume Nodet wrote:
I think they're left over from when we used to embed BND. I can't
find any source file that doesn't seem to come from the ASF. Do you
want me to recut a 2.3.4 ?
Probably, since you are so good at it. :-)
-> richard
On Wed, Feb 2, 2011 at 15:55, Richa
On 2/2/11 10:09, Guillaume Nodet wrote:
They should not have valid signatures. Signatures are supposed to be
always provided by the ASF infrastructure, else anybody can claim
being a valid release.
Depends on how you want to define "valid". The signatures are valid, you
will be able to verify
Hi All
I'm using an embedded instance of Felix, and trying to post a simple event to
the EventAdmin service. My code is trivial:
ServiceReference ref = context.getServiceReference(EventAdmin.class.getName());
if(ref != null) {
EventAdmin ea = (EventAdmin) context.getService(ref);
if(ea != nu
[
https://issues.apache.org/jira/browse/FELIX-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989688#comment-12989688
]
Hiram Chirino commented on FELIX-2817:
--
Not sure if 2.3 is going to pass the vote or
Is this exception happening inside felix/eventadmin code or inside
your code? Could you maybe provide the stacktrace of the exception?
regards,
Karl
On Wed, Feb 2, 2011 at 5:04 PM, Jackson, Bruce wrote:
> Hi All
>
> I'm using an embedded instance of Felix, and trying to post a simple event to
Its from my code: all of the other lines of the stack trace are in my code
and not the framework/event admin service.
On 02/02/2011 16:11, "Karl Pauls" wrote:
>Is this exception happening inside felix/eventadmin code or inside
>your code? Could you maybe provide the stacktrace of the exception
I've added the following code to see what I'm actually getting back from
the service lookup as below:
Object o = context.getService(ref);;
Class c = o.getClass();
while(c != null) {
System.err.println(">> ea service: " + c.getName());
c = c.getSuperclass();
}
I get the following
Ok, but isn't it then just the case that you have the eventadmin
classes on the outside as well as on the inside of the framework? That
would explain the classcast exception as you are trying to assign the
eventadmin service from the inside of the framework to your variable
on the outside.
I guess
I cancel this release to fix the NOTICE / DEPENDENCIES as we don't
include bnd anymore.
On Wed, Feb 2, 2011 at 15:39, Guillaume Nodet wrote:
> I would like to call another vote on the maven-bundle-plugin 2.3.2 release:
>
> Staging repositories:
> https://repository.apache.org/content/repositories
[
https://issues.apache.org/jira/browse/FELIX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989711#comment-12989711
]
Alasdair Nottingham commented on FELIX-2692:
Hi,
I believe this has been fixe
I would like to call another vote on the maven-bundle-plugin 2.3.4 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-029/
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100&version=12316061
You can use this UNIX scr
packageinfo files in src/main/java are ignored
--
Key: FELIX-2819
URL: https://issues.apache.org/jira/browse/FELIX-2819
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Provide a default value when using <_wab/>
--
Key: FELIX-2820
URL: https://issues.apache.org/jira/browse/FELIX-2820
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Hi,
This looks like a classic case of ClassCastException on a
class/interface that was loaded using two different class loaders. The
interface of EventAdmin that you are referencing was loaded using a
different class loader than the class loader that was used by the
framework.
Regards,
Lucas
+1
Regards
JB
On 02/02/2011 06:09 PM, Guillaume Nodet wrote:
I would like to call another vote on the maven-bundle-plugin 2.3.4 release:
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-029/
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.js
+1
Thanks for the hard work on this release Guillaume.
Regards,
Alex
On Wed, Feb 2, 2011 at 8:40 PM, Jean-Baptiste Onofré wrote:
> +1
>
> Regards
> JB
>
> On 02/02/2011 06:09 PM, Guillaume Nodet wrote:
>>
>> I would like to call another vote on the maven-bundle-plugin 2.3.4
>> release:
>>
>> St
+1
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
On Wed, Feb 2, 2011 at 12:09 PM, Guillaume Nodet wrote:
> I would like to call another vote on the maven-bundle-plugin 2.3.4 release:
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-029/
>
+1 (non binding)
Thanks Guillaume!
On Wed, Feb 2, 2011 at 6:47 PM, Alex Karasulu wrote:
> +1
>
> Thanks for the hard work on this release Guillaume.
>
> Regards,
> Alex
>
> On Wed, Feb 2, 2011 at 8:40 PM, Jean-Baptiste Onofré
> wrote:
> > +1
> >
> > Regards
> > JB
> >
> > On 02/02/2011 06:09 P
[
https://issues.apache.org/jira/browse/FELIX-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989749#comment-12989749
]
Simon Chemouil commented on FELIX-2819:
---
This would be nice indeed.
Just for the re
I just had this exception while testing with the latest 3.0.8
java.lang.NullPointerException
at
org.apache.felix.framework.resolver.ResolverImpl.permutateIfNeeded(ResolverImpl.java:1140)[org.apache.felix.framework-3.0.8.jar:]
at
org.apache.felix.framework.resolver.ResolverImpl.ch
I don't think anything changed in that area for 3.0.8, but you could try
it on 3.0.7 to see.
If it is reproducible, then open a bug and tell me how and I'll look
into it.
-> richard
On 2/2/11 16:30, Guillaume Nodet wrote:
I just had this exception while testing with the latest 3.0.8
java.l
52 matches
Mail list logo
