The point is now the conf is hard to understand and no more obvious (why i ask) Le 22 févr. 2013 18:42, "Jean-Louis MONTEIRO" <[email protected]> a écrit :
> As an end user, I would like to keep previous blocks even if we can't get > the most from the new features (that's the life). > If I want new features, I can still move to the new configuration. > > So +1 for new features or new lightweight configuration and +1 to keep as > much as possible the old configuration stuff. > > It eases the adoption and as the plugin is pretty new, we probably don't > want to lose people. > > JLouis > > > 2013/2/21 Romain Manni-Bucau <[email protected]> > > > Hi guys, > > > > Which constraint do we have on tomee mvn plugin config compatibility > > between versions? > > > > Trunk version is no more so consistent regarding synchronization because > of > > new features but fixing it will break old configs. > > > > Basically i'd like: > > > > * get rid of main synchronisation block (since we can have multiple now) > > * set a single source/destination pair by synchro (and not binaries and > > resources ones) > > * add an attribute to guess synchronisation (if xhtml, js, tml....then > auto > > synch it with reload auto or not) > > > > If we can't break current config i'm ok to either keep it as this or just > > work on the diff since last release > > > > > > -- > Jean-Louis >
