I shall have to retract some of my worries and replace them by other worries :-)
There seems to have been a clean problem in both Gradle and Maven builds so I did the tests again. Using source and target mode of 6 then: Gradle with debug: -rw------- 1 russel russel 229210 2009-03-23 13:23 ADS-3.2.0-SNAPSHOT.jar Gradle without debug: -rw------- 1 russel russel 175366 2009-03-23 13:24 ADS-3.2.0-SNAPSHOT.jar Maven without debug: -rw------- 1 russel russel 197939 2009-03-23 13:23 ads-3.2.0-SNAPSHOT.jar Maven with debug: -rw------- 1 russel russel 197940 2009-03-23 13:25 ads-3.2.0-SNAPSHOT.jar So I am not entirely sure what the heck is going on with Maven. From what I can see the Maven plugin for Gradle is not doing a lot. the install target doesn't have the dependency on libs that it should and it doesn't actually install anything anywhere, it just creates the POM. -- Russel. ============================================================ Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected] London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected]
signature.asc
Description: This is a digitally signed message part
