Re: Marshaling a byte array by ref
Roger I Martin PhD <[email protected]> Thu, 13 Jul 2006 16:30:59 -0400
| Newsgroups | gmane.comp.windows.devel.jawin |
|---|---|
| Message-ID | <[email protected]> |
Oh you are a great help, Morten! You have it automated. I'll check with Claude Eisenhut & get the revision updated before pushing it in. Glad work is is happening for you although it be strict:-) No new marshalers have come along and no companies have asked for features like for my other projects. But I may put some of my Jawin changes into cvs. Depends on work transitions similar to your situation. Thank you, Roger Morten Andersen wrote: > Hi Roger, > > Roger I Martin PhD wrote: >> Hi Morten! >> >> Are you still readily setup to zip and put a release online? Then the >> auto gc will be available without cvs. >> > > I am somewhat ashamed to admit, that I did see your and Claude > Eisenhut's support for this, and I would really like to play with it - > it sounds very cool! But unfortunately I am in a "strict work, no fun > (read: no playing with cool tools)" company for the time being, and at > home I really don't do any development these days, partly because my old > win-box died, and I haven't really found the time to find a replacement. > > So no, unfortunately I am not able to create a Jawin deploy-build for > the time being (I haven't even checked out my CVS-repository after > SF.net has changed the CVS-layout). But if I remember correctly we got > this pretty automated using the Ant build file. I think you can do it by: > > 1) update the two app.version and app.version.win properties in > global.properties. E.g. to 2.0-alpha2. And please also update the > revision history in "jawinrevisions.html", and also add Claude Eisenhut > to the contributers list on "jawincontributers.html" (you should > probably ask his permission to do this, of course). > 2) run "ant -Dcpp.compile.enabled=true deploy" > 3) after you check that the output of the deploy folder looks decent, > FTP upload the release with > 4) "ant -Dsourceforge.password=<password> upload" > 5) follow the information from SF.net on how to get the uploaded files > attached to the Jawin project: > http://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1 > 6) finally, tag the CVS with e.g. something like: "jawin_2_0_a2" > > Sorry I can't be of much help. > > Best Regards > Morten >