ew.
>
> Robert
>
> On Wed, 03 Oct 2018 11:15:50 +0200, Olivier Lamy wrote:
>
> > Hi,
> > I'm trying to build maven-plugin-plugin with jdk11.
> > But yup this will not work with import com.sun.javadoc.Tag; import
> > com.sun.tools.doclets.Taglet; etc... The
notice these missing doclettags.
Robert
On Wed, 03 Oct 2018 11:15:50 +0200, Olivier Lamy wrote:
Hi,
I'm trying to build maven-plugin-plugin with jdk11.
But yup this will not work with import com.sun.javadoc.Tag; import
com.sun.tools.doclets.Taglet; etc... There is even some javax.swing
usage...
Hi,
I'm trying to build maven-plugin-plugin with jdk11.
But yup this will not work with import com.sun.javadoc.Tag; import
com.sun.tools.doclets.Taglet; etc... There is even some javax.swing
usage... (well mainly to use only some data structure).
I guess in 2018 everyone is now usin
On 2017-10-26T14:05:01 +
Mark Raynsford wrote:
>
> I'm running into what I think is MPLUGIN-304 [0] when upgrading
> several of my Maven plugins to JDK 9. The issue has been fixed, but I
> don't think that fix has made it into any release yet.
Sorry for the noise: I made a mistake. I thought
Hello.
I'm running into what I think is MPLUGIN-304 [0] when upgrading
several of my Maven plugins to JDK 9. The issue has been fixed, but I
don't think that fix has made it into any release yet. Is there a
release of maven-plugin-plugin due any time soon?
Apologies if this information
@since values ignored in report
> New strategy where we don't need a parameter anymore (who would change it?)
>
> Added:
>
> maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven
> /plugins/
> maven/plugin-tools/trunk/maven-plugin-plugin/src/ma
/plugin-tools/maven-plugin-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-plugin-plugin
3.4
Release Notes - Maven Plugin Tools - Version 3.4
** Bug
* [MPLUGIN-238] - HelpMojo phases fails when using java-annota
1. problem reproduced: in a global plugin-tools build, there is no compilation
issue but if I build only maven-plugin-plugin the compilation failure happens
strange: I wouldn't expect the reactor build to have any impact on build
classpath
2. problem explained:
when I changed the annota
mbre 2014 22:40:17 Robert Scholte a écrit :
> >> Hi,
> >>
> >> This commit gives me compilation errors, e.g.
> >> [ERROR]
> >> /E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-pl
> >> ugi
> >> n/src/main/java/org/a
Hervé BOUTEMY
:
uh, which JDK version?
Regards,
Hervé
Le mardi 30 décembre 2014 22:40:17 Robert Scholte a écrit :
Hi,
This commit gives me compilation errors, e.g.
[ERROR]
/E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-plugi
n/src/main/java/org/apache/maven/plugin/p
uh, which JDK version?
Regards,
Hervé
Le mardi 30 décembre 2014 22:40:17 Robert Scholte a écrit :
> Hi,
>
> This commit gives me compilation errors, e.g.
> [ERROR]
> /E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-plugi
> n/src/main/java/org/apache/m
Hi,
This commit gives me compilation errors, e.g.
[ERROR]
/E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java:[77,6]
E:\java-workspace\apache-maven-plugin-tools\plugin-tools\maven-plugin-plugin\src\main
.
The Maven Plugin Plugin is used to create a Maven plugin descriptor for any
Mojo's found in the source tree, to include in the JAR. It is also used to
generate report files for the Mojos as well as for updating the plugin
registry, the artifact metadata and generating a generic help goal.
Le lundi 28 janvier 2013 23:22:15 Karl Heinz Marbaise a écrit :
> So the question is how does Maven know of the version of the above
> plugin which has been defined in the pluginManagement section before.
see maven-model-builder, phase 2, "plugin management injection" step [1], done
in code [2] by
Hi there,
currently i'm working on a new maven plugin
http://khmarbaise.github.com/itexin-maven-plugin/usage.html
which will make it possible to execute a plugin several times based on
values (iteration).
But my question is related how to get the information about a plugins
version of a defined
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.2.
The Maven Plugin Plugin is used to create a Maven plugin descriptor
for any Mojo's found in the source tree, to include in the JAR. It is
also used to generate report files for the Mojos as well a
06 PM, Ben Tatham wrote:
> Before I report a bug, I thought I'd ask if I'm doing something wrong.
>
> I have a plugin that has a bunch of mojo's as well as defines
> components.xml to set up a new lifecycle.
>
> I recently converted it from maven-plugin-plugin 2.9
Before I report a bug, I thought I'd ask if I'm doing something wrong.
I have a plugin that has a bunch of mojo's as well as defines
components.xml to set up a new lifecycle.
I recently converted it from maven-plugin-plugin 2.9 to 3.1 and used java5
annotations. Note that th
2012/8/1 Jesse Glick :
> On 07/31/2012 02:43 PM, Hervé BOUTEMY wrote:
>>
>> compile is the default scope, isn't it?
>> Or do I miss something?
>
>
> Perhaps provided was meant?
Yup. Just saying this is not needed at runtime level.
I have changed and remove the scope.
>
>
> -
On 07/31/2012 02:43 PM, Hervé BOUTEMY wrote:
compile is the default scope, isn't it?
Or do I miss something?
Perhaps provided was meant?
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-ma
; only scope compile is needed for annotations
>
> Modified:
>
> maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-an
> notations.apt.vm
>
> Modified:
> maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-an
> notations.apt.
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.1.
This version fixes mostly the support of Java annotations for Maven plugins (
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-
annotations.html
)
The Maven Plugin Plugin is used to
e.PACKAGE,
>> threadSafe = false, requiresDependencyResolution =
>> ResolutionScope.RUNTIME)
>>
>>
>> on the class.
> Yes that's because the helpmojo is inovked at generate-sources phase, but
> descriptor is now invoked at process-classes (to proc
>
> on the class.
Yes that's because the helpmojo is inovked at generate-sources phase, but
descriptor is now invoked at process-classes (to process annotations).
to avoid your problem just add in the maven-plugin-plugin this configuration :
true
see
http://maven.
welcome :-)
>
> At final, there is no bug at all :) The report was generated by the
> maven-plugin-plugin 2.9, but now using
> the version 3.0 to generate report, everything is fine.
Good !
I was near a heart attack :-)
>
> Sorry for the noise.
>
> ps: maven-plugin-plugin 3.0
ated by the
maven-plugin-plugin 2.9, but now using
the version 3.0 to generate report, everything is fine.
Sorry for the noise.
ps: maven-plugin-plugin 3.0 rocks :)
--
Tony Chemit
tél: +33 (0) 2 40 50 29 28
email: [email protected]
http:/
2012/6/21 Tony Chemit :
> Hi,
>
> I migrated to the maven-plugin-plugin 3.0 and notice a change in the report
> for mojo property.
>
> In the generated goal page for a mojo, before we had all the java property of
> a mojo, but now we have all the 'mojo' properties
Hi,
I migrated to the maven-plugin-plugin 3.0 and notice a change in the report for
mojo property.
In the generated goal page for a mojo, before we had all the java property of a
mojo, but now we have all the 'mojo' properties of a mojo.
for example with this mojo:
public cl
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.0.
This version add the support of Java annotations for Maven plugins (
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
)
The Maven Plugin Plugin is used to create a
Hi Benson,
about MPLUGIN-181: The right to solve this is a java-escape of the forward
slash, so: default-value="**\/*.xml"
Might be worth an entry for the FAQ's.
-Robert
> Date: Fri, 2 Sep 2011 09:38:24 -0400
> Subject: I'd like to release maven-plug
I hit, and fixed, a bug [MPLUGIN-186] and then I went looking for
low-lying issues. I found MPLUGIN-120 which I'll check in if the
tests all pass.
Is anything else worth doing? I looked at -181, but I'm not sure that
an HTML escape is the notation we want here. Does anyone have a
preferred altern
The Maven team is pleased to announce the release of the Maven Plugin
Plugin and Maven Plugin Tools, version 2.8
This plugin is used to create a Maven plugin descriptor for any Mojo's
found in the source tree, to include in the JAR. It is also used to
generate report files for the Mojos as
gt;>>
>>> URL: http://svn.apache.org/viewvc?rev=1125604&view=rev
>>> Log:
>>> No point sitting on this change any longer.
>>>
>>> Modified:
>>>
>> maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/
1. yes there is a typo. as soon as I am at a pc the typo will be fixed.
2. the pmc is permitting persons who develop plugins for maven to use the
mark maven in their plugin name provided the name and its usage meets
certain criteria, amongst which is the "___ maven plugin" naming scheme. we
will b
strub
--- On Sat, 5/21/11, Karl Heinz Marbaise wrote:
> From: Karl Heinz Marbaise
> Subject: Re: svn commit: r1125604 -
> /maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
> To: [email protected]
> Date: Saturday
Hi, just a question about that...
does this mean that in the future a Maven Plugin is not allowed to be
named like:
maven-WhatEverThisIs-plugin ? Based on the given code this means that
future plugin developers have to change their plugin names into
WhatEverThisIs-maven-plugin...
Is this t
> Date: Sat May 21 00:21:26 2011
>> > New Revision: 1125604
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1125604&view=rev
>> > Log:
>> > No point sitting on this change any longer.
>> >
>> > Modified:
>> >
>>
this change any longer.
> >
> > Modified:
> >
> maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
> >
> > Modified:
> maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plug
v
> Log:
> No point sitting on this change any longer.
>
> Modified:
>
> maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
>
> Modified:
> maven/plugin-tools/trunk/maven-plugin-plugi
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 2.7
The Maven Plugin Plugin is used to create a Maven plugin descriptor for
any Mojo's found in the source tree, to include in the JAR. It is also
used to generate report files for the Mojos as well a
Hi Lukas,
Lukas Theussl wrote:
> Anders Hammar wrote:
>> On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>>
>>>
>>> Ok, I get it. The xdoc should be written with the same encoding that is
>>> used when it is read to generate the final report, which is
>>> project.build.sourceEncoding (by def
I'll attach to MPLUGIN-180. Please reopen that.
/Anders
On Tue, Jan 18, 2011 at 09:10, Lukas Theussl wrote:
>
>
> Anders Hammar wrote:
>
>> On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>>
>>
>>> Ok, I get it. The xdoc should be written with the same encoding that is
>>> used when it is
Anders Hammar wrote:
On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
Ok, I get it. The xdoc should be written with the same encoding that is
used when it is read to generate the final report, which is
project.build.sourceEncoding (by default).
No, it shouldn't. The xdoc xml file shou
On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>
> Ok, I get it. The xdoc should be written with the same encoding that is
> used when it is read to generate the final report, which is
> project.build.sourceEncoding (by default).
>
>
No, it shouldn't. The xdoc xml file should be written with
Ok, I get it. The xdoc should be written with the same encoding that is
used when it is read to generate the final report, which is
project.build.sourceEncoding (by default).
I fixed it, thanks!
-Lukas
Benjamin Bentmann wrote:
Lukas Theussl wrote:
I am confused indeed. I simply used MPLU
Lukas Theussl wrote:
I am confused indeed. I simply used MPLUGIN-180 to verify it works, but
just realized it's not good because both input and output encoding are
the same there.
Right, it gets only interesting if the two encodings have different
values, e.g. setting project.reporting.output
Benjamin Bentmann wrote:
Hi Lukaus,
Author: ltheussl
Date: Sun Jan 16 13:14:04 2011
New Revision: 1059551
URL: http://svn.apache.org/viewvc?rev=1059551&view=rev
Log:
[MPLUGIN-180] forward encoding to the PluginToolsRequest
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/
Hi Lukaus,
Author: ltheussl
Date: Sun Jan 16 13:14:04 2011
New Revision: 1059551
URL: http://svn.apache.org/viewvc?rev=1059551&view=rev
Log:
[MPLUGIN-180] forward encoding to the PluginToolsRequest
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I've a question about the plugin documentation configuration.
We created a documentation site using the standard maven tools.
We created an index page using the doxia apt format as stated on the
doxia site. After that we added the
: svn commit: r639861 - in /maven/plugin-tools/trunk:
maven-plugin-plugin/pom.xml pom.xml
Hi Brian,
I guess it would be better to fix parent pom and provide a new release.
It will avoid to duplicate entry poms (see this revision or also
r638164)
Cheers,
Vincent
2008/3/21, [EMAIL PROTECTED] &l
; New Revision: 639861
>
> URL: http://svn.apache.org/viewvc?rev=639861&view=rev
> Log:
> don't use javadoc 2.3
>
> Modified:
> maven/plugin-tools/trunk/maven-plugin-plugin/pom.xml
> maven/plugin-tools/trunk/pom.xml
>
> Modified: maven/plugin-t
> New Revision: 635240
> >
> > URL: http://svn.apache.org/viewvc?rev=635240&view=rev
> > Log:
> > [maven-release-plugin] prepare release maven-plugin-tools-2.4
> >
> > Modified:
> > maven/plugin-tools/trunk/maven-plugin-plugin/pom.xml
> > maven
wrote:
> >>> Author: vsiveton
> >>> Date: Sun Mar 9 07:11:48 2008
> >>> New Revision: 635240
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=635240&view=rev
> >>> Log:
> >>> [maven-release-plugin] prepare
Mar 9 07:11:48 2008
New Revision: 635240
URL: http://svn.apache.org/viewvc?rev=635240&view=rev
Log:
[maven-release-plugin] prepare release maven-plugin-tools-2.4
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/pom.xml
maven/plugin-tools/trunk/maven-plugin-tools-ant/pom.xml
ma
35240&view=rev
> > Log:
> > [maven-release-plugin] prepare release maven-plugin-tools-2.4
> >
> > Modified:
> > maven/plugin-tools/trunk/maven-plugin-plugin/pom.xml
> > maven/plugin-tools/trunk/maven-plugin-tools-ant/pom.xml
> > maven/plugin
:48 2008
New Revision: 635240
URL: http://svn.apache.org/viewvc?rev=635240&view=rev
Log:
[maven-release-plugin] prepare release maven-plugin-tools-2.4
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/pom.xml
maven/plugin-tools/trunk/maven-plugin-tools-ant/pom.xml
maven/pl
Thanks.
2008/3/3, Vincent Siveton <[EMAIL PROTECTED]>:
> Hi Raphael,
>
> I plan to call a vote this week.
>
> Cheers,
>
> Vincent
>
> 2008/3/3, Raphaël Piéroni <[EMAIL PROTECTED]>:
>
> > Hi,
> >
> > Is there any plan to release th
Hi Raphael,
I plan to call a vote this week.
Cheers,
Vincent
2008/3/3, Raphaël Piéroni <[EMAIL PROTECTED]>:
> Hi,
>
> Is there any plan to release the Maven Plugin Plugin 2.4?
>
> I would it released to close the issue
> http://jira.codehaus.org/browse/AR
Hi,
Is there any plan to release the Maven Plugin Plugin 2.4?
I would it released to close the issue
http://jira.codehaus.org/browse/ARCHETYPE-109
Regards,
Raphaël
:
Author: vsiveton
Date: Thu Feb 21 16:30:17 2008
New Revision: 630055
URL: http://svn.apache.org/viewvc?rev=630055&view=rev
Log:
o accessed directly to TrackableBase
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/
apache/maven/plugin/plugin/UpdatePluginRegistryMojo.
We are pleased to announce the Maven Plugin Plugin 1.7.1 release!
http://maven.apache.org/maven-1.x/plugins/plugin/
Maven Plugin management plugin.
===
Changes in this version include:
Fixed bugs:
o
Here are the results of this vote:
+1 Binding: Dennis Lundberg, Stephane Nicoll, Jason val Zyl, John Casey,
Vincent Siveton
+1 Non-binding: Brian E. Fox, Daniel Kulp, Andrew Williams
I will proceed with the release.
Dennis Lundberg wrote:
Hi,
I'd like to release maven-plugin-plugi
+1
Vincent
2007/3/19, Dennis Lundberg <[EMAIL PROTECTED]>:
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release, but it's an important
one. It adds support for @since tags for mojo parameters. This is an
important improveme
+1
Andy
On 19 Mar 2007, at 22:43, Dennis Lundberg wrote:
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release, but it's an
important one. It adds support for @since tags for mojo parameters.
This is an important improvement to
On Mar 21, 2007, at 12:17 AM, Brett Porter wrote:
I was using 2.2 of m-p-p which appears to be using qdox-1.6.1. I
also tried using 2.3-SNAPSHOT (whatever is up there in the m2-
snapshot-repo) and it looked like it was using qdox-1.6.1 as
well. Both behave the same way.
That should be the
On 21/03/2007, at 6:11 PM, Jason Dillon wrote:
I was using 2.2 of m-p-p which appears to be using qdox-1.6.1. I
also tried using 2.3-SNAPSHOT (whatever is up there in the m2-
snapshot-repo) and it looked like it was using qdox-1.6.1 as well.
Both behave the same way.
That should be the
On Mar 20, 2007, at 11:52 PM, Brett Porter wrote:
I was under the impression the latest release had updated to qdox
and it could deal with it (where it contains annotations, not using
them for the mojo parameters themselves obviously).
What version of the plugin plugin are you using, and wh
I was under the impression the latest release had updated to qdox and
it could deal with it (where it contains annotations, not using them
for the mojo parameters themselves obviously).
What version of the plugin plugin are you using, and what version of
qdox does it drag in?
On 21/03/200
Is there anyway to get the maven-plugin-plugin to work with a module
that contains 1.5 annotations?
When I try to build when the packaging is 'maven-plugin',
'plugin:descriptor' pukes up:
[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extracto
+1
On 3/20/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
+1
On 19 Mar 07, at 6:43 PM 19 Mar 07, Dennis Lundberg wrote:
> Hi,
>
> I'd like to release maven-plugin-plugin-2.3.
>
> There is only one issue fixed for this release, but it's an
> important one. I
+1
On 19 Mar 07, at 6:43 PM 19 Mar 07, Dennis Lundberg wrote:
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release, but it's an
important one. It adds support for @since tags for mojo parameters.
This is an important improvement to
+1
Dan
On Monday 19 March 2007 18:43, Dennis Lundberg wrote:
> Hi,
>
> I'd like to release maven-plugin-plugin-2.3.
>
> There is only one issue fixed for this release, but it's an important
> one. It adds support for @since tags for mojo parameters. This is an
&g
+1
Stéphane
On 3/19/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release, but it's an important
one. It adds support for @since tags for mojo parameters. This is an
important improveme
+1
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2007 6:43 PM
To: Maven Developers List
Subject: [VOTE] Release maven-plugin-plugin 2.3
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release
Hi,
I'd like to release maven-plugin-plugin-2.3.
There is only one issue fixed for this release, but it's an important
one. It adds support for @since tags for mojo parameters. This is an
important improvement to our plugin documentation:
http://jira.codehaus.org/secure/IssueNavi
t requires maven-plugin-plugin-2.3, which in turn has
2.0.5 as a prerequisite.
1. Does maven-plugin-plugin-2.3 get downloaded?
2. Does maven-plugin-plugin-2.3 get used by maven 2.0.4 if it has
been downloaded or installed locally?
No and no. The logic is:
a) use the version requested in the P
: 514383
URL: http://svn.apache.org/viewvc?view=rev&rev=514383
Log:
o Update prerequisites to 2.0.5.
Modified:
maven/plugins/trunk/maven-plugin-plugin/pom.xml
Modified: maven/plugins/trunk/maven-plugin-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-plugin-
pl
fied:
maven/plugins/trunk/maven-plugin-plugin/pom.xml
Modified: maven/plugins/trunk/maven-plugin-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-plugin-
plugin/pom.xml?view=diff&rev=514383&r1=5143
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
How does plugin updates work in a situation like this? Say we have a
user that is running maven 2.0.4. He/she issues "mvn -U site" on a
project that requires maven-plugin-plugin-2.3, which in turn has 2
. The only other changes
to maven-plugin-tools is the handling of "since" and
"implementation" (for parameters). Also maven-plugin-tools-pluggy
has been removed. The pom currently has a version of 2.1-SNAPSHOT.
Is that a suitable version for these changes?
Next we need to
y other changes to
maven-plugin-tools is the handling of "since" and "implementation" (for
parameters). Also maven-plugin-tools-pluggy has been removed. The pom
currently has a version of 2.1-SNAPSHOT. Is that a suitable version for
these changes?
Next we need to update
s-pluggy has been removed. The pom
currently has a version of 2.1-SNAPSHOT. Is that a suitable version for
these changes?
Next we need to update maven-plugin-plugin to use the new version of
maven-plugin-tools. No changes other than pom updates has been made
since the 2.2 release of the plugin
4 binding +1 votes, I will proceed with the release.
On 23/12/2006, at 3:16 PM, Brett Porter wrote:
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot
is 2.0.5-20061223.041242-4
+1
Stéphane
On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot is
2.0.5-20061223.041242-4
- documentation already updated a
+1
fabrizio
On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot is
2.0.5-20061223.041242-4
- documentation already updated a
+1
Emmanuel
Brett Porter a écrit :
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot is
2.0.5-20061223.041242-4
- documentation already updated at
http://maven.apache.org/plugins/maven
On 23/12/2006, at 3:16 PM, Brett Porter wrote:
Vote is open for 72h
Sorry, this should have been longer, just used the template. I'm not
cutting a release at Christmas ;)
Vote is open for 7 * 24h.
- Brett
-
To unsubscri
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot is
2.0.5-20061223.041242-4
- documentation already updated at http://maven.apache.org/plugins/
maven-plugin-plugin/
- changelog available
-SNAPSHOT
Modified:
maven/plugins/trunk/maven-plugin-plugin/pom.xml
Modified: maven/plugins/trunk/maven-plugin-plugin/pom.xml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-plugin-plugin/pom.xml?rev=421484&r1=421483&r2
Binding: John, Brett, Emmanuel, Jason
Non-Binding: Stephane, Vincent S., Fabrizio
I'll get started on the release now.
-john
John Casey wrote:
Hi,
I just realized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
+1 for 2.1
Vincent
2006/1/30, John Casey <[EMAIL PROTECTED]>:
> Hi,
>
> I just realized that we never released a new version of the
> maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
> can support Ant-based mojos. There are still open issues in jira f
+1 for 2.1
fabrizio
On 1/31/06, John Casey <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just realized that we never released a new version of the
> maven-plugin-plugin to accompany Maven 2.0.1.
-
To unsubscri
> John Casey wrote:
> > Hi,
> >
> > I just realized that we never released a new version of the
> > maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
> > can support Ant-based mojos. There are still open issues in jira for
> > this plugin
+1
Emmanuel
John Casey a écrit :
Hi,
I just realized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
can support Ant-based mojos. There are still open issues in jira for
this plugin, but I'm not planning to add an
John Casey wrote:
Hi,
I just realized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
can support Ant-based mojos. There are still open issues in jira for
this plugin, but I'm not planning to add any new code before cu
lized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
can support Ant-based mojos. There are still open issues in jira for
this plugin, but I'm not planning to add any new code before cutting
this release. This is a relat
+1, but prefer calling it 2.1 due to the feature addition.
FWIW, the issues in JIRA are all features/improvements or changes to the
generated report - no bugs in the plugin creation.
- Brett
John Casey wrote:
> Hi,
>
> I just realized that we never released a new version of the
>
Sorry, that was probably a bit too brief. :)
I meant to also say that I'll keep this open for the customary 72 hours,
and see where we are at that point.
-j
John Casey wrote:
Hi,
I just realized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1.
Hi,
I just realized that we never released a new version of the
maven-plugin-plugin to accompany Maven 2.0.1. This needs to happen so we
can support Ant-based mojos. There are still open issues in jira for
this plugin, but I'm not planning to add any new code before cutting
this re
[ http://jira.codehaus.org/browse/MNG-1297?page=all ]
Jason van Zyl updated MNG-1297:
---
Fix Version: (was: 2.0.3)
2.0.4
> Continuum build throws LifecycleExecutionException while building Maven
> PLUGIN
1 - 100 of 180 matches
Mail list logo
