25 Aug
2009
25 Aug
'09
11:16 a.m.
On Tue, Aug 25, 2009 at 08:18, Asiri
Rathnayake<asiri.rathnayake(a)gmail.com> wrote:
Hi Leon,
I'm not the best person to answer your questions but I'll try to answer some
of them until someone else does ;)
On Tue, Aug 25, 2009 at 11:22 AM, Leon Wang <freeleons(a)gmail.com> wrote:
http://dev.xwiki.org/xwiki/bin/view/Community/DebugXEWithEclipse
should work well except for the new WYSIWYG and the screenshots has
been made with Eclipse 3.3 but if you know Eclipse you should not be
too lost ;)
Hi guys,
I really love Xwiki. I think it is pretty and cool. I hope I could build a
tool base on Xwiki Platform for my master thesis. And I want to contribute
to Xwiki Community too. Should I create a new module or component. I could
not distinguish those two.
A maven module is not an implementation detail, it's a way of organizing
related functionalities into a single distributable package. For an example
we have a module that collects all the code related to xwiki rendering...
A component is an implementation detail. A component allows you to define a
high level interface and let you provide different implementations. And
clients of your component will consume your component in a declarative
fashion like:
@Requirement("default")
private LeonsComponent lcomp;
or
LeonsComponent lcomp = componentManager.lookup(LeonsComponent.class,
"funky");
As you can see there is no tight coupling between the clients of
LeonsComponent and the actual LeonsComponent implementation, we just lookup
for an implementation with a "role-hint"
For more information you can refer
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
Finally, a single module may contain a lot of components...
I tried follow this tutorial (
http://dev.xwiki.org/xwiki/bin/view/Community/Debugging) more than 10
times
for automatically build and run Xwiki in Eclipse.
The mostly used method for XWiki development (IMO) is using eclipse +
m2eclipse as a source code editor and a terminal which is used to build
different projects. But you can use eclipse + m2eclipse alone for
development if you prefer.
Debugging with eclipse tutorial might be little outdated but last time i
checked it worked pretty well...
Let's say not worst than in Eclipse 3.4 ;)
There is a quite annoying bug around resources management in m2eclipse
which make it loose them all the time... So you have to trick a
little, i will add something in
http://dev.xwiki.org/xwiki/bin/view/Community/DebugXEWithEclipse_Troublesho…
For Import and link maven jar projects to debug
secttion, I find how to
Link
Jar project to the web project is vague(
http://dev.xwiki.org/xwiki/bin/view/Community/DebugXEWithEclipse_ImportJarP…
),
for "Since M2Eclipse 0.9.4, you need to install Maven Integration for WTP
then you just have to add the imported maven jar project in the pom.xml
file
of the project xe-debug." Could any guru explain a little about how write
pom.xml file for the imported maven jar project?
Does Eclipse 3.5 JEE Galileo work well with Maven and everything？
Thomas Mortagne will answer you on this :)
- Asiri
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne