that would be great, thank you
On Wed, Aug 6, 2014 at 9:08 AM, Perry Nguyen <[email protected]> wrote: > You're right, it needn't be sealed, I'll change it for a future version > > -- > Sent from my phone > On Aug 6, 2014 12:01 AM, "Vyacheslav Blinov" <[email protected]> > wrote: > >> Thanks, looks like I managed to deal with this one, but now have another >> problem - my project is layed out in maven-style (or should I generalize to >> "custom style). Unfortunately, I can't supply such layout because trait >> ProjectLayout is sealed, which doesn't make much sence to me, as one could >> wish for completely wierd layout for his project, if he wants to do so, and >> both maven and gradle plugins for android support such layouts. >> >> пятница, 25 июля 2014 г., 23:50:35 UTC+4 пользователь pfn написал: >>> >>> You can see any of my examples in the test cases that say multi-project. >>> >>> Basically, it works identically to the old-style builds which ant used >>> to provide for android, create 'library projects' which have different >>> resources. >>> >>> An example in action is qicr, available on github. >>> >>> >>> On Fri, Jul 25, 2014 at 12:28 PM, Vyacheslav Blinov < >>> [email protected]> wrote: >>> >>>> Thanks for the info, updating to 1.3.3 really helps. I want to say >>>> thank you, this is awesome job, build times for me are ridiculously small >>>> compared to gradle and especially to maven, yet it feels more comfortable >>>> too! I already feel like I don't want to go back :) >>>> I didn't really understood, how I can do build flavors using >>>> multi-project, could you give me a clue or minimalistic example? I'm not >>>> yet much experienced with sbt. >>>> >>>> >>>> пятница, 25 июля 2014 г., 13:41:39 UTC+4 пользователь pfn написал: >>>>> >>>>> 1.3.3 fixes that, oh, also for build flavors, you can still do multi >>>>> project. >>>>> >>>>> -- >>>>> Sent from my phone >>>>> On Jul 25, 2014 12:47 AM, "Vyacheslav Blinov" <[email protected]> >>>>> wrote: >>>>> >>>>>> Thanks for this, if there is anything I could help with, I would be >>>>>> happy to do so. >>>>>> >>>>>> One more problem I met as for now, is I always have to run clean >>>>>> after changing code to be able to build a new apk with new code. With the >>>>>> simpliest project possible, I run ~android:run in sbt, and on source code >>>>>> change I'm getting this "[info] [debug] cache hit, skipping proguard!" >>>>>> message, and apk is not rebuilt/redeployed. If I manually deploy apk >>>>>> after >>>>>> it, I can see it isn't changed at all. Is there something I'm missing >>>>>> here? >>>>>> Shouldn't proguard + dex + aapt rerun every time source code changes, by >>>>>> default? >>>>>> >>>>>> суббота, 19 июля 2014 г., 19:46:24 UTC+4 пользователь pfn написал: >>>>>>> >>>>>>> I don't have any solution for build flavors yet. >>>>>>> >>>>>>> I am considering some ideas and will probably implement something >>>>>>> for a 1.4.x release. (which can be soon if I have enough interesting new >>>>>>> features to add) >>>>>>> >>>>>>> -- >>>>>>> Sent from my phone >>>>>>> On Jul 19, 2014 5:20 AM, "Vyacheslav Blinov" <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I want to migrate to sbt from Maven. The thing that stops me >>>>>>>> currently is build flavours. I have debug, testing and release build >>>>>>>> profiles in Maven pom.xml, which are replacing some configuration keys, >>>>>>>> like tracking tokens, singing key, package name, version name, etc. I >>>>>>>> want >>>>>>>> to achieve same kind of configuration in sbt. I assume I can use >>>>>>>> something >>>>>>>> like sbt-buildinfo to generate scala file with things like version, >>>>>>>> package >>>>>>>> name, tracking tokens, etc, but not sure about how to do different >>>>>>>> types of >>>>>>>> signing and 3rd build flavour? >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "scala-on-android" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "scala-on-android" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "scala-on-android" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "scala-on-android" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "scala-on-android" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
