Is someone working on moving the tobeconverted blocks?
What needs to be done to correctly convert a block?
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Carsten Ziegeler wrote:
Is someone working on moving the tobeconverted blocks?
What needs to be done to correctly convert a block?
Please read http://marc.theaimsgroup.com/?l=xml-cocoon-devm=11437302989w=2
and compare the directory structure of a block and a tobeconverted block. I'm
not
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Is someone working on moving the tobeconverted blocks?
What needs to be done to correctly convert a block?
Please read
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=11437302989w=2
and compare the directory structure of a block and a
Reinhard Poetz schrieb:
The blocks conversion script by Andreas was very helpful and certainly
saved a
lot of time. One thing that we would need is a script that moves all
resources
from src/main/java to src/main/resources. Could some bash-guru out there
take
care of it please?
They are
Reinhard Poetz wrote:
That's good news! From now on we can use Continuum for continious
integration builds. Jorg, do we already get notification messages, if
the build fails?
Not for the moment no, I figured it would be just flooding the list with
more failure messages.
I'll try this week
Carsten Ziegeler schrieb:
Daniel Fagerstrom wrote:
Agree, but a first step could be to look at the error messages. I did
that and the vast majority of errors are due to that the component
testing framework doesn't find find the role of the component. So before
deactivating all of the test
Carsten Ziegeler skrev:
Carsten Ziegeler schrieb:
Daniel Fagerstrom wrote:
Agree, but a first step could be to look at the error messages. I did
that and the vast majority of errors are due to that the component
testing framework doesn't find find the role of the component. So before
Daniel Fagerstrom wrote:
I also disabled the rest of the non working test until someone fix them.
So now one can run the tests at cocoon-core, at least.
That's good news! From now on we can use Continuum for continious integration
builds. Jorg, do we already get notification messages, if
Reinhard Poetz skrev:
Daniel Fagerstrom wrote:
I also disabled the rest of the non working test until someone fix
them. So now one can run the tests at cocoon-core, at least.
That's good news! From now on we can use Continuum for continious
integration builds. Jorg, do we already get
Reinhard Poetz skrev:
Jorg Heymans wrote:
Jorg Heymans wrote:
One very important thing: Can somebody take care of the unit-tests of
cocoon-core? I got 79 errors and 2 failurs. Either we throw the
failing tests away or fix them. Carsten, WDYT?
I'll have a look at this.
oops i
Daniel Fagerstrom wrote:
Agree, but a first step could be to look at the error messages. I did
that and the vast majority of errors are due to that the component
testing framework doesn't find find the role of the component. So before
deactivating all of the test it could be a good idea to
First, this mail is rather long but everybody who works with trunk (or wants to
work with it again) should read it!!! There are some changes and a couple of
questions and TODOs which can't be solved by me (alone).
What did I change:
~~
As proposed, I split up trunk into
-
Reinhard Poetz wrote:
One very important thing: Can somebody take care of the unit-tests of
cocoon-core? I got 79 errors and 2 failurs. Either we throw the failing tests
away or fix them. Carsten, WDYT?
I think we should try to fix the unit tests - they should have a value
after all. But I
Reinhard Poetz wrote:
First, this mail is rather long but everybody who works with trunk (or
wants to work with it again) should read it!!!
What about branch? We supposed to have a svn freeze tomorrow, but branch can't
be checked out at the moment due to (at least) template block being in
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
First, this mail is rather long but everybody who works with trunk (or
wants to work with it again) should read it!!!
What about branch? We supposed to have a svn freeze tomorrow, but branch
can't be checked out at the moment due to (at least)
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
What about branch? We supposed to have a svn freeze tomorrow, but
branch can't be checked out at the moment due to (at least) template
block being in blocks-tobeconverted:
I'll (try) to fix this.
Is fixed now - sorry for any inconveniences.
--
Reinhard Poetz wrote:
The blocks conversion script by Andreas was very helpful and
certainly saved a lot of time. One thing that we would need is a
script that moves all resources from src/main/java to
src/main/resources. Could some bash-guru out there take care of it
please?
i used
Jorg Heymans wrote:
One very important thing: Can somebody take care of the unit-tests of
cocoon-core? I got 79 errors and 2 failurs. Either we throw the
failing tests away or fix them. Carsten, WDYT?
I'll have a look at this.
oops i interpreted these test errors as compile errors , i
Jorg Heymans wrote:
Jorg Heymans wrote:
One very important thing: Can somebody take care of the unit-tests of
cocoon-core? I got 79 errors and 2 failurs. Either we throw the
failing tests away or fix them. Carsten, WDYT?
I'll have a look at this.
oops i interpreted these test errors as
19 matches
Mail list logo
