try now
On Nov 4, 2012, at 6:05 PM, Dennis Lundberg wrote:
> Thanks Benson,
>
> Unfortunately that didn't help :(
> I still can't enter Administration for the MPOM project.
>
> On 2012-11-04 23:51, Benson Margulies wrote:
>> I made you a 'developer'. I am perplexed that the entire group of
>> co
Sure, I'll give it a try tomorrow.
On 2012-11-04 18:40, Robert Scholte wrote:
> Dennis, could you add an IT for it? It seems to be more of a coincidence
> that it was fixed, and we don't want such regression again, right?
>
> With the IT MPLUGIN-223 can be closed.
>
> Op Sun, 04 Nov 2012 18:34:1
Hi Paul,
This has broken the ITs. Could you please have a look at it.
Here's the relevant part from Jenkins build log:
[INFO] Building: purge-local-repository-manual-include/pom.xml
[INFO] run script
/home/jenkins/jenkins-slave/workspace/maven-plugins-ITs-m2/maven-dependency-plugin/target/it/pur
Thanks Benson,
Unfortunately that didn't help :(
I still can't enter Administration for the MPOM project.
On 2012-11-04 23:51, Benson Margulies wrote:
> I made you a 'developer'. I am perplexed that the entire group of
> committers isn't already there.
>
>
> On Sun, Nov 4, 2012 at 5:39 PM, Denn
I made you a 'developer'. I am perplexed that the entire group of
committers isn't already there.
On Sun, Nov 4, 2012 at 5:39 PM, Dennis Lundberg wrote:
> Hi
>
> Can someone please give me karma so that I can administer
> https://issues.apache.org/jira/browse/MPOM
>
> I need it to do release ma
Hi
Can someone please give me karma so that I can administer
https://issues.apache.org/jira/browse/MPOM
I need it to do release management.
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For addi
Hi,
The vote has passed with the following result :
+1 (binding): Mark Struberg, Hervé Boutemy, Kristian Rosenvold, Benson
Margulies, Olivier Lamy, Robert Scholte, Dennis Lundberg
I will promote the artifacts to the central repo.
On 2012-11-01 23:14, Dennis Lundberg wrote:
> Hi,
>
> Changes sin
+1 from me
On 2012-11-01 23:14, Dennis Lundberg wrote:
> Hi,
>
> Changes since the last release:
> http://svn.apache.org/viewvc/maven/pom/tags/apache-12/pom.xml?r1=HEAD&r2=1369674&diff_format=h
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheapache-007/
> https://
Le dimanche 4 novembre 2012 15:27:20 Benson Margulies a écrit :
> Hervé,
>
> What about the following sketch:
>
> Two goals:
>
> 1: to warn when a plugin param is a class type that either (a) cannot be
> mapped by plexus from XML in the POM,
useful, yes: are there known rules to detect such prob
Hervé,
What about the following sketch:
Two goals:
1: to warn when a plugin param is a class type that either (a) cannot be
mapped by plexus from XML in the POM, or (b) has no documentation for the
fields.
2: to include field-by-field documentation.
Neither of these is ideally met by linking t
yes, I understand the problem, but didn't find for the moment a way to
implement something.
I'm interested in working with anybody trying to make something
Here are some pointers:
- plugin documentation generation is done by PluginXdocGenerator in plugin-
tools [1]
- Modello model documentation g
+1
there is sufficient change to deserve a 3.2
I'm switching Jira and svn
Regards,
Hervé
Le dimanche 4 novembre 2012 17:51:42 Kristian Rosenvold a écrit :
> The dependency change alone should be sufficient for 3.2
>
> Kristian
>
> Den 4. nov. 2012 kl. 16:57 skrev Dennis Lundberg :
> > Hi
> >
Dennis, could you add an IT for it? It seems to be more of a coincidence
that it was fixed, and we don't want such regression again, right?
With the IT MPLUGIN-223 can be closed.
Op Sun, 04 Nov 2012 18:34:15 +0100 schreef Dennis Lundberg
:
On 2012-11-04 17:59, Robert Scholte wrote:
Hi,
On 2012-11-04 17:59, Robert Scholte wrote:
> Hi,
>
> I wasn't aware of this issue, neither of the extractors-property.
> Right now I let the plugin check for the maven-plugin-annotations
> dependency.
> If I can get the same information from the pluginDescriptor, the code
> can be simplified.
> Is
Hi,
I wasn't aware of this issue, neither of the extractors-property.
Right now I let the plugin check for the maven-plugin-annotations
dependency.
If I can get the same information from the pluginDescriptor, the code can
be simplified.
Is it really the same thing?
Robert
Op Sun, 04 Nov 20
The dependency change alone should be sufficient for 3.2
Kristian
Den 4. nov. 2012 kl. 16:57 skrev Dennis Lundberg :
> Hi
>
> Looking at the road map in JIRA, I think the next release should be 3.2
> since we have some improvements now.
>
> https://jira.codehaus.org/browse/MPLUGIN#selectedTab=co
Hi
Looking at the road map in JIRA, I think the next release should be 3.2
since we have some improvements now.
https://jira.codehaus.org/browse/MPLUGIN#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
WDYT?
On 2012-10-29 18:21, Kristian Rosenvold wrote:
> I'm fixing MPLUGIN
Hi
It seems to me that Robert fixed
https://jira.codehaus.org/browse/MPLUGIN-223
when he fixed
https://jira.codehaus.org/browse/MPLUGIN-231
Should I close MPLUGIN-223 as a duplicate?
On 2012-11-02 22:48, Kristian Rosenvold wrote:
> i'll wait for something good ;)
>
> K
>
> Den 2. nov. 2012 kl.
18 matches
Mail list logo