Dmitry, if you are using or want to use the FlowLogix library, and have a specific issue with it, please report it via issue tracking. I don't require patch with tests and I look at them all :)
The library is meant to be primarily a JEE bridge, so if you really don't want any JEE dependencies, this library is not for you. But... if there is enough interest though, I can split it up into two modules, one JEE and one just Tapestry enhancements. I am hoping not to do this because all of the enhancements should really be in Tapestry itself, and I am hoping to use this thread as a catalyst to get some of the stuff that should be in Tapestry into Tapestry anyway. A lot of people give JEE a bad rap, which mostly stems from EJB 2.1 days (long gone now) The only JEE dependency is the API, which requires no runtime support, if its not used. All other dependencies are not required if they are not used. On Oct 28, 2013, at 3:02 AM, Dmitry Gusev wrote: > By modules I mean not maven/gradle sub projects, but tapestry modules which > are simple Java classes: one module -- one class. No need to add these > modules to auto discovery via manifest. Users may include these modules by > using @SubModule on their AppModules. I see no extra-overhead here. > > Your assumption about "everybody want my fixes" is wrong, I don't want them > in my project if they come with 3rd party library that has tons of extra > dependencies like JEE stuff, etc. > > Also I want the ability to opt-out some fixes if I have better workaround > for them. That was my point. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
