[jira] [Commented] (FELIX-5900) Donating a tool able to generate markdown documentation for SCR and Metatype
[ https://issues.apache.org/jira/browse/FELIX-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587437#comment-16587437 ] Simone Tripodi commented on FELIX-5900: --- A I am so glad my contributions are now part of the Felix plugin, I am so happy! :) Thanks for the support! > Donating a tool able to generate markdown documentation for SCR and Metatype > > > Key: FELIX-5900 > URL: https://issues.apache.org/jira/browse/FELIX-5900 > Project: Felix > Issue Type: New Feature >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler >Priority: Major > Fix For: osgicheck-maven-plugin 1.0.0 > > > after collected a series of feedbacks from dev@sling.a.o , I am here to > propose a couple of new Maven MOJOs to be included in the Felix codebase, > able to generate final-user markdown documentation from SCR and Metatype > medata descriptors. > Advantages of producing such documentation, are: > * for an internal use, having such catalogue could reduce the development > efforts, maybe there are services already available for certain operations > that don’t need to be re-implemented; moreover, it can improve/simplify > heterogeneous teams integration work. > * from customers point of view, it would be good to know what solutions are > already offered, to develop their needs on top of our solutions; moreover, > under a security PoV, admins can have an overall view to identify which are > potential entry-points that can be attacked. > If you want to have a look at the output, I tested the MOJOs against a couple > of Apache Sling projects and collected all of them under a private public > GitHub repo[1], it should be easy enough understanding how traverse rendered > data. > How it works: it is a couple of plain-old Maven3 MOJOs which can be > configured directly in the POM, I packaged already all the sources in order > to be donated to the ASF, I just would like to start the discussion in order > to understand if the community is interested on that tool and which steps are > required in order to have it accepted. > I identified the osgicheck-maven-plugin[2] as the best candidate in order to > host the new codebase. > [1] https://github.com/simonetripodi/mddoc-samples > [2] https://github.com/apache/felix/tree/trunk/tools/osgicheck-maven-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FELIX-5900) Donating a tool able to generate markdown documentation for SCR and Metatype
[ https://issues.apache.org/jira/browse/FELIX-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584702#comment-16584702 ] Simone Tripodi commented on FELIX-5900: --- Hi there [~cziegeler], thanks a lot for your feedback and apologise for my late reaction, but I was on PTO. I included in [PR 149|https://github.com/apache/felix/pull/149] your request, you can see the new shiny README generated files on my personal public repo https://github.com/simonetripodi/mddoc-samples/. Hope it looks ok now! > Donating a tool able to generate markdown documentation for SCR and Metatype > > > Key: FELIX-5900 > URL: https://issues.apache.org/jira/browse/FELIX-5900 > Project: Felix > Issue Type: New Feature >Reporter: Simone Tripodi >Priority: Major > > after collected a series of feedbacks from dev@sling.a.o , I am here to > propose a couple of new Maven MOJOs to be included in the Felix codebase, > able to generate final-user markdown documentation from SCR and Metatype > medata descriptors. > Advantages of producing such documentation, are: > * for an internal use, having such catalogue could reduce the development > efforts, maybe there are services already available for certain operations > that don’t need to be re-implemented; moreover, it can improve/simplify > heterogeneous teams integration work. > * from customers point of view, it would be good to know what solutions are > already offered, to develop their needs on top of our solutions; moreover, > under a security PoV, admins can have an overall view to identify which are > potential entry-points that can be attacked. > If you want to have a look at the output, I tested the MOJOs against a couple > of Apache Sling projects and collected all of them under a private public > GitHub repo[1], it should be easy enough understanding how traverse rendered > data. > How it works: it is a couple of plain-old Maven3 MOJOs which can be > configured directly in the POM, I packaged already all the sources in order > to be donated to the ASF, I just would like to start the discussion in order > to understand if the community is interested on that tool and which steps are > required in order to have it accepted. > I identified the osgicheck-maven-plugin[2] as the best candidate in order to > host the new codebase. > [1] https://github.com/simonetripodi/mddoc-samples > [2] https://github.com/apache/felix/tree/trunk/tools/osgicheck-maven-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FELIX-5900) Donating a tool able to generate markdown documentation for SCR and Metatype
[ https://issues.apache.org/jira/browse/FELIX-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570170#comment-16570170 ] Simone Tripodi commented on FELIX-5900: --- Pull Request https://github.com/apache/felix/pull/149 contains the related implementation > Donating a tool able to generate markdown documentation for SCR and Metatype > > > Key: FELIX-5900 > URL: https://issues.apache.org/jira/browse/FELIX-5900 > Project: Felix > Issue Type: New Feature >Reporter: Simone Tripodi >Priority: Major > > after collected a series of feedbacks from dev@sling.a.o , I am here to > propose a couple of new Maven MOJOs to be included in the Felix codebase, > able to generate final-user markdown documentation from SCR and Metatype > medata descriptors. > Advantages of producing such documentation, are: > * for an internal use, having such catalogue could reduce the development > efforts, maybe there are services already available for certain operations > that don’t need to be re-implemented; moreover, it can improve/simplify > heterogeneous teams integration work. > * from customers point of view, it would be good to know what solutions are > already offered, to develop their needs on top of our solutions; moreover, > under a security PoV, admins can have an overall view to identify which are > potential entry-points that can be attacked. > If you want to have a look at the output, I tested the MOJOs against a couple > of Apache Sling projects and collected all of them under a private public > GitHub repo[1], it should be easy enough understanding how traverse rendered > data. > How it works: it is a couple of plain-old Maven3 MOJOs which can be > configured directly in the POM, I packaged already all the sources in order > to be donated to the ASF, I just would like to start the discussion in order > to understand if the community is interested on that tool and which steps are > required in order to have it accepted. > I identified the osgicheck-maven-plugin[2] as the best candidate in order to > host the new codebase. > [1] https://github.com/simonetripodi/mddoc-samples > [2] https://github.com/apache/felix/tree/trunk/tools/osgicheck-maven-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FELIX-5900) Donating a tool able to generate markdown documentation for SCR and Metatype
Simone Tripodi created FELIX-5900: - Summary: Donating a tool able to generate markdown documentation for SCR and Metatype Key: FELIX-5900 URL: https://issues.apache.org/jira/browse/FELIX-5900 Project: Felix Issue Type: New Feature Reporter: Simone Tripodi after collected a series of feedbacks from dev@sling.a.o , I am here to propose a couple of new Maven MOJOs to be included in the Felix codebase, able to generate final-user markdown documentation from SCR and Metatype medata descriptors. Advantages of producing such documentation, are: * for an internal use, having such catalogue could reduce the development efforts, maybe there are services already available for certain operations that don’t need to be re-implemented; moreover, it can improve/simplify heterogeneous teams integration work. * from customers point of view, it would be good to know what solutions are already offered, to develop their needs on top of our solutions; moreover, under a security PoV, admins can have an overall view to identify which are potential entry-points that can be attacked. If you want to have a look at the output, I tested the MOJOs against a couple of Apache Sling projects and collected all of them under a private public GitHub repo[1], it should be easy enough understanding how traverse rendered data. How it works: it is a couple of plain-old Maven3 MOJOs which can be configured directly in the POM, I packaged already all the sources in order to be donated to the ASF, I just would like to start the discussion in order to understand if the community is interested on that tool and which steps are required in order to have it accepted. I identified the osgicheck-maven-plugin[2] as the best candidate in order to host the new codebase. [1] https://github.com/simonetripodi/mddoc-samples [2] https://github.com/apache/felix/tree/trunk/tools/osgicheck-maven-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FELIX-5258) Add a new MOJO which verifies the bundle integrity
[
https://issues.apache.org/jira/browse/FELIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-5258:
--
Attachment: FELIX-5258.patch.2
[~cziegeler] please have a look at the {{.2}} patch, it contains requested
javadoc and more detailed error message, when failing :)
Feedbacks and suggestions are welcome! :)
> Add a new MOJO which verifies the bundle integrity
> --
>
> Key: FELIX-5258
> URL: https://issues.apache.org/jira/browse/FELIX-5258
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-3.0.1
>Reporter: Simone Tripodi
>Assignee: Carsten Ziegeler
> Fix For: maven-bundle-plugin-3.1.0
>
> Attachments: FELIX-5258.patch, FELIX-5258.patch.1, FELIX-5258.patch.2
>
>
> In my company it happens sometimes that people using the _Maven Bundle
> Plugin_ to produce the bundle misinterpret the configuration settings,
> producing a {{MANIFEST}} file with invalid OSGi entries, i.e. given a project
> with the following structure:
> {noformat}
> myproject
> ├── src
> │ ├── main
> │ │ ├── java
> │ │ │ └── org
> │ │ │ └── apache
> │ │ │ ├── acme
> │ │ │ │ ├── utils
> {noformat}
> and the {{pom.xml}} is wrongly configured as:
> {noformat}
>
> org.apache.felix
> maven-bundle-plugin
> true
>
>
>
> nothing
>
>
>
>
> {noformat}
> it makes the {{Export-Package}} header resulting as {{Export-Package:
> nothing}}.
> A MOJO, invoked during the {{verify}} phase, would be very useful to check
> the target bundle integrity and prevent this kind of wrong exports.
> Patch is coming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5258) Add a new MOJO which verifies the bundle integrity
[
https://issues.apache.org/jira/browse/FELIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-5258:
--
Attachment: FELIX-5258.patch.1
Please take in consideration the new {{.1}} patch, there were some refuses in
the previous one :P
Forgot also to mention that the plugin fails on error by default, but behaviour
can be changed by setting the {{failOnError}} to {{false}} and that can be
skipped, by setting the {{skip}} to {{true}}.
Produced output would look like:
{noformat}
[ERROR] Failed to execute goal
org.apache.felix:maven-bundle-plugin:3.1.0-SNAPSHOT:verify (verify) on project
com.acme.myproject: Current bundle
/Users/stripodi/Documents/workspace/com.acme.myproject/target/com.acme.myproject-1.0.0-SNAPSHOT.jar
exports packages that do not exist:
[ERROR] * nothing
[ERROR] * this.is.invented
{noformat}
> Add a new MOJO which verifies the bundle integrity
> --
>
> Key: FELIX-5258
> URL: https://issues.apache.org/jira/browse/FELIX-5258
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-3.0.1
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-3.1.0
>
> Attachments: FELIX-5258.patch, FELIX-5258.patch.1
>
>
> In my company it happens sometimes that people using the _Maven Bundle
> Plugin_ to produce the bundle misinterpret the configuration settings,
> producing a {{MANIFEST}} file with invalid OSGi entries, i.e. given a project
> with the following structure:
> {noformat}
> myproject
> ├── src
> │ ├── main
> │ │ ├── java
> │ │ │ └── org
> │ │ │ └── apache
> │ │ │ ├── acme
> │ │ │ │ ├── utils
> {noformat}
> and the {{pom.xml}} is wrongly configured as:
> {noformat}
>
> org.apache.felix
> maven-bundle-plugin
> true
>
>
>
> nothing
>
>
>
>
> {noformat}
> it makes the {{Export-Package}} header resulting as {{Export-Package:
> nothing}}.
> A MOJO, invoked during the {{verify}} phase, would be very useful to check
> the target bundle integrity and prevent this kind of wrong exports.
> Patch is coming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5258) Add a new MOJO which verifies the bundle integrity
[
https://issues.apache.org/jira/browse/FELIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-5258:
--
Attachment: FELIX-5258.patch
The attached {{FELIX-5258.patch}} is an initial contribution of the new MOJO
which verifies the bundle.
While this feature should be contributed to the BND library, I suggest to
provide this plugin first, then as soon as it will be available in BND, then
the {{checkPackages()}} method in the plugin can be updated.
Please tell me if anything more is needed from my side in order to have this
new feature accepted., TIA! :)
> Add a new MOJO which verifies the bundle integrity
> --
>
> Key: FELIX-5258
> URL: https://issues.apache.org/jira/browse/FELIX-5258
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-3.0.1
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-3.1.0
>
> Attachments: FELIX-5258.patch
>
>
> In my company it happens sometimes that people using the _Maven Bundle
> Plugin_ to produce the bundle misinterpret the configuration settings,
> producing a {{MANIFEST}} file with invalid OSGi entries, i.e. given a project
> with the following structure:
> {noformat}
> myproject
> ├── src
> │ ├── main
> │ │ ├── java
> │ │ │ └── org
> │ │ │ └── apache
> │ │ │ ├── acme
> │ │ │ │ ├── utils
> {noformat}
> and the {{pom.xml}} is wrongly configured as:
> {noformat}
>
> org.apache.felix
> maven-bundle-plugin
> true
>
>
>
> nothing
>
>
>
>
> {noformat}
> it makes the {{Export-Package}} header resulting as {{Export-Package:
> nothing}}.
> A MOJO, invoked during the {{verify}} phase, would be very useful to check
> the target bundle integrity and prevent this kind of wrong exports.
> Patch is coming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5258) Add a new MOJO which verifies the bundle integrity
Simone Tripodi created FELIX-5258:
-
Summary: Add a new MOJO which verifies the bundle integrity
Key: FELIX-5258
URL: https://issues.apache.org/jira/browse/FELIX-5258
Project: Felix
Issue Type: New Feature
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-3.0.1
Reporter: Simone Tripodi
Fix For: maven-bundle-plugin-3.1.0
In my company it happens sometimes that people using the _Maven Bundle Plugin_
to produce the bundle misinterpret the configuration settings, producing a
{{MANIFEST}} file with invalid OSGi entries, i.e. given a project with the
following structure:
{noformat}
myproject
├── src
│ ├── main
│ │ ├── java
│ │ │ └── org
│ │ │ └── apache
│ │ │ ├── acme
│ │ │ │ ├── utils
{noformat}
and the {{pom.xml}} is wrongly configured as:
{noformat}
org.apache.felix
maven-bundle-plugin
true
nothing
{noformat}
it makes the {{Export-Package}} header resulting as {{Export-Package: nothing}}.
A MOJO, invoked during the {{verify}} phase, would be very useful to check the
target bundle integrity and prevent this kind of wrong exports.
Patch is coming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5024) "waiting to lock" message serializes "null" when there is no owner thread
[
https://issues.apache.org/jira/browse/FELIX-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-5024:
--
Attachment: FELIX-5024.patch
Proposed patch fixes the issue simply by checking the owner ID inside the
message format, it skips the owner details rendering if there is no owner
> "waiting to lock" message serializes "null" when there is no owner thread
> -
>
> Key: FELIX-5024
> URL: https://issues.apache.org/jira/browse/FELIX-5024
> Project: Felix
> Issue Type: Bug
> Components: Thread Dumper
>Affects Versions: threaddump-1.0.0
>Reporter: Simone Tripodi
> Fix For: threaddump-1.0.2
>
> Attachments: FELIX-5024.patch
>
>
> It happen that the {{waiting to lock}} message renders a _null_ string when
> there is no owner thread, it must be removed
> {noformat}
> "mythread-323" prio=5 tid=0x143 nid=0x timed_waiting
>java.lang.Thread.State: TIMED_WAITING
> at sun.misc.Unsafe.park(Native Method)
> - waiting to lock <0x406249f1> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) owned
> by "null" tid=0x-1
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
> at
> org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:389)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:531)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.access$700(QueuedThreadPool.java:47)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:590)
> at java.lang.Thread.run(Thread.java:722)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5024) "waiting to lock" message serializes "null" when there is no owner thread
Simone Tripodi created FELIX-5024:
-
Summary: "waiting to lock" message serializes "null" when there is
no owner thread
Key: FELIX-5024
URL: https://issues.apache.org/jira/browse/FELIX-5024
Project: Felix
Issue Type: Bug
Components: Thread Dumper
Affects Versions: threaddump-1.0.0
Reporter: Simone Tripodi
Fix For: threaddump-1.0.2
It happen that the {{waiting to lock}} message renders a _null_ string when
there is no owner thread, it must be removed
{noformat}
"mythread-323" prio=5 tid=0x143 nid=0x timed_waiting
java.lang.Thread.State: TIMED_WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting to lock <0x406249f1> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) owned by
"null" tid=0x-1
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
at
org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:389)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:531)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.access$700(QueuedThreadPool.java:47)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:590)
at java.lang.Thread.run(Thread.java:722)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-4547) Implement the missing resources registration
[ https://issues.apache.org/jira/browse/FELIX-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-4547: -- Attachment: FELIX-4547.patch I think it would be good to start the discussion about resources registration implementation by showing some code... is that direction right? WDYT? Is there anything else that needs to be taken care? TIA! :) > Implement the missing resources registration > > > Key: FELIX-4547 > URL: https://issues.apache.org/jira/browse/FELIX-4547 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-2.4.0 > > Attachments: FELIX-4547.patch > > > Current implementation of RFC189 does not support yet resources registration. > Questions are: > * do we want to have a servlet implementation which serves a static file? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053508#comment-14053508 ] Simone Tripodi commented on FELIX-4548: --- [~jajans] I just terminated to read the whole commit and I think it can work even better that my original implementation :) I think the issue can be considered resolved since code has been checked-in, WDYT? > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi >Assignee: J.W. Janssen > Fix For: http-2.4.0 > > Attachments: FELIX-4548.patch > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4548) Implement the missing errors registration
[
https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-4548:
--
Attachment: FELIX-4548.patch
Please see the initial proposed patch - the strategy is letting the Dispatcher
handling error codes and java exceptions in the {{base}} bundle
> Implement the missing errors registration
> -
>
> Key: FELIX-4548
> URL: https://issues.apache.org/jira/browse/FELIX-4548
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
>Affects Versions: http-2.4.0
>Reporter: Simone Tripodi
> Fix For: http-2.4.0
>
> Attachments: FELIX-4548.patch
>
>
> Current implementation of RFC189 does not support yet errors registration.
> Questions are:
> * do we want to have a servlet (or maybe a filter fits better)
> implementation which serves a static file whenever an HTTP error is detected?
> or
> * looking for a solution that delegates the underlying servlet container?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049780#comment-14049780 ] Simone Tripodi edited comment on FELIX-4548 at 7/2/14 9:38 AM: --- I am going to have a look for a solution based on the second approach was (Author: simone.tripodi): I am going to look at solution based on the second approach > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-2.4.0 > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FELIX-4547) Implement the missing resources registration
[ https://issues.apache.org/jira/browse/FELIX-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049779#comment-14049779 ] Simone Tripodi edited comment on FELIX-4547 at 7/2/14 9:38 AM: --- I am going to have a look for a solution based on the second approach was (Author: simone.tripodi): I am going to look at solution based on the second approach > Implement the missing resources registration > > > Key: FELIX-4547 > URL: https://issues.apache.org/jira/browse/FELIX-4547 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-2.4.0 > > > Current implementation of RFC189 does not support yet resources registration. > Questions are: > * do we want to have a servlet implementation which serves a static file? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049780#comment-14049780 ] Simone Tripodi commented on FELIX-4548: --- I am going to look at solution based on the second approach > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-2.4.0 > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4547) Implement the missing resources registration
[ https://issues.apache.org/jira/browse/FELIX-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049779#comment-14049779 ] Simone Tripodi commented on FELIX-4547: --- I am going to look at solution based on the second approach > Implement the missing resources registration > > > Key: FELIX-4547 > URL: https://issues.apache.org/jira/browse/FELIX-4547 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-2.4.0 > > > Current implementation of RFC189 does not support yet resources registration. > Questions are: > * do we want to have a servlet implementation which serves a static file? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FELIX-4548) Implement the missing errors registration
Simone Tripodi created FELIX-4548: - Summary: Implement the missing errors registration Key: FELIX-4548 URL: https://issues.apache.org/jira/browse/FELIX-4548 Project: Felix Issue Type: Sub-task Components: HTTP Service Affects Versions: http-2.4.0 Reporter: Simone Tripodi Fix For: http-2.4.0 Current implementation of RFC189 does not support yet errors registration. Questions are: * do we want to have a servlet (or maybe a filter fits better) implementation which serves a static file whenever an HTTP error is detected? or * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FELIX-4547) Implement the missing resources registration
Simone Tripodi created FELIX-4547: - Summary: Implement the missing resources registration Key: FELIX-4547 URL: https://issues.apache.org/jira/browse/FELIX-4547 Project: Felix Issue Type: Sub-task Components: HTTP Service Affects Versions: http-2.4.0 Reporter: Simone Tripodi Fix For: http-2.4.0 Current implementation of RFC189 does not support yet resources registration. Questions are: * do we want to have a servlet implementation which serves a static file? or * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (FELIX-4526) Initial RFC189 (HttpService) implementation attempt
[ https://issues.apache.org/jira/browse/FELIX-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi resolved FELIX-4526. --- Resolution: Fixed issue marked as resoled since patch has been applied, thanks [~cziegeler] for taking care of it! > Initial RFC189 (HttpService) implementation attempt > --- > > Key: FELIX-4526 > URL: https://issues.apache.org/jira/browse/FELIX-4526 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.3.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-2.4.0 > > Attachments: FELIX-4526.patch > > > [~cziegeler] already kindly created a dedicated > [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for > that, this will be the place where contributing such implementation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4526) Initial RFC189 (HttpService) implementation attempt
[ https://issues.apache.org/jira/browse/FELIX-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-4526: -- Summary: Initial RFC189 (HttpService) implementation attempt (was: Update RFC189 (HttpService) implementation) > Initial RFC189 (HttpService) implementation attempt > --- > > Key: FELIX-4526 > URL: https://issues.apache.org/jira/browse/FELIX-4526 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.3.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-2.4.0 > > Attachments: FELIX-4526.patch > > > [~cziegeler] already kindly created a dedicated > [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for > that, this will be the place where contributing such implementation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4526) Update RFC189 (HttpService) implementation
[ https://issues.apache.org/jira/browse/FELIX-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016502#comment-14016502 ] Simone Tripodi commented on FELIX-4526: --- Thanks a lot Carsten! The removal of Async* stuff makes indeed the HttpService implementation much easier :) I'll keep providing patches as soon as I have more updates :P Alles Gute! > Update RFC189 (HttpService) implementation > -- > > Key: FELIX-4526 > URL: https://issues.apache.org/jira/browse/FELIX-4526 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.3.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-2.4.0 > > Attachments: FELIX-4526.patch > > > [~cziegeler] already kindly created a dedicated > [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for > that, this will be the place where contributing such implementation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4526) Update RFC189 (HttpService) implementation
[
https://issues.apache.org/jira/browse/FELIX-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-4526:
--
Attachment: FELIX-4526.patch
The proposing initial patch contributes:
* the whiteboard registration update, keeping the backward compatibility, even
if not complete yet (errors and resources still have to be properly registered
as servlets);
* updates on listener managers;
* proposal on how to extend the {{HttpServiceRuntime}} and how it is managed
while registering Filters/Servlets
Feedbacks, suggestions, criticism, ... are all more than welcome :)
TIA!
> Update RFC189 (HttpService) implementation
> --
>
> Key: FELIX-4526
> URL: https://issues.apache.org/jira/browse/FELIX-4526
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
>Affects Versions: http-2.3.0
>Reporter: Simone Tripodi
> Fix For: http-2.3.0
>
> Attachments: FELIX-4526.patch
>
>
> [~cziegeler] already kindly created a dedicated
> [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for
> that, this will be the place where contributing such implementation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (FELIX-4526) Update RFC189 (HttpService) implementation
Simone Tripodi created FELIX-4526: - Summary: Update RFC189 (HttpService) implementation Key: FELIX-4526 URL: https://issues.apache.org/jira/browse/FELIX-4526 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.3.0 Reporter: Simone Tripodi Fix For: http-2.3.0 [~cziegeler] already kindly created a dedicated [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for that, this will be the place where contributing such implementation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001750#comment-14001750
]
Simone Tripodi commented on FELIX-4512:
---
I stumbled in a Bnd [issue|https://github.com/bndtools/bnd/issues/413] where it
is stated that {{Require-Capability}} should be automatically generated only
for _osgi.ee_... WDYT?
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
>Assignee: Carsten Ziegeler
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.1.patch, FELIX-4512.2.patch,
> FELIX-4512.patch, Screen Shot 2014-05-13 at 11.49.44 PM.pdf
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001704#comment-14001704
]
Simone Tripodi commented on FELIX-4512:
---
Is it related to the {{bundle}} plugin, or the {{baseline}} one? The first, I
guess... :(
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
>Assignee: Carsten Ziegeler
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.1.patch, FELIX-4512.2.patch,
> FELIX-4512.patch, Screen Shot 2014-05-13 at 11.49.44 PM.pdf
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997491#comment-13997491
]
Simone Tripodi commented on FELIX-4512:
---
WOW thanks a lot Carsten, much more than appreciated! :)
Thanks a lot for the hints Julian!
bq. With regard to reporting, I think it would be useful to indicate the
severity (major, minor, micro) for each delta. This is to cater for the
use-case, where I want to avoid a major version change and need to identify the
changes that force such an increment.
I'll inspect your codebase and try to migrate your addition to this new one
bq. {{failOnError}} proved insufficient to describe the desired behaviour for
failing the build, instead the following seemed useful
there is another flag available which is called {{failOnWarning}}, setting both
to {{false}} doesn't make the build fail.
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
>Assignee: Carsten Ziegeler
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.1.patch, FELIX-4512.2.patch,
> FELIX-4512.patch, Screen Shot 2014-05-13 at 11.49.44 PM.pdf
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-4512:
--
Attachment: FELIX-4512.2.patch
Please have look at {{FELIX-4512.2.patch}} which should correctly include
missing binary files - if not, I'll provide a zip file containing all the
missing icons
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.1.patch, FELIX-4512.2.patch,
> FELIX-4512.patch, Screen Shot 2014-05-13 at 11.49.44 PM.pdf
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997385#comment-13997385
]
Simone Tripodi commented on FELIX-4512:
---
Thanks for reporting Michael, very appreciated :)
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.1.patch, FELIX-4512.2.patch,
> FELIX-4512.patch, Screen Shot 2014-05-13 at 11.49.44 PM.pdf
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-4512:
--
Attachment: Screen Shot 2014-05-13 at 11.49.44 PM.pdf
FELIX-4512.1.patch
Please have a look at new proposal contained in FELIX-4512.1.patch - plugin
works in almost exactly the same (it does not dump the console log in a textual
file)
this is how console log looks now:
{noformat}
[INFO] --- maven-bundle-plugin:2.4.1-SNAPSHOT:baseline (baseline) @
org.apache.felix.http.api ---
[INFO] Baseline Report - Generated by Apache Felix Maven Bundle Plugin on
2014-05-13T23:51Z based on Bnd - see http://www.aqute.biz/Bnd/Bnd
[INFO] Comparing bundle org.apache.felix.http.api version 2.3.0-SNAPSHOT to
version 2.2.2
[INFO]
[INFO] PACKAGE_NAME DELTA CUR_VER
BASE_VER REC_VERWARNINGS
[INFO] = == ==
== == == ==
[INFO] * org.apache.felix.http.api major 2.0.4
2.0.4 3.0.0 Version increase required
[INFO] > interface org.apache.felix.http.api.ExtHttpService
[INFO] + method createDefaultHttpContext()
[INFO] + access abstract
[INFO] + return org.osgi.service.http.HttpContext
[INFO] + method doSomething()
[INFO] + access abstract
[INFO] + method
registerResources(java.lang.String,java.lang.String,org.osgi.service.http.HttpContext)
[INFO] + access abstract
[INFO] + method
registerServlet(java.lang.String,javax.servlet.Servlet,java.util.Dictionary,org.osgi.service.http.HttpContext)
[INFO] + access abstract
[INFO] + method unregister(java.lang.String)
[INFO] + access abstract
[INFO] + interface org.apache.felix.http.api.ExtHttpServiceRuntime
[INFO] + access abstract
[INFO] + implements org.osgi.service.http.runtime.HttpServiceRuntime
[INFO] + method getRuntimeDTO()
[INFO] + access abstract
[INFO] + return org.osgi.dto.DTO
[INFO] + return org.osgi.service.http.runtime.dto.RuntimeDTO
[INFO] + method
registerFilter(org.osgi.service.http.runtime.dto.FilterDTO)
[INFO] + access abstract
[INFO] + method
registerServlet(org.osgi.service.http.runtime.dto.ServletDTO)
[INFO] + access abstract
[INFO]
---
[INFO] + org.osgi.dto added 1.0.0
0.0.0 1.0.0 -
[INFO] + class org.osgi.dto.DTO
[INFO] + access abstract
[INFO] + method ()
[INFO] + method clone()
[INFO] + access protected
[INFO] + method equals(java.lang.Object)
[INFO] + return boolean
[INFO] + method finalize()
[INFO] + access protected
[INFO] + method hashCode()
[INFO] + return int
[INFO] + method toString()
[INFO] + return java.io.Serializable
[INFO] + return java.lang.CharSequence
[INFO] + return java.lang.Comparable
[INFO] + return java.lang.String
[INFO] + version 1.0.0
[INFO]
---
[INFO] + org.osgi.service.http added 1.3.0
0.0.0 1.0.0 Excessive version increase
[INFO] + class org.osgi.service.http.NamespaceException
[INFO] + extends java.lang.Exception
[INFO] + extends java.lang.Throwable
[INFO] + implements java.io.Serializable
[INFO] + method (java.lang.String)
[INFO] + method (java.lang.String,java.lang.Throwable)
[INFO] + method clone()
[INFO] + access protected
[INFO] + method equals(java.lang.Object)
[INFO] + return boolean
[INFO] + method fillInStackTrace()
[INFO] + return java.io.Serializable
[INFO] + return java.lang.Throwable
[INFO] + method finalize()
[INFO] + access protected
[INFO] + method getCause()
[INFO] + return java.io.Serializable
[INFO] + return java.lang.Throwable
[INFO] + method getException()
[INFO] + return java.io.Serializable
[INFO] + return java.lang.Throwable
[INFO] + method getLocalizedMessage()
[INFO] + return java.io.Serializable
[INFO] + return java.lang.CharSequence
[INFO] + return java.lang.Comparable
[INFO] + return java.lang.String
[INFO] + method getMessage()
[INFO] + return java.io.Serializable
[INFO]
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996897#comment-13996897
]
Simone Tripodi commented on FELIX-4512:
---
Thanks a lot [~mduerig] for reporting - I am going to submit a new patch that
fixes that problem and adds a new feature :)
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.patch
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994971#comment-13994971
]
Simone Tripodi commented on FELIX-4512:
---
Thanks a lot [~mcculls], much more than appreciated! :) I am trying to provide
another patch today in order to generate also the report page :)
[~cziegeler] please apologise but the wiki didn't render properly what I
reported in David's reply: if {{comparisonVersion}} is not set, default value
is {{(,$project.version)}} which means using the latest released version :)
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.patch
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994567#comment-13994567
]
Simone Tripodi edited comment on FELIX-4512 at 5/11/14 7:00 PM:
The proposal contained in {{FELIX-4512.patch}} provides an implementation of
{{org.apache.felix:maven-bundle-plugin:2.4.1-SNAPSHOT:baseline}} MOJO that has
the following configuration parameters:
||Name||Type||Since||Description||
|failOnError|boolean|2.4.1|Whether to fail on errors. Default value is: true.
User property is: failOnError.|
|failOnWarning|boolean|2.4.1|Whether to fail on warnings. Default value is:
false. User property is: failOnWarning.|
|filters|String[]|2.4.1|A list of packages filter, if empty the whole bundle
will be traversed. Values are specified in OSGi package instructions notation,
e.g. {{!org.apache.felix.bundleplugin.}}|
|logResults|boolean|2.4.1|Whether to log the results to the console or not,
true by default. Default value is: true. User property is: logResults.|
|skip|boolean|2.4.1|Flag to easily skip execution.Default value is: false.User
property is: baseline.skip.|
|textOutputFile|File|2.4.1|A text output file to render to
project.build.directory/baseline.txt.|
|xmlOutputFile|File|2.4.1|An XML output file to render to
project.build.directory/baseline.xml.|
It is invoked during {{validate}} phase in order to make sure the current
bundle is produced and contains valid OSGi metadata.
Plugging it in existing projects is quiet easy, i.e.:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache.felix
org.apache.felix.http.parent
3-SNAPSHOT
../parent/pom.xml
Apache Felix Http Api
org.apache.felix.http.api
2.3.0-SNAPSHOT
...
org.apache.felix
maven-bundle-plugin
2.4.1-SNAPSHOT
bundle
bundle
org.osgi.dto;version=${osgi.dto.version},
org.osgi.service.http;version=${http.service.version},
org.osgi.service.http.runtime;version=${http.service.version},
org.apache.felix.http.api;version=${http.api.version}
org.osgi.dto,
org.osgi.service.http,
org.osgi.service.http.runtime,
javax.servlet.*;version="[2.3,4)",
*
baseline
baseline
2.2.2
true
...
...
{code}
it produces two output files by default, a txt one:
{noformat}
# Baseline Report - Generated by Apache Felix Maven Bundle Plugin at Sun May 11
16:06:20 CEST 2014
Analising current bundle org.apache.felix.http.api-2.3.0-SNAPSHOT against
previous released org.apache.felix.http.api-2.2.2
attrs for org.apache.felix.http.api
version="2.0.4";uses:="javax.servlet,org.osgi.service.http,org.osgi.service.http.runtime"
attrs for org.osgi.dto version="1.0.0"
attrs for org.osgi.service.http
version="1.3.0";uses:="javax.servlet,javax.servlet.http"
attrs for org.osgi.service.http.runtime version="1.3.0"
PACKAGE_NAME DELTA CUR_VER
BASE_VER REC_VERWARNINGS
= == == ==
== == ==
* org.apache.felix.http.api MAJOR 2.0.4
2.0.4 3.0.0 Version increase required
> interface org.apache.felix.http.api.ExtHttpService
+ method createDefaultHttpContext()
+ access abstract
+ return org.osgi.service.http.HttpContext
+ method doSomething()
+ access abstract
+ method
registerResources(java.lang.String,java.lang.String,org.osgi.service.http.HttpContext)
+ access abstract
+ method
[jira] [Comment Edited] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994567#comment-13994567
]
Simone Tripodi edited comment on FELIX-4512 at 5/11/14 7:04 PM:
The proposal contained in {{FELIX-4512.patch}} provides an implementation of
{{org.apache.felix:maven-bundle-plugin:2.4.1-SNAPSHOT:baseline}} MOJO that has
the following configuration parameters:
||Name||Type||Since||Description||
|comparisonVersion|String|2.4.1|Version to compare the current code against.
Default value is ,project.version|
|failOnError|boolean|2.4.1|Whether to fail on errors. Default value is: true.
User property is: failOnError.|
|failOnWarning|boolean|2.4.1|Whether to fail on warnings. Default value is:
false. User property is: failOnWarning.|
|filters|String[]|2.4.1|A list of packages filter, if empty the whole bundle
will be traversed. Values are specified in OSGi package instructions notation,
e.g. {{!org.apache.felix.bundleplugin.}}|
|logResults|boolean|2.4.1|Whether to log the results to the console or not,
true by default. Default value is: true. User property is: logResults.|
|skip|boolean|2.4.1|Flag to easily skip execution.Default value is: false.User
property is: baseline.skip.|
|textOutputFile|File|2.4.1|A text output file to render to
project.build.directory/baseline.txt.|
|xmlOutputFile|File|2.4.1|An XML output file to render to
project.build.directory/baseline.xml.|
It is invoked during {{validate}} phase in order to make sure the current
bundle is produced and contains valid OSGi metadata.
Plugging it in existing projects is quiet easy, i.e.:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache.felix
org.apache.felix.http.parent
3-SNAPSHOT
../parent/pom.xml
Apache Felix Http Api
org.apache.felix.http.api
2.3.0-SNAPSHOT
...
org.apache.felix
maven-bundle-plugin
2.4.1-SNAPSHOT
bundle
bundle
org.osgi.dto;version=${osgi.dto.version},
org.osgi.service.http;version=${http.service.version},
org.osgi.service.http.runtime;version=${http.service.version},
org.apache.felix.http.api;version=${http.api.version}
org.osgi.dto,
org.osgi.service.http,
org.osgi.service.http.runtime,
javax.servlet.*;version="[2.3,4)",
*
baseline
baseline
2.2.2
true
...
...
{code}
it produces two output files by default, a txt one:
{noformat}
# Baseline Report - Generated by Apache Felix Maven Bundle Plugin at Sun May 11
16:06:20 CEST 2014
Analising current bundle org.apache.felix.http.api-2.3.0-SNAPSHOT against
previous released org.apache.felix.http.api-2.2.2
attrs for org.apache.felix.http.api
version="2.0.4";uses:="javax.servlet,org.osgi.service.http,org.osgi.service.http.runtime"
attrs for org.osgi.dto version="1.0.0"
attrs for org.osgi.service.http
version="1.3.0";uses:="javax.servlet,javax.servlet.http"
attrs for org.osgi.service.http.runtime version="1.3.0"
PACKAGE_NAME DELTA CUR_VER
BASE_VER REC_VERWARNINGS
= == == ==
== == ==
* org.apache.felix.http.api MAJOR 2.0.4
2.0.4 3.0.0 Version increase required
> interface org.apache.felix.http.api.ExtHttpService
+ method createDefaultHttpContext()
+ access abstract
+ return org.osgi.service.http.HttpContext
+ method doSomething()
+ access abstract
+ method
registerResources(java.lang.String,java.lang.Stri
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994644#comment-13994644
]
Simone Tripodi commented on FELIX-4512:
---
Thanks a lot [~bosschaert]!
Please, read my replies inline:
bq. Do you know whether it can also distinguish between @ConsumerType and
@ProviderType?
uhm I honestly don't know, I need to do an investigation - thanks for the
links! :)
bq I guess the comparisonVersion version also needs to be documented
apologise, I just edited the original comment and added it there :) Thanks :P
bq What happens when it isn't there?
the plugin just takes the default value which is {{(,${project.version})}}
bq does the baselining only get executed when the baseline goal is specified?
Or are the other cases where it also gets executed?
I think you could explicitly invoke it, but I need to test it...
Thanks for reviewing, very appreciated!!! :)
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.patch
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994567#comment-13994567
]
Simone Tripodi commented on FELIX-4512:
---
The proposal contained in {{FELIX-4512.patch}} provides an implementation of
{{org.apache.felix:maven-bundle-plugin:2.4.1-SNAPSHOT:baseline}} MOJO that has
the following configuration parameters:
||Name||Type||Since||Description||
|failOnError|boolean|2.4.1|Whether to fail on errors. Default value is: true.
User property is: failOnError.|
|failOnWarning|boolean|2.4.1|Whether to fail on warnings. Default value is:
false. User property is: failOnWarning.|
|filters|String[]|2.4.1|A list of packages filter, if empty the whole bundle
will be traversed. Values are specified in OSGi package instructions notation,
e.g. {{!org.apache.felix.bundleplugin.}}|
|logResults|boolean|2.4.1|Whether to log the results to the console or not,
true by default. Default value is: true. User property is: logResults.|
|skip|boolean|2.4.1|Flag to easily skip execution.Default value is: false.User
property is: baseline.skip.|
|textOutputFile|File|2.4.1|A text output file to render to
${project.build.directory}/baseline.txt.|
|xmlOutputFile|File|2.4.1|An XML output file to render to
${project.build.directory}/baseline.xml.|
It is invoked during {{validate}} phase in order to make sure the current
bundle is produced and contains valid OSGi metadata.
Plugging it in existing projects is quiet easy, i.e.:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache.felix
org.apache.felix.http.parent
3-SNAPSHOT
../parent/pom.xml
Apache Felix Http Api
org.apache.felix.http.api
2.3.0-SNAPSHOT
...
org.apache.felix
maven-bundle-plugin
2.4.1-SNAPSHOT
bundle
bundle
org.osgi.dto;version=${osgi.dto.version},
org.osgi.service.http;version=${http.service.version},
org.osgi.service.http.runtime;version=${http.service.version},
org.apache.felix.http.api;version=${http.api.version}
org.osgi.dto,
org.osgi.service.http,
org.osgi.service.http.runtime,
javax.servlet.*;version="[2.3,4)",
*
baseline
baseline
2.2.2
true
...
...
{code}
it produces two output files by default, a txt one:
{noformat}
# Baseline Report - Generated by Apache Felix Maven Bundle Plugin at Sun May 11
16:06:20 CEST 2014
Analising current bundle org.apache.felix.http.api-2.3.0-SNAPSHOT against
previous released org.apache.felix.http.api-2.2.2
attrs for org.apache.felix.http.api
version="2.0.4";uses:="javax.servlet,org.osgi.service.http,org.osgi.service.http.runtime"
attrs for org.osgi.dto version="1.0.0"
attrs for org.osgi.service.http
version="1.3.0";uses:="javax.servlet,javax.servlet.http"
attrs for org.osgi.service.http.runtime version="1.3.0"
PACKAGE_NAME DELTA CUR_VER
BASE_VER REC_VERWARNINGS
= == == ==
== == ==
* org.apache.felix.http.api MAJOR 2.0.4
2.0.4 3.0.0 Version increase required
> interface org.apache.felix.http.api.ExtHttpService
+ method createDefaultHttpContext()
+ access abstract
+ return org.osgi.service.http.HttpContext
+ method doSomething()
+ access abstract
+ method
registerResources(java.lang.String,java.lang.String,org.osgi.service.http.HttpContext)
+ access abstract
+ method
registerServlet(java.lang.String,javax
[jira] [Created] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
Simone Tripodi created FELIX-4512:
-
Summary: Add a new Mojo to invoke the BND Baseline tool
Key: FELIX-4512
URL: https://issues.apache.org/jira/browse/FELIX-4512
Project: Felix
Issue Type: New Feature
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.4.0
Reporter: Simone Tripodi
Fix For: maven-bundle-plugin-2.4.1
The BND 2.2.0 library contains an extraordinary tool called
[Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph) that
compares the public API of a bundle with the public API of another bundle.
It would be really useful to have this tool in the {{maven-bundle-plugin}} in
order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FELIX-4512) Add a new Mojo to invoke the BND Baseline tool
[
https://issues.apache.org/jira/browse/FELIX-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-4512:
--
Attachment: FELIX-4512.patch
Uploading Baseline plugin implementation
> Add a new Mojo to invoke the BND Baseline tool
> --
>
> Key: FELIX-4512
> URL: https://issues.apache.org/jira/browse/FELIX-4512
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.4.0
>Reporter: Simone Tripodi
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: FELIX-4512.patch
>
>
> The BND 2.2.0 library contains an extraordinary tool called
> [Baseline|http://www.aqute.biz/Bnd/Versioning] (see Baselining paragraph)
> that compares the public API of a bundle with the public API of another
> bundle.
> It would be really useful to have this tool in the {{maven-bundle-plugin}} in
> order to keep track of APIs modifications during development time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3339:
--
Attachment: FELIX-3339-FINAL.patch
{{FELIX-3339-FINAL.patch}} includes latest released version of
{{org.apache.felix.inventory}}.
Patch is now SNAPSHOTs-free, I think it can be merged in trunk.
Best,
-Simo
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339-FINAL.patch, FELIX-3339_initial-proto.patch,
> FELIX-3339_threaddump-as-inventoryprinter_FIXED.patch,
> FELIX-3339_threaddump-as-inventoryprinter.patch,
> FELIX-3339_threaddump-include-jdk18.patch,
> FELIX-3339_threaddump-smarter-jdk_version-comparison.patch,
> FELIX-3339_threadumper-output_compliant_hotspotVM.patch, Screen Shot
> 2013-05-23 at 3.02.24 PM.pdf
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3339: -- Attachment: Screen Shot 2013-05-23 at 3.02.24 PM.pdf FELIX-3339_threaddump-as-inventoryprinter_FIXED.patch Please have a look at the latest patch FELIX-3339_threaddump-as-inventoryprinter_FIXED.patch which correctly provides an InventoryPrinter implementation of Thread Dumper, have a look at the attached Screen Shot 2013-05-23 at 3.02.24 PM.pdf to see it in action embedded in the WebConsole. I hope you'll like it! :) -Simo > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch, > FELIX-3339_threaddump-as-inventoryprinter_FIXED.patch, > FELIX-3339_threaddump-as-inventoryprinter.patch, > FELIX-3339_threaddump-include-jdk18.patch, > FELIX-3339_threaddump-smarter-jdk_version-comparison.patch, > FELIX-3339_threadumper-output_compliant_hotspotVM.patch, Screen Shot > 2013-05-23 at 3.02.24 PM.pdf > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3339: -- Attachment: FELIX-3339_threadumper-output_compliant_hotspotVM.patch hi all again, here's a new patch where the thread dumper is an inventory printer instance that tries to reproduce the output according to [HotSpot VM format|http://javaeesupportpatterns.blogspot.it/2012/02/how-to-analyze-thread-dump-part-3.html] If it looks fine for you, I can continue on having it integrated in the WebConsole > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch, > FELIX-3339_threaddump-as-inventoryprinter.patch, > FELIX-3339_threaddump-include-jdk18.patch, > FELIX-3339_threaddump-smarter-jdk_version-comparison.patch, > FELIX-3339_threadumper-output_compliant_hotspotVM.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3339: -- Attachment: FELIX-3339_threaddump-as-inventoryprinter.patch Please have a look at leatest patch: I propose the thread dump service as a Felix InventoryPrinter instance - would it make sense? > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch, > FELIX-3339_threaddump-as-inventoryprinter.patch, > FELIX-3339_threaddump-include-jdk18.patch, > FELIX-3339_threaddump-smarter-jdk_version-comparison.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650753#comment-13650753 ] Simone Tripodi commented on FELIX-3339: --- yes, please apologise for the wrong info - unfortunately it does not provide help for the target JVM check, so the latest proposed patch is still the better solution I have found > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch, > FELIX-3339_threaddump-include-jdk18.patch, > FELIX-3339_threaddump-smarter-jdk_version-comparison.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3339:
--
Attachment: FELIX-3339_threaddump-smarter-jdk_version-comparison.patch
Please find the attached latest patch which implements a asmarter
{{java.specification.version}} comparison limiting the checks to jdk 1.6 and 1.5
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339_initial-proto.patch,
> FELIX-3339_threaddump-include-jdk18.patch,
> FELIX-3339_threaddump-smarter-jdk_version-comparison.patch
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650127#comment-13650127
]
Simone Tripodi commented on FELIX-3339:
---
looks like {{java.lang .Package#isCompatibleWith(String)}} refers to
{{@version}} javadoc tag, it cannot be used for that purpose - guess that we
have to fallback to {{java.specification.version}} System Property comparison,
maybe a smarter comparison that understand if JDK version >= 1.6 then use Java6
APIs...
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339_initial-proto.patch,
> FELIX-3339_threaddump-include-jdk18.patch
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649919#comment-13649919 ] Simone Tripodi commented on FELIX-3339: --- Sure, I'll investigate on what you suggested and propose a patch! > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch, > FELIX-3339_threaddump-include-jdk18.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3339:
--
Attachment: FELIX-3339_threaddump-include-jdk18.patch
The {{threaddump-include-jdk18.patch}} includes the JDK1.8 support to use Java6
APIs (and doesn't fall back to JDK1.4)
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339_initial-proto.patch,
> FELIX-3339_threaddump-include-jdk18.patch
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649843#comment-13649843 ] Simone Tripodi commented on FELIX-3339: --- I haven't noticed any difference between Java8 [ThreadMXBean|http://download.java.net/jdk8/docs/api/java/lang/management/ThreadMXBean.html] and [ThreadInfo|http://download.java.net/jdk8/docs/api/java/lang/management/ThreadInfo.html] compared to Java6 [ThreadMXBean|http://docs.oracle.com/javase/6/docs/api/java/lang/management/ThreadMXBean.html] and [ThreadInfo|http://docs.oracle.com/javase/6/docs/api/java/lang/management/ThreadInfo.html] definition, I am providing a new patch in order to support Java8 as well > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649830#comment-13649830
]
Simone Tripodi edited comment on FELIX-3339 at 5/6/13 4:22 PM:
---
Hi [~cziegeler]! :)
If I am not wrong, Java7 and Java6 JXM APIs are exactly the same, so I
configured the main printer to fallback to the {{Jdk16ThreadDumper}}, in case
the JVM version is _1.7_, see the {{CompositeThreadDumper}} class in the patch.
Apologize for not having had a look at Java8 APIs, this is something I can
provide a new patch to fill that lack.
was (Author: simone.tripodi):
Hi [~cziegeler]! :)
If I am not wrong, Java7 and Java6 JXM APIs are exactly the same, so I
configured the main printer to fallback to the {{Jdk16ThreadDumper}}, see the
{{CompositeThreadDumper}} class in the patch.
Apologize for not having had a look at Java8 APIs, this is something I can
provide a new patch to fill that lack.
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339_initial-proto.patch
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[
https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649830#comment-13649830
]
Simone Tripodi commented on FELIX-3339:
---
Hi [~cziegeler]! :)
If I am not wrong, Java7 and Java6 JXM APIs are exactly the same, so I
configured the main printer to fallback to the {{Jdk16ThreadDumper}}, see the
{{CompositeThreadDumper}} class in the patch.
Apologize for not having had a look at Java8 APIs, this is something I can
provide a new patch to fill that lack.
> Consolidate Thread Dump Support
> ---
>
> Key: FELIX-3339
> URL: https://issues.apache.org/jira/browse/FELIX-3339
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
> Attachments: FELIX-3339_initial-proto.patch
>
>
> The Felix Web Console currently has an embedded plugin only using traditional
> Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs.
> These two should be consolidated and extended such that:
> * Separate bundle (not embedded in the Web Console Bundle)
> * one single plugin in Apache Felix
> * Uses Java 6 JMX API if available
> * Falls back to Java 5 JMX API if not Java 6
> * Falls back to regular Java API as a last step
> * Provide Gogo Shell Commands
> The advantage of using Java 6 API is to be able to inject lock information in
> the thread dumps to be able to followup on deadlock and similar situations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644382#comment-13644382 ] Simone Tripodi commented on FELIX-3339: --- Hi there [~cziegeler] and [~fmeschbe], so you have some spare time to check if what I am proposing could work? TIA! > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3339) Consolidate Thread Dump Support
[ https://issues.apache.org/jira/browse/FELIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3339: -- Attachment: FELIX-3339_initial-proto.patch Hi all guys, the attached patch is an initial proposal for a bundle which takes care of dumping running threads in the JVM as described by Felix in the Issue description; if that could work, I can go ahead and providing the WebConsole plugin and GogoChell command implementation based on that service. TIA! > Consolidate Thread Dump Support > --- > > Key: FELIX-3339 > URL: https://issues.apache.org/jira/browse/FELIX-3339 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger > Attachments: FELIX-3339_initial-proto.patch > > > The Felix Web Console currently has an embedded plugin only using traditional > Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. > These two should be consolidated and extended such that: > * Separate bundle (not embedded in the Web Console Bundle) > * one single plugin in Apache Felix > * Uses Java 6 JMX API if available > * Falls back to Java 5 JMX API if not Java 6 > * Falls back to regular Java API as a last step > * Provide Gogo Shell Commands > The advantage of using Java 6 API is to be able to inject lock information in > the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3951) Let users able to specify the directory used to temporarily store uploaded files
[ https://issues.apache.org/jira/browse/FELIX-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi resolved FELIX-3951. --- Resolution: Not A Problem > Let users able to specify the directory used to temporarily store uploaded > files > > > Key: FELIX-3951 > URL: https://issues.apache.org/jira/browse/FELIX-3951 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Simone Tripodi > Fix For: webconsole-4.0.2 > > Attachments: FELIX-3951.patch, Screen Shot 2013-03-05 at 2.36.05 > PM.pdf > > > As per subject, users should be able to dynamically switch the directory used > to temporarily store files, it would be good, for example, to set it to a > non-publicly writeable location, for security reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3951) Let users able to specify the directory used to temporarily store uploaded files
[ https://issues.apache.org/jira/browse/FELIX-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615767#comment-13615767 ] Simone Tripodi commented on FELIX-3951: --- Just to let you aware that the proposed patch is a way to let users handle http://seclists.org/fulldisclosure/2013/Mar/76 Would you available to discuss about it? TIA! > Let users able to specify the directory used to temporarily store uploaded > files > > > Key: FELIX-3951 > URL: https://issues.apache.org/jira/browse/FELIX-3951 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Simone Tripodi > Fix For: webconsole-4.0.2 > > Attachments: FELIX-3951.patch, Screen Shot 2013-03-05 at 2.36.05 > PM.pdf > > > As per subject, users should be able to dynamically switch the directory used > to temporarily store files, it would be good, for example, to set it to a > non-publicly writeable location, for security reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3951) Let users able to specify the directory used to temporarily store files
[ https://issues.apache.org/jira/browse/FELIX-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3951: -- Attachment: Screen Shot 2013-03-05 at 2.36.05 PM.pdf FELIX-3951.patch The proposed patch adds a configuration parameter to the OSGi Management Console, as shown in the screenshot, to allow users change, at run-time, the directory where storing temporarily uploaded files. > Let users able to specify the directory used to temporarily store files > --- > > Key: FELIX-3951 > URL: https://issues.apache.org/jira/browse/FELIX-3951 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Simone Tripodi > Fix For: webconsole-4.0.2 > > Attachments: FELIX-3951.patch, Screen Shot 2013-03-05 at 2.36.05 > PM.pdf > > > As per subject, users should be able to dynamically switch the directory used > to temporarily store files, it would be good, for example, to set it to a > non-publicly writeable location, for security reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3951) Let users able to specify the directory used to temporarily store uploaded files
[ https://issues.apache.org/jira/browse/FELIX-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated FELIX-3951: -- Summary: Let users able to specify the directory used to temporarily store uploaded files (was: Let users able to specify the directory used to temporarily store files) > Let users able to specify the directory used to temporarily store uploaded > files > > > Key: FELIX-3951 > URL: https://issues.apache.org/jira/browse/FELIX-3951 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Simone Tripodi > Fix For: webconsole-4.0.2 > > Attachments: FELIX-3951.patch, Screen Shot 2013-03-05 at 2.36.05 > PM.pdf > > > As per subject, users should be able to dynamically switch the directory used > to temporarily store files, it would be good, for example, to set it to a > non-publicly writeable location, for security reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3951) Let users able to specify the directory used to temporarily store files
Simone Tripodi created FELIX-3951: - Summary: Let users able to specify the directory used to temporarily store files Key: FELIX-3951 URL: https://issues.apache.org/jira/browse/FELIX-3951 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-4.0.0 Reporter: Simone Tripodi Fix For: webconsole-4.0.2 As per subject, users should be able to dynamically switch the directory used to temporarily store files, it would be good, for example, to set it to a non-publicly writeable location, for security reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3936) Main menu items hidden in the Configuration Status page
[
https://issues.apache.org/jira/browse/FELIX-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591720#comment-13591720
]
Simone Tripodi commented on FELIX-3936:
---
LOL, I thought it was intended :D
Chrome Version 24.0.1312.56 on Mac OS X 10.8.2
> Main menu items hidden in the Configuration Status page
> ---
>
> Key: FELIX-3936
> URL: https://issues.apache.org/jira/browse/FELIX-3936
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.0.0
>Reporter: Simone Tripodi
> Fix For: webconsole-4.0.2
>
> Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf, Screen Shot
> 2013-02-27 at 7.06.08 PM.pdf
>
>
> When visiting the Configuration Status page, the tabs in the body hide the
> main menu drop down menu items.
> The reproduce the issue is enough going to
> http://${host}:${port}/system/console/config# and then try to open any Main /
> OSGi / Web Console menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3936) Main menu items hidden in the Configuration Status page
[
https://issues.apache.org/jira/browse/FELIX-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi closed FELIX-3936.
-
Resolution: Not A Problem
the problem is not longer detected on /trunk since the menu has been converted
to a flat list of action buttons
> Main menu items hidden in the Configuration Status page
> ---
>
> Key: FELIX-3936
> URL: https://issues.apache.org/jira/browse/FELIX-3936
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.0.0
>Reporter: Simone Tripodi
> Fix For: webconsole-4.0.2
>
> Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf, Screen Shot
> 2013-02-27 at 7.06.08 PM.pdf
>
>
> When visiting the Configuration Status page, the tabs in the body hide the
> main menu drop down menu items.
> The reproduce the issue is enough going to
> http://${host}:${port}/system/console/config# and then try to open any Main /
> OSGi / Web Console menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3936) Main menu items hidden in the Configuration Status page
[
https://issues.apache.org/jira/browse/FELIX-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3936:
--
Attachment: Screen Shot 2013-02-27 at 7.06.08 PM.pdf
Hi Carsten! :)
Compiling & Installing the Apache Felix Inventory 0.0.1-SNAPSHOT and Apache
Felix Web Management Console 4.0.1-SNAPSHOT, the menu switched back to a flat
action list, as shown in the attached snapshot.
I am closing that issue as it is already fixed.
> Main menu items hidden in the Configuration Status page
> ---
>
> Key: FELIX-3936
> URL: https://issues.apache.org/jira/browse/FELIX-3936
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.0.0
>Reporter: Simone Tripodi
> Fix For: webconsole-4.0.2
>
> Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf, Screen Shot
> 2013-02-27 at 7.06.08 PM.pdf
>
>
> When visiting the Configuration Status page, the tabs in the body hide the
> main menu drop down menu items.
> The reproduce the issue is enough going to
> http://${host}:${port}/system/console/config# and then try to open any Main /
> OSGi / Web Console menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3936) Main menu items hidden in the Configuration Status page
[
https://issues.apache.org/jira/browse/FELIX-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3936:
--
Description:
When visiting the Configuration Status page, the tabs in the body hide the main
menu drop down menu items.
The reproduce the issue is enough going to
http://${host}:${port}/system/console/config# and then try to open any Main /
OSGi / Web Console menu.
was:
When visiting the Configuration Status page, the tabs in the body hide the main
menu drop down menu items.
The reproduce the issue is enough going to
{{http://:/system/console/config#}} and then try to open any
{{Main}} / {{OSGi}} / {{Web Console}} menu.
> Main menu items hidden in the Configuration Status page
> ---
>
> Key: FELIX-3936
> URL: https://issues.apache.org/jira/browse/FELIX-3936
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.0.0
>Reporter: Simone Tripodi
> Fix For: webconsole-4.0.2
>
> Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf
>
>
> When visiting the Configuration Status page, the tabs in the body hide the
> main menu drop down menu items.
> The reproduce the issue is enough going to
> http://${host}:${port}/system/console/config# and then try to open any Main /
> OSGi / Web Console menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3936) Main menu items hidden in the Configuration Status page
Simone Tripodi created FELIX-3936:
-
Summary: Main menu items hidden in the Configuration Status page
Key: FELIX-3936
URL: https://issues.apache.org/jira/browse/FELIX-3936
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.0.0
Reporter: Simone Tripodi
Fix For: webconsole-4.0.2
Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf
When visiting the Configuration Status page, the tabs in the body hide the main
menu drop down menu items.
The reproduce the issue is enough going to
{{http://:/system/console/config#}} and then try to open any
{{Main}} / {{OSGi}} / {{Web Console}} menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3936) Main menu items hidden in the Configuration Status page
[
https://issues.apache.org/jira/browse/FELIX-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-3936:
--
Attachment: Screen Shot 2013-02-27 at 5.22.40 PM.pdf
The attached screenshot shows the menu items are hidden when on the
Configuration Status page
> Main menu items hidden in the Configuration Status page
> ---
>
> Key: FELIX-3936
> URL: https://issues.apache.org/jira/browse/FELIX-3936
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.0.0
>Reporter: Simone Tripodi
> Fix For: webconsole-4.0.2
>
> Attachments: Screen Shot 2013-02-27 at 5.22.40 PM.pdf
>
>
> When visiting the Configuration Status page, the tabs in the body hide the
> main menu drop down menu items.
> The reproduce the issue is enough going to
> {{http://:/system/console/config#}} and then try to open any
> {{Main}} / {{OSGi}} / {{Web Console}} menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
