Re: bundleplugin release

I already called for it On 7/6/07, Karl Pauls <[EMAIL PROTECTED]> wrote: Right, we need to release the parent pom - but, we still need to look into how we want to do this. Can you call the vote for the maven-osgi library in parallel or do you need us to release the parent pom first? regards, K

Re: bundleplugin release

Right, we need to release the parent pom - but, we still need to look into how we want to do this. Can you call the vote for the maven-osgi library in parallel or do you need us to release the parent pom first? regards, Karl On 7/7/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: you'd need to re

Re: bundleplugin release

you'd need to resolve all snapshot dependencies first: release the parent pom and I'll call a vote for maven-osgi library On 7/6/07, Karl Pauls <[EMAIL PROTECTED]> wrote: Hi all, as discussed previously, Rick and I have been working on getting the bundleplugin into shape for the 1.0.0 release.

bundleplugin release

Hi all, as discussed previously, Rick and I have been working on getting the bundleplugin into shape for the 1.0.0 release. I just resolved the last remaining issue and deployed the new version to the snapshot repo. Furthermore, I create a release candidate under releases and added the current do

Re: BundleContextImpl - not serializable ?

Probably because you cannot abitrarily deserialize a BundleContext object. A BundleContext maintains a bundle's context within a running OSGi framework instance. Since that context is stateful and includes things like the set of services registered and used by a bundle, there is no way to arbit

BundleContextImpl - not serializable ?

Is there a reason that org.apache.felix.framework.BundleContextImpl does not implement serializable? I understand that the context should be private to the activator, but other then that is there some other reason for it not being serializable? I have the following scenario: I am embedding Feli

[jira] Commented: (FELIX-322) Registering a PersistenceManager service causes a ClassCastException

[ https://issues.apache.org/jira/browse/FELIX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510707 ] Felix Meschberger commented on FELIX-322: - There were actually more issues with ConfigurationManager and Compa

[jira] Work stopped: (FELIX-322) Registering a PersistenceManager service causes a ClassCastException

[ https://issues.apache.org/jira/browse/FELIX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-322 stopped by Felix Meschberger. > Registering a PersistenceManager service causes a ClassCastException > --

[jira] Closed: (FELIX-294) commons-validator 1.3.1 wrapping

[ https://issues.apache.org/jira/browse/FELIX-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-294. -- Resolution: Fixed Fix Version/s: 1.0.0 Applied your patch - Thanks! > commons-validator

[jira] Work stopped: (FELIX-294) commons-validator 1.3.1 wrapping

[ https://issues.apache.org/jira/browse/FELIX-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-294 stopped by Carsten Ziegeler. > commons-validator 1.3.1 wrapping > - > > Key: FELIX-294 >

[jira] Work started: (FELIX-294) commons-validator 1.3.1 wrapping

[ https://issues.apache.org/jira/browse/FELIX-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-294 started by Carsten Ziegeler. > commons-validator 1.3.1 wrapping > - > > Key: FELIX-294 >

[jira] Assigned: (FELIX-294) commons-validator 1.3.1 wrapping

[ https://issues.apache.org/jira/browse/FELIX-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-294: -- Assignee: Carsten Ziegeler > commons-validator 1.3.1 wrapping > ---

[jira] Created: (FELIX-322) Registering a PersistenceManager service causes a ClassCastException

Registering a PersistenceManager service causes a ClassCastException Key: FELIX-322 URL: https://issues.apache.org/jira/browse/FELIX-322 Project: Felix Issue Type: Bug

[jira] Work started: (FELIX-322) Registering a PersistenceManager service causes a ClassCastException

[ https://issues.apache.org/jira/browse/FELIX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-322 started by Felix Meschberger. > Registering a PersistenceManager service causes a ClassCastException > --

[jira] Assigned: (FELIX-322) Registering a PersistenceManager service causes a ClassCastException

[ https://issues.apache.org/jira/browse/FELIX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-322: --- Assignee: Felix Meschberger > Registering a PersistenceManager service causes a ClassC

Re: How to deal with releasing the parent POM file?

Richard S. Hall wrote: > Karl and I were discussing the maven-bundle-plugin release and a > question came up. > > Ultimately, our sub-projects all use the parent Felix pom file, but > unlike most projects our modules do not comprise a single application > that gets released at once. Instead, each

Re: How to deal with releasing the parent POM file?

Is that correct? Is there a better way? Hello, I think you may need a more "parent" pom than current Felix parent pom. If you look at logical Maven structure itself, you can see : org.apache.maven.maven-parent +-- org.apache.maven.maven + maven components ... +-- org.apache.maven.