> Have you tried just adding a `provided`-scope dependency on that, as is
suggested for old mojo versions, rather than configuring
`maven-compiler-plugin`?
Brilliant! Thanks this did the trick. I removed the whole build block and
added the dagger-compiler as a provided dependency and now
On Wed, Sep 11, 2019 at 4:19 PM Mez Pahlan wrote:
> I tried removing the following from my POM which had the effect of making my
> plugin visible again in the snippet generator.
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
>
I tried removing the following from my POM which had the effect of making
my plugin visible again in the snippet generator.
org.apache.maven.plugins
maven-compiler-plugin
On Wed, Sep 11, 2019 at 2:35 PM Mez Pahlan wrote:
> > As for running an annotation processor in a plugin, isn't that how
> > @MetaInfService, @Indexed, @Restricted, and the like, are handled at
> > compile time?
>
> Errr.. pass. I don't know about these. Are you saying I should use these
>
Hi Slide
Good question. They have been like that since before this branch of the
plugin I am working on. Do you think I've not got the correct ones? Or
they're in the wrong scope?
On Wednesday, 11 September 2019 20:22:21 UTC+1, slide wrote:
>
> Are all the required plugins installed? I noticed
The pipeline steps are annotations symbols right? @Extension for the step,
and @Symbol for the short name
Would an extra annotation parser cause any issue? I would guess they are
non destructive and able to overlap quite easily.
What error are you getting when you are trying to use steps?
Also
Hi Matt
I don't have any experience with Guice but do with Dagger 2. I did try and
understand the differences but there wasn't a lot of guidance on how to use
it within Jenkins so I started to implement the Dagger 2 alternative. It
worked in the IDE in the sense that it compiled correctly and
Are all the required plugins installed? I noticed you had several items
marked as test scope in the pom.xml.
On Wed, Sep 11, 2019, 12:17 Mez Pahlan wrote:
> Thanks for the answers Jesse!
>
> > Try specifically: mvn clean hpi:run
>
> Same issue. Builds fine no obvious errors in the terminal
Thanks for the answers Jesse!
> Try specifically: mvn clean hpi:run
Same issue. Builds fine no obvious errors in the terminal output and
Jenkins starts normally. Plugin is listed in the list of installed plugins
but I cannot use it in a Pipeline or Freestyle job.
> Why? This would be
On Wed, Sep 11, 2019 at 3:20 AM Mez Pahlan wrote:
> I've looked at the local work directory in my IDE that is created when
> hpi:run is executed and I can see a file called appcenter.hpl but there isn't
> an expanded folder called appcenter in the way that other plugins have
> expanded
Hi there
I am trying to test my plugin using hpi:run which builds and compiles with
no errors but I can't see my plugin in the list of plugins when using the
Snippet Generator. I can see it in the list of installed plugins in the
Plugin Manager but it is also not available for use in a
11 matches
Mail list logo
