[slf4j-user] taglib

[Ceki Gulcu]

Hello Matt,

It would be no problem at all to grant you commit access to
slf4j.org's SVN under say
http://svn.slf4j.org/repos/slf4j-taglib. This would work just as any
other remote SVN repository. For the project site, you could use
either http://taglib.slf4j.org or http://www.slf4j.org/taglib at your
choice. Of course, you would also be able to deploy a new version of
the project at any time.

Let me know if you are interested so that we can make the necessary
arrangements. If you rather create the project on sourceforge, that
would be perfectly OK too.


Matt Humphreys wrote:
> Is there a preference for if the planned taglib is part of the slf4j
> project or has a separate (sourceforge?) project? My guess is that it
> will be easier as a separate project.
> 
> The code should only consist of a few classes (+ tests) and related
> files (the tld file will need to end up under META-INF). There will be
> some compile-time web depedencies (servlet api etc).
> 
> Presumably, if the taglib project is separate to slf4j then it
> shouldn't use the "org.slf4j" package naming but something like
> "net.sourceforge.slf4jtaglib" instead. If it goes on sourceforge, a
> suitable (unix) name would be "slf4j-taglib" i think.
> 
> The log4j taglib has a separate project and package to log4j.
> 
-- 
Ceki Gülcü