Hi!
Sorry that I didn't have more time yesterday night, so I missed the most
important question:
Is the @Component annotation meant to be used on the component itself (for
defining the factory rule, like @ApplicationScoped) or is it used on the
InjectionPoint like @Inject?
Or is it like a @Qu
On 21/05/2012, at 3:45 AM, Hervé BOUTEMY wrote:
> here, the end-user is a plugin developer, then someone who should be able to
> create a (Plexus) component when necessary
>
> Yes, I liked @Component too but as soon as you write a component and inject
> somponents inside it, you discover the d
On 21/05/2012, at 8:48 AM, Barrie Treloar wrote:
> On Sun, May 20, 2012 at 8:12 PM, Hervé BOUTEMY wrote:
>> bingo: you got it!
>> ok, now I understand, you're right, I was focused at my property vs
>> expression
>> task and forgot the most normal way of configuring plugins...
>>
>> I'll revert
hello
i don't know whom to ask on this question , so i mail u.
i set SCOPE of all my dependencies to be PROVIDED, just because i don't
want all the related jars to be deploy and package. after the commond "mvn
clean package" i found all the jars were pakaged in the final war file, and
when i run
On 12-05-20 11:45 AM, Hervé BOUTEMY wrote:
I'm looking at code, improving easy to do things (like generics).
I like MPLUGINTESTING-23: I suppose that's *the* big feature :)
is it related to MPLUGINTESTING-7?
Right. I marked MPLUGINTESTING-7 as duplicate of MPLUGINTESTING-23.
another quest
On Sun, May 20, 2012 at 8:12 PM, Hervé BOUTEMY wrote:
> bingo: you got it!
> ok, now I understand, you're right, I was focused at my property vs expression
> task and forgot the most normal way of configuring plugins...
>
> I'll revert and improve the docs
I've been lurking on this discussion, so
IMHO, it can let users think at new extensions: anybody interested in Groovy
or scala?
:)
Le lundi 21 mai 2012 00:13:57 Olivier Lamy a écrit :
> Sounds good.
>
> I'm not sure mojo with beanshell is really use :-)
>
> 2012/5/20 Hervé BOUTEMY :
> > see https://jira.codehaus.org/browse/MPLUGIN-200
Sounds good.
I'm not sure mojo with beanshell is really use :-)
2012/5/20 Hervé BOUTEMY :
> see https://jira.codehaus.org/browse/MPLUGIN-200
>
> comments welcome
>
> Regards,
>
> Hervé
>
> -
> To unsubscribe, e-mail: dev-unsubscr
Le dimanche 20 mai 2012 20:36:14 Christian Grobmeier a écrit :
> > is it better to continue this discussion on Maven list or on logging?
>
> I think only less people from logging are subscribed to the maven
> lists. If you would join us at gene...@logging.apache.org, then it
> would help much. Tha
Am 20.05.2012 19:46 schrieb "Hervé BOUTEMY" :
>
> here, the end-user is a plugin developer, then someone who should be able
to
> create a (Plexus) component when necessary
>
> Yes, I liked @Component too but as soon as you write a component and
inject
> somponents inside it, you discover the discre
On Sun, May 20, 2012 at 7:28 PM, Hervé BOUTEMY wrote:
> Le dimanche 20 mai 2012 18:46:06 Christian Grobmeier a écrit :
>> That being said, we have not had a vote on that, but it seems that the
>> majority of us doesn't want to use the CMS directly. Therefore we were
>> initially looking for a mvn
here, the end-user is a plugin developer, then someone who should be able to
create a (Plexus) component when necessary
Yes, I liked @Component too but as soon as you write a component and inject
somponents inside it, you discover the discrepency: the more I work on this,
the more I discover th
Le dimanche 20 mai 2012 18:46:06 Christian Grobmeier a écrit :
> That being said, we have not had a vote on that, but it seems that the
> majority of us doesn't want to use the CMS directly. Therefore we were
> initially looking for a mvn based solution. Did I understand you
> correct that the "mai
Hi Hervé,
>> As I could understand, it checks out a specific svn repository path,
>> diffs/merges it with my locally generated site, and then commits it
>> back to the specific repository. This is basically what apache
>> projects could need with svnpubsub.
> exactly
> notice that if you have unve
I'm looking at code, improving easy to do things (like generics).
I like MPLUGINTESTING-23: I suppose that's *the* big feature :)
is it related to MPLUGINTESTING-7?
another question, I didn't find answer in FAQ:
- why is it restricted to Maven 3? probably some explanations and site work
for mvn2
Thank you for your feedback, Hervé.
I've opened three jira issues to document changes that went into
r1185951. Looking at svn log I believe all user-visible changes since
alpha-1 have corresponding jiras now.
Anything else you think will make release review easier to proceed?
--
Regards,
Igor
Hi Igor,
Yes, the release process is the basic way to go: I can help if you need.
The hard part IMHO will be to have people being sufficiently confident to vote
on
the content, since this is a "hard-core" component :)
I had a look at actual site [1]: looks promising, with actual release being
Heh. I finally got some time to follow up on my proposal to make mvn 3.x
compatible plugin-testing the new trunk and move mvn 2.x code to a
branch [1]. I would like to make plugin-testing 2.0 release now, but not
sure about the release process. Can I just stage a release and call a
vote or there i
Le dimanche 20 mai 2012 14:23:59 Christian Grobmeier a écrit :
> Hello folks,
>
> what is the state of the maven-site-scm-publish plugin?
>
> As I could understand, it checks out a specific svn repository path,
> diffs/merges it with my locally generated site, and then commits it
> back to the sp
for sure you can use
@Component( role = ArtifactMetadataSource.class, roleHint = "maven" )
protected Object artifactMetadataSource;
:-)
2012/5/20 Mirko Friedenhagen :
> Hello Olivier,
>
> hopefully the role and the type of the member are not always redundant :-):
>
> --- snip ---
> @Component(
Perso, I prefer @Component more "auto documented" name.
IMHO The goal is to hide to end user what is used in core so why using
plexus naming.
2012/5/20 Hervé BOUTEMY :
> of course, +1 since we discussed it :)
>
> but thinking once more at it, I just found that @Component should be renamed
> to @Re
Hello folks,
what is the state of the maven-site-scm-publish plugin?
As I could understand, it checks out a specific svn repository path,
diffs/merges it with my locally generated site, and then commits it
back to the specific repository. This is basically what apache
projects could need with svn
of course, +1 since we discussed it :)
but thinking once more at it, I just found that @Component should be renamed
to @Requirement, to match corresponding plexus annotation, isn't it?
Regards,
Hervé
Le dimanche 20 mai 2012 09:00:05 Olivier Lamy a écrit :
> Hi,
>
> After discussion on irc wit
bingo: you got it!
ok, now I understand, you're right, I was focused at my property vs expression
task and forgot the most normal way of configuring plugins...
I'll revert and improve the docs
thank you!
Hervé
Le dimanche 20 mai 2012 12:04:31 Robert Scholte a écrit :
> Consider
>
> @Parameter
Consider
@Parameter default-value="${project}"
private MavenProject mavenProject
This would suggest, that you use it inside the configuration of the plugin
???
Also, it will appear in the goal-reports. If I'm correct readonly is used
as a marker to ignore this parameter in the report.
Hello Olivier,
hopefully the role and the type of the member are not always redundant :-):
--- snip ---
@Component( role = ArtifactMetadataSource.class, roleHint = "maven" )
protected ArtifactMetadataSource artifactMetadataSource;
--- snap ---
Regards Mirko
On Sun, May 20, 2012 at 10:56 AM, Ro
see https://jira.codehaus.org/browse/MPLUGIN-200
comments welcome
Regards,
Hervé
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
@Parameter default-value="${project}"
or with javadoc tags
/**
* @parameter default-value="${project}"
*/
no?
IIUC, the old habbit to use expression because the attribute name let think
it
can do more than default-value is the culprit: that's why renaming expression
is really important IMH
+1
Robert
Op Sun, 20 May 2012 09:00:05 +0200 schreef Olivier Lamy :
Hi,
After discussion on irc with Hervé, I think role attribute in
@Component can be of type Class rather than String.
@Component( role = ArtifactMetadataSource.class, roleHint = "maven" )
protected ArtifactMetadataSo
Hmm, maybe I was a bit too fast.
How about those standard expressions like ${project}, ${settings},
${localRepository}, etc.
These should stay readonly and AFAIK the @parameter is the only way to set
these fields.
-Robert
Op Sun, 20 May 2012 00:10:22 +0200 schreef Hervé BOUTEMY
:
ok,
Hi,
After discussion on irc with Hervé, I think role attribute in
@Component can be of type Class rather than String.
@Component( role = ArtifactMetadataSource.class, roleHint = "maven" )
protected ArtifactMetadataSource artifactMetadataSource;
Any objections on this change ?
Thanks,
--
31 matches
Mail list logo
