Thanks Marius !
BR,
Jeremie
2013/5/19 Marius Dumitru Florea
> On Sat, May 18, 2013 at 7:09 PM, Jeremie BOUSQUET
> wrote:
> > Mmmm...
> >
> > [WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed
> > with message:
> > Don't depend on a XWiki Legacy module!
> > Found Banned D
On Sat, May 18, 2013 at 7:09 PM, Jeremie BOUSQUET
wrote:
> Mmmm...
>
> [WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed
> with message:
> Don't depend on a XWiki Legacy module!
> Found Banned Dependency:
> org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2
> Foun
So, after merging back the 4.5.2 macros, my test works !!
That was... exhausting :)
J.
Le 18 mai 2013 18:09, "Jeremie BOUSQUET" a
écrit :
> Mmmm...
>
> [WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed
> with message:
> Don't depend on a XWiki Legacy module!
> Found Banne
Mmmm...
[WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed
with message:
Don't depend on a XWiki Legacy module!
Found Banned Dependency:
org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2
Found Banned Dependency:
org.xwiki.platform:xwiki-platform-legacy-observation
Hello,
I think I found the problem and why it happened ...
I performed a diff between a fresh install of xe 4.5.2 and the xwiki
created by my functional tests, and restricted to the following list of
dependencies that were missing:
xwiki-platform-legacy-annotation-4.5.2.jar
xwiki-platform-legacy-m
Thanks,
But I did not find any noticeable differences with my own setup ... I've
got the same list of dependencies, with additional ones.
Only difference would be that I depend on 4.5.3 artifacts, and use packager
plugin 5.0-milestone-2 (for a fix I need).
I tried also with packager 5.0-rc-1, but
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwiki-platform-index/xwiki-platform-index-test/xwiki-platform-index-test-tests
) since they test indirectly the live table.
Hope this helps,
Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUS
Hello,
Pinging about last point below ... I really don't understand what's bad in
my setup, so any help to unblock would be very nice :-)
BR,
Jeremie
2013/3/29 Jeremie BOUSQUET
> Another one: I'm debugging a livetable display, that shows empty rows
> instead of expected values.
> The issue I
Another one: I'm debugging a livetable display, that shows empty rows
instead of expected values.
The issue I have seems to drill down to the fact that "$request.limit"
resolves to "10" (well, the limit value), while "$request.get('limit')"
resolves to null. Also, "$request.reqNo" equals "1" as exp
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne
> On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne
> wrote:
> > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET
> > wrote:
> >> Mmmm, what could explain that standard login for "Admin" user does not
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne
wrote:
> On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET
> wrote:
>> Mmmm, what could explain that standard login for "Admin" user does not work
>> in the xwiki created by the packager plugin ? ("invalid credentials").
>> It used to work, maybe w
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET
wrote:
> Mmmm, what could explain that standard login for "Admin" user does not work
> in the xwiki created by the packager plugin ? ("invalid credentials").
> It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ...
> ?
It's no
Mmmm, what could explain that standard login for "Admin" user does not work
in the xwiki created by the packager plugin ? ("invalid credentials").
It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ...
?
Br,
Jeremie
2013/3/29 Thomas Mortagne
> On Fri, Mar 29, 2013 at 3:05
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET
wrote:
> Ok found it in xwiki-rendering-macro-message.
> That's nice, looking into it, just realized that there existed a
> {{success}} macro ! Seems nice, is it intended that it's not described on
> extensions wiki as info/warning/error are ?
Pro
Ok found it in xwiki-rendering-macro-message.
That's nice, looking into it, just realized that there existed a
{{success}} macro ! Seems nice, is it intended that it's not described on
extensions wiki as info/warning/error are ?
Thanks,
Jeremie
2013/3/29 Jeremie BOUSQUET
> Thanks !
> I'm progr
Thanks !
I'm progressing, but it seems I have a hard time finding what to declare to
get the info/warning/error macros ...
BR,
Jeremie
2013/3/29 Vincent Massol
>
> On Mar 29, 2013, at 12:21 PM, Vincent Massol wrote:
>
> >
> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
> jeremie.bousq..
On Mar 29, 2013, at 12:21 PM, Vincent Massol wrote:
>
> On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET
> wrote:
>
>> Hello,
>>
>> Me again ... :-)
>> With fixed version of packager plugin, things go better now. XWiki is
>> downloaded and launched, my test browses to the page as I expect.
>>
On Fri, Mar 29, 2013 at 12:31 PM, Jeremie BOUSQUET
wrote:
> Thanks, I understand ... I added dependency on velocity macro, but of
> course a whole bunch of dependencies are still missing.
> I would have 2 feedbacks on that point:
> - I understand your point, but when writing a contrib app xar, you
Thanks, I understand ... I added dependency on velocity macro, but of
course a whole bunch of dependencies are still missing.
I would have 2 feedbacks on that point:
- I understand your point, but when writing a contrib app xar, you target
it to work on a specific XE version, and not on a combinati
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET
wrote:
> Hello,
>
> Me again ... :-)
> With fixed version of packager plugin, things go better now. XWiki is
> downloaded and launched, my test browses to the page as I expect.
>
> Problem is that when browsing to my page, I can see the following
On Fri, Mar 29, 2013 at 11:03 AM, Jeremie BOUSQUET
wrote:
> Hello,
>
> Me again ... :-)
> With fixed version of packager plugin, things go better now. XWiki is
> downloaded and launched, my test browses to the page as I expect.
>
> Problem is that when browsing to my page, I can see the following
Hello,
Me again ... :-)
With fixed version of packager plugin, things go better now. XWiki is
downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the
html content logged by the build:
Unknown macro: velocity[...]
Thanks !
Jeremie
2013/3/28 Thomas Mortagne
> On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET
> wrote:
> > Hi,
> >
> > I proposed a pull request to fix XWIKI-8960:
> > https://github.com/xwiki/xwiki-platform/pull/89
> >
> > Seems to work well, and I added an IT test to check it. I'm not sure
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET
wrote:
> Hi,
>
> I proposed a pull request to fix XWIKI-8960:
> https://github.com/xwiki/xwiki-platform/pull/89
>
> Seems to work well, and I added an IT test to check it. I'm not sure of the
> naming though ...
> It's my first pull request so I ho
Hi,
I proposed a pull request to fix XWIKI-8960:
https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure of the
naming though ...
It's my first pull request so I hope I did things correctly :-)
Br,
Jeremie
2013/3/27 Marius Dumitru Fl
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET
wrote:
> Hi again,
>
> On this topic I created a new JIRA:
> http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the
packager plugin outside platform and we didn't took this use case into
acco
Hi again,
On this topic I created a new JIRA:
http://jira.xwiki.org/browse/XWIKI-8960
... and proposed some sort of solution as a comment.
If you agree with the problem and proposal, I could try to contribute a
patch, as anyway I need it for the mailarchive tests.
Of course if you want to fix it
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts
with "this.getProject().getVersion()", meaning if I'm correct that it
returns correct version only if project is part of xwiki platform - or if
it shares the same v
Note: it goes a bit further if I declare a bunch of xwiki platform
dependencies in my pom, but breaks again, trying to look at those platform
artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ...
[WARNING] Missing POM for
org.xwiki.platform:x
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal
org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package
(default) on project xwiki-contrib-mailarchive-test-tests: Failed to
resolve art
ifact
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zi
Thanks Marius, that's exactly what I was looking for !
I'll follow that practice,
BR,
Jeremie
2013/3/20 Marius Dumitru Florea
> Hi Jeremie,
>
> We have started moving functional tests from xwiki-enterprise to
> xwiki-platform so that they are grouped by functional domain. Thus
> xwiki-enterpri
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to
xwiki-platform so that they are grouped by functional domain. Thus
xwiki-enterprise-test-ui is not the best example. You should take a
look at the platform modules that have functional tests:
https://github.com/xwiki/xwi
32 matches
Mail list logo
