Hi devs,
Following upon an issue with migration encountered by Jeremie Bousquet, I
felt on an unexpected issue that I do not really know how to fix.
When you made a copy of a document containing a custom mapped class, a new
custom mapped class is created by the exact copy of the original document
class definition, but the custom mapping for this copied class is probably
incorrect or not available.
For exemple, if you made a copy of XWiki.XWikiPreferences, you get a new
class that has an internal mapping, but since the .xbm is unchanged, there
is probably no chance that the newly defined class has a mapped entity in
the hibernate mapping. This is precisely the cause of the issue I have
encounter with Jeremie, since the migration tried to migrate IDs of that
new class, which was unusable. Initially, I had an NPE that I have
transformed into an exception now, since I see this as a corruption
somewhere in the store.
The issue with a dynamically custom mapped class could even be worse, since
both class will have the same mapping.
So my question is more generally about how we handle copy of custom mapped
classes ? now and in the future ?
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Hi,
In the development of Cassandra attachments, I found I want to load an attachment one chunk at a time and
write that chunk to a provided OutputStream, this is how I envision next generation Hibernate attachments working too.
I would like to add to XWikiAttachmentContent:
public OutputStream addContent();
which returns an OutputStream that allows writing the attachment content and upon close,
sets the attachment content as dirty and resets the size field.
WDYT?
Caleb
xwiki activity stream is very very slow
My 4.1.3 instance performance is not acceptable.
It takes me more than 10 seconds to display the activity stream.
Is there a simple workaround to remove 'activity stream' from user profile view?
I have already remove 'activity stream' from WebHome.
✉ Kirby Zhou
Hello devs,
I want to cast a vote regarding the following proposal:
Remove the section about manual testing and the link to the MTR's from
M1, M2 and RC1 Release Notes, since we test against MTR only after we
release RC1.
This means that we will have a MTR only for final releases, which will
be linked from the RN page of the final version.
After releasing each M1, M2 and RC1, only the newly added features are tested.
The rationale behind this is that ATM we point a link to a MTR (for
every minor release) but the MTR will be empty ("Not Tested"), so this
renders it useless for minor releases.
Waiting for your votes/opinions
Regards,
Sorin B.
Hi devs,
One of the main goals of 4.2 release was to be able to upgrade an
XWiki farm in a few minutes. Thomas has started working on this and I
need to improve the UI which is currently very minimal. We are pretty
late overall and one way to still have this in 4.2 is to postpone the
final release by adding a third milestone.
The current planning is:
* 4.2M2: 6 Aug 2012 (Today!)
* 4.2RC1: 20 Aug 2012
* 4.2Final: 27 Aug 2012
With a third milestone we could have this:
* 4.2M2: 6 Aug 2012 (Today!)
* 4.2M3: 27 Aug 2012
* 4.2RC1: 10 Sep 2012
* 4.2Final: 17 Sep 2012
However, doing this means we're going to miss the unofficial "1 cycle
per year rule" (we were already over 1 year at the current rate but
it's going to be worse with this) which means we would need from now
on to have shorter release cycle for the 4.x cycle:
* 4.3: October (2 months)
* 4.4: December (1 month)
* 4.5: January (1 month)
In any case the 4.4 and 4.5 release are supposed to be cycle
stabilization releases so it's not a bad thing.
We just need to agree we're not going to put any more big stuff in the
4.x cycle. One thing we would still need to put in is a new skin which
must go in 4.3 (would be too late afterwards).
I'm +1.
Thanks,
Marius
P.S.: This is actually Vincent's proposal, but I'm sending the vote
myself because he's on holiday.
I think that's a great idea, it would make the skin more extensible. Right
now I am exploring creating a xar to create a page where there can be
options-- right now for the colors, like you did with the "fluid" option on
lyrebird.
As I am separating the codes, i am wondering how far i should separate the
core? Should i just leave enough css that there is a sidebar, the header,
and the main content area?
Thank you,
Jonathan Solichin
On Mon, Jul 30, 2012 at 1:09 PM, Jonathan Solichin
<j.s.solichin(a)gmail.com>wrote:
> I think that's a great idea, it would make the skin more extensible. Right
> now I am exploring creating a xar to create a page where there can be
> options-- right now for the colors, like you did with the "fluid" option on
> lyrebird.
>
> As I am separating the codes, i am wondering how far i should separate the
> core? Should i just leave enough css that there is a sidebar, the header,
> and the main content area?
>
> Thank you,
> Jonathan Solichin
>
>
> On Thu, Jul 26, 2012 at 1:42 AM, Jonathan Solichin <jssolichin(a)gmail.com>wrote:
>
>> Hi Jerome,
>>
>> All the advise you mentioned should now be fixed on github. Ajax search
>> is now implemented.
>>
>> I will be working on color themes, while still trying to ensure
>> consistency through out XE UI.
>>
>> Thank you again!
>> Jonathan Solichin
>>
>>
>> On Tue, Jul 17, 2012 at 11:50 AM, Jonathan Solichin <jssolichin(a)gmail.com
>> > wrote:
>>
>>> Hello Friends,
>>>
>>> As you may or may not know, I have been working on a responsive skin for
>>> XWiki for GSOC (http://23.21.87.183:8080/xwiki/bin/view/Main/WebHome).
>>> As I continue to add further details and refinements into the skin, I would
>>> like to kindly ask for your help in doing so. In order to make sure that I
>>> did not miss anything and the skin is as complete as possible, I would like
>>> to, if possible, request a XAR of an existing wiki (or complex pages) so
>>> that I may see the result of implementing the skin on more than the default
>>> wiki data.
>>>
>>> If this is not a possible, I would like to still enlist your help in
>>> testing some basic/your favorite functionality/features of xwiki. There are
>>> several ways to do this:
>>>
>>> - By downloading the current skin and testing it on your XWiki:
>>> https://github.com/jssolichin/xo5
>>> - By playing around with the live instance (uses default admin
>>> user/password): http://23.21.87.183:8080/xwiki/bin/view/Main/WebHome
>>> - By letting me know of your favorite applications (so that I may
>>> look into implementing them)
>>>
>>> Anything you want to note is fine. Bug and feature request are both
>>> welcome, as I think communal ideas are often better than one. Even if you
>>> did not have a chance to play too much with the skin, go ahead and let me
>>> know what you think I should check on (based on your experience) and/or
>>> give me any suggestions that may have come up while reading this.
>>> Technicality permitting, I will check myself.
>>>
>>> Helping with this process will help make the skin better, and maybe help
>>> it to be tailored to your (/type of) wiki and the community surrounding the
>>> platform in general.
>>>
>>> Thank you in advance for your time!
>>> Jonathan Solichin
>>>
>>
>>
>
The XWiki development team is proud to announce the availability of
XWiki Enterprise 4.2 Milestone 2. This release adds support for
storing an email address and a list of wiki page names in XWiki
objects using dedicated xclass property types. It also adds the
ability to have an object property whose value is computed from the
other properties. For developers this release introduces default
custom displayers for easier customization of the way XWiki object
properties are displayed.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
Thanks
-The XWiki dev team
Hi devs,
I'd like to start the release this afternoon (EET). The CI looks in
good shape. I'll check the two failing tests in
xwiki-enterprise-test-extension. Please let me know if you have any
pending commits for 4.2M2 or any blocking issues that needs to be
fixed before the release.
Thanks,
Marius
Hi Thomas,
This is the latest result for xwiki-android-tests-instrumentation (The
UI stress testing test module)
[INFO] *Found 0 devices connected with the Android Debug Bridge*
mojoFailed com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.3.0(default-internal-pre-integration-test)
projectFailed org.xwiki.android:xwiki-android-tests-instrumentation:1.0-SNAPSHOT
sessionEnded
Need an AVD / Device connected to Jenkins to run the tests.
Also the ....test-rest will have failures if some preconditions are not
met. (like having a page named Blog/test2 )
Is there a testing server instance running on the Jenkins server?.
Best Regards
Sasinda.
PS: I created a login with username sasindar.
On Thu, Jul 12, 2012 at 6:08 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com>wrote:
> BTW don't put too much details in mail in general, better making sure
> that references places like
> https://github.com/xwiki-contrib/android-client/blob/master/README and
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Android+Client
> are up to date and link to them. Unless the mail is about asking some
> details of course, I mostly talking about announcement mails.
>
> On Thu, Jul 12, 2012 at 2:35 PM, Thomas Mortagne
> <thomas.mortagne(a)xwiki.com> wrote:
> > On Thu, Jul 12, 2012 at 1:10 PM, sasinda rukshan
> > <sasindarukshan(a)gmail.com> wrote:
> >> Hi
> >> :-)
> >> Do you mean to put a mail to Xwiki Users list users(a)xwiki.org., Not
> >> Developers list ?
> >
> > I mean users and dev list. The idea is to talk about your project to
> > the community (what already exist, what coming, etc). Note that dev
> > mailing list is not for developers, it's for developers of XWiki
> > itself, developers that are going to use XWiki and in this case
> > android framework are users from mailing list point or view.
> >
> >> Well did you check the apk ? is it enough to show off.
> >
> > As long as it's working and there anything new to advertise it's
> > enough. The important things here is to show that there is something
> > produced which is easy to test and that people can try it whenever
> > they want to check last stuff.
> >
> >>
> >> Regards
> >> Sasinda.
> >>
> >>
> >>
> >>
> >> On Thu, Jul 12, 2012 at 3:55 PM, Thomas Mortagne <
> thomas.mortagne(a)xwiki.com>
> >> wrote:
> >>>
> >>> It's an announcement mail, not a documentation. It's made to show off
> ;)
> >>>
> >>> On Thu, Jul 12, 2012 at 12:23 PM, Thomas Mortagne
> >>> <thomas.mortagne(a)xwiki.com> wrote:
> >>> > On Thu, Jul 12, 2012 at 12:15 PM, sasinda rukshan
> >>> > <sasindarukshan(a)gmail.com> wrote:
> >>> >> Hi,
> >>> >> You mean to a real phone?
> >>> >> I was thinking about an emulator. :-)
> >>> >
> >>> > Not was talking about real quick test for end user.
> >>> >
> >>> >>>>I don't understand, you don't need command line to install any APK
> on
> >>> >>>>a phone. You just need to enable it.
> >>> >> Well I mean for the developers to test what the API offers. Not the
> >>> >> application users to check what is available.
> >>> >> The demo blog app was not meant for real users. I only spent about
> 7-8
> >>> >> hours
> >>> >> developing the UI of it.
> >>> >
> >>> > It's not a big deal, it's just about showing that you have something
> >>> > working and that it's easy to try it.
> >>> >
> >>> > You should also obviously talk about what's not visible yet and
> >>> > provide links for developers. But no need to explain developer how to
> >>> > put an APK in an emulator, just indicate what new and where it is.
> >>> >
> >>> >>
> >>> >> Regards
> >>> >> Sasinda.
> >>> >>
> >>> >>
> >>> >> On Thu, Jul 12, 2012 at 3:07 PM, Thomas Mortagne
> >>> >> <thomas.mortagne(a)xwiki.com>
> >>> >> wrote:
> >>> >>>
> >>> >>> On Thu, Jul 12, 2012 at 11:35 AM, Thomas Mortagne
> >>> >>> <thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> > On Thu, Jul 12, 2012 at 11:32 AM, sasinda rukshan
> >>> >>> > <sasindarukshan(a)gmail.com> wrote:
> >>> >>> >> Hi,
> >>> >>> >> Thanks.
> >>> >>> >>>>Evaluation (you passed by the way unless Google has soemthing
> to
> >>> >>> >>>> say
> >>> >>> >>>>about it but I think they let us decide)
> >>> >>> >> Thanks a lot! I am happy to here that.
> >>> >>> >>
> >>> >>> >> By the way I did not care about making the visual aspects. Since
> >>> >>> >> you
> >>> >>> >> said
> >>> >>> >> that the API is the most important one.
> >>> >>> >> So it looks only little work.
> >>> >>> >> I mean, no one will see that I have automated the work of
> sending
> >>> >>> >> the
> >>> >>> >> representation of the Xwiki Document to the server
> >>> >>> >> with just one method call (i.e. create()). I am very happy to
> have
> >>> >>> >> made
> >>> >>> >> such an abstraction because I were originally planning to show
> the
> >>> >>> >> Blog
> >>> >>> >> demo
> >>> >>> >> using earlier project's fine grained API directly. The
> abstraction
> >>> >>> >> was
> >>> >>> >> made
> >>> >>> >> such that XE can keep on changing the ReST API without affecting
> >>> >>> >> the
> >>> >>> >> upper
> >>> >>> >> application layers.
> >>> >>> >> But I am afraid nobody(not you :-)) will notice that because all
> >>> >>> >> that
> >>> >>> >> is
> >>> >>> >> internal technical functionality.
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>>> But try to do
> >>> >>> >>>>a not too technical mail and gives phone/tablet oriented
> >>> >>> >>>> instructions
> >>> >>> >>>>to install the APK
> >>> >>> >> I'll send a mail to the community without tech stuff. ( I mean
> the
> >>> >>> >> ORM
> >>> >>> >> frameworks , restful abstractions etc)
> >>> >>> >> But they will have to install it using cmd line any way.
> >>> >>> >> adb install <apk> . No GUI ;-)
> >>> >>> >> Navigation is intuitive.
> >>> >>> >
> >>> >>> > I don't understand, you don't need command line to install any
> APK
> >>> >>> > on
> >>> >>> > a phone. You just need to enable it.
> >>> >>>
> >>> >>> Talking about enable installing APK comming from "unkown sources"
> in
> >>> >>> Applications preferences.
> >>> >>>
> >>> >>> >
> >>> >>> >>
> >>> >>> >>
> >>> >>> >> I will only mention the internals in the design docs.
> >>> >>> >>
> >>> >>> >>
> >>> >>> >> Thanks.
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>
> >>> >>> >> On Thu, Jul 12, 2012 at 2:00 PM, Thomas Mortagne
> >>> >>> >> <thomas.mortagne(a)xwiki.com>
> >>> >>> >> wrote:
> >>> >>> >>>
> >>> >>> >>> I'm the one that is assigned to this project as the most
> available
> >>> >>> >>> to
> >>> >>> >>> help you and follow you work but your are actually working with
> >>> >>> >>> XWiki
> >>> >>> >>> community, not just me ;)
> >>> >>> >>>
> >>> >>> >>> On Thu, Jul 12, 2012 at 10:28 AM, Thomas Mortagne
> >>> >>> >>> <thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> >>> > On Thu, Jul 12, 2012 at 10:02 AM, sasinda rukshan
> >>> >>> >>> > <sasindarukshan(a)gmail.com> wrote:
> >>> >>> >>> >> Hi,
> >>> >>> >>> >> PS:
> >>> >>> >>> >>>> * Post, Publish a blog post
> >>> >>> >>> >>>> (
> >>> >>> >>> >>>> These two features use the internal functionality as
> >>> >>> >>> >>>> follows.
> >>> >>> >>> >>>> Posting a Document in the server using the new ReSTful
> >>> >>> >>> >>>> Access
> >>> >>> >>> >>>> Layer
> >>> >>> >>> >>>> simplified API.
> >>> >>> >>> >>>> Actually an API user would only have to call a
> create(doc)
> >>> >>> >>> >>>> method
> >>> >>> >>> >>>> passing the Xwik Document he made. All the logic of
> >>> >>> >>> >>>> transforming
> >>> >>> >>> >> ...
> >>> >>> >>> >> All the logic of transforming is done behind the scenes. The
> >>> >>> >>> >> developer
> >>> >>> >>> >> need
> >>> >>> >>> >> not know much about the underlying restful api. That is
> >>> >>> >>> >> he does not need to know he has to post objects to a page,
> then
> >>> >>> >>> >> post
> >>> >>> >>> >> tags
> >>> >>> >>> >> comments and etc.
> >>> >>> >>> >> All the ReST calls are done under the ReSTful Access layer.
> It
> >>> >>> >>> >> is
> >>> >>> >>> >> just
> >>> >>> >>> >> like
> >>> >>> >>> >> the hibernate layer above the Xwiki Enterprise Database
> ;-).
> >>> >>> >>> >>
> >>> >>> >>> >> Also For the API user's ease, we have integrated ORMLite a
> ORM
> >>> >>> >>> >> library. So
> >>> >>> >>> >> Hibernate, JPA users will feel familiar here.
> >>> >>> >>> >>
> >>> >>> >>> >> Those are the important points in a summary.
> >>> >>> >>> >> Further details will be provided when I update the
> >>> >>> >>> >> documentations.
> >>> >>> >>> >
> >>> >>> >>> > Again do not send all that only to me.
> >>> >>> >>> >
> >>> >>> >>> > Evaluation (you passed by the way unless Google has
> soemthing to
> >>> >>> >>> > say
> >>> >>> >>> > about it but I think they let us decide) is good period to
> start
> >>> >>> >>> > announcing what you have done so far and how to test it. But
> try
> >>> >>> >>> > to
> >>> >>> >>> > do
> >>> >>> >>> > a not too technical mail and gives phone/tablet oriented
> >>> >>> >>> > instructions
> >>> >>> >>> > to install the APK people should try since most people are
> not
> >>> >>> >>> > going
> >>> >>> >>> > to test it with the debugger ;)
> >>> >>> >>> >
> >>> >>> >>> >>
> >>> >>> >>> >> Please feel free to suggest.
> >>> >>> >>> >>
> >>> >>> >>> >> Thanks.
> >>> >>> >>> >> Best Regards.
> >>> >>> >>> >> Sasinda.
> >>> >>> >>> >>
> >>> >>> >>> >>
> >>> >>> >>> >>
> >>> >>> >>> >> On Thu, Jul 12, 2012 at 1:21 PM, sasinda rukshan
> >>> >>> >>> >> <sasindarukshan(a)gmail.com>
> >>> >>> >>> >> wrote:
> >>> >>> >>> >>>
> >>> >>> >>> >>> Hi Thomas , all,
> >>> >>> >>> >>>
> >>> >>> >>> >>> Oops.Very Sorry. I was doing it on my office machine. I
> >>> >>> >>> >>> commented
> >>> >>> >>> >>> out
> >>> >>> >>> >>> the
> >>> >>> >>> >>> parent reference. Big mistake with removing comments.
> >>> >>> >>> >>> The build did work in the local machine. The earlier
> build's
> >>> >>> >>> >>> problem
> >>> >>> >>> >>> was
> >>> >>> >>> >>> that it did not export the dependencies. Now with the older
> >>> >>> >>> >>> jayway
> >>> >>> >>> >>> plugin
> >>> >>> >>> >>> the export of dependencies to the apk is done ok.
> >>> >>> >>> >>> Thanks for pointing out.
> >>> >>> >>> >>>
> >>> >>> >>> >>> >>Note that it still not fully building.
> >>> >>> >>> >>>
> >>> >>> >>> >>> [INFO] XWiki Android - Parent POM ........................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [5.786s]
> >>> >>> >>> >>> [INFO] XWiki REST Model ..................................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [1.991s]
> >>> >>> >>> >>> [INFO] XWiki REST Simple-Xml Model .......................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [4.136s]
> >>> >>> >>> >>> [INFO] XWiki REST GSON Model .............................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [3.222s]
> >>> >>> >>> >>> [INFO] XWiki Android REST Connector ......................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [4.277s]
> >>> >>> >>> >>> [INFO] XWiki android core lib ............................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [6.672s]
> >>> >>> >>> >>> [INFO] Xwiki Android Components ..........................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [4.882s]
> >>> >>> >>> >>> [INFO] XWiki Client Apps .................................
> >>> >>> >>> >>> SUCCESS
> >>> >>> >>> >>> [12.440s]
> >>> >>> >>> >>> [INFO] XWiki Android REST Tests ..........................
> >>> >>> >>> >>> FAILURE
> >>> >>> >>> >>> [8.884s]
> >>> >>> >>> >>> [INFO] XWiki Android Instrumentation Tests ...............
> >>> >>> >>> >>> SKIPPED
> >>> >>> >>> >>>
> >>> >>> >>> >>> The two test modules are not building. Well I did not check
> >>> >>> >>> >>> there
> >>> >>> >>> >>> build,
> >>> >>> >>> >>> as I did not change the lower layer APIs which they
> depended
> >>> >>> >>> >>> on.
> >>> >>> >>> >>> Well, the
> >>> >>> >>> >>> Junit version tag is missing in their poms.
> >>> >>> >>> >
> >>> >>> >>> > There were building well before you change the plugin version
> >>> >>> >>> > (and
> >>> >>> >>> > many things that has nothing to do with the plugin version
> >>> >>> >>> > despite
> >>> >>> >>> > what you indicated in the commit log) so it would be nice
> that
> >>> >>> >>> > you
> >>> >>> >>> > fix
> >>> >>> >>> > this. Having them working should be first priority. Generally
> >>> >>> >>> > specking
> >>> >>> >>> > the whole build should always work on master especially
> >>> >>> >>> > automated
> >>> >>> >>> > tests which are checking for you automatically if you
> introduce
> >>> >>> >>> > any
> >>> >>> >>> > regression.
> >>> >>> >>> >
> >>> >>> >>> >>>
> >>> >>> >>> >>> I did not add my own tests yet.
> >>> >>> >>> >>>
> >>> >>> >>> >>> But you can check out the apk at
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> http://maven.xwiki.org/snapshots/org/xwiki/android/xwiki-android-client/1.0…
> >>> >>> >>> >>> It is working.
> >>> >>> >>> >>> Steps to install.
> >>> >>> >>> >>> 1) Download android SDK
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> http://developer.android.com/sdk/installing/adding-packages.html
> >>> >>> >>> >>> 2) Start SDK Manager.exe in the extracted folder and
> download
> >>> >>> >>> >>> Android
> >>> >>> >>> >>> 2.1
> >>> >>> >>> >>> API 7 or later. (I test on API 7).
> >>> >>> >>> >>> 3) Start AVD Manager.exe and make a Android Virtual Device
> >>> >>> >>> >>> named
> >>> >>> >>> >>> exactly
> >>> >>> >>> >>> "android-7".
> >>> >>> >>> >>> 4) Make sure you have added the path to
> >>> >>> >>> >>> <android-sdk-installation
> >>> >>> >>> >>> path>/platform-tools and <android-sdk-installation
> path>/tools
> >>> >>> >>> >>> as
> >>> >>> >>> >>> described
> >>> >>> >>> >>> in the above guide at (Tip in the bottom)
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> http://developer.android.com/sdk/installing/adding-packages.html
> >>> >>> >>> >>>
> >>> >>> >>> >>> 5) download
> xwiki-android-client-1.0-20120711.121416-177.apk
> >>> >>> >>> >>> or a
> >>> >>> >>> >>> later
> >>> >>> >>> >>> apk in
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> http://maven.xwiki.org/snapshots/org/xwiki/android/xwiki-android-client/1.0…
> >>> >>> >>> >>> 6) run command>> adb install <your apk> ex: for the
> build on
> >>> >>> >>> >>> July 11
> >>> >>> >>> >>> adb install
> xwiki-android-client-1.0-20120711.121416-177.apk
> >>> >>> >>> >>>
> >>> >>> >>> >>> After install is successful please press the XWiki icon in
> >>> >>> >>> >>> the
> >>> >>> >>> >>> android
> >>> >>> >>> >>> virtual device's launcher.
> >>> >>> >>> >>> Features:
> >>> >>> >>> >>> * Password , username, server url remember feature added.
> >>> >>> >>> >>> * Connection timeouts added
> >>> >>> >>> >>> * Generalized Launch pad added for android client apps. (
> >>> >>> >>> >>> Client
> >>> >>> >>> >>> app
> >>> >>> >>> >>> icons
> >>> >>> >>> >>> are shown in the launch pad).
> >>> >>> >>> >>> * Post, Publish a blog post
> >>> >>> >>> >>> (
> >>> >>> >>> >>> These two features use the internal functionality as
> >>> >>> >>> >>> follows.
> >>> >>> >>> >>> Posting a Document in the server using the new ReSTful
> >>> >>> >>> >>> Access
> >>> >>> >>> >>> Layer
> >>> >>> >>> >>> simplified API.
> >>> >>> >>> >>> Actually an API user would only have to call a
> create(doc)
> >>> >>> >>> >>> method
> >>> >>> >>> >>> passing the Xwik Document he made. All the logic of
> >>> >>> >>> >>> transforming
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>> Conversion of XWiki Domain model to relevant rest model
> >>> >>> >>> >>> objects.
> >>> >>> >>> >>> )
> >>> >>> >>> >>>
> >>> >>> >>> >>> * Save, Load blog posts ( Persisting the XWiki Domain
> model)
> >>> >>> >>> >>>
> >>> >>> >>> >>> The UI here is just demo purpose only.
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>> On Wed, Jul 11, 2012 at 9:39 PM, Thomas Mortagne
> >>> >>> >>> >>> <thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> >>> >>>>
> >>> >>> >>> >>>> On Wed, Jul 11, 2012 at 2:13 PM, Thomas Mortagne
> >>> >>> >>> >>>> <thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> >>> >>>> > I fixed many mistakes in the root pom.xml, there is no
> way
> >>> >>> >>> >>>> > you
> >>> >>> >>> >>>> > could
> >>> >>> >>> >>>> > build anything with that so I don't understand exactly
> what
> >>> >>> >>> >>>> > you
> >>> >>> >>> >>>> > tested...
> >>> >>> >>> >>>>
> >>> >>> >>> >>>> Note that it still not fully building.
> >>> >>> >>> >>>>
> >>> >>> >>> >>>> >
> >>> >>> >>> >>>> > On Tue, Jul 10, 2012 at 9:13 AM, Thomas Mortagne
> >>> >>> >>> >>>> > <thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> >>> >>>> >> The build is still failing on
> >>> >>> >>> >>>> >> http://ci.xwiki.org/job/xwiki-android-client/, you
> should
> >>> >>> >>> >>>> >> always
> >>> >>> >>> >>>> >> make
> >>> >>> >>> >>>> >> sure this is working well.
> >>> >>> >>> >>>> >>
> >>> >>> >>> >>>> >> On Mon, Jul 9, 2012 at 2:07 PM, sasinda rukshan
> >>> >>> >>> >>>> >> <sasindarukshan(a)gmail.com> wrote:
> >>> >>> >>> >>>> >>> Hi Thomas,
> >>> >>> >>> >>>> >>> The issue with the build was solved by reverting back
> to
> >>> >>> >>> >>>> >>> older
> >>> >>> >>> >>>> >>> version of
> >>> >>> >>> >>>> >>> jayway android maven plugin. This seems not the
> correct
> >>> >>> >>> >>>> >>> option,
> >>> >>> >>> >>>> >>> but
> >>> >>> >>> >>>> >>> it
> >>> >>> >>> >>>> >>> works now. :-).
> >>> >>> >>> >>>> >>>
> >>> >>> >>> >>>> >>> Thanks
> >>> >>> >>> >>>> >>> Regards.
> >>> >>> >>> >>>> >>> Sasinda.
> >>> >>> >>> >>>> >>>
> >>> >>> >>> >>>> >>> On Mon, Jul 9, 2012 at 12:51 PM, sasinda rukshan
> >>> >>> >>> >>>> >>> <sasindarukshan(a)gmail.com>wrote:
> >>> >>> >>> >>>> >>>
> >>> >>> >>> >>>> >>>> Hi Thomas,
> >>> >>> >>> >>>> >>>> >As you want, was just a suggestion to make it
> easier.
> >>> >>> >>> >>>> >>>> > Not
> >>> >>> >>> >>>> >>>> > sure
> >>> >>> >>> >>>> >>>> > how
> >>> >>> >>> >>>> >>>> >XWord deal with macros.
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> Well actually I did not use code macro there. Just
> copy
> >>> >>> >>> >>>> >>>> pasted
> >>> >>> >>> >>>> >>>> from
> >>> >>> >>> >>>> >>>> eclipse ;-). Less work it was!.
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> >From what I can see this is not a real issue.
> >>> >>> >>> >>>> >>>> Yes, its not a real issue.
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> > I need
> >>> >>> >>> >>>> >>>> > to finish something before 4.2M1, will try to look
> at
> >>> >>> >>> >>>> >>>> > it
> >>> >>> >>> >>>> >>>> > after
> >>> >>> >>> >>>> >>>> > that.
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> No problem. Don't be distracted with this. I am
> trying a
> >>> >>> >>> >>>> >>>> workaround,
> >>> >>> >>> >>>> >>>> to
> >>> >>> >>> >>>> >>>> copy the needed jars with maven-dependancy plugin.(I
> >>> >>> >>> >>>> >>>> upgraded
> >>> >>> >>> >>>> >>>> maven
> >>> >>> >>> >>>> >>>> to
> >>> >>> >>> >>>> >>>> 3.0.4. also) . I will try more and hopefully get this
> >>> >>> >>> >>>> >>>> thing
> >>> >>> >>> >>>> >>>> done. It
> >>> >>> >>> >>>> >>>> is not
> >>> >>> >>> >>>> >>>> halting my development because I can build with
> eclipse.
> >>> >>> >>> >>>> >>>> Thanks for offering me help. :-).
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> Best Regards.
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>> On Mon, Jul 9, 2012 at 12:37 PM, Thomas Mortagne <
> >>> >>> >>> >>>> >>>> thomas.mortagne(a)xwiki.com> wrote:
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>> On Mon, Jul 9, 2012 at 6:35 AM, sasinda rukshan
> >>> >>> >>> >>>> >>>>> <sasindarukshan(a)gmail.com> wrote:
> >>> >>> >>> >>>> >>>>> > Hi,
> >>> >>> >>> >>>> >>>>> > Thanks for the info.
> >>> >>> >>> >>>> >>>>> > I did it using XWord . I will do some more
> >>> >>> >>> >>>> >>>>> > documentation
> >>> >>> >>> >>>> >>>>> > after
> >>> >>> >>> >>>> >>>>> > reaching
> >>> >>> >>> >>>> >>>>> the
> >>> >>> >>> >>>> >>>>> > milestone 3( security module). That documentation
> is
> >>> >>> >>> >>>> >>>>> > not
> >>> >>> >>> >>>> >>>>> > enough
> >>> >>> >>> >>>> >>>>> > to give
> >>> >>> >>> >>>> >>>>> the
> >>> >>> >>> >>>> >>>>> > whole picture. Need to separate the API how to s,
> >>> >>> >>> >>>> >>>>> > from
> >>> >>> >>> >>>> >>>>> > the
> >>> >>> >>> >>>> >>>>> > design
> >>> >>> >>> >>>> >>>>> > and architecture descriptions.So the documentation
> >>> >>> >>> >>>> >>>>> > will
> >>> >>> >>> >>>> >>>>> > get
> >>> >>> >>> >>>> >>>>> > changed in
> >>> >>> >>> >>>> >>>>> the
> >>> >>> >>> >>>> >>>>> > future. Is it ok if I edit the formatting later at
> >>> >>> >>> >>>> >>>>> > that
> >>> >>> >>> >>>> >>>>> > time?.
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>> As you want, was just a suggestion to make it
> easier.
> >>> >>> >>> >>>> >>>>> Not
> >>> >>> >>> >>>> >>>>> sure
> >>> >>> >>> >>>> >>>>> how
> >>> >>> >>> >>>> >>>>> XWord deal with macros.
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> > By the way the maven build of the android project
> is
> >>> >>> >>> >>>> >>>>> > currently
> >>> >>> >>> >>>> >>>>> > having
> >>> >>> >>> >>>> >>>>> the
> >>> >>> >>> >>>> >>>>> > following issue.
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> http://code.google.com/p/maven-android-plugin/issues/detail?id=266
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>> From what I can see this is not a real issue. Also
> note
> >>> >>> >>> >>>> >>>>> that
> >>> >>> >>> >>>> >>>>> it's
> >>> >>> >>> >>>> >>>>> working well with the other application
> >>> >>> >>> >>>> >>>>> (xwiki-android-client).
> >>> >>> >>> >>>> >>>>> I
> >>> >>> >>> >>>> >>>>> need
> >>> >>> >>> >>>> >>>>> to finish something before 4.2M1, will try to look
> at
> >>> >>> >>> >>>> >>>>> it
> >>> >>> >>> >>>> >>>>> after
> >>> >>> >>> >>>> >>>>> that.
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>> > I am trying to resolve it, but still not
> successful.
> >>> >>> >>> >>>> >>>>> > The
> >>> >>> >>> >>>> >>>>> > build
> >>> >>> >>> >>>> >>>>> > works in
> >>> >>> >>> >>>> >>>>> > eclipse.
> >>> >>> >>> >>>> >>>>> > Currently I have implemented the functionality for
> >>> >>> >>> >>>> >>>>> > saving
> >>> >>> >>> >>>> >>>>> > and
> >>> >>> >>> >>>> >>>>> > loading
> >>> >>> >>> >>>> >>>>> back
> >>> >>> >>> >>>> >>>>> > xwiki document model. It is working fine.
> >>> >>> >>> >>>> >>>>> > (We can save, load , list documents stored in the
> >>> >>> >>> >>>> >>>>> > system). I
> >>> >>> >>> >>>> >>>>> > have
> >>> >>> >>> >>>> >>>>> stopped
> >>> >>> >>> >>>> >>>>> > development until the maven build issue is solved.
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> > Thanks.
> >>> >>> >>> >>>> >>>>> > Regards.
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> > On Sun, Jul 8, 2012 at 11:11 PM, Thomas Mortagne
> >>> >>> >>> >>>> >>>>> > <thomas.mortagne(a)xwiki.com>wrote:
> >>> >>> >>> >>>> >>>>> >
> >>> >>> >>> >>>> >>>>> >> On Sun, Jul 8, 2012 at 2:53 PM, sasinda rukshan
> >>> >>> >>> >>>> >>>>> >> <sasindarukshan(a)gmail.com> wrote:
> >>> >>> >>> >>>> >>>>> >> > Hi,
> >>> >>> >>> >>>> >>>>> >> > I updated the documentation for XWiki Android
> >>> >>> >>> >>>> >>>>> >> > project
> >>> >>> >>> >>>> >>>>> >> > at,
> >>> >>> >>> >>>> >>>>> >> >
> >>> >>> >>> >>>> >>>>> >> >
> >>> >>> >>> >>>> >>>>> >> >
> http://dev.xwiki.org/xwiki/bin/view/Design/XWikiAndroid.
> >>> >>> >>> >>>> >>>>> >> >
> >>> >>> >>> >>>> >>>>> >> > Sorry for the little formatting errors.
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> >> You should use code macro instead of setting your
> >>> >>> >>> >>>> >>>>> >> own
> >>> >>> >>> >>>> >>>>> >> styling.
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> >> >
> >>> >>> >>> >>>> >>>>> >> > Thanks
> >>> >>> >>> >>>> >>>>> >> > Sasinda.
> >>> >>> >>> >>>> >>>>> >> > _______________________________________________
> >>> >>> >>> >>>> >>>>> >> > devs mailing list
> >>> >>> >>> >>>> >>>>> >> > devs(a)xwiki.org
> >>> >>> >>> >>>> >>>>> >> > http://lists.xwiki.org/mailman/listinfo/devs
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> >> --
> >>> >>> >>> >>>> >>>>> >> Thomas Mortagne
> >>> >>> >>> >>>> >>>>> >>
> >>> >>> >>> >>>> >>>>> > _______________________________________________
> >>> >>> >>> >>>> >>>>> > devs mailing list
> >>> >>> >>> >>>> >>>>> > devs(a)xwiki.org
> >>> >>> >>> >>>> >>>>> > http://lists.xwiki.org/mailman/listinfo/devs
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>> --
> >>> >>> >>> >>>> >>>>> Thomas Mortagne
> >>> >>> >>> >>>> >>>>> _______________________________________________
> >>> >>> >>> >>>> >>>>> devs mailing list
> >>> >>> >>> >>>> >>>>> devs(a)xwiki.org
> >>> >>> >>> >>>> >>>>> http://lists.xwiki.org/mailman/listinfo/devs
> >>> >>> >>> >>>> >>>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>>>
> >>> >>> >>> >>>> >>> _______________________________________________
> >>> >>> >>> >>>> >>> devs mailing list
> >>> >>> >>> >>>> >>> devs(a)xwiki.org
> >>> >>> >>> >>>> >>> http://lists.xwiki.org/mailman/listinfo/devs
> >>> >>> >>> >>>> >>
> >>> >>> >>> >>>> >>
> >>> >>> >>> >>>> >>
> >>> >>> >>> >>>> >> --
> >>> >>> >>> >>>> >> Thomas Mortagne
> >>> >>> >>> >>>> >
> >>> >>> >>> >>>> >
> >>> >>> >>> >>>> >
> >>> >>> >>> >>>> > --
> >>> >>> >>> >>>> > Thomas Mortagne
> >>> >>> >>> >>>>
> >>> >>> >>> >>>>
> >>> >>> >>> >>>>
> >>> >>> >>> >>>> --
> >>> >>> >>> >>>> Thomas Mortagne
> >>> >>> >>> >>>
> >>> >>> >>> >>>
> >>> >>> >>> >>
> >>> >>> >>> >
> >>> >>> >>> >
> >>> >>> >>> >
> >>> >>> >>> > --
> >>> >>> >>> > Thomas Mortagne
> >>> >>> >>>
> >>> >>> >>>
> >>> >>> >>>
> >>> >>> >>> --
> >>> >>> >>> Thomas Mortagne
> >>> >>> >>
> >>> >>> >>
> >>> >>> >
> >>> >>> >
> >>> >>> >
> >>> >>> > --
> >>> >>> > Thomas Mortagne
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> --
> >>> >>> Thomas Mortagne
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Thomas Mortagne
> >>>
> >>>
> >>>
> >>> --
> >>> Thomas Mortagne
> >>
> >>
> >
> >
> >
> > --
> > Thomas Mortagne
>
>
>
> --
> Thomas Mortagne
>