On 17 Jun 06, at 6:55 PM 17 Jun 06, Dennis Lundberg wrote:
Hi all
As I continue to work on the maven-maven1-plugin in the sandbox, I
have found the need for a small API for relocating plugins. It is
needed to be able to properly translate M1 plugins to their M2
counterparts, when the plu
So I really need to be in the loop regarding that particular plugin.
Knowing which features has been added after the last version was
released and when the site was last deployed. In that case I think I'll
refrain from deploying sites for a while :)
Mike Perham wrote:
I would think the main t
Hi all
As I continue to work on the maven-maven1-plugin in the sandbox, I have
found the need for a small API for relocating plugins. It is needed to
be able to properly translate M1 plugins to their M2 counterparts, when
the plugin has changed artifactId or groupId.
Is this something that c
On 17 Jun 06, at 6:37 PM 17 Jun 06, Dennis Lundberg wrote:
Hi
Having applied a few patches to sites and documentation I am
curious if there is a policy for when a site should be deployed. As
an example, if I patch an apt file for a plugin, should I also
deploy the site for that plugin?
I would think the main thing to consider is whether those docs reflect
the latest release. Documenting features which have not been released
yet is a no-no.
> -Original Message-
> From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 17, 2006 5:37 PM
> To: Maven Develope
Hi
Having applied a few patches to sites and documentation I am curious if
there is a policy for when a site should be deployed. As an example, if
I patch an apt file for a plugin, should I also deploy the site for that
plugin?
--
Dennis Lundberg
Edwin Punzalan wrote:
You're right. I got it mixed up...
I thought were also available in the section.
Sorry about that.
I searched jira and found no request for this as of now and you can
create a "New Feature" issue in there... I think that's the best I can
offer you to do for now as
You're right. I got it mixed up...
I thought were also available in the section.
Sorry about that.
I searched jira and found no request for this as of now and you can
create a "New Feature" issue in there... I think that's the best I can
offer you to do for now as I do not have any work
+1
fabrizio
On 6/15/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
I'd like to release the 2.0.1 with only one bug fix,
http://jira.codehaus.org/browse/MPIR-2
I know there are some pending issues but until somebody has time to go
for them releasing 2.0.1 will help avoid the innumerable times pe
