On Wed, Feb 1, 2017 at 1:27 PM Robert Scholte wrote:
> bq. If you want to use JSR-330, you must understand that your code won't
> be compatible with Maven 2 or 3.0.x but only with Maven 3.1.0+
>
> this is probably the reason why *I* haven't seen it used that much.
>
Sure. In my case, this won't
bq. If you want to use JSR-330, you must understand that your code won't
be compatible with Maven 2 or 3.0.x but only with Maven 3.1.0+
this is probably the reason why *I* haven't seen it used that much.
Your confusion is probably coming from 2 different descriptors, which both
use @Componen
So...sorry, I am still confused. :-( If I look at the Maven and JSR 330
guide, especially with regard to plugins (
http://maven.apache.org/maven-jsr330.html#How_to_use_JSR-330_in_plugins),
then @Component is not used (see line 17 in the code sample). Are you
saying this is a mistake?
I think no
@Component works for sure. We're still within the Maven Plugin Context, so
better use the Plugin Annotations.
And yes, you can refer to both Plexus @Component instances and JSR330
@Named instance.
Robert
On Wed, 01 Feb 2017 21:01:10 +0100, Laird Nelson
wrote:
Thanks; yeah, I understan
Thanks; yeah, I understand--maybe I don't actually--that there are certain
Maven plugin annotations that get converted into the XML descriptor. But
what about line 52 and following in the link you sent:
1. @Component( role = MyComponentExtension.class,
2. hint = "..." )
3. private MyCom
No, plugin annotation are used to generate a plugin descriptor, i.e.
META-INF/maven/plugin.xml
At runtime this file is used to initialize the plugin, whereas the
specified components are injected with sisu/guice
Robert
On Wed, 01 Feb 2017 20:52:19 +0100, Laird Nelson
wrote:
Thanks. But
Thanks. But isn't _that_, in turn, replaced by JSR-330? This is what I'm
confused about.
On Wed, Feb 1, 2017 at 11:26 AM Robert Scholte wrote:
> This is what is used nowadays:
>
> https://maven.apache.org/components/plugin-tools/maven-plugin-tools-annotations/index.html
>
> Robert
>
> On Wed,
This is what is used nowadays:
https://maven.apache.org/components/plugin-tools/maven-plugin-tools-annotations/index.html
Robert
On Wed, 01 Feb 2017 19:21:09 +0100, Laird Nelson
wrote:
I apologize in advance for the inarticulate nature of this question.
I have this faint sense that Sisu a
JSR330 is supported [1]
JSR250 not yet [2]
-D
http://maven.apache.org/maven-jsr330.html
https://issues.apache.org/jira/browse/MNG-6084 cast your note
On Wed, Feb 1, 2017 at 10:21 AM, Laird Nelson wrote:
> I apologize in advance for the inarticulate nature of this question.
>
> I have this f
I apologize in advance for the inarticulate nature of this question.
I have this faint sense that Sisu and Guice are at the core of Maven these
days, with a Plexus layer on top.
This makes me think that perhaps I should be using different annotations in
my maven plugins than @Component etc.
Is t
One additional question,
I'm generating site.xml during pre-site phase and storing it into
target/generated-site/site.xml
But it seems to be not used
Is it by design? Or maybe I'm doing something wrong?
On Wed, Feb 1, 2017 at 8:16 PM, Maxim Solodovnik wrote:
> Thanks a lot!
> Works as expected!
Hi Hector,
please check the documentation of Nexus...and of course a google search
would have helped as well..
https://books.sonatype.com/nexus-book/reference/config-maven.html
Kind regards
Karl Heinz Marbaise
On 01/02/17 17:43, Magnanao, Hector wrote:
How do I setup my maven builds to us
How do I setup my maven builds to use the nexus repository for dependencies ?
Hector Magnanao Jr.
SCM Analyst
SAP Fieldglass
hector.magna...@sap.com
Thanks a lot!
Works as expected!
On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl wrote:
>
> Heya,
>
> Try ${project.build.directory}/generated-site or change the
> generatedSiteDirectory parameter, see
>
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
>
>
Heya,
Try ${project.build.directory}/generated-site or change the
generatedSiteDirectory parameter, see
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
HTH,
-Lukas
Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
Hello Karl,
Thanks a lot for the q
Hello Karl,
Thanks a lot for the quick response
pre-site phase is being called if I'm using "mvn site"
but XML files from target/generated-sources/site/xdoc/ are not being
used while site generation ...
Should it be generated to the different folder?
On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Mar
Hi,
On 01/02/17 06:52, Maxim Solodovnik wrote:
Hello All,
I wonder is it possible to generate content for maven site plugin?
We are using xdoc for our site. I would like to generate source using
xml-maven-plugin.
Right now I do it in generate-sources phase and polluting src/site/xdoc/ folder
I
17 matches
Mail list logo