Yes I know I've updated but it should not be a problem. You can always define the dep of the plugin right ?
Anyway I will isolate the wagon use. Regards JB Le 25 févr. 2019 à 22:18, à 22:18, Grzegorz Grzybek <[email protected]> a écrit: >Hello > >I added a comment under >https://issues.apache.org/jira/browse/KARAF-6097 >(wagon-http 3.2.0 → 3.3.1 upgrade) that this broke invocation of >nexus-staging-maven-plugin:deploy too. However I call this plugin from >cli >as goal and I have no way of changing the dependency explicitly to >wagon-http 3.2.0 (which works btw). > >I'm not saying that we should revert >https://github.com/apache/karaf/commit/5097abd6d4c - just saying that >I've >found the root cause of the problem ;) > >regards >Grzegorz Grzybek > >niedz., 24 lut 2019 o 12:14 Jean-Baptiste Onofré <[email protected]> >napisał(a): > >> Not really, it's updated, but deploy plugin didn't yet. Do you just >have >> to define wagon version dep. >> >> Regards >> JB >> >> Le 24 févr. 2019 à 11:39, à 11:39, Fabian Lange ><[email protected]> >> a écrit: >> >Hi JB, >> >happened on 3.3 - 3.6 >> >On deploy 2.8.2 and 3.0.0.M1 >> > >> >In typical rubber ducking style, I managed to get it working just 2 >> >minutes ago, by overriding wagon for deploy >> > >> ><plugin> >> > <groupId>org.apache.maven.plugins</groupId> >> > <artifactId>maven-deploy-plugin</artifactId> >> > <version>2.8.2</version> >> > <dependencies> >> > <dependency> >> > <groupId>org.apache.maven.wagon</groupId> >> > <artifactId>wagon-http</artifactId> >> > <version>2.12</version> >> > </dependency> >> > </dependencies> >> ></plugin> >> > >> > >> >So I guess somehow the new karaf maven plugin messes with the wagon >> >dependency for deploy >> > >> >Fabian >> > >> >On Sun, Feb 24, 2019 at 11:31 AM Jean-Baptiste Onofré ><[email protected]> >> >wrote: >> >> >> >> Hi Fabian, >> >> >> >> What Maven version are you using ? And do you have wagon defined >in >> >your >> >> pom.xml ? >> >> >> >> Karaf itself is a custom distribution, so, it works fine. I think >> >it's >> >> dependency version issue on wagon. >> >> >> >> Regards >> >> JB >> >> >> >> On 24/02/2019 11:20, Fabian Lange wrote: >> >> > Hi, >> >> > >> >> > did anyone come across this problem when deploying a 4.2.3 >custom >> >distribution? >> >> > >> >> > [ERROR] Failed to execute goal >> >> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy >> >> > (default-deploy) on project karaf-assembly: Execution >> >default-deploy >> >> > of goal >org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy >> >> > failed: An API incompatibility was encountered while executing >> >> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy: >> >> > java.lang.NoSuchMethodError: >> >> > >> >> >>org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I >> >> > >> >> > >> >> > I have the feeling that there is a new dependency from pax-url / >> >karaf >> >> > maven plugin interfering with mvn-deploy? >> >> > >> >> > I will dig into this and report findings, if somebody has seen >and >> >> > solved this let me know. Thx >> >> > >> >> > Fabian >> >> > >> >> >> >> -- >> >> Jean-Baptiste Onofré >> >> [email protected] >> >> http://blog.nanthrax.net >> >> Talend - http://www.talend.com >>
