Re: [xwiki-devs] [Proposal] Plan to remove XWiki Enterprise

2015-03-09 Thread Ecaterina Moraru (Valica)
Just some mentions about these removes/moves:
- We moved before things from XE to Platform. It's a pain if you want to
'blame' the source and in the JIRA issue we don't have a link from where
the page was moved from. Tracking the history for a moved page is difficult
and a comment stating where the location was is useful.
- What will happen with the history if we remove the XE repository?

Although the history + the blame use case might not be interesting for
everyone, myself I'm using it often to understand the initial purpose of
the feature, to determine if it's a regression, to know which person to
contact, etc.

Do we have a strategy for keeping the history somehow?

Thanks,
Caty

On Sat, Mar 7, 2015 at 11:21 AM, vinc...@massol.net vinc...@massol.net
wrote:






 On 7 Mar 2015 at 02:23:35, Eduard Moraru (enygma2...@gmail.com(mailto:
 enygma2...@gmail.com)) wrote:

  Hi,
 
  On Tue, Mar 3, 2015 at 11:38 AM, Thomas Mortagne
  wrote:
 
   Sounds good. I would take this opportunity to not migrate what's in
   xwiki-enterprise-installers/xwiki-enterprise-installer-generic and
   xwiki-enterprise-installers/xwiki-enterprise-installer-window but
   that's another discussion.
  
   On Tue, Mar 3, 2015 at 10:23 AM, vinc...@massol.net
   wrote:
Hi devs,
   
I’d like to work on the following (and any help will be most
 welcome).
   
What

   
1 - Finish moving XE pages into xwiki-platform
2 - Introduce flavor concept in xwiki-platform:
   
xwiki-platform/xwiki-platform-core/xwiki-platform-flavors/
|_ xwiki-platform-flavor-minimal/
|_ xwiki-platform-flavor-xwiki/
|_ xwiki-platform-flavor-xwiki-main/
|_ xwiki-platform-flavor-xwiki-wiki/
|_ xwiki-platform-flavor-test/
   
where:
* minimal: the base for the “xwiki” and “test” flavors. Contains the
   core deps that need to be present in any xwiki runtime
* xwiki: the only runtime flavor that we distribute as part of the
 xwiki
   github organization. A generic flavor with no vertical. See
   http://markmail.org/message/keo7cs6u3fuf676w
* test: minimal + the export feature (since when writing functional
   tests there's is often the need to export pages as XAR)
  
 
  Wouldn't basic import/export be part of the minimal flavor? Not sure I
  understand the difference between minimal and test.

 The minimal flavor is theoretically supposed to be an empty flavor, it
 contains the bare minimum for XWiki to start. Right now this means a lot of
 modules (those that are defined in the Packager plugin). In the future, as
 we divide modules into smaller feature set, we should be able to reduce the
 size of the minimal flavor. Just to give one example, the WYSIWYG editor
 shouldn’t be something that you have in the minimal flavor; it shouldn’t be
 required to start XWiki and it should be possible to install the WYSIWYG
 editor if you want.

 The test flavor shouldn’t exist: the functional tests for each module
 should have a dep on the minimal flavor + all the deps for what they are
 testing. In the past, I added the export dep in the Packager plugin because
 the way I work when I develop a module is like this:
 * Code the API up to a point
 * Create the functional test infrastructure and create a basic functional
 test
 * Run it to generate a runtime XWiki instance (in target/xwiki)
 * Create the UI in that XWiki instance and export the pages to
 src/main/resources
 * Iterate: Add more test lines at the same time as I add the wiki pages

 So for this way of working, I needed to be able to export wiki page easily
 and I was fed up to have to import the export feature all the time so I put
 it in the Packager plugin.

 So we can decide if we want to continue this or if there’s a better flow.
 When I defined the test flavor above, I was thinking about minimal + export
 module.

 Hope it’s more clear :)

 Thanks
 -Vincent

3 - Modify the XWiki Packager Plugin:
   
* Do not include any dep by default, instead only rely on the plugin
   user’s declared deps. Users of the plugin will use flavors as deps.
* Split the current PackageMojo into 2 mojos:
** WarMojo: generates a WAR file (WAR distribution)
** StandalonePackageMojo: generates a standalone ZIP (Jetty+HSQLDB)
   
4 - Refactor functional tests in xwiki-platform to use the new
   StandalonePackageMojo with deps on xwiki-platform-flavor-test
   
5 - Introduce Distribution modules in xwiki-platform:
   
xwiki-platform/xwiki-platform-distributions/
|_ xwiki-platform-distribution-war/
|_ xwiki-platform-distribution-standalone/
|_ xwiki-platform-distribution-installers/
|_ xwiki-platform-distribution-images/
|_ xwiki-platform-distribution-image-mysql/
|_ (more later)
|_ xwiki-platform-distribution-archetype/
|_ xwiki-platform-distribution-xar/
   
where:
   
* xwiki-platform-distribution-war and
   xwiki-platform-distribution-standalone will use the XWiki Packager
 Plugin’s
   mojos and will 

Re: [xwiki-devs] [Proposal] Plan to remove XWiki Enterprise

2015-03-09 Thread Thomas Mortagne
I usually use https://github.com/git/git/tree/master/contrib/subtree
for this kind of things, it's starting to be a bit old but it work
well. For example I used it when moving deprecated platform modules to
their own repository on contrib like
https://github.com/xwiki-contrib/xwiki-platform-wiki-manager.

On Mon, Mar 9, 2015 at 3:57 PM, Sergiu Dumitriu ser...@xwiki.com wrote:
 That is doable, in two ways:

 1. Merge xwiki-enterprise into xwiki-platform, move the modules we want
 to keep in their new location, delete the modules we don't need anymore.
 This requires planning where every module goes in advance, and fixes
 everything at once.

 2. Extract each module that we want to keep in a separate git
 repository, using https://gist.github.com/sdumitriu/1993357 (I need to
 update this with a better version), and merge it into xwiki-platform.
 This lets us handle each module at a time, but extracting a module takes
 a while.

 On 03/09/2015 08:56 AM, Ecaterina Moraru (Valica) wrote:
 Just some mentions about these removes/moves:
 - We moved before things from XE to Platform. It's a pain if you want to
 'blame' the source and in the JIRA issue we don't have a link from where
 the page was moved from. Tracking the history for a moved page is difficult
 and a comment stating where the location was is useful.
 - What will happen with the history if we remove the XE repository?

 Although the history + the blame use case might not be interesting for
 everyone, myself I'm using it often to understand the initial purpose of
 the feature, to determine if it's a regression, to know which person to
 contact, etc.

 Do we have a strategy for keeping the history somehow?

 --
 Sergiu Dumitriu
 http://purl.org/net/sergiu
 ___
 devs mailing list
 devs@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/devs



-- 
Thomas Mortagne
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs


Re: [xwiki-devs] [Proposal] Plan to remove XWiki Enterprise

2015-03-09 Thread Sergiu Dumitriu
That is doable, in two ways:

1. Merge xwiki-enterprise into xwiki-platform, move the modules we want
to keep in their new location, delete the modules we don't need anymore.
This requires planning where every module goes in advance, and fixes
everything at once.

2. Extract each module that we want to keep in a separate git
repository, using https://gist.github.com/sdumitriu/1993357 (I need to
update this with a better version), and merge it into xwiki-platform.
This lets us handle each module at a time, but extracting a module takes
a while.

On 03/09/2015 08:56 AM, Ecaterina Moraru (Valica) wrote:
 Just some mentions about these removes/moves:
 - We moved before things from XE to Platform. It's a pain if you want to
 'blame' the source and in the JIRA issue we don't have a link from where
 the page was moved from. Tracking the history for a moved page is difficult
 and a comment stating where the location was is useful.
 - What will happen with the history if we remove the XE repository?
 
 Although the history + the blame use case might not be interesting for
 everyone, myself I'm using it often to understand the initial purpose of
 the feature, to determine if it's a regression, to know which person to
 contact, etc.
 
 Do we have a strategy for keeping the history somehow?

-- 
Sergiu Dumitriu
http://purl.org/net/sergiu
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs


[xwiki-devs] xwiki home page throws NullPointerException

2015-03-09 Thread glen sane
Hi,I installed xwiki-enterprise-web-6.4.2.war on tomcat 7.  I followed the 
installation instruction mentioned 
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationTomcat.  But I 
got following error on main page (http://localhost:8080/xwiki/bin/view/Main/)
org.apache.catalina.core.StandardWrapperValve invokeSEVERE: Servlet.service() 
for servlet [action] in context with path [/xwiki] threw 
exceptionjava.lang.NullPointerExceptionat 
com.xpn.xwiki.web.Utils.getContextComponentManager(Utils.java:699)at 
com.xpn.xwiki.web.Utils.getComponent(Utils.java:756)at 
com.xpn.xwiki.web.Utils.getComponent(Utils.java:723)at 
com.xpn.xwiki.web.XWikiRequestProcessor.processPath(XWikiRequestProcessor.java:47)
at 
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:154)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)  
  at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)   
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina
 .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:115)at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:127)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
at 
org.xwiki.container.servlet.filters.internal.SetHTTPHeaderFilter.doFilter(SetHT
 TPHeaat 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
at 
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:66) 
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
at 
org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(Sav
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
at 
org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(Set
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCh
at org.apache.catalina.core.ApplicationFilt
 erChain.doFilter(ApplicationFilterChain.javaat 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:50
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)   
 at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)   
 at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)   
 at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421) 
   at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.jav
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtoco
at org.apache.tomcat.util.net.JIoE
 ndpoint$SocketProcessor.run(JIoEndpoint.java:316)at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) 
   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627) 
   at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:863)
Please help me.Thanks,Glen
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs


Re: [xwiki-devs] devs Digest, Vol 93, Issue 12

2015-03-09 Thread Eduard Moraru
Hi,

Please reply to individual mails, not to digests, since they make having a
conversation difficult.

Regarding your question, please have a look at the existing
guides/documentation on internationalizing XWiki applications [1] and, more
generally, by using the Localization Module [2].

In your particular case, in a JSX, you need to enable content parsing on
the JSX object (Parse content: Yes) and then use a velocity call to the
Localization Script service [3].

Example:
alert($services.localization.render('my.hello.world.key'));
...where 'my.hello.world.key' is a translation key registered in a
translation document or whatever you choose, according to the documentation
[4]

Thanks,
Eduard

--
[1]
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplications
[2] http://extensions.xwiki.org/xwiki/bin/view/Extension/Localization+Module
[3]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Localization+Scripting
[4]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Localization+Module#HRegisterawikitranslation

On Mon, Mar 9, 2015 at 6:19 AM, /xin蜗牛 445686...@qq.com wrote:

 How I Can Internationalizing ‍Hello World?



 -- Original --
 From:  devs-requ...@xwiki.org;devs-requ...@xwiki.org;
 Date:  Sun, Mar 8, 2015 08:00 PM
 To:  devsdevs@xwiki.org;

 Subject:  devs Digest, Vol 93, Issue 12



 Send devs mailing list submissions to
 devs@xwiki.org

 To subscribe or unsubscribe via the World Wide Web, visit
 http://lists.xwiki.org/mailman/listinfo/devs
 or, via email, send a message with subject or body 'help' to
 devs-requ...@xwiki.org

 You can reach the person managing the list at
 devs-ow...@xwiki.org

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of devs digest...


 Today's Topics:

1. Re: How Internationalizing UIExtension Module? (Eduard Moraru)


 --

 Message: 1
 Date: Sun, 8 Mar 2015 00:40:29 +0200
 From: Eduard Moraru enygma2...@gmail.com
 To: XWiki Developers devs@xwiki.org
 Subject: Re: [xwiki-devs] How Internationalizing UIExtension Module?
 Message-ID:
 
 cadgdyyjay5tz5equpevmlt4ktjvkwn9ifdxs5t_xo+cxtmv...@mail.gmail.com
 Content-Type: text/plain; charset=UTF-8

 Hi,

 You would need to try to be more specific in your question. What is it that
 you want to achieve, what did you try and did not work, etc.

 Thanks,
 Eduard

 On Sat, Mar 7, 2015 at 11:02 AM, /xin?? 445686...@qq.com wrote:

  Hi?
 I want to know How Internationalizing UIExtension Module??
 Thanks?
  ___
  devs mailing list
  devs@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/devs
 


 --

 Subject: Digest Footer

 ___
 devs mailing list
 devs@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/devs


 --

 End of devs Digest, Vol 93, Issue 12
 
 ___
 devs mailing list
 devs@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/devs


___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs