Hi Anca -- thanks for supporting XWikiWatch. I agree with your proposal to leave XWikiWatch as a component-only and not worry about installers or making it a standalone distribution. I look forward to trying your changes after you commit them. Once promoted to component-only, it would be nice to have XWikiwatch updated to work with 2.3.X, and to continue keeping it working along with the trunk. You mention 2.3.2 explicitly. Is there any reason why that wouldn't work with the current trunk or 2.4? FYI, I had problems building against 2.3, after reading here that there was even a chance of it working with versions > 2.0. Following instructions at http://watch.xwiki.org/xwiki/bin/view/Main/Installation#HBuildingandinstalli...

"go to gwt-client, gwt-server, wikis modules (in this order) and type mvn clean install in each of them"

I can successfully build gwt-server and wikis, but have problems w/ gwt-client: http://nielsmayer.com/npm/xwatch-error-gwt-client.txt But I am stopped by the following error: [INFO] [dependency:unpack {execution: unzip-gwt-libs}] [INFO] Configured Artifact: com.google.gwt:gwt-dev:linux-libs:2.0.3:zipDownloading: http://maven.xwiki.org/externals/com/google/gwt/gwt-dev/2.0.3/gwt-dev-2.0.3-... I'm compiling/running using: Apache Maven 2.2.1 (r801777; 2009-08-06 11:16:01-0800) OS name: "linux" version: "2.6.32.21-166.fc12.x86_64" arch: "amd64" Family: "unix" I haven't been able to find this gwt-dev-2.0.3-linux-libs.zip anywhere. Any suggestions on how to get past this step in the instructions? Also, In the course of the build, it I noticed attempts at retrieving 1.5 Xwiki Core, rather that the 2.X.X version specified in the POM "building over existing XE" instructions. Perhaps there are subcomponents that still reference 1.5? Will these be remedied by your proposed checkin? -- Niels http://nielsmayer.com

+1 for 1B (I would go even for 1A). Thanks, Marius On 09/15/2010 04:47 PM, Anca Luca wrote:

Hi devs,

I updated locally XWiki Watch trunk to work with XWiki Enterprise 2.3.2 (right now it's 1.8.4 version) and I would like to commit this in the Watch trunk.

There is a little issue though, with the modules for building the standalone distribution(s) (distribution, database, installers, web), which need to be handled, for which there are 3 options:

0/ update the distribution related modules to make them compatible with 2.3 and the process is not straightforward due to Watch particularities (this would mean extra work and since I don't know when I will be able to do it, it means not commit right away)

1A/ remove the distribution related modules from the watch trunk and leave it installable as a .xar + component (as described at http://watch.xwiki.org/xwiki/bin/view/Main/Installation#HXWikiWatchoveranexi... ) drawback is that users installing it need to edit the web.xml which is not that easy for everyone.

1B/ leave the distribution related modules, just exclude them from the default build since they will fail, until 0/ can be fixed right.

I would go for 1B since I think partial update to 2.3 is better than nothing (current version on 1.8.4 is not really useful in most cases) and earlier is better than later.

WDYT?

Thanks, Anca _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

Hi Anca, On Sep 15, 2010, at 3:47 PM, Anca Luca wrote:

Hi devs,

I updated locally XWiki Watch trunk to work with XWiki Enterprise 2.3.2 (right now it's 1.8.4 version) and I would like to commit this in the Watch trunk.

There is a little issue though, with the modules for building the standalone distribution(s) (distribution, database, installers, web), which need to be handled, for which there are 3 options:

0/ update the distribution related modules to make them compatible with 2.3 and the process is not straightforward due to Watch particularities (this would mean extra work and since I don't know when I will be able to do it, it means not commit right away)

+1

1A/ remove the distribution related modules from the watch trunk and leave it installable as a .xar + component (as described at http://watch.xwiki.org/xwiki/bin/view/Main/Installation#HXWikiWatchoveranexi... ) drawback is that users installing it need to edit the web.xml which is not that easy for everyone.

I don't know why we would make it harder for someone to install watch. Maintaining the distribution is really easy and requires almost no change at all (as we can see from our XE experience). I'd definitely agree with 0/ once we can install Watch as a single bundle (maybe with the extension manager ;)). To summarize, we need to make it as easy as possible for users to try it out. Re the web.xml merge it's not hard to do it with a maven plugin or ant task. In the future we should do without the need to modify web.xml of course. BTW would be interesting to see how long it takes to get rid of this need. I don't think that fixing the distribution would require more than 2 hours of work. I can help too if you have questions on how to do it. Thanks -Vincent

1B/ leave the distribution related modules, just exclude them from the default build since they will fail, until 0/ can be fixed right.

I would go for 1B since I think partial update to 2.3 is better than nothing (current version on 1.8.4 is not really useful in most cases) and earlier is better than later.

WDYT?

Thanks, Anca