Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists.
-0 ... nothing against Max, it is just that i
Le 12 oct. 05, à 05:16, Stefano Mazzocchi a écrit :
...I think a better, leaner, cleaner javadoc would go a *LNG* way
to make things easier...
I was thinking about that recently - does anyone know a tool for
tag-based navigation of javadocs?
A better *navigation* of the javadocs, like
Le 12 oct. 05, à 08:13, David Crossley a écrit :
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists.
Vadim Gritsenko wrote:
I don't recall that m2 will be ready when 2.2 is out. If m2 is not ready, it
should not delay the release. So, I suggest slight change of plan:
According to the m2 dev list, there will be a m2 final next week (if I'm
not mistaken). But of course a final version might
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 00:48, Torsten Curdt a écrit :
...is 2.1 slowly moving to bug fixing only?...
I'm +1 on not adding any more features to 2.1 and doing only
bug-related maintenance there.
Yepp, exactly - but as we agreed to this already several times, and
Bertrand Delacretaz wrote:
David Crossley a ?crit :
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
Vadim Gritsenko wrote:
Afaik, there are only two use cases for this: auth-fw and global sitemap
variables. Now, the reason why auth-fw is using this (or the
authentication manager of auth-fw) is to avoid name clashes. So you can
have two different sitemaps, let's say on the same level (both
Hi,
I find many xml files in cocoon are actually encoded with UTF-16 but the declarations in their
xml PI are given UTF-8. For example, the file webapp/pom.xml is actually
encoded in UTF-16 (we can tell this from the first two byes, which are FF FE) but its first line is
?xml version=1.0
Carsten Ziegeler wrote:
Hm :-) Are you sure it will be better than SitemapConfigurable? :-)
No :) Ok, for example we could have properties file next to the sitemap
and these properties are available as global variables for this sitemap
and all sub sitemaps. This might be a little bit
Stefano Mazzocchi wrote:
[EMAIL PROTECTED] wrote:
Author: lgawron
Date: Tue Oct 11 16:00:10 2005
New Revision: 312973
URL: http://svn.apache.org/viewcvs?rev=312973view=rev
Log:
support for compact blocks.properties:
exclude.all.blocks=true
include.block.template=true
include.block.forms=true
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Hm :-) Are you sure it will be better than SitemapConfigurable? :-)
No :) Ok, for example we could have properties file next to the sitemap
and these properties are available as global variables for this sitemap
and all sub sitemaps. This might
Leszek Gawron wrote:
Stefano Mazzocchi wrote:
[EMAIL PROTECTED] wrote:
Author: lgawron
Date: Tue Oct 11 16:00:10 2005
New Revision: 312973
URL: http://svn.apache.org/viewcvs?rev=312973view=rev
Log:
support for compact blocks.properties:
exclude.all.blocks=true
include.block.template=true
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32784.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
...
I was thinking about that recently - does anyone know a tool for
tag-based navigation of javadocs?
A better *navigation* of the javadocs, like being able to see all
classes which have the sitemap generator tags, would help a lot.
Can't you use the refdoc stuff for that? If it's not
On 12.10.2005, at 08:20, Bertrand Delacretaz wrote:
Le 12 oct. 05, à 05:16, Stefano Mazzocchi a écrit :
...I think a better, leaner, cleaner javadoc would go a *LNG*
way to make things easier...
I was thinking about that recently - does anyone know a tool for
tag-based navigation
...is 2.1 slowly moving to bug fixing only?...
I'm +1 on not adding any more features to 2.1 and doing only
bug-related maintenance there.
Yepp, exactly - but as we agreed to this already several times, and
people started adding stuff to 2.1.x nevertheless, I fear it's just
a wish.
Le 12 oct. 05, à 09:32, Max Pfingsthorn a écrit :
...Can't you use the refdoc stuff for that? If it's not ready, which I
guess it isn't from the STATUS at
http://svn.apache.org/repos/asf/cocoon/gsoc/rgraham/refdoc/STATUS, I
could take it from where Robert left it...
It's not far from being
Ralph Goers wrote:
Torsten Curdt wrote:
What has stopped us is that we need to keep a track of these to give
credit. And also show to the world the incredibly large developer
group we are :-)
But if you give credit without a connection to parts of the code it's
just a list of the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29405.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 05:16, Stefano Mazzocchi a écrit :
...I think a better, leaner, cleaner javadoc would go a *LNG* way
to make things easier...
I was thinking about that recently - does anyone know a tool for
tag-based navigation of javadocs?
A better
David Crossley wrote:
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists.
-0 ... nothing
On 11 Oct 2005, at 18:19, Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
Can you explain how it will work then? Having xconf file sitting
next to sitemap
is just syntax sugar, it does not implement any new feature. So
how this feature
is getting implementing by taking extra syntax
Pier Fumagalli wrote:
Sorry if I sound silly, but in the XCONF we can define what
components we load in the ComponentManager, and are exposed
throughout the entire Cocoon.
Now, given that 2.2 has a classloader-per-sitemap feature, would that
mean that the components declared in the
Sylvain Wallez wrote:
Or more simpler, and we already talked about this, what about tagging
the source files themselves to be able to produce javadocs of a
restricted set of classes, i.e. those that are considered public API and
that people can safely rely on.
And now, it's time for
Le 11 oct. 05, à 15:36, hepabolu a écrit :
...Just had a quick look and some things came to mind:
- as Carsten pointed out, the link to all samples is very
unobtrusive...
Fixed, you cannot miss the link anymore.
- I really feel the need for a back link on each overview page or
maybe the
Hi,
I've noticed that in 2.1-head all widgets have in their HTML rendering
the text -input added to their widget id (and are contained in a span
which has the original widget id).
I assume this is to support the new ajax stuff, but is there a reason
why this couldn't have been done the other way
hepabolu wrote:
Ross Gardler wrote:
...
See http://people.apache.org/~rgardler/cocoon-site/659.daisy.html
(don't worry, there is a robot.txt file on there so this should not be
indexed)
...
just had a brief look and this is what I noted:
- you should use the navigation.xml file that
Now that I am a Cocoon committer, can someone with the necessary karma
please create an account for me on the Cocoon Zone. I would like to set
up the ForrestBot to publish a staged site from Daisy every X hours.
Ross
Le 11 oct. 05, à 10:25, hepabolu a écrit :
Bertrand Delacretaz wrote:
How about doing a bug amnesty as follows?
As already said by others, I too am not fond of a bug amnesty
...I know this means a lot of work, and takes certainly a lot more
effort than simply expire, but it really
Bertrand Delacretaz wrote:
Le 11 oct. 05, à 10:25, hepabolu a écrit :
Bertrand Delacretaz wrote:
How about doing a bug amnesty as follows?
As already said by others, I too am not fond of a bug amnesty
...I know this means a lot of work, and takes certainly a lot more
effort than
Doing an amnesty would *not* mean that we don't care about the
bugs, quite the contrary: we care enough about them to setup a
quick an efficient process to find out which ones really need our
attention.
Think so too!
But if you think we have enough collective energy and manpower to
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Hm :-) Are you sure it will be better than SitemapConfigurable? :-)
No :) Ok, for example we could have properties file next to the sitemap
and these properties are available as global variables for this sitemap
and
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37030.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37030.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Pier Fumagalli wrote:
On 11 Oct 2005, at 20:16, Bertrand Delacretaz wrote:
Le 11 oct. 05, à 07:31, Reinhard Poetz a écrit :
...- Cocoon 2.2 will not use OSGi but will support blocks as far as
possible:...
...- Cocoon 3.0 will use OSGi -- shielding classloader and hot
plugablillity...
Joerg Heinicke wrote:
Jaka Jaksic jaka.jaksic at telemach.net writes:
But even then you realize that accessing the natural functionality (and power)
of Cocoon is often very difficult, because there is no obvious API and no
function library to access the core functionality.
BTW, this
Le 12 oct. 05, à 13:06, Torsten Curdt a écrit :
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how do you suggest asking?
We could add a comment to each open issue with
Ross Gardler wrote:
See: http://people.apache.org/~rgardler/cocoon-site/653.daisy.html
Correct. It looks much slicker than the official site, although my
fingers itch to do something about the navigation (CSS wise).
There are broken links now we switched to the new navigation. See
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 13:06, Torsten Curdt a écrit :
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how do you suggest asking?
We could add a
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
I don't recall that m2 will be ready when 2.2 is out. If m2 is not ready, it
should not delay the release. So, I suggest slight change of plan:
According to the m2 dev list, there will be a m2 final next week (if I'm
not mistaken). But of course
hepabolu wrote:
I've turned PDF's off for now. Currently the Forrest plugin does not
support Daisy Books, but it should. In the meantime we can pull the
published book from Daisy. This is not a problem as long as we are not
trying to integrate content from different sources into the book
hepabolu wrote:
Ross Gardler wrote:
See: http://people.apache.org/~rgardler/cocoon-site/653.daisy.html
Correct. It looks much slicker than the official site, although my
fingers itch to do something about the navigation (CSS wise).
My SVN committership has now been enabled. As soon as I
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
I don't recall that m2 will be ready when 2.2 is out. If m2 is not
ready, it should not delay the release. So, I suggest slight change
of plan:
According to the m2 dev list, there will be a m2 final next week (if I'm
Bertrand Delacretaz wrote:
Note also that the aim is to remove as many
exotic blocks as possible from 2.2 and move them to contrib, so it
shouldn't be that bad in the end.
Please, blocks are *already* removed from 2.2, they reside in separate location:
hepabolu wrote:
Ross Gardler wrote:
See: http://people.apache.org/~rgardler/cocoon-site/653.daisy.html
Correct. It looks much slicker than the official site, although my
fingers itch to do something about the navigation (CSS wise).
Please do :-) Black border around current page is ...
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
I don't recall that m2 will be ready when 2.2 is out. If m2 is not
ready, it should not delay the release. So, I suggest slight change
of plan:
According to the m2 dev list, there will be a m2
On 12 Oct 2005, at 12:40, Daniel Fagerstrom wrote:
Pier Fumagalli wrote:
On 11 Oct 2005, at 20:16, Bertrand Delacretaz wrote:
Just one small nitpicking comment, we should say 3.0 will *most
probably* use OSGI - as you said, it's a nice goal to have but
I don't think we're 100% positive
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
I don't recall that m2 will be ready when 2.2 is out. If m2 is not
ready, it should not delay the release. So, I suggest slight change
of plan:
According to the m2 dev
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I think a long time ago we decided to remove the author tags, upto now
nothing really happend :(
Yep. There was a positive vote (probably more than one actually), and
since then nobody adds new @author tags, meaning the information is
Torsten Curdt wrote:
What has stopped us is that we need to keep a track of these to give
credit. And also show to the world the incredibly large developer
group we are :-)
But if you give credit without a connection to parts of the code it's
just a list of the committers (more or less)
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
I think a build/deployment system is a must as soon as we reach the
release candidate phase of 2.2. Currently the best bet is M2. Do
you see any alternatives that could be implemented faster?
2.1 is using Ant build for
Berin Loritsch wrote:
Torsten Curdt wrote:
So either remove them or don't. But giving credit besides the
community credits does not make much sense to me.
*shrug*
You know, I still get people emailing me about some code that I wrote
well over two years ago just because my name is in
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how do you suggest asking?
We could add a comment to each open issue with the question (which
would send a mail to bug
Le 12 oct. 05, à 14:08, hepabolu a écrit :
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 13:06, Torsten Curdt a écrit :
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how
Vadim Gritsenko wrote:
Well, I think m2 should be able to:
* Build Cocoon
* Build all blocks
* Copy over blocks to WEB-INF/blocks or simialr :-)
* Patch wiring.xml (as soon as we start using it)
* Prepare a source release
* Prepare a binary release
* Build subset of blocks (using
Le 12 oct. 05, à 14:35, Vadim Gritsenko a écrit :
Bertrand Delacretaz wrote:
Note also that the aim is to remove as many exotic blocks as
possible from 2.2 and move them to contrib, so it shouldn't be that
bad in the end.
Please, blocks are *already* removed from 2.2, they reside in
Le 12 oct. 05, à 14:33, Reinhard Poetz a écrit :
...I think a build/deployment system is a must as soon as we reach the
release candidate phase of 2.2. Currently the best bet is M2. Do you
see any alternatives that could be implemented faster?...
IIUC we're currently talking of a first
On 12.10.2005 15:24, Bertrand Delacretaz wrote:
IIUC we're currently talking of a first milestone release of 2.2, not
a release candidate. So the current ant build could be good enough for
that until the m2 stuff matures, if this allows the milestone to be out
earlier.
+1
Jörg
Bertrand Delacretaz wrote:
Yes, do a query like http://tinyurl.com/9nxs2 and select change several
bugs at once. Then we can enter a comment (which people will get by
mail) and change the issue state.
Caveats:
-For some reason the mark as NEEDINFO option does not appear in this
case, so we
hepabolu wrote:
If the ideas of keeping track of changes in a changes.xml per block
are going to be implemented, there should be a proper configuration of
the site generating aspects, i.e.
m2 site:site should result in a smallish site that includes basic info
with a link to the Daisy
Vadim Gritsenko wrote:
hepabolu wrote:
Ross Gardler wrote:
See: http://people.apache.org/~rgardler/cocoon-site/653.daisy.html
Correct. It looks much slicker than the official site, although my
fingers itch to do something about the navigation (CSS wise).
Please do :-) Black border
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 14:35, Vadim Gritsenko a écrit :
Bertrand Delacretaz wrote:
Note also that the aim is to remove as many exotic blocks as
possible from 2.2 and move them to contrib, so it shouldn't be that
bad in the end.
Please, blocks are *already* removed
I thought we were going to get rid of the portal's variable resolver?
Ralph
[EMAIL PROTECTED] wrote:
Author: cziegeler
Date: Wed Oct 12 05:44:59 2005
New Revision: 314865
URL: http://svn.apache.org/viewcvs?rev=314865view=rev
Log:
Fix possible ClassCastException in
Le 12 oct. 05, à 15:34, hepabolu a écrit :
...Fine by me, but in the wiki page you say something along the lines
if you don't respond, the state stays WONTFIX, which in effect means
you have to mark all bugs for WONTFIX...
Yes, using the change several bugs at once means we have to set all
Le 12 oct. 05, à 15:36, Vadim Gritsenko a écrit :
...By the time m2 is properly done, we should remove svn externals
and cut bocks loose :-) and treat them as separate projects...
Ok, fine then, let's wait for this - there's no hurry but 2.2 should
give a clear signal that we want to travel
Ralph Goers wrote:
I thought we were going to get rid of the portal's variable resolver?
Yeah, sure - but the current version was buggy, and we don't have the
replacement yet. Is anyone working on it?
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
Did someone notice this on the Docs list?
I think it would be cool to add this graphics to our docs.
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Le 12 oct. 05, à 15:39, Bertrand Delacretaz a écrit :
Le 12 oct. 05, à 15:34, hepabolu a écrit :
...Fine by me, but in the wiki page you say something along the lines
if you don't respond, the state stays WONTFIX, which in effect
means you have to mark all bugs for WONTFIX...
Yes, using
Carsten Ziegeler wrote:
Did someone notice this on the Docs list?
I think it would be cool to add this graphics to our docs.
Didn't you forget something ? :)
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp.
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
I don't think you need any special privilege to download it, just an
ADC account.
It's a 110 Mb download!
forwarding this to a more appropriate list
On 08 Oct 2005, at 00:40, g[R]eK wrote:
Hello!
I have very mysterious error while using forms with
@enctype=multipart/form-data. _Some times_ while submiting the form
I get org.apache.cocoon.servlet.multipart.MultipartException:
Malformed
Ross Gardler wrote:
The number is because daisy uses numbers rather than names to identify
every page. There are ways around this in either Forrest or Daisy but it
is quite a bit of work.
Well, as I wrote earlier: I've entered a nodeId for each page in the
navigation.xml. You could use that
Pier Fumagalli wrote:
On 12 Oct 2005, at 12:40, Daniel Fagerstrom wrote:
Pier Fumagalli wrote:
On 11 Oct 2005, at 20:16, Bertrand Delacretaz wrote:
Just one small nitpicking comment, we should say 3.0 will *most
probably* use OSGI - as you said, it's a nice goal to have but I
don't
Ralph Goers wrote:
hepabolu wrote:
If the ideas of keeping track of changes in a changes.xml per block
are going to be implemented, there should be a proper configuration of
the site generating aspects, i.e.
m2 site:site should result in a smallish site that includes basic info
with a
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
Thanks for the info - I hope the install does not wipe out
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=6200.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
Thanks for the info - I hope
[EMAIL PROTECTED] wrote:
Added:
cocoon/blocks/core-samples-additional/trunk/samples/resources/i18n/messages.xml
URL:
http://svn.apache.org/viewcvs/cocoon/blocks/core-samples-additional/trunk/samples/resources/i18n/messages.xml?rev=314929view=auto
Leszek Gawron wrote:
Carsten Ziegeler wrote:
Did someone notice this on the Docs list?
I think it would be cool to add this graphics to our docs.
Didn't you forget something ? :)
Ups, yepp, sorry and thanks!
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
On 12 Oct 2005, at 15:30, Bertrand Delacretaz wrote:
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using
Mac OS/X), the ADC http://developer.apple.com/ just posted to
everyone the J2SE 5.0 Release 3 Developer Preview 2...
Ok, here is the original message - unfortunately I can't post the
attachement into this list...so if someone is interested to put it up,
he can either pick it up from this list or I can send it directly to him.
Carsten
Merico Raffaele wrote:
Hi Community
In the attachments you will find a
Bertrand Delacretaz wrote:
So here's the suggested plan:
1) Set all open issues (except those filed since September 1st) to LATER
and add to each issue the comment shown under Bugzilla comment to send
on http://wiki.apache.org/cocoon/BugzillaIssuesCleanup
2) People who want to confirm
Ross Gardler wrote:
Vadim Gritsenko wrote:
Another problem I noticed - all URLs are number.daisy.html - we can't
publish these to official website...
Which part(s) are you objecting to?
This URL
/424.daisy.html
Should be
http://cocoon.apache.org/2.1/tracks/first-steps-track.html
hepabolu wrote:
Grr. I checked this and thought it was properly set up. What should I
have done?
Check your ~/.subversion/config, it should have [auto-props] section set up. For
files already added to the svn, use this shell script:
#!/bin/sh
svn propset svn:eol-style native $*
svn
Carsten Ziegeler wrote:
Ralph Goers wrote:
I thought we were going to get rid of the portal's variable resolver?
Yeah, sure - but the current version was buggy, and we don't have the
replacement yet. Is anyone working on it?
Carsten
Well - there's you and me. And I'm not (at
Bertrand Delacretaz wrote:
Steps 1) and 4) can be done en masse via the change several bugs at
once function of bugzilla.
En masse. That is exactly the approach I was trying to avoid. :-(
What is the primary goal - do you want simply to get rid of issues or you want
to make Cocoon better? I
Carsten Ziegeler wrote:
Ok, here is the original message - unfortunately I can't post the
attachement into this list...so if someone is interested to put it up,
he can either pick it up from this list or I can send it directly to him.
Carsten
Merico Raffaele wrote:
Hi Community
In the
hepabolu wrote:
Carsten Ziegeler wrote:
Ok, here is the original message - unfortunately I can't post the
attachement into this list...so if someone is interested to put it up,
he can either pick it up from this list or I can send it directly to him.
Carsten
Merico Raffaele wrote:
Hi
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37030.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Vadim Gritsenko wrote:
hepabolu wrote:
Grr. I checked this and thought it was properly set up. What should I
have done?
Check your ~/.subversion/config, it should have [auto-props] section set
up. For files already added to the svn, use this shell script:
#!/bin/sh
svn propset
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37049.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37049.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37049.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On 12 Oct 2005, at 15:21, Daniel Fagerstrom wrote:
Pier Fumagalli wrote:
On 12 Oct 2005, at 12:40, Daniel Fagerstrom wrote:
Pier Fumagalli wrote:
On 11 Oct 2005, at 20:16, Bertrand Delacretaz wrote:
Just one small nitpicking comment, we should say 3.0 will
*most probably* use OSGI - as
Upayavira wrote:
We really need the source for the diagram, rather than the finished
thing, so we can make changes like the above ourselves.
It's there: the powerpoint presentation. I know it's horrible, but at
least it's reusable.
Bye, Helma
Le 12 oct. 05, à 16:53, Vadim Gritsenko a écrit :
What is the primary goal - do you want simply to get rid of issues or
you want to make Cocoon better?...
My goal is to prioritize the issues, find out among these 300 those who
are worth working on. Without having to spend lonely hours on
On 12.10.2005 17:03, Bertrand Delacretaz wrote:
My goal is to prioritize the issues, find out among these 300 those who
are worth working on.
Don't we have the votes feature of bugzilla for prioritizing the issues?
Jörg
PS:
I can send emails the standard way again (POP3, GMX). GMX got
hepabolu wrote:
And Windows? At work I use Windows and handle all SVN actions using
subclipse.
Subclipse? You are asking wrong dude :-)
In TortoiseSVN probably there is some settings dialogue for that; and you can
use File - Properties - Subversion tab to edit properties.
Vadim
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 16:53, Vadim Gritsenko a écrit :
We could also, after three weeks, reopen the issues to which people
haven't responded, and set them to a low priority or use another flag to
identify them, instead of letting them in LATER state as suggested.
I can
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
1 - 100 of 161 matches
Mail list logo
