commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita" <brunodepau...@yahoo.com.br>
Subject Re: [TEXT] Problems with the site build
Date Mon, 01 Dec 2014 01:24:13 GMT
Hi there, 
Tried the mvn clean site-deploy, and noticed a similar message.
kinow@chuva:~/java/apache/commons-text$ mvn clean site-deploy -e -XApache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T15:37:52-03:00)Maven home: /opt/apache-maven-3.2.1Java version: 1.7.0_65, vendor:
Oracle CorporationJava home: /opt/jdk1.7.0_65/jreDefault locale: en_US, platform encoding:
UTF-8OS name: "linux", version: "3.13.0-36-generic", arch: "amd64", family: "unix"
Looking at the commons-parent-35 pom.xml [1], it contains the following comment:
        <plugin>          <groupId>org.apache.maven.plugins</groupId> 
        <artifactId>maven-site-plugin</artifactId>          <version>${commons.site-plugin.version}</version> 
        <configuration>            <!-- don't deploy site with maven-site-plugin
-->            <skipDeploy>true</skipDeploy>          </configuration> 
      </plugin>
So I guess that's why we are are presented with this message.
In another part of the commons-parent pom, it mentions the scm-publish. Maybe mvn clean scm-publish:publish-scm
? Just my 0.02 cents.HTH,Bruno
[1] https://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-35/pom.xml
 
      From: Benedikt Ritter <britter@apache.org>
 To: Commons Developers List <dev@commons.apache.org> 
 Sent: Sunday, November 30, 2014 4:23 PM
 Subject: Re: [TEXT] Problems with the site build
   
TEXT inherits from commons parent (like BeanUtils2 does) because the
sandbox parent pom only adds unnecessary complexity and yet another thing
we need to release. I updated BeanUtils2 to commons parent because I wanted
to use the new commons skin for example. Since the BeanUtils2 site build
works, I think it has nothing to do with the parent pom.

I'm trying to deploy the site with
mvn clean site-deploy
and
mvn clean site-deploy -Dmaven.site.deploy.skip=false

Thank you,
Benedikt

2014-11-29 12:55 GMT+01:00 sebb <sebbaz@gmail.com>:

> TEXT is a Sandbox component, so it should inherit from the Commons-Sandbox
> POM.
>
> That may or may not help, but ought to be done to prevent accidental
> deployment.
>
> What exact commands have you used?
>
>
> On 29 November 2014 at 11:31, Benedikt Ritter <britter@apache.org> wrote:
> > Hi all,
> >
> > I've tried to create the site for commons-text but the site build doesn't
> > work. It always prints out "maven.site.deploy.skip = true: Skipping site
> > deployment" [1]. I've tried to override this via -D but it doesn't work.
> > Can anybody help?
> >
> > TIA!
> > Benedikt
> >
> > [1]
> >
> https://github.com/apache/maven-plugins/blob/3b34d1bbf0ff0347fce83084ce4670755e1cee7c/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java#L162
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org


>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter


   

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message