maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <rfscho...@apache.org>
Subject Re: maven install plugin version 2.5 installAtEnd question
Date Wed, 09 Oct 2013 18:30:51 GMT
Tonio,

I've created and fixed https://jira.codehaus.org/browse/MINSTALL-99
I've deployed a 2.5.1-SNAPSHOT to  
https://repository.apache.org/content/repositories/snapshots/ ready for  
test, would be nice if you could test this.

thanks,

Robert


Op Tue, 01 Oct 2013 16:08:53 +0200 schreef Tonio Caputo  
<tonioc@exeo.com.ar>:

> Hi,
>
> Continuing with this issue, I'll describe one more unexpected behaviour  
> I'm
> facing in my project.
>
> Just to describe the project, its a kind of plugin-project that has an
> implementation that should be hidden from
> the developer that uses the plugin,  so my project contains these poms
>
> - main pom (should be deployed/installed)
> - API pom contains the API for the plugin (should be deployed/installed)
> - SPI pom contains the implementation (should NOT be deployed/installed)
> - INTEGRATION-TEST test the plugin as a plugin (should NOT be
> deployed/installed)
>
> So after Robert answer I just made the integration-test module
> "installable" to see everything is working ok
> and now I'm realizing the SPI is also installed although it is configured
> to skip install.
>
> Hope this is helpful somehow for the new "special cases"
> thanks
> tonio
>
>
>
>
> On Mon, Sep 30, 2013 at 6:36 PM, Tonio Caputo <tonioc@exeo.com.ar> wrote:
>
>> Hi Robert,
>>
>> Thanks for your quick answer, expecting the special cases handling !!!!!
>> :-)
>>
>> And now that you mention it, I remember wondering why it was not set to
>> true by default :-).
>>
>> Sorry I might have missed reading some documentation, and that's my  
>> fault.
>>
>> thanks again
>> tonio
>>
>>
>>
>> On Mon, Sep 30, 2013 at 6:30 PM, Robert Scholte  
>> <rfscholte@apache.org>wrote:
>>
>>> Hi Tonio,
>>>
>>> that's one of the reasons why I didn't changed this to the default
>>> behavior for both plugins.
>>> Current implementation checks if it is installing/deploying the final
>>> module. If so, it will continue with the configuration of that module.  
>>> This
>>> should cover most of the usecases, so now we can gather those special  
>>> cases
>>> and start tweaking those plugins.
>>>
>>> Robert
>>>
>>>
>>> Op Mon, 30 Sep 2013 23:11:12 +0200 schreef Tonio Caputo <
>>> tonioc@exeo.com.ar>:
>>>
>>>
>>>  Hi,
>>>>
>>>> I was trying this new great feature but,
>>>>
>>>> I found that if the last module of the project skips the install,  it
>>>> will not install any of the other modules.
>>>>
>>>> Is this the expected behaviour ?
>>>>
>>>> Just to let you know:
>>>>
>>>> My project last module is an integration-test that should be ran after
>>>> all
>>>> other modules are packaged, it should not be installed nor deployed,
>>>> so it will be great if this configuration option can handle scenarios
>>>> like
>>>> this.
>>>>
>>>>
>>>> Thanks in advance
>>>> tonio
>>>> PS: Seems maven-deploy-plugin version 2.8 deployAtEnd works in a  
>>>> similar
>>>> way.
>>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail:  
>>> users-unsubscribe@maven.**apache.org<users-unsubscribe@maven.apache.org>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message