The maven-web plugin was upgraded as part of ZEPPELIN-2: https://issues.apache.org/jira/browse/ZEPPELIN-2
I think that we should investigate whether the issues can be solved without updating the plugin and potentially revert the patch in favor of a patch that doesn't require a newer version of maven. What does the community think? On Wed, Apr 1, 2015 at 1:46 PM, Konstantin Boudnik <[email protected]> wrote: > That's a great point! While no one can dictate how a project manages their > dependencies and stuff, this input is quite valueable as it comes from > people > very close to the matter (Centos/EPEL) in question. > > Thanks RJ! > Cos > > On Tue, Mar 31, 2015 at 04:08PM, RJ Nowling wrote: > > Hi all, > > > > I noticed that the maven web front end plugin was recently updated. > > Unfortunately, this requires a never version of Maven which may be an > issue > > for CentOS / RHEL users since EPEL has an older version of Maven. > > > > I realize that this is a challenge for Zeppelin and ideally, would not be > > something Zeppelin should care about. However, it affects a prominent > > distribution and may hurt uptake. > > > > Any thoughts on how the project should handle this? > > > > Thanks, > > RJ >
