Re: [paho-dev] Fixed build.xml for the Java client

[Dave Locke <locke@xxxxxxxxxx>]

I have a tidied up version based on the
buzzilla report.  There are a few additional changes to make based
on feedback once that is in place I'll sync it up. 


All the best 
Dave Locke

Senior Inventor, Pervasive and Advanced Messaging Technologies

locke@xxxxxxxxxx Dave Locke/UK/IBM@ibmgb 7-246165 (int) +44 1962816165 (ext) 37274133 (mobex) +44 7764132584 (ext)

Fringe Bluepages with fuel injection My Cattail: Share files in IBM and save your in-box

From:      
 "Nicholas O'Leary"
<nick.oleary@xxxxxxxxx>
To:      
 General development
discussions for paho project <paho-dev@xxxxxxxxxxx>, 
Date:      
 29/05/2012 12:24
Subject:    
   Re: [paho-dev]
Fixed build.xml for the Java client
Sent by:    
   paho-dev-bounces@xxxxxxxxxxx

---

Hi Andy,

> Many of you will know that the version of the Java client currently
in
> Eclipse Git will not build using the included build.xml file (well
- it
> *can* be built, but the Ant build will delete the client .jar file
at the
> end of the process, making it slightly pointless).

Ummm, it doesn't delete the jar file when I run it.... both from
within Eclipse or the command-line.

The clean target deletes the tree ${output.folder}/micro-client-v3 -
which is the temporary build area.
The jar file is left untouched in ${ship.folder}

If you overlap these directories, then the ship tree might end up
getting deleted - but that isn't the default setup.

It would be better for output.folder and ship.folder to be within the
project structure and not under /tmp - but I wasn't involved in
porting our internal version to the Paho contribution.

So I agree there are things to tidy up, but I disagree that it is as
fundamentally broken as you suggest.

Nick

On 29 May 2012 11:42, andypiperuk@xxxxxxxxx <andypiperuk@xxxxxxxxx>
wrote:
> Many of you will know that the version of the Java client currently
in
> Eclipse Git will not build using the included build.xml file (well
- it
> *can* be built, but the Ant build will delete the client .jar file
at the
> end of the process, making it slightly pointless).
>
> After the third time I checked the code into a fresh workspace and
had to
> fix this, I got a bit annoyed...
>
> I've now completely rewritten the build.xml file so that all of the
rules
> correctly depend on one another, there are proper descriptions, and
the
> "micro-client" and other legacy references are gone. See
the attachment on
> bug 375449 if you want to try it for yourself. Hopefully this can
get merged
> into Git before too long!
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=375449#c2
>
>
> (unfortunately there are still a bunch of warnings generated by the
javadoc
> target, but the docs still get generated - I'll try to find time to
look at
> that sometime soon)
>
> ((unfortunately the bugzilla stuff is still not linked to the mailing
list
> so it is still necessary to manually go check Bugzilla to see the
latest
> state of the nation))
>
> --
> Andy Piper | Farnborough, Hampshire (UK)
> blog: http://andypiper.co.uk
  |   skype: andypiperuk
> twitter: @andypiper  |  images: http://www.flickr.com/photos/andypiper
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/paho-dev
>
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU