[ http://jira.codehaus.org/browse/MNG-1952?page=all ]
John Casey updated MNG-1952:
Fix Version: documentation
> Give equal footing to all m2 plugins and add Cargo plugin to the l
> Give equal footing to all m2 plugins and add Cargo plugin to the list
> -
>
> Key: MNG-1952
> URL: http://jira.codehaus.org/browse/MNG-1952
> Project: Maven 2
> Type: Improvement
[ http://jira.codehaus.org/browse/MNG-1952?page=all ]
Vincent Massol updated MNG-1952:
Attachment: siteplugin2.patch
> Give equal footing to all m2 plugins and add Cargo plugin to the l
[ http://jira.codehaus.org/browse/MNG-1952?page=all ]
Vincent Massol updated MNG-1952:
Attachment: (was: siteplugin.patch)
> Give equal footing to all m2 plugins and add Cargo plugin to the l
Give equal footing to all m2 plugins and add Cargo plugin to the list
-
Key: MNG-1952
URL: http://jira.codehaus.org/browse/MNG-1952
Project: Maven 2
Type: Improvement
Components: documentation
Please direct your question to the users list in future.
Mattias Olofsson wrote:
>
> I have some questions about maven2 plugins.
>
>
> * How could I see the last versions of all plugins?
http://repo1.maven.org/maven2/org/apache/maven/plugins
http://repo1.maven.org/maven2/org/codehau
I have some questions about maven2 plugins.
* How could I see the last versions of all plugins?
* Is there any plans to make a page for maven2 like maven1,
http://maven.apache.org/maven-1.x/reference/plugins/multichanges-report.html to
list the releases ?
* Why do I get these BUI
Raised http://jira.codehaus.org/browse/MNG-1649 to track this.
Mark
On 03/11/05, Mark Hobson <[EMAIL PROTECTED]> wrote:
> On 03/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > Can you reiterate why you need tomcat:exploded and tomcat:inplace
> > instead of just using the war:* goals?
> >
> > T
I think it's also time to use the changes plugin. WDYT?
On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> So what's the status on this?
>
> - Have we decided to create separate JIRA projects for m2 plugins?
> - Can I create a Clover JIRA project the m2
Vincent
>
> > -Original Message-
> > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 16 novembre 2005 23:30
> > To: 'Maven Developers List'
> > Subject: RE: JIRA projects for m2 plugins?
> >
> > >
> > > I think w
16 novembre 2005 23:30
> To: 'Maven Developers List'
> Subject: RE: JIRA projects for m2 plugins?
>
> >
> > I think we should vote to solve this asap, I believe these
> > are the options:
> >
> > [+1] create a new project for new m2 plugins, reuse m
>
> I think we should vote to solve this asap, I believe these
> are the options:
>
> [+1] create a new project for new m2 plugins, reuse m1 projects adding a new
> version
Actually it could be the simplest way to do it.
Users are already creating issues in m1 plugins and
27;s not working (version issues). :-)
>
>
>
> -Vincent
>
>
>
> _
>
> From: David Sag [mailto:[EMAIL PROTECTED]
> Sent: mercredi 16 novembre 2005 09:03
> To: Maven Developers List
> Subject: Re: JIRA projects for m2 plugins?
>
>
>
>
> I wo
Jason van Zyl a écrit :
On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote:
I think we should vote to solve this asap, I believe these are the options:
[ ] create a new project for new m2 plugins, reuse m1 projects adding
a new version
[ ] create a new project for every m2 plugin
+1
cts for m2 plugins?
I would vote to make a new jira component within the maven 2 project for
each new plugin.
Kind regards,
Dave Sag
[EMAIL PROTECTED] wrote on 15-11-2005 21:27:39:
> I think we should vote to solve this asap, I believe these are the
options:
>
> [ ] create a new
or new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
> [ ] keep it as it's now
>
> On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > So what's the status on this?
> >
> > - Have we decided to
> [ ] create a new project for new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
> [ ] keep it as it's now
>
> On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > So what's the status on this?
> &g
My vote
> [x] create a new project for new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
> [ ] keep it as it's now
>
-
To unsubscribe, e-mail: [
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 16 novembre 2005 01:04
> To: Maven Developers List
> Subject: Re: JIRA projects for m2 plugins?
>
> On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote:
> > I think w
On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote:
> I think we should vote to solve this asap, I believe these are the options:
>
> [ ] create a new project for new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
+1
&
I think we should vote to solve this asap, I believe these are the options:
[ ] create a new project for new m2 plugins, reuse m1 projects adding
a new version
[ ] create a new project for every m2 plugin
[ ] keep it as it's now
On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
ECTED]
www.soaringeagleco.com
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 1:58 AM
To: 'Maven Developers List'
Subject: JIRA projects for m2 plugins?
So what's the status on this?
- Have we decided to create separate
So what's the status on this?
- Have we decided to create separate JIRA projects for m2 plugins?
- Can I create a Clover JIRA project the m2 clover plugin? I'd like to get
moving on this.
- Is there any recommendation for versioning the plugins? Should we start at
2.0 and simply in
On 03/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Can you reiterate why you need tomcat:exploded and tomcat:inplace
> instead of just using the war:* goals?
>
> This was probably discussed in the users list thread, but good to
> elaborate here. I find it really helpful to see how you intend to
Can you reiterate why you need tomcat:exploded and tomcat:inplace
instead of just using the war:* goals?
This was probably discussed in the users list thread, but good to
elaborate here. I find it really helpful to see how you intend to use
the plugin, then look at how that would be implemente
On 02/11/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> On Wed, 2 Nov 2005, Mark Hobson wrote:
>
> Just some thoughts:
>
> The 'war' packaging _NEEDS_ a .war to be produced in case it will be used
> in an ear. If you replace the war packaging by 'exploded', then there is
> no artifact which will
On Wed, 2 Nov 2005, Mark Hobson wrote:
Just some thoughts:
The 'war' packaging _NEEDS_ a .war to be produced in case it will be used
in an ear. If you replace the war packaging by 'exploded', then there is
no artifact which will fail the install goal etc.
People want to test their webapps withou
Hi all,
To summarise the problem here, we need a way for plugins to depend on
other plugin's goals. The example use case is the tomcat:exploded
goal which needs to depend on war:exploded, and not war:war since this
has a performance hit. The tomcat:exploded goal depends on the
package phase, so
On 31/10/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> I see - you are right, that was by design.
Thanks for clarifying, it seemed that way but wasn't sure if I was
missing something.
> I'll have to think about the best path forward on this. Can we move it
> to the dev list?
Sure, I've posted to
Arnaud HERITIER wrote:
>Who can do that ?
>I think it will concern only updates and new features on plugins (bugs are not
>significant because m2 plugins were totally rewriten
>from scratch).
>
>
an example of a bug is MPIDEA-39. This probably affects both.
>But actual
is would include minor features (ie other options or
> configurations).
Who can do that ?
I think it will concern only updates and new features on plugins (bugs are not
significant because m2 plugins were totally rewriten
from scratch).
But actually I don't know which features are done in
Sounds reasonable to me. Somebody wants to come up with a template for
the plugin feature list?
Concerning all the great work we've done recently (:)), it shouldn't be
too hard to extract the information from the entries in changes.xml.
Maybe this could be implemented as part of the changes
Hi,
We discussed this briefly before. From looking at that, this seems to be
the most workable solution:
- for any new features added in m1 or m2, we add a description to the
plugin site so that we have a comparitive checklist
- for any bugs fixed in m1 that potentially impact m2, when fixed, clon
Hi,
Sorry for the delay ..
>
> Hi,
>
> I notice some great work going into m1 plugins. Thanks to
> everyone for the work going on there and for keeping them
> going. In addition, there are new jira issues coming in,
> sometimes with patches.
>
> As we progress towards a final release of Mav
e can do this.
>
> > - open an issue on the m2 plugin when the m1 version is closed, linking
> > to the original
>
> +1
>
> At least we can then see how the features are changing in the m1 version
> wrt to the mojo.
>
> > - others?
>
> It would be nice to t
to the original
+1
At least we can then see how the features are changing in the m1 version
wrt to the mojo.
> - others?
It would be nice to track features provided by each plugin. I certainly
don't want to go back through each m1 plugin and enumerate each feature
but this might be something we co
Hi,
I notice some great work going into m1 plugins. Thanks to everyone for
the work going on there and for keeping them going. In addition, there
are new jira issues coming in, sometimes with patches.
As we progress towards a final release of Maven 2.0 and look to
maintaining both in parallel in
Brett,
thanks for your reply. if m2 can generate the m1 plugin for me, then
there's no point anymore to code it :) sadly i ve begun with core and m1
part. anyway i think this removes the need for repo synchronization at
the moment.
regards,
-- gd
Brett Porter wrote:
Gilles Dodinet wrote:
hi
Gilles Dodinet wrote:
> hi-
>
> i'd like to know if it would be possible to upload m2 libraries to an
> m1-friendly repository.
yes, we want to get to the point that everything gets into both. Well,
actually the point to get to is to allow Maven 1.1 to use the new repo
so we can start looking at
hi-
i'd like to know if it would be possible to upload m2 libraries to an
m1-friendly repository. should i create a jira entry for this ?
i'll try to explain my needs in case i took the wrong approach: i'm
writing a plugin which i'd like to be both m1 and m2 compliant. so i
have three modules
On Wed, 2005-04-27 at 01:01 +0200, Vincent Massol wrote:
> Hi,
>
> I am thinking about writing a m2 plugin for Cargo
> (http://cargo.codehaus.org). Here's what a typical configuration for such a
> plugin could be:
>
>
>
>
> resin3x
> c:/apps/resin-3.0.9 |
>
Hi,
I am thinking about writing a m2 plugin for Cargo
(http://cargo.codehaus.org). Here's what a typical configuration for such a
plugin could be:
resin3x
c:/apps/resin-3.0.9 |
http://www.caucho.com/download/resin-3.0.9.zip
${ba
Vincent Massol wrote:
>Yes, Jason explained to me what Mojos are. So ideally we would have:
>
>mojos/ (java beans equivalent to Ant tasks and not tied to plexus nor maven)
>
>
right - but implement the Plugin interface and contribute to a
descriptor through some metadata
>plexus/ (focus only on
Maczka Michal wrote:
>With exception for versioning it is all already implemented in plexus and
>just needs to be exposed.
>
>
If you look at the code before emailing, you'll save yourself a lot of
time. The plugin manager already uses plexus configuration to some
extent and has comments to move
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 13, 2005 12:30 AM
> To: Maven Developers List
> Subject: Re: [M2] Plugins vs Mojo vs Plexus components?
>
>
> This is really a name confusion. The plexus things being u
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 13 avril 2005 00:30
> To: Maven Developers List
> Subject: Re: [M2] Plugins vs Mojo vs Plexus components?
>
> This is really a name confusion. The plexus things being used, for
onstructed as a normal bean in most cases and configured
manually.
What's probably missing for use outside of Maven is getters and setters :)
We are currently working on the external Mojo API, so feel free to mail
any more comments about it.
Cheers,
Brett
Vincent Massol wrote:
>Hi,
&
Hi,
I see that several m2 plugins in maven-components/maven-*-plugin/** are
using other java components located directly in maven-components/ such as
maven-archiver, maven-archetype, etc. What are those projects? Are they
Mojos? Of not, are they meant to become mojos in the future?
Also some of
48 matches
Mail list logo
