Raymond Auge | 26 Mar 19:34 2015

equinox console optionality of available commands

Would people object to a change in equinox.console which would optionally allow for specific commands not to be published?

For instance, when running equinox embedded we're controlling the lifecycle of the framework along with the lifecycle of the embedding application.

I would like to not expose the shutdown related commands which are there.


exit, close, shutdown are commands I'd like to be able to not provide.

--
Raymond Augé ( <at> rotty3000)
Senior Software Architect Liferay, Inc. ( <at> Liferay)
Board Member & EEG Co-Chair, OSGi Alliance ( <at> OSGiAlliance)
<div><div dir="ltr">Would people object to a change in equinox.console which would optionally allow for specific commands not to be published?<br clear="all"><div><br></div>
<div>For instance, when running equinox embedded we're controlling the lifecycle of the framework along with the lifecycle of the embedding application.<br><br>
</div>
<div>I would like to not expose the shutdown related commands which are there.<br><br><br>
</div>
<div>exit, close, shutdown are commands I'd like to be able to not provide.<br><br>
</div>
<div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">
<span><a href="http://www.liferay.com/web/raymond.auge/profile" target="_blank">Raymond Aug&eacute;</a>&nbsp;( <at> rotty3000)</span><div>
<span>Senior Software Architect&nbsp;</span><a href="http://www.liferay.com" target="_blank">Liferay, Inc.</a><span>&nbsp;( <at> Liferay)</span>
</div>Board Member &amp; EEG Co-Chair, <a href="http://osgi.org" target="_blank">OSGi Alliance</a> ( <at> OSGiAlliance)</div></div></div></div>
</div>
</div></div>
Marc-André Laperle | 18 Mar 19:49 2015
Picon

Gerrit job failure

Hi,

The rt.equinox.bundles-Gerrit Hudson job is failing because of the Maven version in the job configuration is too low (3.1.1 required versus 3.0.5). Can anyone with permissions change it to apache-maven-latest?

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message:
Detected Maven Version: 3.0.5 is not in the allowed range 3.1.1.

https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/configure
Example failure:
https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/87/console

Thank you!
Marc-Andre Laperle
<div>
<div>Hi,<br><br>
The rt.equinox.bundles-Gerrit Hudson job is failing because of the Maven version in the job configuration is too low (3.1.1 required versus 3.0.5). Can anyone with permissions change it to apache-maven-latest?<br><br>
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message:<br>
Detected Maven Version: 3.0.5 is not in the allowed range 3.1.1.<br><br><a href="https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/configure" target="_blank">https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/configure</a><br>
Example failure:<br><a href="https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/87/console" target="_blank">https://hudson.eclipse.org/platform/job/rt.equinox.bundles-Gerrit/87/console</a><br><br>
Thank you!<br>
Marc-Andre Laperle<br>
</div>
</div>
Mikael Barbero | 10 Mar 14:51 2015

OS X native launcher build

Hi,

While currently trying to build natives on the Eclipse FoundationiInfra (see cbi-dev ML for information and https://hudson.eclipse.org/cbi/view/natives/ for builds), I hit an issue with Mac native launchers.

Don't take the green status of https://hudson.eclipse.org/cbi/view/natives/job/cbi-launcher-macosx-x86_64/ for granted. It is actually failing. 

The issue is that features/org.eclipse.equinox.executable.feature/pom.xml starts features/org.eclipse.equinox.executable.feature/library/carbon/build.xml which itself starts features/org.eclipse.equinox.executable.feature/library/carbon/build.sh

build.sh takes arguments about the platform to build but build.xml does not set any.

pom.xml on the other hand defines the variable "native" as a string "ws.os.arch". So I updated build.xml to take these string and split it to be able to run build.sh accordingly. See my patch here https://git.eclipse.org/r/#/c/43538/. With this patch, I am able to properly build native launcher my local OS X with the command "mvn clean verify -P build-individual-bundles -Dnative=cocoa.macosx.x86_64 -f rt.equinox.framework/features/org.eclipse.equinox.executable.feature/pom.xml"

Another issue is with the "mvn clean". It was not triggering the "build.sh clean" in the end, so I update the  features/org.eclipse.equinox.executable.feature/pom.xml for that too (https://git.eclipse.org/r/#/c/43539/1).

Do you agree with my analysis and solution? Thank you for your feedback.

Mikael
<div>Hi,<div class=""><br class=""></div>
<div class="">While currently trying to build natives on the Eclipse FoundationiInfra (see cbi-dev ML for information and&nbsp;<a href="https://hudson.eclipse.org/cbi/view/natives/" class="">https://hudson.eclipse.org/cbi/view/natives/</a>&nbsp;for builds), I hit an issue with Mac native launchers.</div>
<div class=""><br class=""></div>
<div class="">Don't take the green status of&nbsp;<a href="https://hudson.eclipse.org/cbi/view/natives/job/cbi-launcher-macosx-x86_64/" class="">https://hudson.eclipse.org/cbi/view/natives/job/cbi-launcher-macosx-x86_64/</a>&nbsp;for granted. It is actually failing.&nbsp;</div>
<div class=""><br class=""></div>
<div class="">The issue is that&nbsp;features/org.eclipse.equinox.executable.feature/pom.xml starts features/org.eclipse.equinox.executable.feature/library/carbon/build.xml which itself starts features/org.eclipse.equinox.executable.feature/library/carbon/build.sh</div>
<div class=""><br class=""></div>
<div class="">build.sh takes arguments about the platform to build but build.xml does not set any.</div>
<div class=""><br class=""></div>
<div class="">pom.xml on the other hand defines the variable "native" as a string "ws.os.arch". So I updated build.xml to take these string and split it to be able to run build.sh accordingly. See my patch here&nbsp;<a href="https://git.eclipse.org/r/#/c/43538/" class="">https://git.eclipse.org/r/#/c/43538/</a>. With this patch, I am able to properly build native launcher my local OS X with the command "mvn clean verify -P build-individual-bundles -Dnative=cocoa.macosx.x86_64 -f rt.equinox.framework/features/org.eclipse.equinox.executable.feature/pom.xml"</div>
<div class=""><br class=""></div>
<div class="">Another issue is with the "mvn clean". It was not triggering the "build.sh clean" in the end, so I update the &nbsp;features/org.eclipse.equinox.executable.feature/pom.xml for that too (<a href="https://git.eclipse.org/r/#/c/43539/1" class="">https://git.eclipse.org/r/#/c/43539/1</a>).</div>
<div class=""><br class=""></div>
<div class="">Do you agree with my analysis and solution? Thank you for your feedback.</div>
<div class=""><br class=""></div>
<div class="">Mikael</div>
</div>
Raghavendra Nilekani | 3 Mar 11:05 2015
Picon

Issues in Eclipse Equinox OSGi v3.10.1

Hello 

I have a java application where we use OSGi equinox v3.4.0 to use and manage different OSGi bundles as part of our application deployment.

Now we have a plan to migrate to OSGi equinox v3.10.1. With this new OSGi container, I see some of the, open source, bundles are not getting resolved even though all the dependant bundles/fragments are available to the container.

Please refer to the below examples for complete details. 

I could start the OSGi container successfully and the 'ss' command (listing all bundles) shows the following result.

osgi> ss
"Framework is launched."

id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.10.1.v20140909-1633
1       ACTIVE      com.springsource.javax.annotation_1.0.0
2       ACTIVE      com.springsource.javax.ejb_3.0.0
3       ACTIVE      com.springsource.javax.el_2.1.0
4       ACTIVE      com.springsource.javax.management.j2ee_1.0.1
5       ACTIVE      com.springsource.javax.persistence_1.0.0
6       ACTIVE      com.springsource.javax.resource_1.5.0
7       ACTIVE      com.springsource.javax.servlet_2.5.0
8       ACTIVE      com.springsource.javax.servlet.jsp_2.1.0
9       INSTALLED   com.springsource.javax.servlet.jsp.jstl_1.1.2
10      ACTIVE      com.springsource.javax.transaction_1.1.0
11      ACTIVE      com.springsource.javax.xml.soap_1.3.0
12      ACTIVE      com.springsource.javax.xml.stream_1.0.1
13      ACTIVE      com.springsource.javax.xml.ws_2.1.1
14      INSTALLED   com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956
15      INSTALLED   com.springsource.org.apache.coyote.springsource_6.0.20.S2-r5956
16      ACTIVE      com.springsource.org.apache.el.springsource_6.0.20.S2-r5956
17      ACTIVE      com.springsource.org.apache.jasper.org.eclipse.jdt_6.0.16
18      INSTALLED   com.springsource.org.apache.jasper.springsource_6.0.20.S2-r5956
19      ACTIVE      com.springsource.org.apache.juli.extras.springsource_6.0.20.S2-r5956
20      ACTIVE      javax.interceptor_1.1.0
21      ACTIVE      javax.jms_1.1.0
22      ACTIVE      javax.mail_1.4.0
23      ACTIVE      javax.xml.rpc_1.1.0
24      ACTIVE      org.apache.felix.gogo.command_0.10.0.v201209301215
25      ACTIVE      org.apache.felix.gogo.runtime_0.10.0.v201209301036
26      ACTIVE      org.apache.felix.gogo.shell_0.10.0.v201212101605
27      INSTALLED   org.apache.jasper.glassfish_2.2.2.v201205150955
28      INSTALLED   org.eclipse.core.runtime_3.10.0.v20140318-2214
29      ACTIVE      org.eclipse.equinox.common_3.6.200.v20130402-1505
30      ACTIVE      org.eclipse.equinox.console_1.1.0.v20140131-1639
31      ACTIVE      org.eclipse.osgi.services_3.4.0.v20140312-2051

You can notice that the bundle  com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956 is just INSTALLED but not started. The bundles com.springsource.org.apache.coyote.springsource_6.0.20.S2-r5956 and com.springsource.org.apache.jasper.springsource_6.0.20.S2-r5956 are fragment bundles and are attached to apache catalina springsource bundle.

When I tried to start the bundle com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956 I get following exception. 

osgi> start 14
gogo: BundleException: Could not resolve module: com.springsource.org.apache.catalina.springsource [14]
  Unresolved requirement: Import-Package: org.apache.tomcat; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
    -> Export-Package: org.apache.tomcat; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.jasper.springsource"; version="6.0.20.S2-r5956"; uses:="javax.servlet"
       com.springsource.org.apache.jasper.springsource [18]
         Unresolved requirement: Import-Package: org.apache.tools.ant; version="[1.7.0,2.0.0)"; resolution:="optional"
         Unresolved requirement: Import-Package: org.apache.tools.ant.taskdefs; version="[1.7.0,2.0.0)"; resolution:="optional"
         Unresolved requirement: Import-Package: org.apache.tools.ant.types; version="[1.7.0,2.0.0)"; resolution:="optional"
         Unresolved requirement: Import-Package: org.apache.tools.ant.util; version="[1.7.0,2.0.0)"; resolution:="optional"
         Unresolved requirement: Fragment-Host: com.springsource.org.apache.catalina.springsource; version="[6.0.20.S2-r5956, 6.0.20.S2-r5956]"
  Unresolved requirement: Import-Package: org.apache.coyote; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
    -> Export-Package: org.apache.coyote; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.tomcat.util.buf,org.apache.tomcat.util.http,org.apache.tomcat.util.net"
       com.springsource.org.apache.coyote.springsource [15]
         Unresolved requirement: Fragment-Host: com.springsource.org.apache.catalina.springsource; bundle-version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
           -> Bundle-SymbolicName: com.springsource.org.apache.catalina.springsource; bundle-version="6.0.20.S2-r5956"
         Unresolved requirement: Import-Package: org.apache.catalina; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
           -> Export-Package: org.apache.catalina; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.catalina.springsource"; version="6.0.20.S2-r5956"; uses:="javax.naming.directory,javax.servlet,javax.servlet.http,org.apache.catalina.connector,org.apache.catalina.deploy,org.apache.catalina.util,org.apache.juli.logging,org.apache.tomcat,org.apache.tomcat.util.http.mapper"
         Unresolved requirement: Import-Package: org.apache.catalina.deploy; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
           -> Export-Package: org.apache.catalina.deploy; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.catalina.springsource"; version="6.0.20.S2-r5956"
  Unresolved requirement: Import-Package: org.apache.coyote.ajp; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
    -> Export-Package: org.apache.coyote.ajp; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.coyote,org.apache.tomcat.util.buf,org.apache.tomcat.util.net"
  Unresolved requirement: Import-Package: org.apache.coyote.http11; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"
    -> Export-Package: org.apache.coyote.http11; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.coyote,org.apache.tomcat.util.buf,org.apache.tomcat.util.net"

Looking at the above exception, the bundles are not getting resolved. But, I see, the import and exports packages are maintained properly and all the bundles and packages are available to the container.
I got these bundles from springsource repository and are maintained by spring source.

The same configuration/bundles  works fine with Eclipse Equinox v3.4.0 container. But When I replace the OSGi container with 3.10.1 related jars, it fails.

Do you see any problem in this? Has anything changed with respect to fragment bundles in new OSGi (v3.10.x) container specification ?

Thanks and Regards
-------------------------------
Raghavendra Neelekani

<div><div dir="ltr">
<div>Hello&nbsp;</div>
<div><br></div>
<div>
<div>I have a java application where we use OSGi equinox v3.4.0 to use and manage different OSGi bundles as part of our application deployment.</div>
<div><br></div>
<div>Now we have a plan to migrate to OSGi equinox v3.10.1. With this new OSGi container, I see some of the, open source, bundles are not getting resolved even though all the dependant bundles/fragments are available to the container.</div>
<div><br></div>
<div>Please refer to the below examples for complete details.&nbsp;</div>
<div><br></div>
<div>I could start the OSGi container successfully and the 'ss' command (listing all bundles) shows the following result.</div>
<div><br></div>
<div>osgi&gt; ss</div>
<div>"Framework is launched."</div>
<div><br></div>
<div>id &nbsp; &nbsp; &nbsp;State &nbsp; &nbsp; &nbsp; Bundle</div>
<div>0 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;org.eclipse.osgi_3.10.1.v20140909-1633</div>
<div>1 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.annotation_1.0.0</div>
<div>2 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.ejb_3.0.0</div>
<div>3 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.el_2.1.0</div>
<div>4 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.management.j2ee_1.0.1</div>
<div>5 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.persistence_1.0.0</div>
<div>6 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.resource_1.5.0</div>
<div>7 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.servlet_2.5.0</div>
<div>8 &nbsp; &nbsp; &nbsp; ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.servlet.jsp_2.1.0</div>
<div>9 &nbsp; &nbsp; &nbsp; INSTALLED &nbsp; com.springsource.javax.servlet.jsp.jstl_1.1.2</div>
<div>10 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.transaction_1.1.0</div>
<div>11 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.xml.soap_1.3.0</div>
<div>12 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.xml.stream_1.0.1</div>
<div>13 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.javax.xml.ws_2.1.1</div>
<div>14 &nbsp; &nbsp; &nbsp;INSTALLED &nbsp; com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956</div>
<div>15 &nbsp; &nbsp; &nbsp;INSTALLED &nbsp; com.springsource.org.apache.coyote.springsource_6.0.20.S2-r5956</div>
<div>16 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.org.apache.el.springsource_6.0.20.S2-r5956</div>
<div>17 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.org.apache.jasper.org.eclipse.jdt_6.0.16</div>
<div>18 &nbsp; &nbsp; &nbsp;INSTALLED &nbsp; com.springsource.org.apache.jasper.springsource_6.0.20.S2-r5956</div>
<div>19 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;com.springsource.org.apache.juli.extras.springsource_6.0.20.S2-r5956</div>
<div>20 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;javax.interceptor_1.1.0</div>
<div>21 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;javax.jms_1.1.0</div>
<div>22 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;javax.mail_1.4.0</div>
<div>23 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;javax.xml.rpc_1.1.0</div>
<div>24 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.apache.felix.gogo.command_0.10.0.v201209301215</div>
<div>25 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.apache.felix.gogo.runtime_0.10.0.v201209301036</div>
<div>26 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.apache.felix.gogo.shell_0.10.0.v201212101605</div>
<div>27 &nbsp; &nbsp; &nbsp;INSTALLED &nbsp; org.apache.jasper.glassfish_2.2.2.v201205150955</div>
<div>28 &nbsp; &nbsp; &nbsp;INSTALLED &nbsp; org.eclipse.core.runtime_3.10.0.v20140318-2214</div>
<div>29 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.eclipse.equinox.common_3.6.200.v20130402-1505</div>
<div>30 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.eclipse.equinox.console_1.1.0.v20140131-1639</div>
<div>31 &nbsp; &nbsp; &nbsp;ACTIVE &nbsp; &nbsp; &nbsp;org.eclipse.osgi.services_3.4.0.v20140312-2051</div>
<div><br></div>
<div>You can notice that the bundle &nbsp;com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956&nbsp;is just INSTALLED but not started. The bundles&nbsp;com.springsource.org.apache.coyote.springsource_6.0.20.S2-r5956&nbsp;and&nbsp;com.springsource.org.apache.jasper.springsource_6.0.20.S2-r5956&nbsp;are fragment bundles and are attached to apache catalina springsource bundle.</div>
<div><br></div>
<div>When I tried to start the bundle&nbsp;com.springsource.org.apache.catalina.springsource_6.0.20.S2-r5956&nbsp;I get following exception.&nbsp;</div>
<div><br></div>
<div>osgi&gt; start 14</div>
<div>gogo: BundleException: Could not resolve module: com.springsource.org.apache.catalina.springsource [14]</div>
<div>&nbsp; Unresolved requirement: Import-Package: org.apache.tomcat; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; -&gt; Export-Package: org.apache.tomcat; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.jasper.springsource"; version="6.0.20.S2-r5956"; uses:="javax.servlet"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp;com.springsource.org.apache.jasper.springsource [18]</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.tools.ant; version="[1.7.0,2.0.0)"; resolution:="optional"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.tools.ant.taskdefs; version="[1.7.0,2.0.0)"; resolution:="optional"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.tools.ant.types; version="[1.7.0,2.0.0)"; resolution:="optional"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.tools.ant.util; version="[1.7.0,2.0.0)"; resolution:="optional"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Fragment-Host: com.springsource.org.apache.catalina.springsource; version="[6.0.20.S2-r5956, 6.0.20.S2-r5956]"</div>
<div>&nbsp; Unresolved requirement: Import-Package: org.apache.coyote; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; -&gt; Export-Package: org.apache.coyote; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.tomcat.util.buf,org.apache.tomcat.util.http,<a href="http://org.apache.tomcat.util.net/" target="_blank">org.apache.tomcat.util.net</a>"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp;com.springsource.org.apache.coyote.springsource [15]</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Fragment-Host: com.springsource.org.apache.catalina.springsource; bundle-version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-&gt; Bundle-SymbolicName: com.springsource.org.apache.catalina.springsource; bundle-version="6.0.20.S2-r5956"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.catalina; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-&gt; Export-Package: org.apache.catalina; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.catalina.springsource"; version="6.0.20.S2-r5956"; uses:="javax.naming.directory,javax.servlet,javax.servlet.http,org.apache.catalina.connector,org.apache.catalina.deploy,org.apache.catalina.util,org.apache.juli.logging,org.apache.tomcat,org.apache.tomcat.util.http.mapper"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unresolved requirement: Import-Package: org.apache.catalina.deploy; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-&gt; Export-Package: org.apache.catalina.deploy; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.catalina.springsource"; version="6.0.20.S2-r5956"</div>
<div>&nbsp; Unresolved requirement: Import-Package: org.apache.coyote.ajp; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; -&gt; Export-Package: org.apache.coyote.ajp; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.coyote,org.apache.tomcat.util.buf,<a href="http://org.apache.tomcat.util.net/" target="_blank">org.apache.tomcat.util.net</a>"</div>
<div>&nbsp; Unresolved requirement: Import-Package: org.apache.coyote.http11; version="[6.0.20.S2-r5956,6.0.20.S2-r5956]"</div>
<div>&nbsp; &nbsp; -&gt; Export-Package: org.apache.coyote.http11; bundle-version="6.0.20.S2-r5956"; bundle-symbolic-name="com.springsource.org.apache.coyote.springsource"; version="6.0.20.S2-r5956"; uses:="javax.management,org.apache.coyote,org.apache.tomcat.util.buf,<a href="http://org.apache.tomcat.util.net/" target="_blank">org.apache.tomcat.util.net</a>"</div>
<div><br></div>
<div>Looking at the above exception, the bundles are not getting resolved. But, I see, the import and exports packages are maintained properly and all the bundles and packages are available to the container.</div>
<div>I got these bundles from springsource repository and are maintained by spring source.</div>
<div><br></div>
<div>The same configuration/bundles &nbsp;works fine with Eclipse Equinox v3.4.0 container. But When I replace the OSGi container with 3.10.1 related jars, it fails.</div>
<div><br></div>
<div>Do you see any problem in this? Has anything changed with respect to fragment bundles in new OSGi (v3.10.x) container specification ?</div>
</div>
<div><div class="gmail_signature"><div dir="ltr">
<div><br></div>Thanks and Regards<div>-------------------------------</div>
<div>Raghavendra Neelekani<br><div><br></div>
</div>
</div></div></div>
</div></div>
David M Williams | 27 Feb 16:29 2015
Picon

A new maintenance release of Eclipse (4.4.2) and Equinox (LunaSR2) is available

Congratulations to the teams responsible for improving the quality of the 4.4 stream of Eclipse and Equinox (Luna stream) and
making the release available on schedule!

        Eclipse downloads:
        http://download.eclipse.org/eclipse/downloads/drops4/R-4.4.2-201502041700/

        Update existing (non-production) installs:
        http://download.eclipse.org/eclipse/updates/4.4/

        Specific repository good for building against:
        http://download.eclipse.org/eclipse/updates/4.4/R-4.4.2-201502041700/

        Equinox specific downloads:
        http://download.eclipse.org/equinox/drops/R-LunaSR2-201502041700/


Thanks to everyone who contributed and tested this release. It is much appreciated!

<div>Congratulations to the teams responsible
for improving the quality of the 4.4 stream of Eclipse and Equinox (Luna
stream) and
<br>making the release available on schedule!

<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Eclipse
downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/downloads/drops4/R-4.4.2-201502041700/">http://download.eclipse.org/eclipse/downloads/drops4/R-4.4.2-201502041700/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Update existing
(non-production) installs:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4/">http://download.eclipse.org/eclipse/updates/4.4/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Specific
repository good for building against:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4/R-4.4.2-201502041700/">http://download.eclipse.org/eclipse/updates/4.4/R-4.4.2-201502041700/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Equinox
specific downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/equinox/drops/R-LunaSR2-201502041700/">http://download.eclipse.org/equinox/drops/R-LunaSR2-201502041700/</a>
<br><br><br>Thanks to everyone who contributed and
tested this release. It is much appreciated! 
<br><br>
</div>
Tom Schindl | 20 Feb 18:36 2015
Picon

Huge performance loss between Kepler and Luna/Mars on first start

Hi,

I've been with a customer today who wants to update from Eclipse 3.x
Kepler to the 4.x code base and so he naturally inherits the latest
Equinox implementation who has changed in between those releases.

The intial boot time increased from about 2 seconds to ~20 seconds on
Mars (on Luna Equinox or better said Felix-Resolver crashes).

We profiled the bootstrap process and the whole time (95%) is eaten up
the by felix resolver ResolverImpl#mergeCandidatePackages

Looking at tbe hot methods we see:
* 15% of the time is spend in ArrayList.contains()

* 30% of the time in HashMap.getNode()
  - called from ResolverImpl#mergeCanidatePackages 7%
  - called from ResolverImpl#calculateExportedPackages 5%
  - called from ResolverImpl#mergeUses 5%

Looking Allocation counts we see the biggest amount (1.9GB) being caused
by ArrayList.grow where we could track back 1.84GB to
mergeCandidatePackages once more which suggests that the initial sizes
choosen for the arrays there are probably not optimal.

One very interesting to this piece of software is that it uses:
a) only require bundle - not very unnatural for Eclipse apps
b) a loooot of reexports!

Would it be possible to:
a) replace the lists through sets? This should improve the contains check
b) use better initial array sizes?

Tom

--

-- 
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
Scott Lewis | 20 Feb 02:04 2015

equinox ds

Questions:

1) Has the org.eclipse.equinox.ds implementation of Declarative Services 
yet incorporated the additions from RFC190?  The version in Mars M5 
appears to be org.eclipse.equinox.ds_1.4.200.v20131126-2331 which based 
upon qualifier I would guess doesn't have support for RFC190, but wanted 
to ask anyway.

2) Assuming the answer to 1 is 'no', what implementation(s) of DS *do* 
currently support RFC190?

3) Are there plans to update org.eclipse.equinox.ds to support RFC190?

Thanksinadvance,

Scott

portal on behalf of emo | 16 Feb 06:00 2015

IP CQs waiting on your team

equinox-dev,
IPZilla records show that one or more of the projects on which you are
developer are in need of attention.  The following CQs have been in the
'awaiting_project' status for over 3 weeks  and need your team to take
action.

  rt.equinox:

    8618 OSGi Enterprise Companion Code -- checkin, sourceandbinary,
thirdparty, unmodified, 3 weeks ago
    https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8618

If you have any questions, please do not hesitate to contact your project
lead, PMC member, or the EMO <emo@...>

David M Williams | 13 Feb 23:39 2015
Picon

Eclipse 4.4.2 RC4 and Equinox (Luna SR2 RC4) are available (same bits as RC3)

There were no changes after RC3, for the Eclipse Platform Project and Equinox, but I have copied and renamed that RC3 delivery to RC4, to make it more obvious this is our planed contribution to Luna SR2, assuming no blocking issues found.


        Eclipse downloads:
        http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC4-201502041700/

        Update existing (non-production) installs:
        http://download.eclipse.org/eclipse/updates/4.4-M-builds/

        Specific repository good for building against:
        http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC4-201502041700/

        Equinox specific downloads:
        http://download.eclipse.org/equinox/drops/M-LunaSR2RC4-201502041700/


NOTE: it appears there is sorting issue on the Equinox DL page, and "LunaSR2RC3" shows up under "Latest Builds", and "LunaSR2RC4" shows up under "Luna Maintenance Builds". But, again, they are the same ... just wanted to explain in advance.

Thanks to all,
<div>There were no changes after RC3, for the
Eclipse Platform Project and Equinox, but I have copied and renamed that
RC3 delivery to RC4, to make it more obvious this is our planed contribution
to Luna SR2, assuming no blocking issues found. 
<br><br><br>&nbsp; &nbsp; &nbsp; &nbsp; Eclipse
downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC4-201502041700/">http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC4-201502041700/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Update existing
(non-production) installs:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4-M-builds/">http://download.eclipse.org/eclipse/updates/4.4-M-builds/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Specific
repository good for building against:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC4-201502041700/">http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC4-201502041700/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Equinox
specific downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/equinox/drops/M-LunaSR2RC4-201502041700/">http://download.eclipse.org/equinox/drops/M-LunaSR2RC4-201502041700/</a>
<br><br><br>NOTE: it appears there is sorting issue
on the Equinox DL page, and "LunaSR2RC3" shows up under "Latest
Builds", and "LunaSR2RC4" shows up under "Luna Maintenance
Builds". But, again, they are the same ... just wanted to explain
in advance. 
<br><br>Thanks to all, 
<br>
</div>
David M Williams | 30 Jan 21:55 2015
Picon

Eclipse Platform Project 4.5 M5 and Equinox (MarsM5) are available

 Read what is New and Noteworthy [1]

 Then download or update to give it a test drive:

        Eclipse downloads:
        http://download.eclipse.org/eclipse/downloads/drops4/S-4.5M5-201501291830/

        Update existing (non-production) installs:
        http://download.eclipse.org/eclipse/updates/4.5milestones/

        Specific repository good for building against:
        http://download.eclipse.org/eclipse/updates/4.5milestones/S-4.5M5-201501291830/

        Equinox specific downloads:
        http://download.eclipse.org/equinox/drops/S-MarsM5-201501291830/

Thanks to everyone who contributed to making this milestone available.

And thanks in advance to all of you who will test and report any issues.

(Note: performance test results will be uploaded when they are finished ... either very late tonight, or Saturday.)

[1] https://www.eclipse.org/eclipse/news/4.5/M5/
<div>&nbsp;Read what is <a href="https://www.eclipse.org/eclipse/news/4.5/M5/">New
and Noteworthy</a> [1]
<br><br>&nbsp;Then download or update to give
it a test drive: 
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Eclipse
downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.5M5-201501291830/">http://download.eclipse.org/eclipse/downloads/drops4/S-4.5M5-201501291830/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Update existing
(non-production) installs:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.5milestones/">http://download.eclipse.org/eclipse/updates/4.5milestones/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Specific
repository good for building against:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.5milestones/S-4.5M5-201501291830/">http://download.eclipse.org/eclipse/updates/4.5milestones/S-4.5M5-201501291830/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Equinox
specific downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/equinox/drops/S-MarsM5-201501291830/">http://download.eclipse.org/equinox/drops/S-MarsM5-201501291830/</a>
<br><br>Thanks to everyone who contributed to
making this milestone available. 
<br><br>And thanks in advance to all of you
who will test and report any issues. 
<br><br>(Note: performance test results will
be uploaded when they are finished ... either very late tonight, or Saturday.)
<br><br>[1] <a href="https://www.eclipse.org/eclipse/news/4.5/M5/">https://www.eclipse.org/eclipse/news/4.5/M5/</a>
<br>
</div>
David M Williams | 30 Jan 21:55 2015
Picon

Eclipse Platform Project 4.4.2 RC2 and Equinox (Luna SR2 RC2) are available

We are getting close to our SR2 service release. Now is the time to test well and be sure nothing has regressed.

        Eclipse downloads:
        http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC2-201501281000/

        Update existing (non-production) installs:
        http://download.eclipse.org/eclipse/updates/4.4-M-builds/

        Specific repository good for building against:
        http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC2-201501281000/

        Equinox specific downloads:
        http://download.eclipse.org/equinox/drops/M-LunaSR2RC2-201501281000/


And, remember, as usual, this is only the Eclipse Project that's being announced. The EPP packages for RC2 will be available in one week.

Thanks,
<div>We are getting close to our SR2 service
release. Now is the time to test well and be sure nothing has regressed.

<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Eclipse
downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC2-201501281000/">http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.2RC2-201501281000/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Update existing
(non-production) installs:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4-M-builds/">http://download.eclipse.org/eclipse/updates/4.4-M-builds/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Specific
repository good for building against:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC2-201501281000/">http://download.eclipse.org/eclipse/updates/4.4-M-builds/M-4.4.2RC2-201501281000/</a>
<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Equinox
specific downloads:
<br>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://download.eclipse.org/equinox/drops/M-LunaSR2RC2-201501281000/">http://download.eclipse.org/equinox/drops/M-LunaSR2RC2-201501281000/</a>
<br><br><br>And, remember, as usual, this is only
the Eclipse Project that's being announced. The EPP packages for RC2 will
be available in one week. 
<br><br>Thanks, 
<br>
</div>

Gmane