Hello, allow me to repost Alvaro Diaz's post. Here we go:
ROXES Technologies today announced the availability of ROXES Ant Tasks 1.2 as Open Source. This suite provides 17 custom tasks for the famous Apache Ant (http://ant.apache.org/) targeting java application deployment. Version 1.2 includes a whole bunch of bugfixes, improvements and new the tasks find, properties, compare, execute, call, os.properties win32.shortcut, win32.properties, win32.registry, unix.link, unix.properties, unix.kde.shortcut and unix.kde.directoryshortcut. Also new in this relaease is the integration of ROXES Win32 for Java (not offical released yet) which is used by the win32* tasks of this suite. In detail ROXES Ant Tasks contains: 1. win32.properties The win32.properties task provides access to special Windows directories like desktop, program menu, program files and many more. To use this task no special deployment for the native part is needed. ROXES Ant Tasks auto deploy's the Windows dll's. 2. win32.registry (since version 1.2) win32.registry lets you create/read/write/delete windows registry subtrees and entries. To use this task no special deployment for the native part is needed. ROXES Ant Tasks auto deploy's the Windows dll's. 3. win32.shortcut (since version 1.2) The win32.shortcut task is able to create Windows Shortcuts. Both Windows Shortcut file formats (.url and .lnk) can be read and written. To use this task no special deployment for the native part is needed. ROXES Ant Tasks auto deploy's the Windows dll's. 4. sfx (since version 1.2) sfx creates native self extracting executables out of ZIP archives. Currently supported target platforms are Windows, MacOS X, almost any Unix and self executable JAVA Jar files. For Windows the executable command may contain placeholders for registry, enviroment and executable filename which are evaluated at runtime. The icon for the windows executable can be defined be the task. 5. jstub jstub creates native executables for Windows, MacOS X and almost any Unix System out of a working JAR archive. For Windows the executable command may contain placeholders for registry, enviroment and executable filename which are evaluated at runtime. The icon for the windows executable can be defined be the task. 6. jnlp jnlp simplifies the creation of JNLP files for JAVA Web Start (http://java.sun.com/products/javawebstart/). The jnlp task is able to handle ANT Filesets as resources. This feature makes jnlp file creation using the jnlp Task much more easier. Find out more here: http://www.roxes.com/produkte/rat.html 7. preferences (since version 1.1) preferences lets you access the JAVA Preferences API. You can read, write, import, export and test preferences data and nodes. Using this task is very useful for configuring applications. 8. properties (since version 1.2) The properties task is able to write Java property files. This task can merge existing properties files with custom properties defined in the ant build file. The custom property definition can be used in conjunction with conditions. properties can be used to store user input during build for later use. 9. find (since version 1.2) The find task is able find files using a pattern. This task is especially useful when you use libraries which name contain version/build information which may vary over the time. Using the find task you can use the file of your choice without changing the build file again and again. 9. compare (since version 1.2) compare is able to compare 2 values either numerical or alphanumerical and set customziable properties depending of the result. 10. execute (since version 1.2) execute executes a block of tasks one ore more times depending of a condition. 11. call (since version 1.2) call executes a task one ore more times depending of a condition. 12. os.properties (since version 1.2) creates properties containing informations about the underlying os. 13. unix.properties (since version 1.2) makes important properties of the underlying unix system available as ant properties. espcially common kde directories like program menu, desktop etc. are supported. 14. unix.link (since version 1.2) creates a unix soft link. works only under unix. 15. unix.kde.shortcut (since version 1.2) creates a kde shortcut file used to create desktop or program menu entries. 16. unix.kde.directoryshortcut (since version 1.2) creates a kde directory shortcut file used to create desktop or program menu entries. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ lopica-announce mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lopica-announce
