just wondering why this move was made?
i'm using xdoclet on several projects and rather than copying all the
xdoc .jars to each project's lib directory, i'm using a build.properties
file to store references to each module.jar located in the cvs-downloaded
target/lib directory. now that the version number has been tacked on to
each module's .jar (i.e. module-1.2b2), each reference in build.properties
needs to be updated.
for those of us using the cvs version, is it possible to just use the
version number scheme for non-beta/rc releases, as updating all the
build.properties files for each beta release is somewhat a laborious
effort, or to just include the version number if making one large
xdoclet-all-version.jar (that includes everything)?
for those using build.properties file to include a reference to each of the
xdoclet module.jars that your project needs, how are you handling this change?
thank you and congrats on the 1.2b2 release!
-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
- [Xdoclet-devel] Re: [Xdoclet-user] modules .jar namin... tek1
- [Xdoclet-devel] Re: [Xdoclet-user] modules .jar ... Erik Hatcher
- Re: [Xdoclet-devel] modules .jar naming change t... Konstantin Priblouda