Stefano Mazzocchi wrote:
So, what do we do?
Good question.
a) Fix GUMP so that it can take stuff from a branch.
b) Include a Cocoon owned stub.
c) Do nothing.
In either case, check
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAvalonization
before it goes stale.
Send nag mails to Jeremias who pr
J.Pietschmann wrote:
Santiago Gala wrote:
Nagging FOP developers to deprecate those classes but keep an
implementation in term of the new ones at least during one full
development/release cycle?
Wont help in this case. The old API was really botched.
So, what do we do?
Stefano.
Santiago Gala wrote:
Nagging FOP developers to deprecate those classes but keep an
implementation in term of the new ones at least during one full
development/release cycle?
Wont help in this case. The old API was really botched.
J.Pietschmann
Vadim Gritsenko wrote:
Is it good idea to start software (have first release) with
deprecations? :)
Is it a good idea to release software with a 0.x version? ;-)
When I released Cocoon 1.0, I felt that 0.01alpha was a much better
indication of its functionality.
But if I did so, probably all o
Santiago Gala wrote:
Vadim Gritsenko wrote:
...
They have those classes. In the branch. Same situation as we had
recently before repository split-up.
But, If they have documented
(http://xml.apache.org/fop/embedding.html) the use of the Options
class, they should be aware that users are not l
Vadim Gritsenko wrote:
Santiago Gala wrote:
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch
Santiago Gala wrote:
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch us.
Currently, 6 block
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch us.
Currently, 6 blocks fail. I'm listing the
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch us.
Currently, 6 blocks fail. I'm listing the problems
the really
It seems that we are converging toward a stable gump setup. This is very
nice and very useful to help us solidify our contracts and make it
visible for other projects underneath our food chain to watch us.
Currently, 6 blocks fail. I'm listing the problems
- databases -> doesn't pickup mock cl
10 matches
Mail list logo
