You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by Glenn Nielsen <gl...@voyager.apg.more.net> on 2001/05/22 03:13:18 UTC

[PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Attached is my previous file which documents the current jakarta-taglibs dir/file
layout and build process.  Included at the end is my proposal for a new
dir/file layout and build process.

Comments?  Votes?

The usual rules apply:
  [ ] +1 = I agree with this proposal and will support it
  [ ] +0 = I agree with this proposal, but do not have time to support it
  [ ] -0 = I do not agree with this proposal, but don't want to try
           to block it
  [ ] -1 = I do not agree with this proposal (requires reasons)

If approved, I can make the overall changes to jakarta-taglibs.
Once those are in place the individual taglibs can be migrated.
I will take care of the taglibs I authored, the request, response, 
session, regexp, datetime, and foundation taglibs.  It would be nice
if other taglib authors would volunteer to migrate the taglibs they
wrote.

Regards,

Glenn

----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Re: [PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
James Strachan wrote:
> 
> +1
> 
> A couple of minor points below...
> 
> > Attached is my previous file which documents the current jakarta-taglibs
> dir/file
> > layout and build process.  Included at the end is my proposal for a new
> > dir/file layout and build process.
> >
> > Comments?  Votes?
> 
> > Configuration Files (taglib-doc-kit)
> > ------------------------------------
> >
> > <taglib>/xml/<taglib>-tags.xml - Taglib and tag XML data transformed by
> taglib-doc-kit/xml/taglib-doc.xsl into the taglib index.html documentation
> and by taglib-doc-kit/xml/tld.xsl into the <taglib>.tld
> 
> I've been using the pattern
> 
>     <taglib>/xml/<taglib>.xml
> 
> (i.e. without the trailing "-tags") in the IO, Log and XTags libraries. Is
> this a problem or can we relax the restriction? I'm happy to go either way
> on this.
> 

<taglib>/xml/<taglib>.xml works for me.

> > Build Files
> > -----------
> >
> > .cvsignore - CVS file specifying what files to ignore, add build, dist,
> and build.properties
> 
> Cool!
> 
> > build.properties.sample
> >
> >    Example build properties file used to configure ant properties for
> required jar files.
> >    The jar file properties will be in the form "servlet.jar=<path to jar
> file>",
> >    version specific jars would be "servlet-2.2.jar=<path to jar file>.
> This means that
> >    the build.bat and build.sh scripts can be removed. $ANT_HOME/bin would
> have to be
> >    in your PATH so that you could build by using "ant dist".
> 
> Cool - like it.
> 
> > build.bat - Windows build script: Remove, no longer needed
> > build.sh - Unix build script: Remove, no longer needed
> > build.xml - Overall taglibs Ant build config
> > common.properties - common properties for building a taglib
> > common.xml - common Ant config for building a taglib:
> >
> >    Switch common.xml from using env vars for jar files to using
> build.properties.
> 
> +1
> 
> >    Add the ability to generate documentation using the new taglib-doc-kit.
> 
> I've already added the gen-doc target to the common.xml so that any task
> that depends on the gen-docs target gets this stuff for free. Its all in use
> in IO, Log and XTags right now.
>

Thanks
 
> I've no idea where the <taglib>-tags.xml files are for all the other
> libraries. I assume people have been creating the HTML and TLD by hand up to
> now? Maybe we can reverse engineer them all via XSLT then add the
> documentation back in by hand?
> 

Yeah, taglibs developed before the taglib-doc-kit was available haven't been
converted over to use it.

> Great piece of work Glenn.
>

Thanks, but this is only the start, there are enough +1 votes for me to implement
the changes.
 
> James
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Re: [PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Posted by James Strachan <ja...@yahoo.co.uk>.
+1

A couple of minor points below...

> Attached is my previous file which documents the current jakarta-taglibs
dir/file
> layout and build process.  Included at the end is my proposal for a new
> dir/file layout and build process.
>
> Comments?  Votes?


> Configuration Files (taglib-doc-kit)
> ------------------------------------
>
> <taglib>/xml/<taglib>-tags.xml - Taglib and tag XML data transformed by
taglib-doc-kit/xml/taglib-doc.xsl into the taglib index.html documentation
and by taglib-doc-kit/xml/tld.xsl into the <taglib>.tld

I've been using the pattern

    <taglib>/xml/<taglib>.xml

(i.e. without the trailing "-tags") in the IO, Log and XTags libraries. Is
this a problem or can we relax the restriction? I'm happy to go either way
on this.


> Build Files
> -----------
>
> .cvsignore - CVS file specifying what files to ignore, add build, dist,
and build.properties


Cool!

> build.properties.sample
>
>    Example build properties file used to configure ant properties for
required jar files.
>    The jar file properties will be in the form "servlet.jar=<path to jar
file>",
>    version specific jars would be "servlet-2.2.jar=<path to jar file>.
This means that
>    the build.bat and build.sh scripts can be removed. $ANT_HOME/bin would
have to be
>    in your PATH so that you could build by using "ant dist".

Cool - like it.

> build.bat - Windows build script: Remove, no longer needed
> build.sh - Unix build script: Remove, no longer needed
> build.xml - Overall taglibs Ant build config
> common.properties - common properties for building a taglib
> common.xml - common Ant config for building a taglib:
>
>    Switch common.xml from using env vars for jar files to using
build.properties.

+1

>    Add the ability to generate documentation using the new taglib-doc-kit.

I've already added the gen-doc target to the common.xml so that any task
that depends on the gen-docs target gets this stuff for free. Its all in use
in IO, Log and XTags right now.

I've no idea where the <taglib>-tags.xml files are for all the other
libraries. I assume people have been creating the HTML and TLD by hand up to
now? Maybe we can reverse engineer them all via XSLT then add the
documentation back in by hand?

Great piece of work Glenn.

James


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


Re: [PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
Pierre Delisle wrote:
> 
> >   [X] +1 = I agree with this proposal and will support it (after JavaOne :-))
> 
> Also, I assume our new build process would be in sync with the
> latest proposal made by Craig on tomcat-dev?
> 
> Thanks Glenn,
> 
>     -- Pierre

Yes.

----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Re: [PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Posted by Pierre Delisle <pi...@sun.com>.
>   [X] +1 = I agree with this proposal and will support it (after JavaOne :-))

Also, I assume our new build process would be in sync with the
latest proposal made by Craig on tomcat-dev?

Thanks Glenn,

    -- Pierre

Re: [PROPOSAL/VOTE] Jakarta-taglibs dir/file layout and build restructuring

Posted by Rich Catlett <ri...@more.net>.
This looks pretty cool! +1

---------------------------------------------------------------------
Rich Catlett        rich@more.net |  Confuscious say "Man who stand |
Programmer                        |   on toilet, high on pot!"      |
                                  |                                 |
---------------------------------------------------------------------

On Mon, 21 May 2001, Glenn Nielsen wrote:

> Attached is my previous file which documents the current jakarta-taglibs dir/file
> layout and build process.  Included at the end is my proposal for a new
> dir/file layout and build process.
> 
> Comments?  Votes?
> 
> The usual rules apply:
>   [ ] +1 = I agree with this proposal and will support it
>   [ ] +0 = I agree with this proposal, but do not have time to support it
>   [ ] -0 = I do not agree with this proposal, but don't want to try
>            to block it
>   [ ] -1 = I do not agree with this proposal (requires reasons)
> 
> If approved, I can make the overall changes to jakarta-taglibs.
> Once those are in place the individual taglibs can be migrated.
> I will take care of the taglibs I authored, the request, response, 
> session, regexp, datetime, and foundation taglibs.  It would be nice
> if other taglib authors would volunteer to migrate the taglibs they
> wrote.
> 
> Regards,
> 
> Glenn
> 
> ----------------------------------------------------------------------
> Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> MOREnet System Programming               |  * if iz ina coment.      |
> Missouri Research and Education Network  |  */                       |
> ----------------------------------------------------------------------