hello Emmanuel, Emmanuel Bourg <ebo...@apache.org> writes: > Le 16/12/2018 à 12:00, Felix Natter a écrit : > >> True, the 3.1 pom is installed, but the debian pom isn't, and I think >> that maven-repo-helper usually creates/links >> .../javax.servlet-api/debian/javax.servlet-api-debian.(pom,jar) >> as well. > > libservlet3.1-java never contained the 'debian' version, but the new
Yes, that's what I said above: It is a riddle to me which change triggered it (also the last fop release was before the last Freeplane release, which obviously worked for me), but having the debian/*.pom would fix it :-) > libservlet-api-java which will arrive soon does have it. > > >> One important question: How can I prevent the AUTORM from happening? > > Either wait for libservlet-api-java to hit unstable, or add this rule to > debian/maven.rules: > > javax.servlet javax.servlet-api * s/.*/3.1/ * * I can confirm that this fixes the issue. I kindly ask for your advice: Freeplane is due to be removed in 20 days, so I tend to wait for libservlet-api-java, also because the rule would be broken as soon as different version of javax.servlet-api enters Debian (right?). Will you also update r-deps (like libfop-java) and will it take less than 20 days? Many Thanks and Best Regards, -- Felix Natter debian/rules!
