Re: JAWin install
Morten Andersen <[email protected]>
| Newsgroups | gmane.comp.windows.devel.jawin |
|---|---|
| Organization | Arosii Information Systems A/S |
| Message-ID | <[email protected]> |
Roger I Martin PhD wrote:
> And what Java version is Jdeveloper using?
>
> I'll bundle and post an update download at the sourceforge site...
Hi Roger
I think the ant-build file makes this possible in only a few steps:
ant -Dcpp.compile.enabled=true deploy
Which creates the "release"-able file (containing the relevant jars,
dll's and docs and javadocs - but no source):
deploy/jawin-1.0.18.zip
(you should probably update the app.version property in
global.properties to eg. 1.0.19, before doing the build)
The following ant target should then (hopefully, I haven't tested this
part) upload the file as described in the SourceForge guide to file
release -
http://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1#howtoupload
ant -Dsourceforge.password=EMAIL upload
where you should replace EMAIL with your SourceForge email address.
After that it should only be necessary to follow the manual steps in the
SourceForge guide.
If you want to update the Jawin main page
(http://jawinproject.sourceforge.net/) with the uptodate documentation
in the same step, a full web-site is generated by the deploy ant-target
too, and is placed in
deploy/web
The ant build-file, does not pt. contain any helper targets for
uploading this, please let me know if you want this.
Please also let me know if you think the deploy-target should also make
a source release, eg. jawin-1.0.18-src.zip. So that users like Yuli, who
are unable to access the SourceForge CVS, can still get the source (I
think that tasks that can be automated, should be automated in the
ant-file so that you don't manually have to "waste" time on packaging a
source release).
Best Regards
Morten