Re: [Browserlaunch2-development] Archives for file releases

[Jeff C. <sdv...@ya...>]

Thanks Thomas,

Here's the targets and properties file that I was using for deployment.

    <target name="deployApp" depends="buildApp">
         <jar destfile="${deploy.dir}/BrowserLauncher2.jar"
            index="true"
            update="overwrite"
            manifest="${app.manifest}" >
            <fileset dir="${build.dir}" 
includes="edu/stanford/ejalbert/**" />
            <fileset file="${gnu.copying}" />
            <fileset file="${readme}" />
        </jar>
         <jar destfile="${deploy.dir}/BrowserLauncher2Test.jar"
            index="true"
            update="overwrite"
            manifest="${app.manifest.test}" >
            <fileset dir="${build.dir}" 
includes="edu/stanford/ejalbert/**" />
            <fileset file="${gnu.copying}" />
            <fileset file="${readme}" />
        </jar>
    </target>

-----------------------------

# build properties for BrowserLauncher project

src.dir=/home/jeffery/browserlauncher_stuff/source

build.dir=/home/jeffery/java_dev/classes
class.path=${build.dir}
optimize=on

deploy.dir=/home/jeffery/browserlauncher_stuff/release

app.manifest=/home/jeffery/browserlauncher_stuff/deployment/manifest.mf
app.manifest.test=/home/jeffery/browserlauncher_stuff/deployment/manifest.test.mf

gnu.copying=/home/jeffery/java_dev/gnu_stuff/lgpl/COPYING.txt
readme=/home/jeffery/browserlauncher_stuff/deployment/README.txt

--------------------------------------------------------

Thomas Aglassinger wrote:

> The CVS now contains a build.xml for ant. Right now, running
>
>   ant
>
> eventually yields two archives:
>
> - BrowserLauncher2.jar: a small JAR file containing only the *.class 
> files. This is intended to be included in (distributed) client 
> applications that use BrowserLauncher2.
>
> - BrowserLauncher2-all.zip: a "big" Zip archive again containing the 
> class files. Additionally, it includes the source and Javadoc API 
> documentation. This is intended to be used by developers that want to 
> develop applications that use BrowseLauncher2. They occasionally will 
> want to take a look at the API or source.
>
> Open issues:
>
> - The archives do not yet include COPYING.txt and stuff.
>
> - The archives do not yet include the MANIFEST.mf.
>
> Once these are addressed, we could make these archives available for 
> download.
>
> Any thoughts?
>
> Thomas.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Browserlaunch2-development mailing list
> Bro...@li...
> https://lists.sourceforge.net/lists/listinfo/browserlaunch2-development
>