Hi, If you are available around 10PST tomorrow, we could try to make this conversation public during the https://www.meetup.com/Jenkins-online-meetup/events/243555567/ .
Cyrille On Monday, September 25, 2017 at 1:14:38 PM UTC+2, Cyrille Le Clerc wrote: > > Hello, > > I guess you are referring to the code of the jenkins whitesource plugin > and referring to MavenOssInfoExtractor.java > <https://github.com/jenkinsci/whitesource-plugin/blob/release-tag-1.8.2/src/main/java/org/whitesource/jenkins/extractor/maven/MavenOssInfoExtractor.java> > . > > The withMaven plugin works quite differently from the MavenJob type, the > way to list the dependencies is different and the documentation for plugins > authors is not written (because the APIs are not finalized). > > Would you have a moment for an hangout session so that I can walk you > through the withMaven plugin architecture? > > > > On Sunday, September 24, 2017 at 2:33:19 PM UTC+2, > [email protected] wrote: >> >> Hi all, >> I'm trying to integrate a Pipeline job, while using 'withMaven' step - >> means I have a pom.xml file in that specific workspace. >> This run is represented in the code as 'Workflow Run', and not as >> 'MavenModuleSetBuild' - which makes it difficult to go over the pom.xml >> file, and collect it's (transitive) dependencies. >> My question is - is it possible to resolve somehow the pom.xml *transitive >> *dependencies, in a similar way to a MavenModuleSetBuild (Maven job) run? >> >> Thanks in advance! >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2362a9c2-f077-4d24-ba82-800aa113d2e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
