Folks!
Thanks for caring that much and sorry for me being quiet until now as
I am the guilty person.
The design we are talking about actually is quite weird as it is a
stub of a former implementation. There is this interface and there is
*exactly* one implementation for that interface and IMHO
+1 to both, assuming the project documentation on the main site has nothing to
do with the skin,
since I think we don't want that menu on the main site.
Mvgr,
Martin
Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I
+1 to both
Oleg
On Sat, 2007-01-13 at 02:16 +0100, Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[x] +1 Do
Just one question: I noticed that the links to the Cobertura report open
an empty site for some components (did not check all). Is there a
problem? (I am asking because I had some trouble when playing with the
maven 2 cobertura plug-in a while ago.)
Otherwise I am +1 for both.
Oliver
Dennis
Martin van den Bemt wrote:
+1 to both, assuming the project documentation on the main site has nothing to
do with the skin,
since I think we don't want that menu on the main site.
The skin is only about looks. It couldn't care less about the content ;)
I'll start a thread about menus, links
Oliver Heger wrote:
Just one question: I noticed that the links to the Cobertura report open
an empty site for some components (did not check all). Is there a
problem? (I am asking because I had some trouble when playing with the
maven 2 cobertura plug-in a while ago.)
There are 2 things that
+1/+1 :)
Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because...
2.
Author: oheger
Date: Sat Jan 13 08:33:02 2007
New Revision: 495918
URL: http://svn.apache.org/viewvc?view=revrev=495918
Log:
CONFIGURATION-245: Added support for ConfigurationErrorListeners to EventSource
Modified:
Author: oheger
Date: Sat Jan 13 09:06:29 2007
New Revision: 495926
URL: http://svn.apache.org/viewvc?view=revrev=495926
Log:
CONFIGURATION-245: New event and listener classes for configuration errors
Added:
[
https://issues.apache.org/jira/browse/CONFIGURATION-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464489
]
Michiel Kalkman commented on CONFIGURATION-215:
---
My apologies for not reacting sooner. This
Matt Benson wrote:
What's the current status of collections? It needs to
be broken into smaller pieces before any more weight
can be added?
Yes, I believe thats a good approach. And the Java 5 branch needs finshing.
Stephen
Hello,every one.I'm a graduate studying Automation in
China. Now I'm trying to find out how to interpete an
execute a xml script and wish to borrow ideas from
jelly.I want to understand how jelly interprte the xml
script and execute.I have read some of the codes.
Now I have some qustions:
Is there
Author: oheger
Date: Sat Jan 13 11:37:34 2007
New Revision: 495952
URL: http://svn.apache.org/viewvc?view=revrev=495952
Log:
AbstractConfiguration now supports setting a specific logger for a
configuration instance. Derived classes were updated to use this logger. This
update is related to
Author: dennisl
Date: Sat Jan 13 15:35:57 2007
New Revision: 496002
URL: http://svn.apache.org/viewvc?view=revrev=496002
Log:
Add a combined source and binary assembly.
It differs from the one produced by Ant in these areas:
- the docs folder is called site
- the complete src/ directory is
14 matches
Mail list logo
