Re: [xwiki-devs] [PROPOSAL] Yet another new platform flavor proposal or how to get rid of XWiki Enterprise

[Vincent Massol]

> On 14 Apr 2017, at 22:34, Sergiu Dumitriu  wrote:
> 
> On 04/14/2017 09:51 AM, Thomas Mortagne wrote:
>> Here is a new proposal on this subject.
>> 
>> This supersets the following threads:
>> * http://markmail.org/message/mhhurc7lbyfanph7
>> * http://markmail.org/message/nav5a77hzmhq4gq6
>> * http://markmail.org/message/fd5ijxdquzdhtykw
>> 
>> We discussed with other committers (Vincent and Ludovic) and came to
>> the conclusion that it was not core dev team job to provide a specific
>> flavor like Knowledge Base and that we should focus only on a very
>> generic one (pretty much XE without the Blog).
>> 
>> Here are the details:
>> 
>> = One flavor
>> 
>> We develop only 1 flavor located in xwiki-platform repository. It's a
>> generic flavor not targeting any specific use case (the first version
>> with be XE without the Blog). We will discuss the name in another
>> thread later, let's call it "Wiki Flavor" for now.
>> 
>> Of course everyone is free and welcomed to build lots of contrib
>> flavors which will be proposed when you install XWiki ("Development
>> Flavor", "Demo Flavor", "Blog Flavor", etc.).
>> 
>> = No "Base flavor"
>> 
>> But platform will provide an extension that can be used as dependency
>> by various flavors to get "core" UI extensions that we think make
>> sense in any kind of flavor.
>> 
>> = Demo package
>> 
>> We currently have a jetty/hsqldb based package in platform which let
>> you choose which flavor you want. We will show it in the download
>> page.
>> 
>> We will add another one with the Wiki Flavor already installed in it
>> (pretty much like the XE jetty/hsqldb package). Listed on the download
>> page too.
> 
> Why? Is it that bad to always let the user choose the flavor? We can
> split flavors into three levels:
> 
> - The "Raw XWiki" flavor is on top, pre-selected
> - Recommended flavors are next, in a list
> - All flavors behind a "browse more" button
> 
> The only case when leaving the standalone package empty might fail is in
> a no-internet environment, but for this we can have a workaround: make
> the jars, xars and poms needed for installing the base flavor available
> in the package.

Yes the reason is for the offline test use case.

Bundling all flavors could be a solution indeed but it seems a bit overkill to 
me, especially if the user only wants a single one, don’t you think?

Thanks
-Vincent

> Everything else sounds good, +1.
> 
>> We don't maintain exe/jar installers anymore in platform, they die
>> with XWiki Enterprise. They are a real pain to maintain and we are
>> actually failing since they don't really work properly everywhere they
>> are supposed to work. It does not worth the trouble for what is not a
>> production ready package and it's better anyway to make more clear
>> XWiki is a server thing.
>> 
>> WDYT ?
> 
> 
> -- 
> Sergiu Dumitriu
> http://purl.org/net/sergiu/

Re: [xwiki-devs] [PROPOSAL] Yet another new platform flavor proposal or how to get rid of XWiki Enterprise

[Sergiu Dumitriu]

On 04/14/2017 09:51 AM, Thomas Mortagne wrote:
> Here is a new proposal on this subject.
> 
> This supersets the following threads:
> * http://markmail.org/message/mhhurc7lbyfanph7
> * http://markmail.org/message/nav5a77hzmhq4gq6
> * http://markmail.org/message/fd5ijxdquzdhtykw
> 
> We discussed with other committers (Vincent and Ludovic) and came to
> the conclusion that it was not core dev team job to provide a specific
> flavor like Knowledge Base and that we should focus only on a very
> generic one (pretty much XE without the Blog).
> 
> Here are the details:
> 
> = One flavor
> 
> We develop only 1 flavor located in xwiki-platform repository. It's a
> generic flavor not targeting any specific use case (the first version
> with be XE without the Blog). We will discuss the name in another
> thread later, let's call it "Wiki Flavor" for now.
> 
> Of course everyone is free and welcomed to build lots of contrib
> flavors which will be proposed when you install XWiki ("Development
> Flavor", "Demo Flavor", "Blog Flavor", etc.).
> 
> = No "Base flavor"
> 
> But platform will provide an extension that can be used as dependency
> by various flavors to get "core" UI extensions that we think make
> sense in any kind of flavor.
> 
> = Demo package
> 
> We currently have a jetty/hsqldb based package in platform which let
> you choose which flavor you want. We will show it in the download
> page.
> 
> We will add another one with the Wiki Flavor already installed in it
> (pretty much like the XE jetty/hsqldb package). Listed on the download
> page too.

Why? Is it that bad to always let the user choose the flavor? We can
split flavors into three levels:

- The "Raw XWiki" flavor is on top, pre-selected
- Recommended flavors are next, in a list
- All flavors behind a "browse more" button

The only case when leaving the standalone package empty might fail is in
a no-internet environment, but for this we can have a workaround: make
the jars, xars and poms needed for installing the base flavor available
in the package.

Everything else sounds good, +1.

> We don't maintain exe/jar installers anymore in platform, they die
> with XWiki Enterprise. They are a real pain to maintain and we are
> actually failing since they don't really work properly everywhere they
> are supposed to work. It does not worth the trouble for what is not a
> production ready package and it's better anyway to make more clear
> XWiki is a server thing.
> 
> WDYT ?


-- 
Sergiu Dumitriu
http://purl.org/net/sergiu/

Re: [xwiki-devs] [error] Building XWiki

[Vincent Massol]

Hi,

> On 14 Apr 2017, at 20:10, Sarthak Gupta  wrote:
> 
> After sorting out the previous error with some effort, I am getting another
> error. Could someone please tell me how to resolve this?
> 
> After giving "mvn clean install" command.

[snip]

> [ERROR] Failed to execute goal on project
> application-ckeditor-test-pageobjects: Could not resolve dependencies for
> project
> org.xwiki.contrib:application-ckeditor-test-pageobjects:jar:1.14-SNAPSHOT:
> Could not find artifact org.xwiki.platform:xwiki-platform-test-ui:jar:9.1.2
> in central (https://repo.maven.apache.org/maven2) -> [Help 1]

This probably means you don’t have the right maven remote repo configured in 
your settings.xml.

See http://dev.xwiki.org/xwiki/bin/view/Community/Building#HInstallingMaven

Thanks
-Vincent

> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :application-ckeditor-test-pageobjects

[xwiki-devs] [error] Building XWiki

[Sarthak Gupta]

After sorting out the previous error with some effort, I am getting another
error. Could someone please tell me how to resolve this?

After giving "mvn clean install" command.
.
.
.
.
T/application-ckeditor-test-1.14-SNAPSHOT.pom
[INFO]

[INFO]

[INFO] Building CKEditor Integration Test Page Objects 1.14-SNAPSHOT
[INFO]

Downloading:
https://repo.maven.apache.org/maven2/org/xwiki/platform/xwiki-platform-test-ui/9.1.2/xwiki-platform-test-ui-9.1.2.pom
[WARNING] The POM for org.xwiki.platform:xwiki-platform-test-ui:jar:9.1.2
is missing, no dependency information available
Downloading:
https://repo.maven.apache.org/maven2/org/xwiki/platform/xwiki-platform-test-ui/9.1.2/xwiki-platform-test-ui-9.1.2.jar
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] CKEditor Integration Parent POM  SUCCESS [
10.360 s]
[INFO] CKEditor Integration Base .. SUCCESS [05:06
min]
[INFO] CKEditor Integration Plugins ... SUCCESS [01:02
min]
[INFO] CKEditor Integration Test Modules .. SUCCESS [
 0.249 s]
[INFO] CKEditor Integration Test Page Objects . FAILURE [
 9.993 s]
[INFO] CKEditor Integration WebJar  SKIPPED
[INFO] CKEditor Integration UI  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 06:56 min
[INFO] Finished at: 2017-04-14T22:40:32+05:30
[INFO] Final Memory: 37M/126M
[INFO]

[ERROR] Failed to execute goal on project
application-ckeditor-test-pageobjects: Could not resolve dependencies for
project
org.xwiki.contrib:application-ckeditor-test-pageobjects:jar:1.14-SNAPSHOT:
Could not find artifact org.xwiki.platform:xwiki-platform-test-ui:jar:9.1.2
in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :application-ckeditor-test-pageobjects

Re: [xwiki-devs] [PROPOSAL] Yet another new platform flavor proposal or how to get rid of XWiki Enterprise

[Vincent Massol]

Hi,

> On 14 Apr 2017, at 15:51, Thomas Mortagne  wrote:
> 
> Here is a new proposal on this subject.
> 
> This supersets the following threads:
> * http://markmail.org/message/mhhurc7lbyfanph7
> * http://markmail.org/message/nav5a77hzmhq4gq6
> * http://markmail.org/message/fd5ijxdquzdhtykw
> 
> We discussed with other committers (Vincent and Ludovic) and came to
> the conclusion that it was not core dev team job to provide a specific
> flavor like Knowledge Base and that we should focus only on a very
> generic one (pretty much XE without the Blog).
> 
> Here are the details:
> 
> = One flavor
> 
> We develop only 1 flavor located in xwiki-platform repository. It's a
> generic flavor not targeting any specific use case (the first version
> with be XE without the Blog). We will discuss the name in another
> thread later, let's call it "Wiki Flavor" for now.
> 
> Of course everyone is free and welcomed to build lots of contrib
> flavors which will be proposed when you install XWiki ("Development
> Flavor", "Demo Flavor", "Blog Flavor", etc.).
> 
> = No "Base flavor"
> 
> But platform will provide an extension that can be used as dependency
> by various flavors to get "core" UI extensions that we think make
> sense in any kind of flavor.
> 
> = Demo package
> 
> We currently have a jetty/hsqldb based package in platform which let
> you choose which flavor you want. We will show it in the download
> page.
> 
> We will add another one with the Wiki Flavor already installed in it
> (pretty much like the XE jetty/hsqldb package). Listed on the download
> page too.
> 
> We don't maintain exe/jar installers anymore in platform, they die
> with XWiki Enterprise. They are a real pain to maintain and we are
> actually failing since they don't really work properly everywhere they
> are supposed to work. It does not worth the trouble for what is not a
> production ready package and it's better anyway to make more clear
> XWiki is a server thing.
> 
> WDYT ?

Fine with me obviously (since we discussed it together :)).

Thanks
-Vincent

> Thanks,
> -- 
> Thomas Mortagne

[xwiki-devs] [PROPOSAL] Yet another new platform flavor proposal or how to get rid of XWiki Enterprise

[Thomas Mortagne]

Here is a new proposal on this subject.

This supersets the following threads:
* http://markmail.org/message/mhhurc7lbyfanph7
* http://markmail.org/message/nav5a77hzmhq4gq6
* http://markmail.org/message/fd5ijxdquzdhtykw

We discussed with other committers (Vincent and Ludovic) and came to
the conclusion that it was not core dev team job to provide a specific
flavor like Knowledge Base and that we should focus only on a very
generic one (pretty much XE without the Blog).

Here are the details:

= One flavor

We develop only 1 flavor located in xwiki-platform repository. It's a
generic flavor not targeting any specific use case (the first version
with be XE without the Blog). We will discuss the name in another
thread later, let's call it "Wiki Flavor" for now.

Of course everyone is free and welcomed to build lots of contrib
flavors which will be proposed when you install XWiki ("Development
Flavor", "Demo Flavor", "Blog Flavor", etc.).

= No "Base flavor"

But platform will provide an extension that can be used as dependency
by various flavors to get "core" UI extensions that we think make
sense in any kind of flavor.

= Demo package

We currently have a jetty/hsqldb based package in platform which let
you choose which flavor you want. We will show it in the download
page.

We will add another one with the Wiki Flavor already installed in it
(pretty much like the XE jetty/hsqldb package). Listed on the download
page too.

We don't maintain exe/jar installers anymore in platform, they die
with XWiki Enterprise. They are a real pain to maintain and we are
actually failing since they don't really work properly everywhere they
are supposed to work. It does not worth the trouble for what is not a
production ready package and it's better anyway to make more clear
XWiki is a server thing.

WDYT ?

Thanks,
-- 
Thomas Mortagne

Re: [xwiki-devs] [Contrib] request for 2 project repositories

[Ludovic Dubost]

Thanks !

Ludovic

--
*Ludovic Dubost*
*Founder and CEO*
ludo...@xwiki.com
skype: ldubost
Blog: http://blog.ludovic.orgTry XWiki on the cloud
  - Try Cryptpad: Secure
realtime Wysiwyg Editing 


On Fri, Apr 14, 2017 at 9:51 AM, Thomas Mortagne 
wrote:

> I also created Jira projects for them.
>
> Here are all the links:
>
> * https://github.com/xwiki-contrib/application-search-spellcheck
> * https://jira.xwiki.org/browse/SCSEARCH
>
> * https://github.com/xwiki-contrib/application-office365
> * https://jira.xwiki.org/browse/MSOFFICEOL
>
> On Fri, Apr 14, 2017 at 9:20 AM, Thomas Mortagne
>  wrote:
> > Done.
> >
> > Enjoy !
> >
> > On Fri, Apr 14, 2017 at 8:52 AM, Ludovic Dubost 
> wrote:
> >> Hi,
> >>
> >> I would like to request two projects repositories for:
> >>
> >> 1/ Search Extension Spellchecker
> >>
> >> application-search-spellcheck
> >>
> >> This extension uses jazzy (https://github.com/tupilabs/jazzy) to
> provide
> >> spell checking of search queries (in english for now)
> >>
> >> 2/ Office365 integration
> >>
> >> application-office365
> >>
> >> This extension provides a macro allowing to display office365 documents
> >> inside XWiki, as well as display search results on office365 as a
> widget in
> >> the solr search screen (it needs a UI extension for this which I will
> >> propose in a jira issue)
> >>
> >> Thanks
> >> Ludovic
> >>
> >>
> >> --
> >> *Ludovic Dubost*
> >> *Founder and CEO*
> >> ludo...@xwiki.com
> >> skype: ldubost
> >> Blog: http://blog.ludovic.org
> >>  9e?d=http%3A%2F%2Fblog.ludovic.org>Try
> >> XWiki on the cloud
> >>  9e?d=http%3A%2F%2Fwww.xwiki.com%2Fen%2Fproducts%2Ftry-xwiki-cloud>
> >> - Try Cryptpad: Secure realtime Wysiwyg Editing
> >>  9e?d=https%3A%2F%2Fcryptpad.fr>
> >
> >
> >
> > --
> > Thomas Mortagne
>
>
>
> --
> Thomas Mortagne
>

Re: [xwiki-devs] [Contrib] request for 2 project repositories

[Thomas Mortagne]

I also created Jira projects for them.

Here are all the links:

* https://github.com/xwiki-contrib/application-search-spellcheck
* https://jira.xwiki.org/browse/SCSEARCH

* https://github.com/xwiki-contrib/application-office365
* https://jira.xwiki.org/browse/MSOFFICEOL

On Fri, Apr 14, 2017 at 9:20 AM, Thomas Mortagne
 wrote:
> Done.
>
> Enjoy !
>
> On Fri, Apr 14, 2017 at 8:52 AM, Ludovic Dubost  wrote:
>> Hi,
>>
>> I would like to request two projects repositories for:
>>
>> 1/ Search Extension Spellchecker
>>
>> application-search-spellcheck
>>
>> This extension uses jazzy (https://github.com/tupilabs/jazzy) to provide
>> spell checking of search queries (in english for now)
>>
>> 2/ Office365 integration
>>
>> application-office365
>>
>> This extension provides a macro allowing to display office365 documents
>> inside XWiki, as well as display search results on office365 as a widget in
>> the solr search screen (it needs a UI extension for this which I will
>> propose in a jira issue)
>>
>> Thanks
>> Ludovic
>>
>>
>> --
>> *Ludovic Dubost*
>> *Founder and CEO*
>> ludo...@xwiki.com
>> skype: ldubost
>> Blog: http://blog.ludovic.org
>> Try
>> XWiki on the cloud
>> 
>> - Try Cryptpad: Secure realtime Wysiwyg Editing
>> 
>
>
>
> --
> Thomas Mortagne



-- 
Thomas Mortagne

Re: [xwiki-devs] [XWiki Day] BFD#140

[Alexandru Cotiuga]

Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug%20Fixing%20Day%20140

Thanks,
Alex

On Thu, Apr 13, 2017 at 8:11 AM, Alexandru Cotiuga <
alexandru.coti...@xwiki.com> wrote:

> Hello devs,
>
> Today is BFD#140:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
>
> Our current status for the 500 days period is 56 bugs behind. See:
> http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=103
> 52#Created-vs-Resolved-Chart/16742
>
> Here's the BFD#140 dashboard to follow the progress during the day:
> http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13814
>
> Happy BugFixing Day,
> Alex
>

Re: [xwiki-devs] Bug in XObjects, or am I using them incorrectly?

[Thomas Mortagne]

On Fri, Apr 14, 2017 at 12:01 AM, ktc  wrote:
> I'm running into what appears to be a bug in how XObjects are removed and
> added, and wanted to ask if I am perhaps using them incorrectly.
>
> Basically I am performing the following sequence of steps:
>
> 1. Insert some XObjects to an XWikiDocument using document.newXObject().
> Save the document and reload.
> 2. Delete one of the XObjects in the middle of the list of XObjects, using
> document.removeXObject(). Save the document and reload.
> 3. Add another XObject using document.newXObject(). Save.
>
> Here is that the document's xObjects data looks like after each step
> (simplified for demonstration purposes):
>
> AFTER STEP 1:
> index=0 object="...0..."
> index=1 object="...1..."
> index=2 object="...2..."
>
> AFTER STEP 2 (assume I delete the xObject with index=1):
> index=0 object="...0..."
> index=1 object=null
> index=2 object="...2..."
>
> AFTER STEP 3:
> index=0 object="...0..."
> index=1 object=null
> index=2 object="...2..."
> index=3 object="...2..."
>
>
> As you can see there are two related problems here:
>
> 1. A null object is being preserved in the list of XObjects, even after
> being rehydrated from Hibernate following a server restart.

This is done on purpose so that xobjects keep the same index in the list.

> 2. The index=3 object has been given a 'number' of '2' -- but that number is
> already in use by index=2 object.

This is not expected. Since as you said the assigned number is based
on list size - 1 it should be 3.

Would be great if you could create an issue on http://jira.xwiki.org
for it with the steps to reproduce it.

>
> Because of this, saving the document actually fails: I am receiving a
> NonUniqueObjectException as follows:
>
> org.hibernate.NonUniqueObjectException: a different object with the same
> identifier value was already associated with the session:
> [com.xpn.xwiki.objects.BaseObject#-1957000305211198111]
>
> Looking in the XWiki code it looks like this is essentially happening
> because the value of 'number' is computed as 'list size - 1'. So that 'null'
> that gets preserved in the list seems to be throwing off the logic.
>
> Am I using newXObject()/removeXObject() improperly?
>
> Please advise.
>
> Thanks!
>
>
>
>
> --
> View this message in context: 
> http://xwiki.475771.n2.nabble.com/Bug-in-XObjects-or-am-I-using-them-incorrectly-tp7603477.html
> Sent from the XWiki- Dev mailing list archive at Nabble.com.



-- 
Thomas Mortagne

Re: [xwiki-devs] [Contrib] request for 2 project repositories

[Thomas Mortagne]

Done.

Enjoy !

On Fri, Apr 14, 2017 at 8:52 AM, Ludovic Dubost  wrote:
> Hi,
>
> I would like to request two projects repositories for:
>
> 1/ Search Extension Spellchecker
>
> application-search-spellcheck
>
> This extension uses jazzy (https://github.com/tupilabs/jazzy) to provide
> spell checking of search queries (in english for now)
>
> 2/ Office365 integration
>
> application-office365
>
> This extension provides a macro allowing to display office365 documents
> inside XWiki, as well as display search results on office365 as a widget in
> the solr search screen (it needs a UI extension for this which I will
> propose in a jira issue)
>
> Thanks
> Ludovic
>
>
> --
> *Ludovic Dubost*
> *Founder and CEO*
> ludo...@xwiki.com
> skype: ldubost
> Blog: http://blog.ludovic.org
> Try
> XWiki on the cloud
> 
> - Try Cryptpad: Secure realtime Wysiwyg Editing
> 



-- 
Thomas Mortagne

[xwiki-devs] [Contrib] request for 2 project repositories

[Ludovic Dubost]

Hi,

I would like to request two projects repositories for:

1/ Search Extension Spellchecker

application-search-spellcheck

This extension uses jazzy (https://github.com/tupilabs/jazzy) to provide
spell checking of search queries (in english for now)

2/ Office365 integration

application-office365

This extension provides a macro allowing to display office365 documents
inside XWiki, as well as display search results on office365 as a widget in
the solr search screen (it needs a UI extension for this which I will
propose in a jira issue)

Thanks
Ludovic


--
*Ludovic Dubost*
*Founder and CEO*
ludo...@xwiki.com
skype: ldubost
Blog: http://blog.ludovic.org
Try
XWiki on the cloud

- Try Cryptpad: Secure realtime Wysiwyg Editing