Not releasing an integration-tests module

[Dan Adams <da...@ifactory.com>]

I have a project that is a jar library with the following structure:
/
  /lib
  /integration-tests
    /web
    /tests

I want to release it but I don't want to deploy the integration-test
module or check it's dependecies for snapshots and such. Can I ignore it
using the release plugin?

-- 
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857


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

Re: Not releasing an integration-tests module

[Rémy Sanlaville <re...@gmail.com>]

>
> You can put the integration test's <module> in a profile, and not
> activate that profile when you release.  You'll have to update the
> version number for that module since the release plugin won't do it
> for you.



Yes it's possible to use profiles but it would be better to have a <skip>
configuration as discussed in [1].

Rémy

[1]
http://www.nabble.com/-Proposal--New-profile-activation-tf3240038s177.html#a9006410

Re: Not releasing an integration-tests module

[Wendy Smoak <ws...@gmail.com>]

On 3/1/07, Dan Adams <da...@ifactory.com> wrote:
> I have a project that is a jar library with the following structure:
> /
>   /lib
>   /integration-tests
>     /web
>     /tests
>
> I want to release it but I don't want to deploy the integration-test
> module or check it's dependecies for snapshots and such. Can I ignore it
> using the release plugin?

You can put the integration test's <module> in a profile, and not
activate that profile when you release.  You'll have to update the
version number for that module since the release plugin won't do it
for you.

-- 
Wendy

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