geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <ja...@planet57.com>
Subject Re: M2 Issues and Actions
Date Tue, 04 Jul 2006 00:51:14 GMT
FYI... issue opened to fix the problem using extensions here:

     http://jira.codehaus.org/browse/MNG-1911

And you were right... m2 will reload the plugin :-)

--jason


On Jul 3, 2006, at 3:26 PM, anita kulshreshtha wrote:

>    I used our project. Here are the steps -
> 1. add a print statements to say PackageBuilderShellMojo.
> 2. To make this test go faster comment out modules, applications from
> the parent pom.
> 3. use mvn clean install
>     The .m2 Repo already has a packaging plugin with version 1.2.0. So
> maven happily builds. After the plugin is built, the configs are  
> built.
> That is when the "reloading plugin container ...." message appears.  
> You
> should see the message you added to the packaging plugin. The message
> should appear in all the configs except may be gbean-deployer. The
> gbean-delpoyer config is a special case, you must make sure that the
> new statement is executed.
>
> Thanks
> Anita
>
>
> --- Jason Dillon <jason@planet57.com> wrote:
>
>> Do you have an simple example project that implements the build and
>> use of the plugin in the same cycle that I can peek at?
>>
>> --jason
>>
>>
>> On Jul 3, 2006, at 5:59 AM, anita kulshreshtha wrote:
>>
>>> inline..
>>>
>>> --- Jason Dillon <jason@planet57.com> wrote:
>>>
>>>>>> While this may work most of the time, it is not ideal as when
>>>> making
>>>>>> changes to plugins, users will be mystified when those changes
>> are
>>>>>> not used on the first build.
>>>>>
>>>>>    This is not true. The plugin is *not* used before it is built.
>>>> The
>>>>> problem is that maven does not even start the build until it has
>>>>> downloaded all the plugins. Even a dummy plugin would work.
>>>>
>>>> Um... it is completely true.  I am aware that the plugin is not
>> used
>>>>
>>>> before it is built.
>>>>
>>>> BUT the point that I was making was that Maven must resolve the
>>>> plugin before the build commences... that means that the plugin
>> must
>>>>
>>>> exist in a repository (or cache) already, and that is the version
>>>> that will be used for the current build cycle... NOT the plugin
>> that
>>>>
>>>> will be compiled and installed as part of the current build.
>>>>
>>>> Therefor the current build will always use the version of the
>> plugin
>>>>
>>>> that was built BEFORE the build started, NOT the version that is
>>>> actually getting built.
>>>
>>>      I ran a test. A totally bogus plugin will not work, but a
>> plugin
>>> with correctly defined component.xml will work. Maven indeed uses
>> the
>>> plugin that was built (see the message below). If we want to use
>>> SNAPSHOT versions for the plugin, we can create a skeletal dummy
>>> plugin
>>> (s) and publish it. And the build will work like charm with just
>>> 'mvn'!
>>>     If we want to use numbered versions like M1, we need multi step
>>> build. Whenever the version is changed we will have to use 'mvn'
>> more
>>> than once to get a full build.
>>>
>>> Thanks
>>> Anita
>>>
>>> m
>>> [INFO]
>>>
>>
> ----------------------------------------------------------------------
>>
>>> ------
>>> [INFO] Building Geronimo Configuration for performing service
>>> deployments
>>> [INFO]    task-segment: [clean, install]
>>> [INFO]
>>>
>>
> ----------------------------------------------------------------------
>>
>>> ------
>>> [INFO] Reloading plugin container for:
>>> org.apache.geronimo.plugins:geronimo-packaging-plugin. The pl
>>> ugin artifact has changed.
>>> [INFO] [clean:clean]
>>> [INFO] Deleting directory
>>>
>> D:\anita\geronimo\geronimo-1.2\configs\geronimo-gbean-deployer\target
>>> [INFO] Deleting directory
>>> D:\anita\geronimo\geronimo-1.2\configs\geronimo-gbean-deployer
>>> \target\clas
>>> ses
>>> [INFO] Deleting directory
>>> D:\anita\geronimo\geronimo-1.2\configs\geronimo-gbean-deployer
>>> \target\test
>>> -classes
>>>>
>>>> This is why I suggested that the plugin either be part of another
>>>> project (detached from the main build) or as part of a bootstrap
>>>> phase that is executed before the main build cycle.
>>>>
>>>> --jason
>>>>
>>>>
>>>>
>>>
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam?  Yahoo! Mail has the best spam protection around
>>> http://mail.yahoo.com
>>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com


Mime
View raw message