You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jeff Genender <jg...@savoirtech.com> on 2006/06/30 16:56:30 UTC
[RTC] - Fix top pom to reference right plugin
The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
1.2.0. I wan tto update it to 1.2-SNAPSHOT:
Index: pom.xml
===================================================================
--- pom.xml (revision 418149)
+++ pom.xml (working copy)
@@ -136,7 +136,7 @@
| Geronimo plugin versions
|
-->
-
<geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
+
<geronimoPackagingPluginVersion>1.2-SNAPSHOT</geronimoPackagingPluginVersion>
<!--
|
Re: [RTC] - Fix top pom to reference right plugin
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I think that this is a bug fix as well. But, just in case, +1.
Regards,
Alan
David Jencks wrote:
> I think this is a bug fix and doesn't need a vote. I also thought I'd
> fixed this already, but see that it must be in some of the other trees
> I'm maintaining locally.
>
> In case anyone disagrees with my bug-fix theoty, +1.
>
> thanks
> david jencks
> On Jun 30, 2006, at 7:56 AM, Jeff Genender wrote:
>
>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>
>> Index: pom.xml
>> ===================================================================
>> --- pom.xml (revision 418149)
>> +++ pom.xml (working copy)
>> @@ -136,7 +136,7 @@
>> | Geronimo plugin versions
>> |
>> -->
>> -
>> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
>> +
>> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</geronimoPackagingPluginVersion>
>>
>>
>> <!--
>> |
>
Re: [RTC] - Fix top pom to reference right plugin
Posted by David Jencks <da...@yahoo.com>.
I think this is a bug fix and doesn't need a vote. I also thought
I'd fixed this already, but see that it must be in some of the other
trees I'm maintaining locally.
In case anyone disagrees with my bug-fix theoty, +1.
thanks
david jencks
On Jun 30, 2006, at 7:56 AM, Jeff Genender wrote:
> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 418149)
> +++ pom.xml (working copy)
> @@ -136,7 +136,7 @@
> | Geronimo plugin versions
> |
> -->
> -
> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
> +
> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</
> geronimoPackagingPluginVersion>
>
> <!--
> |
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
+1
I agree its a bug.
I would remove this property though and reference ${pom.version}
where this property is used. Or in the short-term set the property
to ${pom.version} so that the version is only defined in one location.
--jason
On Jun 30, 2006, at 7:56 AM, Jeff Genender wrote:
> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 418149)
> +++ pom.xml (working copy)
> @@ -136,7 +136,7 @@
> | Geronimo plugin versions
> |
> -->
> -
> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
> +
> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</
> geronimoPackagingPluginVersion>
>
> <!--
> |
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
> That was due to maven 1 incompetence in plugin management. It's
> caused untold headaches. Although it appears m2 has a whole new
> set of things it cant do with plugins, handling snapshot plugins
> allegedly works fine. Due to the problems with the m1 versioning
> I'd like to give m2 snapshot plugins a chance.
m2 is very different than m1... so many of the things we were forced
to do in m1 to make it work for us are no longer valid.
There is no reason that we need to or want to continue doing things
in a m1-style w/m2.
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jeff Genender <jg...@apache.org>.
Ok...I acquiesce ;-) I be quiet until after the conversion is complete ;-)
Jason Dillon wrote:
>> I'm not sure I agree that this is easiest or best. I think I would be
>> interested in getting others' input on this as well.
>
> I believe that while we move to m2 that simpler is better and thus
> easier to complete the migration.
>
> So, one version is simperer than many versions. If all modules in the
> same tree have the same version, then ${pom.version} can be used to
> resolve the correct version of dependencies. w/o that you are forced to
> setup top-level properties for versions and manage those versions...
> which is more work, more configuration and more error prone.
>
> My recommendation is that all modules in a build tree use the same
> version. If they should logically have different versions, then they
> belong in a different build tree. And there are cases that look like
> this now... no question, but lets fix this after the conversion is
> completed and functional.
>
>
>> One of the problems we have now is the chicken/egg issue with the
>> plugin being in
>> the build itself. I think this would be alleviated by moving the plugin
>> to its own project and push it out as a reliable dependency for the
>> geronimo project. I have tried the internal plugin thing on a few
>> projects, and it always ended up making life easier having the plugin as
>> its own project.
>
> There are a few ways to resolve this, which I have listed before in
> previous emails. Looks like short-term to get the conversion finished
> that we may need to introduce a bootstrap. Longer-term we will want to
> reorganize the modules that are needed by the plugins and then put them,
> in a separate tree and then put the plugins in their own tree. Or...
> remove the need for those plugins to need access to the G codebase.
> There are quite a few different ways to fix this problem. But none of
> the long term fixes are likely to happen now as we implement the migration.
>
> --jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
> I'm not sure I agree that this is easiest or best. I think I would be
> interested in getting others' input on this as well.
I believe that while we move to m2 that simpler is better and thus
easier to complete the migration.
So, one version is simperer than many versions. If all modules in
the same tree have the same version, then ${pom.version} can be used
to resolve the correct version of dependencies. w/o that you are
forced to setup top-level properties for versions and manage those
versions... which is more work, more configuration and more error prone.
My recommendation is that all modules in a build tree use the same
version. If they should logically have different versions, then they
belong in a different build tree. And there are cases that look like
this now... no question, but lets fix this after the conversion is
completed and functional.
> One of the problems we have now is the chicken/egg issue with the
> plugin being in
> the build itself. I think this would be alleviated by moving the
> plugin
> to its own project and push it out as a reliable dependency for the
> geronimo project. I have tried the internal plugin thing on a few
> projects, and it always ended up making life easier having the
> plugin as
> its own project.
There are a few ways to resolve this, which I have listed before in
previous emails. Looks like short-term to get the conversion
finished that we may need to introduce a bootstrap. Longer-term we
will want to reorganize the modules that are needed by the plugins
and then put them, in a separate tree and then put the plugins in
their own tree. Or... remove the need for those plugins to need
access to the G codebase. There are quite a few different ways to
fix this problem. But none of the long term fixes are likely to
happen now as we implement the migration.
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
> Aren't all these problems due to maven not handling this rather
> obvious and important use case of building a plugin and then using
> it in the same build? If a tool is broken you have to do something
> to fix it.... but often fixing the tool works best.
If we want to get migrated then we have to work with the tool asis
and then we can work on fixing it... if we try to fix everything then
we will move nowhere.
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jeff Genender <jg...@apache.org>.
David Jencks wrote:
>> I'm not sure I agree that this is easiest or best. I think I would be
>> interested in getting others' input on this as well. One of the
>> problems we have now is the chicken/egg issue with the plugin being in
>> the build itself. I think this would be alleviated by moving the plugin
>> to its own project and push it out as a reliable dependency for the
>> geronimo project. I have tried the internal plugin thing on a few
>> projects, and it always ended up making life easier having the plugin as
>> its own project.
>
> Aren't all these problems due to maven not handling this rather obvious
> and important use case of building a plugin and then using it in the
> same build? If a tool is broken you have to do something to fix it....
> but often fixing the tool works best.
Have you opened a JIRA over on the maven side of the house?
>
> thanks
> david jencks
>>
>>> --jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by David Jencks <da...@yahoo.com>.
On Jun 30, 2006, at 11:12 AM, Jeff Genender wrote:
>
>
> Jason Dillon wrote:
>>> Jason Dillon wrote:
>>>> FYI, we should be using ${pom.version} anywhere the project
>>>> version is
>>>> needed. No need for a custom property.
>>>
>>> I think its by coincidence that we have 1.2-SNAPSHOT for both the
>>> plugin
>>> and the G codebase...if its not coincidence, then it shouldn't be.
>>> IMHO, the plugin should be versioned differently. In fact...I may
>>> even
>>> go as far as to say, the packaging plugin can be useful outside of
>>> geronimo itself (people building their own packages, etc) and
>>> probably
>>> should be in its own tree or even be a mojo. I am personally
>>> against
>>> locking the G verison to the plugin version...I would like to see
>>> them
>>> seperated.
>>
>> All modules that are part of the build should share the same
>> version to
>> simply the release process and make effective use of the m2
>> release plugin.
>>
>> I agree that the plugins should probably be moved to their own
>> project
>> and have independent versioning... and we will get there, but
>> right now
>> the easiest/best thing to do is to use the same version for all
>> modules.
>>
>
> I'm not sure I agree that this is easiest or best. I think I would be
> interested in getting others' input on this as well. One of the
> problems we have now is the chicken/egg issue with the plugin being in
> the build itself. I think this would be alleviated by moving the
> plugin
> to its own project and push it out as a reliable dependency for the
> geronimo project. I have tried the internal plugin thing on a few
> projects, and it always ended up making life easier having the
> plugin as
> its own project.
Aren't all these problems due to maven not handling this rather
obvious and important use case of building a plugin and then using it
in the same build? If a tool is broken you have to do something to
fix it.... but often fixing the tool works best.
thanks
david jencks
>
>> --jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jeff Genender <jg...@apache.org>.
Jason Dillon wrote:
>> Jason Dillon wrote:
>>> FYI, we should be using ${pom.version} anywhere the project version is
>>> needed. No need for a custom property.
>>
>> I think its by coincidence that we have 1.2-SNAPSHOT for both the plugin
>> and the G codebase...if its not coincidence, then it shouldn't be.
>> IMHO, the plugin should be versioned differently. In fact...I may even
>> go as far as to say, the packaging plugin can be useful outside of
>> geronimo itself (people building their own packages, etc) and probably
>> should be in its own tree or even be a mojo. I am personally against
>> locking the G verison to the plugin version...I would like to see them
>> seperated.
>
> All modules that are part of the build should share the same version to
> simply the release process and make effective use of the m2 release plugin.
>
> I agree that the plugins should probably be moved to their own project
> and have independent versioning... and we will get there, but right now
> the easiest/best thing to do is to use the same version for all modules.
>
I'm not sure I agree that this is easiest or best. I think I would be
interested in getting others' input on this as well. One of the
problems we have now is the chicken/egg issue with the plugin being in
the build itself. I think this would be alleviated by moving the plugin
to its own project and push it out as a reliable dependency for the
geronimo project. I have tried the internal plugin thing on a few
projects, and it always ended up making life easier having the plugin as
its own project.
> --jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
> Jason Dillon wrote:
>> FYI, we should be using ${pom.version} anywhere the project
>> version is
>> needed. No need for a custom property.
>
> I think its by coincidence that we have 1.2-SNAPSHOT for both the
> plugin
> and the G codebase...if its not coincidence, then it shouldn't be.
> IMHO, the plugin should be versioned differently. In fact...I may even
> go as far as to say, the packaging plugin can be useful outside of
> geronimo itself (people building their own packages, etc) and probably
> should be in its own tree or even be a mojo. I am personally against
> locking the G verison to the plugin version...I would like to see them
> seperated.
All modules that are part of the build should share the same version
to simply the release process and make effective use of the m2
release plugin.
I agree that the plugins should probably be moved to their own
project and have independent versioning... and we will get there, but
right now the easiest/best thing to do is to use the same version for
all modules.
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
> Who was the question directed at, me or Jason?
You I believe. I don't think we can easily do this right now...
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jeff Genender <jg...@apache.org>.
David Jencks wrote:
>
> On Jun 30, 2006, at 10:54 AM, Jeff Genender wrote:
>
>>
>>
>> Jason Dillon wrote:
>>> FYI, we should be using ${pom.version} anywhere the project version is
>>> needed. No need for a custom property.
>>
>> I think its by coincidence that we have 1.2-SNAPSHOT for both the plugin
>> and the G codebase...if its not coincidence, then it shouldn't be.
>> IMHO, the plugin should be versioned differently. In fact...I may even
>> go as far as to say, the packaging plugin can be useful outside of
>> geronimo itself (people building their own packages, etc) and probably
>> should be in its own tree or even be a mojo. I am personally against
>> locking the G verison to the plugin version...I would like to see them
>> seperated.
>
> Can you explain how this could possibly work since the packaging plugin
> uses geronimo core code to do all its work? How can it possibly make
> sense to version something that is a way of running some code in maven
> differently than the code that is being run?
Who was the question directed at, me or Jason?
>
> thanks
> david jencks
>
>>
>>>
>>> --jason
>>>
>>>
>>> On Jun 30, 2006, at 9:19 AM, David Jencks wrote:
>>>
>>>>
>>>> On Jun 30, 2006, at 9:07 AM, anita kulshreshtha wrote:
>>>>
>>>>> It was my understanding that we do not use snapshots for plugins.
>>>>> This is from etc/project.properties -
>>>>> geronimo_packaging_plugin_version=1.2.0-4
>>>>> geronimo_assembly_plugin_version=1.2.0-9
>>>>> geronimo_deployment_plugin_version=1.2.0-2
>>>>> geronimo_dependency_plugin_version=1.2.0-2
>>>>
>>>> That was due to maven 1 incompetence in plugin management. It's
>>>> caused untold headaches. Although it appears m2 has a whole new set
>>>> of things it cant do with plugins, handling snapshot plugins allegedly
>>>> works fine. Due to the problems with the m1 versioning I'd like to
>>>> give m2 snapshot plugins a chance.
>>>>
>>>> thanks
>>>> david jencks
>>>>
>>>>>
>>>>> Thnaks
>>>>> Anita
>>>>>
>>>>> --- Jeff Genender <jg...@savoirtech.com> wrote:
>>>>>
>>>>>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
>>>>>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>>>>>
>>>>>> Index: pom.xml
>>>>>> ===================================================================
>>>>>> --- pom.xml (revision 418149)
>>>>>> +++ pom.xml (working copy)
>>>>>> @@ -136,7 +136,7 @@
>>>>>> | Geronimo plugin versions
>>>>>> |
>>>>>> -->
>>>>>> -
>>>>>>
>>>>> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
>>>>>> +
>>>>>>
>>>>> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</geronimoPackagingPluginVersion>
>>>>>
>>>>>
>>>>>>
>>>>>> <!--
>>>>>> |
>>>>>>
>>>>>
>>>>>
>>>>> __________________________________________________
>>>>> Do You Yahoo!?
>>>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>>>> http://mail.yahoo.com
>>>>
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
>> I think its by coincidence that we have 1.2-SNAPSHOT for both the
>> plugin
>> and the G codebase...if its not coincidence, then it shouldn't be.
>> IMHO, the plugin should be versioned differently. In fact...I may
>> even
>> go as far as to say, the packaging plugin can be useful outside of
>> geronimo itself (people building their own packages, etc) and
>> probably
>> should be in its own tree or even be a mojo. I am personally against
>> locking the G verison to the plugin version...I would like to see
>> them
>> seperated.
>
> Can you explain how this could possibly work since the packaging
> plugin uses geronimo core code to do all its work? How can it
> possibly make sense to version something that is a way of running
> some code in maven differently than the code that is being run?
Short-term I do not believe it can...
And I don't think we should try to resolve this until we have a
functional m2 build. After we are up on m2 then we can fix issues
like this, but I believe it is premature to try to do so now.
--jason
Re: [RTC] - Fix top pom to reference right plugin
Posted by David Jencks <da...@yahoo.com>.
On Jun 30, 2006, at 10:54 AM, Jeff Genender wrote:
>
>
> Jason Dillon wrote:
>> FYI, we should be using ${pom.version} anywhere the project
>> version is
>> needed. No need for a custom property.
>
> I think its by coincidence that we have 1.2-SNAPSHOT for both the
> plugin
> and the G codebase...if its not coincidence, then it shouldn't be.
> IMHO, the plugin should be versioned differently. In fact...I may even
> go as far as to say, the packaging plugin can be useful outside of
> geronimo itself (people building their own packages, etc) and probably
> should be in its own tree or even be a mojo. I am personally against
> locking the G verison to the plugin version...I would like to see them
> seperated.
Can you explain how this could possibly work since the packaging
plugin uses geronimo core code to do all its work? How can it
possibly make sense to version something that is a way of running
some code in maven differently than the code that is being run?
thanks
david jencks
>
>>
>> --jason
>>
>>
>> On Jun 30, 2006, at 9:19 AM, David Jencks wrote:
>>
>>>
>>> On Jun 30, 2006, at 9:07 AM, anita kulshreshtha wrote:
>>>
>>>> It was my understanding that we do not use snapshots for plugins.
>>>> This is from etc/project.properties -
>>>> geronimo_packaging_plugin_version=1.2.0-4
>>>> geronimo_assembly_plugin_version=1.2.0-9
>>>> geronimo_deployment_plugin_version=1.2.0-2
>>>> geronimo_dependency_plugin_version=1.2.0-2
>>>
>>> That was due to maven 1 incompetence in plugin management. It's
>>> caused untold headaches. Although it appears m2 has a whole new set
>>> of things it cant do with plugins, handling snapshot plugins
>>> allegedly
>>> works fine. Due to the problems with the m1 versioning I'd like to
>>> give m2 snapshot plugins a chance.
>>>
>>> thanks
>>> david jencks
>>>
>>>>
>>>> Thnaks
>>>> Anita
>>>>
>>>> --- Jeff Genender <jg...@savoirtech.com> wrote:
>>>>
>>>>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references
>>>>> it as
>>>>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>>>>
>>>>> Index: pom.xml
>>>>> ==================================================================
>>>>> =
>>>>> --- pom.xml (revision 418149)
>>>>> +++ pom.xml (working copy)
>>>>> @@ -136,7 +136,7 @@
>>>>> | Geronimo plugin versions
>>>>> |
>>>>> -->
>>>>> -
>>>>>
>>>> <geronimoPackagingPluginVersion>1.2.0</
>>>> geronimoPackagingPluginVersion>
>>>>> +
>>>>>
>>>> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</
>>>> geronimoPackagingPluginVersion>
>>>>
>>>>>
>>>>> <!--
>>>>> |
>>>>>
>>>>
>>>>
>>>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>>> http://mail.yahoo.com
>>>
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jeff Genender <jg...@apache.org>.
Jason Dillon wrote:
> FYI, we should be using ${pom.version} anywhere the project version is
> needed. No need for a custom property.
I think its by coincidence that we have 1.2-SNAPSHOT for both the plugin
and the G codebase...if its not coincidence, then it shouldn't be.
IMHO, the plugin should be versioned differently. In fact...I may even
go as far as to say, the packaging plugin can be useful outside of
geronimo itself (people building their own packages, etc) and probably
should be in its own tree or even be a mojo. I am personally against
locking the G verison to the plugin version...I would like to see them
seperated.
>
> --jason
>
>
> On Jun 30, 2006, at 9:19 AM, David Jencks wrote:
>
>>
>> On Jun 30, 2006, at 9:07 AM, anita kulshreshtha wrote:
>>
>>> It was my understanding that we do not use snapshots for plugins.
>>> This is from etc/project.properties -
>>> geronimo_packaging_plugin_version=1.2.0-4
>>> geronimo_assembly_plugin_version=1.2.0-9
>>> geronimo_deployment_plugin_version=1.2.0-2
>>> geronimo_dependency_plugin_version=1.2.0-2
>>
>> That was due to maven 1 incompetence in plugin management. It's
>> caused untold headaches. Although it appears m2 has a whole new set
>> of things it cant do with plugins, handling snapshot plugins allegedly
>> works fine. Due to the problems with the m1 versioning I'd like to
>> give m2 snapshot plugins a chance.
>>
>> thanks
>> david jencks
>>
>>>
>>> Thnaks
>>> Anita
>>>
>>> --- Jeff Genender <jg...@savoirtech.com> wrote:
>>>
>>>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
>>>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>>>
>>>> Index: pom.xml
>>>> ===================================================================
>>>> --- pom.xml (revision 418149)
>>>> +++ pom.xml (working copy)
>>>> @@ -136,7 +136,7 @@
>>>> | Geronimo plugin versions
>>>> |
>>>> -->
>>>> -
>>>>
>>> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
>>>> +
>>>>
>>> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</geronimoPackagingPluginVersion>
>>>
>>>>
>>>> <!--
>>>> |
>>>>
>>>
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>> http://mail.yahoo.com
>>
Re: [RTC] - Fix top pom to reference right plugin
Posted by Jason Dillon <ja...@planet57.com>.
FYI, we should be using ${pom.version} anywhere the project version
is needed. No need for a custom property.
--jason
On Jun 30, 2006, at 9:19 AM, David Jencks wrote:
>
> On Jun 30, 2006, at 9:07 AM, anita kulshreshtha wrote:
>
>> It was my understanding that we do not use snapshots for plugins.
>> This is from etc/project.properties -
>> geronimo_packaging_plugin_version=1.2.0-4
>> geronimo_assembly_plugin_version=1.2.0-9
>> geronimo_deployment_plugin_version=1.2.0-2
>> geronimo_dependency_plugin_version=1.2.0-2
>
> That was due to maven 1 incompetence in plugin management. It's
> caused untold headaches. Although it appears m2 has a whole new
> set of things it cant do with plugins, handling snapshot plugins
> allegedly works fine. Due to the problems with the m1 versioning
> I'd like to give m2 snapshot plugins a chance.
>
> thanks
> david jencks
>
>>
>> Thnaks
>> Anita
>>
>> --- Jeff Genender <jg...@savoirtech.com> wrote:
>>
>>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references
>>> it as
>>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>>
>>> Index: pom.xml
>>> ===================================================================
>>> --- pom.xml (revision 418149)
>>> +++ pom.xml (working copy)
>>> @@ -136,7 +136,7 @@
>>> | Geronimo plugin versions
>>> |
>>> -->
>>> -
>>>
>> <geronimoPackagingPluginVersion>1.2.0</
>> geronimoPackagingPluginVersion>
>>> +
>>>
>> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</
>> geronimoPackagingPluginVersion>
>>>
>>> <!--
>>> |
>>>
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>
Re: [RTC] - Fix top pom to reference right plugin
Posted by David Jencks <da...@yahoo.com>.
On Jun 30, 2006, at 9:07 AM, anita kulshreshtha wrote:
> It was my understanding that we do not use snapshots for plugins.
> This is from etc/project.properties -
> geronimo_packaging_plugin_version=1.2.0-4
> geronimo_assembly_plugin_version=1.2.0-9
> geronimo_deployment_plugin_version=1.2.0-2
> geronimo_dependency_plugin_version=1.2.0-2
That was due to maven 1 incompetence in plugin management. It's
caused untold headaches. Although it appears m2 has a whole new set
of things it cant do with plugins, handling snapshot plugins
allegedly works fine. Due to the problems with the m1 versioning I'd
like to give m2 snapshot plugins a chance.
thanks
david jencks
>
> Thnaks
> Anita
>
> --- Jeff Genender <jg...@savoirtech.com> wrote:
>
>> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
>> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>>
>> Index: pom.xml
>> ===================================================================
>> --- pom.xml (revision 418149)
>> +++ pom.xml (working copy)
>> @@ -136,7 +136,7 @@
>> | Geronimo plugin versions
>> |
>> -->
>> -
>>
> <geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
>> +
>>
> <geronimoPackagingPluginVersion>1.2-SNAPSHOT</
> geronimoPackagingPluginVersion>
>>
>> <!--
>> |
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
Re: [RTC] - Fix top pom to reference right plugin
Posted by anita kulshreshtha <a_...@yahoo.com>.
It was my understanding that we do not use snapshots for plugins.
This is from etc/project.properties -
geronimo_packaging_plugin_version=1.2.0-4
geronimo_assembly_plugin_version=1.2.0-9
geronimo_deployment_plugin_version=1.2.0-2
geronimo_dependency_plugin_version=1.2.0-2
Thnaks
Anita
--- Jeff Genender <jg...@savoirtech.com> wrote:
> The packaging plugin is at 1.2-SNAPSHOT, and the pom references it as
> 1.2.0. I wan tto update it to 1.2-SNAPSHOT:
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 418149)
> +++ pom.xml (working copy)
> @@ -136,7 +136,7 @@
> | Geronimo plugin versions
> |
> -->
> -
>
<geronimoPackagingPluginVersion>1.2.0</geronimoPackagingPluginVersion>
> +
>
<geronimoPackagingPluginVersion>1.2-SNAPSHOT</geronimoPackagingPluginVersion>
>
> <!--
> |
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com