[Studio] Using the Maven Release Plugin

[Felix Knecht-2]

Pierre-Arnaud Marcelot schrieb:

> We're almost there...
>
> This time it's not failing, but it is trying to deploy the
> distribution on p.a.o, instead of using the altDeploymentRepository
> property.
>
> See the log attached to this mail.
>
> Any hints about that?
>

If this are the just fixed dist from the studio/studio deploy-file
you'll need to add similar to your settings.xml as I did on the Ci
server and adapt it to your needs (e.g. profile ...). deploy:deploy-file
doesn't seems to respect altDeploymentRepository but only accepts a url.
Otherwise it's taken from Apache TLP pom pointing to p.a.o.

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <profiles>
    <profile>
      <id>CI</id>
      <properties>
       
<studio.dist.url>${pom.distributionManagement.snapshotRepository.url}</studio.dist.url>
      </properties>
    </profile>
  </profiles>
</settings>

HTH
Felix

[Pierre-Arnaud Marcelot-2]

Oh yeah. That's a very good idea!

I'm pretty confident it will work now (as it's working on the CI server).

I'm going to test that.

Thanks,
Pierre-Arnaud

On Thu, Oct 9, 2008 at 5:44 PM, Felix Knecht <felixk@...> wrote:

Pierre-Arnaud Marcelot schrieb:

> We're almost there...
>
> This time it's not failing, but it is trying to deploy the
> distribution on p.a.o, instead of using the altDeploymentRepository
> property.
>
> See the log attached to this mail.
>
> Any hints about that?
>

If this are the just fixed dist from the studio/studio deploy-file
you'll need to add similar to your settings.xml as I did on the Ci
server and adapt it to your needs (e.g. profile ...). deploy:deploy-file
doesn't seems to respect altDeploymentRepository but only accepts a url.
Otherwise it's taken from Apache TLP pom pointing to p.a.o.

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
 <profiles>
   <profile>
     <id>CI</id>
     <properties>

<studio.dist.url>${pom.distributionManagement.snapshotRepository.url}</studio.dist.url>
     </properties>
   </profile>
 </profiles>
</settings>

HTH
Felix

[Pierre-Arnaud Marcelot-2]

Hi,

It's now completely working now !
Both goals of the Release plugin are working great (release:prepare and release:perform).
Once again, thanks a lot Felix for your help on Maven. ;)

However, I still have one important question.

As it is right now the build will deploy on the Maven repository all our plugins and all our distributions.
That's a total of 500 MB for a single release!!!

Which makes me wonder if it's really necessary to deploy the distributions on the Maven repository.
If we remove the distributions, we _only_ have to deploy 200 MB, which is much more reasonable...

WDYT?

Thanks,
Pierre-Arnaud

On Thu, Oct 9, 2008 at 6:02 PM, Pierre-Arnaud Marcelot <pa@...> wrote:

Oh yeah. That's a very good idea!

I'm pretty confident it will work now (as it's working on the CI server).

I'm going to test that.

Thanks,
Pierre-Arnaud

On Thu, Oct 9, 2008 at 5:44 PM, Felix Knecht <felixk@...> wrote:

Pierre-Arnaud Marcelot schrieb:

> We're almost there...
>
> This time it's not failing, but it is trying to deploy the
> distribution on p.a.o, instead of using the altDeploymentRepository
> property.
>
> See the log attached to this mail.
>
> Any hints about that?
>

If this are the just fixed dist from the studio/studio deploy-file
you'll need to add similar to your settings.xml as I did on the Ci
server and adapt it to your needs (e.g. profile ...). deploy:deploy-file
doesn't seems to respect altDeploymentRepository but only accepts a url.
Otherwise it's taken from Apache TLP pom pointing to p.a.o.

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
 <profiles>
   <profile>
     <id>CI</id>
     <properties>

<studio.dist.url>${pom.distributionManagement.snapshotRepository.url}</studio.dist.url>
     </properties>
   </profile>
 </profiles>
</settings>

HTH
Felix

[Emmanuel Lecharny]

Pierre-Arnaud Marcelot wrote:

> Hi,
>
> It's now completely working now !
> Both goals of the Release plugin are working great (release:prepare and
> release:perform).
> Once again, thanks a lot Felix for your help on Maven. ;)
>
> However, I still have one important question.
>
> As it is right now the build will deploy on the Maven repository all our
> plugins and all our distributions.
> That's a total of 500 MB for a single release!!!
>
> Which makes me wonder if it's really necessary to deploy the distributions
> on the Maven repository.
> If we remove the distributions, we _only_ have to deploy 200 MB, which is
> much more reasonable...
>
> WDYT?
>
>  

IMO, we don't have to deploy distribs on maven repo. Maven repo is
supposed to store shared libraries, no products.

so +1 to avoid deploying those dists on the repo.

--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org