Re: Merging maven-plugin-api and maven-plugin-descriptor in trunk
On 4 Sep 07, at 10:50 PM 4 Sep 07, Jason van Zyl wrote: Hi, I would like to make a single module for plugin execution and this is the first step. The motivator is being able to isolate a version of a plugin apis runtime. These modules do not vary independently in practice and they are not useful separately. I really would like people to look at the top-level source tree and easily see the key moving parts. Any objections? Doesn't seem to be, I'm going to merge these now. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging maven-plugin-api and maven-plugin-descriptor in trunk
On 06/09/2007, at 4:21 AM, Jason van Zyl wrote: On 4 Sep 07, at 10:50 PM 4 Sep 07, Jason van Zyl wrote: Hi, I would like to make a single module for plugin execution and this is the first step. The motivator is being able to isolate a version of a plugin apis runtime. These modules do not vary independently in practice and they are not useful separately. I really would like people to look at the top-level source tree and easily see the key moving parts. Any objections? Doesn't seem to be, I'm going to merge these now. Sorry, only just got around to this mail. This will introduce a dependency on the plexus container and maven- artifact for every single plugin - is that really desirable? Currently, the plugins can depend on the API without needing the plugin descriptor (which is basically used by tooling and the maven internals). Seems best separated to me. Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging maven-plugin-api and maven-plugin-descriptor in trunk
On 5 Sep 07, at 3:43 PM 5 Sep 07, Brett Porter wrote: On 06/09/2007, at 4:21 AM, Jason van Zyl wrote: On 4 Sep 07, at 10:50 PM 4 Sep 07, Jason van Zyl wrote: Hi, I would like to make a single module for plugin execution and this is the first step. The motivator is being able to isolate a version of a plugin apis runtime. These modules do not vary independently in practice and they are not useful separately. I really would like people to look at the top-level source tree and easily see the key moving parts. Any objections? Doesn't seem to be, I'm going to merge these now. Sorry, only just got around to this mail. This will introduce a dependency on the plexus container and maven- artifact for every single plugin - is that really desirable? No it won't introduce a dependency because they aren't going to be there. Focus on the motivation to isolate the complete runtime, the few files in the descriptor who cares about. No one is going to see them. The descriptor shouldn't be coupled to plexus or maven artifact either but I'm going to remove them. Plugins will still only need to depend on the plugin api which has, and will continue to have, no dependencies. Currently, the plugins can depend on the API without needing the plugin descriptor (which is basically used by tooling and the maven internals). Seems best separated to me. Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging maven-plugin-api and maven-plugin-descriptor in trunk
On 5 Sep 07, at 3:43 PM 5 Sep 07, Brett Porter wrote: On 06/09/2007, at 4:21 AM, Jason van Zyl wrote: On 4 Sep 07, at 10:50 PM 4 Sep 07, Jason van Zyl wrote: Hi, I would like to make a single module for plugin execution and this is the first step. The motivator is being able to isolate a version of a plugin apis runtime. These modules do not vary independently in practice and they are not useful separately. I really would like people to look at the top-level source tree and easily see the key moving parts. Any objections? Doesn't seem to be, I'm going to merge these now. Sorry, only just got around to this mail. This will introduce a dependency on the plexus container and maven- artifact for every single plugin - is that really desirable? Currently, the plugins can depend on the API without needing the plugin descriptor (which is basically used by tooling and the maven internals). Seems best separated to me. The other way to think about it is the way anno-mojo is where the metadata model is inherently pushed along with the model and they become tied together. I would like the same for the pre java5. This will actually made working with anno-mojo easier. Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging maven-plugin-api and maven-plugin-descriptor in trunk
On 06/09/2007, at 9:18 AM, Jason van Zyl wrote: Doesn't seem to be, I'm going to merge these now. Sorry, only just got around to this mail. This will introduce a dependency on the plexus container and maven- artifact for every single plugin - is that really desirable? No it won't introduce a dependency because they aren't going to be there. Focus on the motivation to isolate the complete runtime, the few files in the descriptor who cares about. No one is going to see them. The descriptor shouldn't be coupled to plexus or maven artifact either but I'm going to remove them. Plugins will still only need to depend on the plugin api which has, and will continue to have, no dependencies. Cool - if you are doing all that in one hit it totally makes sense. - Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Merging maven-plugin-api and maven-plugin-descriptor in trunk
Hi, I would like to make a single module for plugin execution and this is the first step. The motivator is being able to isolate a version of a plugin apis runtime. These modules do not vary independently in practice and they are not useful separately. I really would like people to look at the top-level source tree and easily see the key moving parts. Any objections? Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
