[jira] [Updated] (FELIX-3466) Pojoization.directoryManipulation() does not take MANIFEST file location into account.

2012-04-18 Thread Updated

 [ 
https://issues.apache.org/jira/browse/FELIX-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Göktürk Gezer updated FELIX-3466:
-

Fix Version/s: ipojo-manipulator-1.8.6
   Labels: ipojo ipojo-manipulator  (was: ipojo-manipulator)
Affects Version/s: ipojo-manipulator-1.8.4

> Pojoization.directoryManipulation() does not take MANIFEST file location into 
> account.
> --
>
> Key: FELIX-3466
> URL: https://issues.apache.org/jira/browse/FELIX-3466
> Project: Felix
>  Issue Type: Bug
>  Components: iPOJO
>Affects Versions: ipojo-manipulator-1.8.4
>Reporter: Göktürk Gezer
>  Labels: ipojo, ipojo-manipulator
> Fix For: ipojo-manipulator-1.8.6
>
> Attachments: org.apache.felix.ipojo.manipulator.patch
>
>
> Pojoization.directoryManipulation(File dir,File metadata,File manifest) 
> method does not use the given manifest file location while saving it. Instead 
> it uses a hard-coded ${project.output}/target/classes/META-INF/MANIFEST.MF 
> path.
> It should be modified to write back its changes to the given file when given 
> file is not null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (FELIX-3451) "instance.name" attribute not recognized

2012-04-18 Thread Fabio Lattario Fonseca (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/FELIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256489#comment-13256489
 ] 

Fabio Lattario Fonseca commented on FELIX-3451:
---

Clement,

Still not working... :-( Something is very wrong here. I don't know what is
preventing me to have the same result you had... I have followed the exact
steps below:

1. Downloaded the latest trunk and got the message:
Checked out revision 1327457.

2. mvn clean install at trunk/ipojo directory

3. Created a clean instance of the framework,
downloading org.apache.felix.main-4.0.2.jar, org.apache.felix.shell-1.4.3.jar
and org.apache.felix.shell.tui-1.4.1.jar from the
http://felix.apache.org/site/downloads.cgi site.

4. Started the framework and installed the bundles below:
. trunk/ipojo/core/target/org.apache.felix.ipojo-1.9.0-SNAPSHOT.jar
. 
trunk/ipojo/composite/target/org.apache.felix.ipojo.composite-1.9.0-SNAPSHOT.jar
. trunk/ipojo/arch/target/org.apache.felix.ipojo.arch-1.7.0-SNAPSHOT.jar
. trunk/ipojo/api/target/org.apache.felix.ipojo.api-1.7.0-SNAPSHOT.jar

5. Started all the bundles, having the following state:

-> ps
START LEVEL 1
   ID   State Level  Name
[   0] [Active ] [0] System Bundle (4.0.2)
[   1] [Active ] [1] Apache Felix Shell Service (1.4.3)
[   2] [Active ] [1] Apache Felix Shell TUI (1.4.1)
[   3] [Active ] [1] Apache Felix iPOJO (1.9.0.SNAPSHOT)
[   4] [Active ] [1] Apache Felix iPOJO Composite (1.9.0.SNAPSHOT)
[   5] [Active ] [1] Apache Felix iPOJO Arch Command
(1.7.0.SNAPSHOT)
[   6] [Active ] [1] Apache Felix iPOJO API (1.7.0.SNAPSHOT)

6. Then, I have installed my Comanche bundles and started the bundle with
my composite compiled with with the "bad_pom.xml" that I sent in a previous
message.

7. Got the same f... error:

WARNING] comanche.backend : The 'name' (RequestAnalyzer) attribute, used as
the instance name, is deprecated, please use the 'instance.name' attribute
[WARNING] ErrorRH : The 'name' (RequestAnalyzer) attribute, used as the
instance name, is deprecated, please use the 'instance.name' attribute
[WARNING] FileRH : The 'name' (RequestAnalyzer) attribute, used as the
instance name, is deprecated, please use the 'instance.name' attribute
[ERROR] FileRH : The configuration is not acceptable : Name already used
[ERROR] comanche.requestHandler : A factory is available for the
configuration but the configuration is not acceptable
org.apache.felix.ipojo.UnacceptableConfiguration: FileRH : Name already
used : RequestAnalyzer
at
org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:290)
at
org.apache.felix.ipojo.composite.FactoryProxy.createComponentInstance(FactoryProxy.java:87)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.__createInstance(InstanceHandler.java:160)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.createInstance(InstanceHandler.java)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.__bindFactory(InstanceHandler.java:184)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.bindFactory(InstanceHandler.java)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.felix.ipojo.util.Callback.call(Callback.java:260)
at
org.apache.felix.ipojo.handlers.dependency.DependencyCallback.callOnInstance(DependencyCallback.java:309)
at
org.apache.felix.ipojo.handlers.dependency.Dependency.invokeCallback(Dependency.java:315)
at
org.apache.felix.ipojo.handlers.dependency.Dependency.onObjectCreation(Dependency.java:280)
at
org.apache.felix.ipojo.handlers.dependency.DependencyHandler.__onCreation(DependencyHandler.java:643)
at
org.apache.felix.ipojo.handlers.dependency.DependencyHandler.onCreation(DependencyHandler.java)
at org.apache.felix.ipojo.HandlerManager.start(HandlerManager.java:132)
at
org.apache.felix.ipojo.composite.CompositeManager.start(CompositeManager.java:355)
at
org.apache.felix.ipojo.composite.CompositeFactory.createInstance(CompositeFactory.java:147)
at
org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:301)
at
org.apache.felix.ipojo.composite.FactoryProxy.createComponentInstance(FactoryProxy.java:87)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.__createInstance(InstanceHandler.java:160)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.createInstance(InstanceHandler.java)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.__bindFactory(InstanceHandler.java:184)
at
org.apache.felix.ipojo.composite.instance.InstanceHandler.bindFactory(InstanceHandler.java)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Meth

Re: [VOTE] Release FileInstall 3.2.2

2012-04-18 Thread Jamie G.
+1 (non binding)

Cheers,
Jamie

2012/4/18 Jean-Baptiste Onofré :
> +1 (non binding)
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com


Re: [VOTE] Release FileInstall 3.2.2

2012-04-18 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


[jira] [Commented] (FELIX-3468) Restarting the framework from the web console does not work

2012-04-18 Thread Felix Meschberger (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/FELIX-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256280#comment-13256280
 ] 

Felix Meschberger commented on FELIX-3468:
--

Yes, the only issue with the Web Console is, that it may not be appropriate to 
have such functionality. Other than that, this is what's being done:

   Restart: BundleContext.getBundle(0).update();
   Shutdown: BundleContext.getBundle(0).stop();

In the Sling Launcher we overwrite the Felix class to implement our own update 
method and to restart the framework in a fresh class loader. This works 
perfectly but has the drawback of not being portable

> Restarting the framework from the web console does not work
> ---
>
> Key: FELIX-3468
> URL: https://issues.apache.org/jira/browse/FELIX-3468
> Project: Felix
>  Issue Type: Bug
>  Components: Karaf
>Affects Versions: webconsole-3.1.8
>Reporter: Hugh Rodgers
>
> I am running Karaf v2.2.5 (which uses felix web console v3.1.8) on Windows 7. 
> Once I start karaf (using the karaf.bat script), I go to the web console and 
> click on the System Information tab. I then click the Restart button and Ok 
> in its popup. I see in the Karaf command line console that Karaf shuts down 
> and restarts. When I click in the command line console and press return (to 
> get a prompt), the command line console window disappears and Karaf shuts 
> down.
> When I try this with Karaf v2.2.5 and only install the webconsole feature, 
> when I click Restart, the Karaf command line console disappears and Karaf 
> shuts down (never comes back up).
> I have reproduced this issue with Karaf v2.2.5 and only loading the following 
> bundles:
> 
> 
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saxon/${saxon.bundle.plugin}
>   
>  
>   
> mvn:commons-io/commons-io/${commons-io.version}
>   
>  
>   
> mvn:org.slf4j/slf4j-ext/${org.slf4j-ext.version}
>   
>  
>   
>  start-level='70'>mvn:org.ops4j.base/ops4j-base-lang/${org.ops4j-base-lang}
>   
>  
>   
>   ops4j-base-lang
>  start-level='70'>mvn:org.ops4j.pax.swissbox/pax-swissbox-lifecycle/${org.ops4j.pax.swissbox.version}
>  start-level='70'>mvn:org.ops4j.pax.swissbox/pax-swissbox-optional-jcl/${org.ops4j.pax.swissbox.version}
>  start-level='70'>mvn:org.ops4j.pax.swissbox/pax-swissbox-extender/${org.ops4j.pax.swissbox.version}
>   
> The dev:restart command works from the Karaf command line console, and it 
> works if I issue it from a second terminal window using the Karaf client.bat 
> script.
> At this point, I have yet to see the Restart button in the web console work 
> properly.
> Thanks. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[VOTE] Release FileInstall 3.2.2

2012-04-18 Thread Guillaume Nodet
We solved 18 issues in this
release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12320555&styleName=Html&projectId=12310100
There are still 9 outstanding
issues:https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22File+Install%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hideThree
of those are bugs and will have to be fixed in a following up
maintenance release.

Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-069/
You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
Usage:
sh check_staged_release.sh 069 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for at least 72 hours.


-- 

Guillaume Nodet

Blog: http://gnodet.blogspot.com/

FuseSource, Integration everywhere
http://fusesource.com