Andreas Hartmann wrote:
Robert Goene wrote:
[...]
I need some help! I have been trying to get a working development
environment for a couple of days now. I have 11 days to meet the SoC
goals and i am certain that i won't make it if i keep on wasting my
time with all kinds of unrelated problems. When i would have the
time, i would love to dig into them , but since i don't...
I wouldn't care too much about the deadline. After all, it's about
creating valuable software and not about "hacking" something because
there's not enough time. I'm sure it will be more appreciated if you
take your time to do things properly, at least by the Lenya community.
If we get a cool piece of code running a couple of weeks after the
deadline, you should feel better than meeting the deadline with a
half-baked approach ... But that's just my CHF 0.02.
I would have this intention if the google deadline wasn't strict.
Besides the fact that i won't get the grant if i do not deliver on time,
i should do everything possible to make it, because i took one of the
grants that otherwise could be attributed to someone else.
I will be working on the code after the deadline to add features that
are not part of the google SoC proposal, but my first interest is to
meet those proposed features.
Beleive me, i am much more comfortable without a deadline like this.
I want to develop and test my usecases without relying on the
condition of the trunk of 1.4. Could ou give me some advice on this,
because i am freaking out on the idea that i won't make the deadline
because of all these strange little annoyances.
Actually I guess you won't get around this. My suggestion is that you
make familiar with the usecase fw and the underlying concepts (flowscript,
Avalon, Lenya workflow etc.), which exist quite a lot of tutorials for
(well, maybe not for the Lenya workflow ...). If you're looking for
something particular, just ask on the list. 1.4 is not yet stable, so you
will have to live with these little annoyances.
Is it possible to use the LENYA_1_4_ALPHA_1 tag? I have looked at the
Publish.java code and some other parts and they seem identical.
How can i develop and test a couple of usecases? I am sure you have
some experience in this. I am working on the Deactivate and Publish
usecase alongside some new ones.
My tool of choice is the Eclipse debugger. When problems in the repository
layer occur, it starts to become complex quite soon.
Start developing incrementally. It's quite ambitious to start with a
LuceneIndexTransformer usecase, using CInclude etc. Maybe it makes sense
to get a simple no-op usecase running and add functionality step by step.
This is what i am trying to do...
I saw another thread in which you mention the repository integration as
a possible source of problems. Aren't the problems i am talking about of
the same sort? I havn't tried to install the jcr repository, but i think
this could be a good idea.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
