[xwiki-devs] [CONTRIB] Panel Macro
Hi all It's a following of the recent discussion on this list :) I have provided the basis for a java backed {{panel}} macro implementation. The source code is currently hosted on my github account, but I would like to move it under xwiki-contrib. See https://github.com/sauthieg/xwiki-panel-macro I've inited an extension page for this macro on the extension wiki: http://extensions.xwiki.org/xwiki/bin/view/Extension/Panel+Macro BTW, what is the type for a Java Macro ? Macro type seems to be restricted to Velocity ... Any interest ? --G
Hi Guillaume, On Nov 28, 2011, at 4:40 PM, Guillaume Sauthier (Objectweb) wrote:
Hi all
It's a following of the recent discussion on this list :)
I have provided the basis for a java backed {{panel}} macro implementation. The source code is currently hosted on my github account, but I would like to move it under xwiki-contrib.
I've created a repo for you: https://github.com/xwiki-contrib/macro-panel
See https://github.com/sauthieg/xwiki-panel-macro
I've inited an extension page for this macro on the extension wiki: http://extensions.xwiki.org/xwiki/bin/view/Extension/Panel+Macro
BTW, what is the type for a Java Macro ? Macro type seems to be restricted to Velocity …
It should be components (the other macro types are for old deprecated technology). I've fixed it and added the download link too for you (there are instructions when you edit the extension page on how to do that BTW).
Any interest ?
Yes looks useful to me and we should move it to xwiki-platform IMO (after reviewing it and finding a way to remove the hack that I saw there to get the panel doc, if possible ;)). Thanks! -Vincent
2011/11/28 Vincent Massol <[email protected]>
Hi Guillaume,
On Nov 28, 2011, at 4:40 PM, Guillaume Sauthier (Objectweb) wrote:
Hi all
It's a following of the recent discussion on this list :)
I have provided the basis for a java backed {{panel}} macro implementation. The source code is currently hosted on my github account, but I would like to move it under xwiki-contrib.
I've created a repo for you: https://github.com/xwiki-contrib/macro-panel
Thanks I've moved the code from my own repo to this one.
See https://github.com/sauthieg/xwiki-panel-macro
I've inited an extension page for this macro on the extension wiki: http://extensions.xwiki.org/xwiki/bin/view/Extension/Panel+Macro
BTW, what is the type for a Java Macro ? Macro type seems to be restricted to Velocity …
It should be components (the other macro types are for old deprecated technology). I've fixed it and added the download link too for you (there are instructions when you edit the extension page on how to do that BTW).
Oops, missed that point :)
Any interest ?
Yes looks useful to me and we should move it to xwiki-platform IMO (after reviewing it and finding a way to remove the hack that I saw there to get the panel doc, if possible ;)).
I'm sure that I couldn't invent that piece of code myself, someone had probably helped me :) Maybe you ;) BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies, and when launching the tests, a component was probably still using it. I found that class in an older commons module (3.2-milestone-x), but it was not very clean :'( The other one (and I gave up on this one) was that the RenderingTest was complaining about not being able to find a Parser component ... --G
Thanks! -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Nov 28, 2011, at 6:24 PM, Guillaume Sauthier (Objectweb) wrote:
2011/11/28 Vincent Massol <[email protected]>
Hi Guillaume,
On Nov 28, 2011, at 4:40 PM, Guillaume Sauthier (Objectweb) wrote:
Hi all
It's a following of the recent discussion on this list :)
I have provided the basis for a java backed {{panel}} macro implementation. The source code is currently hosted on my github account, but I would like to move it under xwiki-contrib.
I've created a repo for you: https://github.com/xwiki-contrib/macro-panel
Thanks I've moved the code from my own repo to this one.
I had forgotten to configure email notifications. Done now.
See https://github.com/sauthieg/xwiki-panel-macro
I've inited an extension page for this macro on the extension wiki: http://extensions.xwiki.org/xwiki/bin/view/Extension/Panel+Macro
BTW, what is the type for a Java Macro ? Macro type seems to be restricted to Velocity …
It should be components (the other macro types are for old deprecated technology). I've fixed it and added the download link too for you (there are instructions when you edit the extension page on how to do that BTW).
Oops, missed that point :)
Any interest ?
Yes looks useful to me and we should move it to xwiki-platform IMO (after reviewing it and finding a way to remove the hack that I saw there to get the panel doc, if possible ;)).
I'm sure that I couldn't invent that piece of code myself, someone had probably helped me :) Maybe you ;)
It was me indeed.
BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
and when launching the tests, a component was probably still using it. I found that class in an older commons module (3.2-milestone-x), but it was not very clean :'( The other one (and I gave up on this one) was that the RenderingTest was complaining about not being able to find a Parser component …
Can't think of an issue for this one, I'd need to try it out to see the full error. Thanks -Vincent
--G
Thanks! -Vincent
BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
and when launching the tests, a component was probably still using it. I found that class in an older commons module (3.2-milestone-x), but it was not very clean :'( The other one (and I gave up on this one) was that the RenderingTest was complaining about not being able to find a Parser component …
Can't think of an issue for this one, I'd need to try it out to see the full error.
I'll create a branch for that stuff so that you can take a look at it. Thanks --G
Thanks -Vincent
--G
Thanks! -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
2011/11/29 Guillaume Sauthier (Objectweb) <[email protected]>
BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
In fact, the error comes from the fact that my code is using DocumentModelBridge The only artifact I found providing that interface is org.xwiki.platform:xwiki-core-bridge And its latest version is 3.0.1, and some components provided by this module are still using the AbstractLogEnabled class ... Is there a replacement for DocumentModelBridge in 3.3.x versions ? --G
On Tue, Nov 29, 2011 at 10:40 AM, Guillaume Sauthier (Objectweb) <[email protected]> wrote:
2011/11/29 Guillaume Sauthier (Objectweb) <[email protected]>
BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
In fact, the error comes from the fact that my code is using DocumentModelBridge The only artifact I found providing that interface is org.xwiki.platform:xwiki-core-bridge And its latest version is 3.0.1, and some components provided by this module are still using the AbstractLogEnabled class ...
Is there a replacement for DocumentModelBridge in 3.3.x versions ?
since 3.0 all platform modules had been renamed as org.xwiki.platform:xwiki-platform-* and some moved to commons but it's pretty rare something is removed. You can check in http://maven.xwiki.org/snapshots/org/xwiki/platform/. The bridge is non in org.xwiki.platform:xwiki-platform-bridge
--G _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Tue, Nov 29, 2011 at 10:48 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 29, 2011 at 10:40 AM, Guillaume Sauthier (Objectweb) <[email protected]> wrote:
2011/11/29 Guillaume Sauthier (Objectweb) <[email protected]>
BTW, I tried to move to latest xwiki-commons module (3.3-milestone-1), and I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
In fact, the error comes from the fact that my code is using DocumentModelBridge The only artifact I found providing that interface is org.xwiki.platform:xwiki-core-bridge And its latest version is 3.0.1, and some components provided by this module are still using the AbstractLogEnabled class ...
Is there a replacement for DocumentModelBridge in 3.3.x versions ?
since 3.0 all platform modules had been renamed as org.xwiki.platform:xwiki-platform-* and some moved to commons but it's pretty rare something is removed.
You can check in http://maven.xwiki.org/snapshots/org/xwiki/platform/.
The bridge is non in org.xwiki.platform:xwiki-platform-bridge
s/non/now/
--G _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
Thanks That's better now. I'm now facing an error where my ComponentManager in the tests cannot find a suitable Parser instance. org.xwiki.component.manager.ComponentLookupException: Can't find descriptor for the component [role = [org.xwiki.rendering.parser.Parser] hint = [xwiki/2.0]] at org.xwiki.component.embed.EmbeddableComponentManager.initialize(EmbeddableComponentManager.java:315) at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:112) at org.xwiki.rendering.test.integration.RenderingTest.runTestInternal(RenderingTest.java:125) --G 2011/11/29 Thomas Mortagne <[email protected]>
On Tue, Nov 29, 2011 at 10:48 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 29, 2011 at 10:40 AM, Guillaume Sauthier (Objectweb) <[email protected]> wrote:
2011/11/29 Guillaume Sauthier (Objectweb) < [email protected]>
BTW, I tried to move to latest xwiki-commons module
(3.3-milestone-1),
and
I hit some issues, so I did not incorporate theses changes in what I pushed. The first one is that the AbstractLogEnabled class is no more in the dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
In fact, the error comes from the fact that my code is using DocumentModelBridge The only artifact I found providing that interface is org.xwiki.platform:xwiki-core-bridge And its latest version is 3.0.1, and some components provided by this module are still using the AbstractLogEnabled class ...
Is there a replacement for DocumentModelBridge in 3.3.x versions ?
since 3.0 all platform modules had been renamed as org.xwiki.platform:xwiki-platform-* and some moved to commons but it's pretty rare something is removed.
You can check in http://maven.xwiki.org/snapshots/org/xwiki/platform/.
The bridge is non in org.xwiki.platform:xwiki-platform-bridge
s/non/now/
--G _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
I've added xwiki-rendering-standalone as dependency (that groups xwiki2.0 syntax parser and a lot of other stuff). And I have now: java.lang.AbstractMethodError: org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.createWikiModelParser()Lorg/wikimodel/wem/IWikiParser; at org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.parse(AbstractWikiModelParser.java:140) at org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.parse(AbstractWikiModelParser.java:99) at org.xwiki.rendering.test.integration.RenderingTest.runTestInternal(RenderingTest.java:126) --G 2011/11/29 Guillaume Sauthier (Objectweb) <[email protected]>
Thanks
That's better now.
I'm now facing an error where my ComponentManager in the tests cannot find a suitable Parser instance.
org.xwiki.component.manager.ComponentLookupException: Can't find descriptor for the component [role = [org.xwiki.rendering.parser.Parser] hint = [xwiki/2.0]] at org.xwiki.component.embed.EmbeddableComponentManager.initialize(EmbeddableComponentManager.java:315) at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:112) at org.xwiki.rendering.test.integration.RenderingTest.runTestInternal(RenderingTest.java:125)
--G
2011/11/29 Thomas Mortagne <[email protected]>
On Tue, Nov 29, 2011 at 10:48 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 29, 2011 at 10:40 AM, Guillaume Sauthier (Objectweb) <[email protected]> wrote:
2011/11/29 Guillaume Sauthier (Objectweb) < [email protected]>
> BTW, I tried to move to latest xwiki-commons module
(3.3-milestone-1),
and > I hit some issues, so I did not incorporate theses changes in what I pushed. > The first one is that the AbstractLogEnabled class is no more in the > dependencies,
To get logs now you just need to get the SLF4J logger injected, see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HCompo...
My component is not yet using logging, I suspect that there is an old component somewhere in my dependencies that is using the AbstractLogEnabled class, and when the ComponentManager find it, it cannot load that class ...
In fact, the error comes from the fact that my code is using DocumentModelBridge The only artifact I found providing that interface is org.xwiki.platform:xwiki-core-bridge And its latest version is 3.0.1, and some components provided by this module are still using the AbstractLogEnabled class ...
Is there a replacement for DocumentModelBridge in 3.3.x versions ?
since 3.0 all platform modules had been renamed as org.xwiki.platform:xwiki-platform-* and some moved to commons but it's pretty rare something is removed.
You can check in http://maven.xwiki.org/snapshots/org/xwiki/platform/.
The bridge is non in org.xwiki.platform:xwiki-platform-bridge
s/non/now/
--G _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Guillaume Sauthier (Objectweb) -
Thomas Mortagne -
Vincent Massol