You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ryan Wynn <bi...@gmail.com> on 2006/04/21 04:08:58 UTC

Support for Multi-project Web Sites

I haven't been able to find maven2 documentation on how to create a
parent site that automatically includes links to all the modules under
it.  Has a solution for this been developed yet, and if so where can I
find documentation on it?  Maven is invoking site:site on all the
reactor projects but the parent site does not include the links.

Using ${modules} in the site.xml for the parent but not sure if this
is even currently supported.

Any help would be appreciated.

Thanks,
Ryan

RE: Support for Multi-project Web Sites

Posted by RobJac <ro...@caritor.com>.
Hi,

I am also trying to get a parent site created which will show details of all
my child projects.  As mentioned in the chains of mails here, I found I need
to install snapshot version 2.0-SNAPSHOT of maven-site-plugin. I have added
this in my pom xml but. it gives me this error saying it not able to
download . I have Maven-2.0.4 version.

+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   Maven
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]   Maven Quick Start Archetype
[INFO]
----------------------------------------------------------------------------
[INFO] Building Maven
[INFO]    task-segment: [site]
[INFO]
----------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-site-plugin
Version: 2.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-site-plugin:pom:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build
project for plugin 'org.apache.maven.plugins:maven-site-plugin': POM
'org.apache.maven.plugins:maven-site-plugin' not found in repository: Unable
to download the artifact from any repository

  org.apache.maven.plugins:maven-site-plugin:pom:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1269)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1011)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:975)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build
project for plugin 'org.apache.maven.plugins:maven-site-plugin': POM
'org.apache.maven.plugins:maven-site-plugin' not found in repository: Unable
to download the artifact from any repository

  org.apache.maven.plugins:maven-site-plugin:pom:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

	at
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265)
	at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:183)
	at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
	... 18 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM
'org.apache.maven.plugins:maven-site-plugin' not found in repository: Unable
to download the artifact from any repository

  org.apache.maven.plugins:maven-site-plugin:pom:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

	at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:513)
	at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225)
	at
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:249)
	... 21 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-site-plugin:pom:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

	at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136)
	at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
	at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467)
	... 23 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
download the artifact from any repository
	at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260)
	at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124)
	... 25 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Tue May 02 10:05:18 BST 2006
[INFO] Final Memory: 1M/3M
[INFO]
------------------------------------------------------------------------

Please find below my parent site.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="Maven">
  <bannerLeft>
    <name>Maven</name>
    <src>http://maven.apache.org/images/apache-maven-project.png</src>
    <href>http://maven.apache.org/</href>
  </bannerLeft>
  <bannerRight>
    <src>http://maven.apache.org/images/maven-small.gif</src>
  </bannerRight>
  <skin> 
    <groupId>org.apache.maven.skins</groupId> 
    <artifactId>maven-default-skin</artifactId> 
    <version>1.0-SNAPSHOT</version> 
  </skin> 
  <body>
    <links>
      <item name="Apache" href="http://www.apache.org/" />
      <item name="Maven 1.0" href="http://maven.apache.org/"/>
      <item name="Maven 2" href="http://maven.apache.org/maven2/"/>
    </links>

    <menu name="Maven 2.0">
      <item name="APT Format" href="format.html"/>
      <item name="FAQ" href="faq.html"/>
      <item name="Xdoc Example" href="xdoc.html"/>      
    </menu>
    ${modules}
  </body>
</project>

my parent pom.xml

<project 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/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>Parent_Build</groupId>
  <artifactId>Parent_Build</artifactId>
  <packaging>pom</packaging>
  <version>1.0</version>
  <name>Maven</name>
  <url>http://maven.apache.org/maven2</url>
  <inceptionYear>2001</inceptionYear>
  <modules>
	<module>Project_A</module>
	<module>Project_B</module>	
	<module>Project_C</module>
	<module>Project_D</module>
	<module>Project_E</module>
	<module>Project_F</module>
	<module>Project_G</module>
	<module>Project_H</module>
	<module>Project_I</module>
	<module>Project_J</module>
  </modules>
<distributionManagement>
    <site>
      <id>website</id>
      <url>scp://webhost.company.com/www/website</url>
    </site>
   <snapshotRepository>
     <id>snapshots</id>
      <name>Maven Central Plugins Development Repository</name>
     
<url>scp://repo1.maven.org/home/projects/maven/repository-staging/snapshots/maven2</url>
    </snapshotRepository>
  </distributionManagement>
  <build>
    <plugins>
      <plugin>
	<groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <version>2.0-SNAPSHOT</version>
        <configuration>
          <locales>en,fr</locales>
        </configuration>
      </plugin>
    </plugins>
  </build>  
</project>
Please let me know if i am doing some thing wrong here. or could some one
who has got this right send me a sample of your pom.xml and site.xml for
your parent project. Thanks in advance
--
View this message in context: http://www.nabble.com/Support-for-Multi-project-Web-Sites-t1484154.html#a4172319
Sent from the Maven - Users forum at Nabble.com.


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


RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Ryan,
 
Thanks for explaining changes.
I did include skin tag in site.xml but did not put <menu ref="modules" />. Even after installing suggested site plugin and skin, somehow, index.html files are not getting generated while with default site and skin, these files are generated. That is why, for right now, I am using defaults and  have created one modules.xml under rootproject/src/site/xdoc and provided links with submodules in this file. I did not create site.xml files for child modules. As per requirement it is sufficient.
 
Thanks again.
 
Vijay
  

________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Wed 4/26/2006 11:13 AM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



Hi Vijay,

Did you add the following to your parent site.xml?

...
<skin>
        <groupId>org.apache.maven.skins</groupId>
        <artifactId>maven-default-skin</artifactId>
        <version>1.0-SNAPSHOT</version>
</skin>

<body>
    <link/>

    <menu/>

   <menu ref="modules" /> <!-- this creates the link to submodules-->
</body>

...

Then in the children site.xml you can create a link to the parent with

${parentProject}



On 4/26/06, Vijay Shanker <vs...@comframe.com> wrote:
> Ryan,
>
> My root report, still, does not have links to submodules. Could you please suggest what steps you followed? I did same thing given in your given link.
>
> Thanks,
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Mon 4/24/2006 5:30 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> > Hi Ryan,
> >
> > I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
> >
> > If it is working for you then could you please gives steps and suggestions to achieve it.
>
>
> See
> http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
>
> that's what helped me.
>
> You will need to download the skins plugin and do a mvn
> -updateReleaseInfo=true install on it.
>
>
> >
> > Thanking you.
> >
> > Vijay
> >
> >
> > ________________________________
> >
> > From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> > Sent: Fri 4/21/2006 1:32 PM
> > To: Maven Users List
> > Subject: Re: Support for Multi-project Web Sites
> >
> >
> >
> > On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > > Hi -
> > >
> > > See
> > > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > > and see if that doesn't help!
> > >
> >
> > Thanks, that help worked.  I needed to use install with
> > -updateReleaseInfo=true instead of install-file.
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: 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
>
>




Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
Hi Vijay,

Did you add the following to your parent site.xml?

...
<skin>
        <groupId>org.apache.maven.skins</groupId>
        <artifactId>maven-default-skin</artifactId>
        <version>1.0-SNAPSHOT</version>
</skin>

<body>
    <link/>

    <menu/>

   <menu ref="modules" /> <!-- this creates the link to submodules-->
</body>

...

Then in the children site.xml you can create a link to the parent with

${parentProject}



On 4/26/06, Vijay Shanker <vs...@comframe.com> wrote:
> Ryan,
>
> My root report, still, does not have links to submodules. Could you please suggest what steps you followed? I did same thing given in your given link.
>
> Thanks,
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Mon 4/24/2006 5:30 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> > Hi Ryan,
> >
> > I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
> >
> > If it is working for you then could you please gives steps and suggestions to achieve it.
>
>
> See
> http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
>
> that's what helped me.
>
> You will need to download the skins plugin and do a mvn
> -updateReleaseInfo=true install on it.
>
>
> >
> > Thanking you.
> >
> > Vijay
> >
> >
> > ________________________________
> >
> > From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> > Sent: Fri 4/21/2006 1:32 PM
> > To: Maven Users List
> > Subject: Re: Support for Multi-project Web Sites
> >
> >
> >
> > On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > > Hi -
> > >
> > > See
> > > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > > and see if that doesn't help!
> > >
> >
> > Thanks, that help worked.  I needed to use install with
> > -updateReleaseInfo=true instead of install-file.
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: 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
>
>

RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Ryan,
 
My root report, still, does not have links to submodules. Could you please suggest what steps you followed? I did same thing given in your given link.
 
Thanks,
Vijay
 

________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Mon 4/24/2006 5:30 PM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> Hi Ryan,
>
> I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
>
> If it is working for you then could you please gives steps and suggestions to achieve it.


See
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html

that's what helped me.

You will need to download the skins plugin and do a mvn
-updateReleaseInfo=true install on it.


>
> Thanking you.
>
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Fri 4/21/2006 1:32 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > Hi -
> >
> > See
> > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > and see if that doesn't help!
> >
>
> Thanks, that help worked.  I needed to use install with
> -updateReleaseInfo=true instead of install-file.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>




RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Got it. syntax is 
mvn -DupdateReleaseInfo=true install
 
Vijay
 

________________________________

From: Vijay Shanker [mailto:vshanker@comframe.com]
Sent: Tue 4/25/2006 1:14 PM
To: Maven Users List
Subject: RE: Support for Multi-project Web Sites



Ryan,

Could you please send me example of installing site skin using -updateReleaseInfo?

Thanks,
Vijay


________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Mon 4/24/2006 5:30 PM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> Hi Ryan,
>
> I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
>
> If it is working for you then could you please gives steps and suggestions to achieve it.


See
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html

that's what helped me.

You will need to download the skins plugin and do a mvn
-updateReleaseInfo=true install on it.


>
> Thanking you.
>
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Fri 4/21/2006 1:32 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > Hi -
> >
> > See
> > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > and see if that doesn't help!
> >
>
> Thanks, that help worked.  I needed to use install with
> -updateReleaseInfo=true instead of install-file.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>







RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Ryan,
 
Could you please send me example of installing site skin using -updateReleaseInfo?
 
Thanks,
Vijay
 

________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Mon 4/24/2006 5:30 PM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> Hi Ryan,
>
> I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
>
> If it is working for you then could you please gives steps and suggestions to achieve it.


See
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html

that's what helped me.

You will need to download the skins plugin and do a mvn
-updateReleaseInfo=true install on it.


>
> Thanking you.
>
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Fri 4/21/2006 1:32 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > Hi -
> >
> > See
> > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > and see if that doesn't help!
> >
>
> Thanks, that help worked.  I needed to use install with
> -updateReleaseInfo=true instead of install-file.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>




RE: Support for Multi-project Web Sites

Posted by dv...@improve.fr.
I confirm this information, https://svn.apache.org is down.

Damien Viel

Selon Vijay Shanker <vs...@comframe.com>:

> Ryan,
>  
> Looks like https://svn.apache.org is not working right now. Or may be , I am
> working from home so unable to access from here.
>  
> Thanks for the link.
>  
> Vijay
>  
> 
> ________________________________
> 
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Mon 4/24/2006 5:30 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
> 
> 
> 
> On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> > Hi Ryan,
> >
> > I am facing the same problem while building reports for multiple modules.
> Parent report does not include links of child modules' reports.
> >
> > If it is working for you then could you please gives steps and suggestions
> to achieve it.
> 
> 
> See
> http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> 
> that's what helped me.
> 
> You will need to download the skins plugin and do a mvn
> -updateReleaseInfo=true install on it.
> 
> 
> >
> > Thanking you.
> >
> > Vijay
> >
> >
> > ________________________________
> >
> > From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> > Sent: Fri 4/21/2006 1:32 PM
> > To: Maven Users List
> > Subject: Re: Support for Multi-project Web Sites
> >
> >
> >
> > On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > > Hi -
> > >
> > > See
> > > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > > and see if that doesn't help!
> > >
> >
> > Thanks, that help worked.  I needed to use install with
> > -updateReleaseInfo=true instead of install-file.
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: 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


RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Ryan,
 
Looks like https://svn.apache.org is not working right now. Or may be , I am working from home so unable to access from here.
 
Thanks for the link.
 
Vijay
 

________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Mon 4/24/2006 5:30 PM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> Hi Ryan,
>
> I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
>
> If it is working for you then could you please gives steps and suggestions to achieve it.


See
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html

that's what helped me.

You will need to download the skins plugin and do a mvn
-updateReleaseInfo=true install on it.


>
> Thanking you.
>
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Fri 4/21/2006 1:32 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > Hi -
> >
> > See
> > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > and see if that doesn't help!
> >
>
> Thanks, that help worked.  I needed to use install with
> -updateReleaseInfo=true instead of install-file.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>




Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/24/06, Vijay Shanker <vs...@comframe.com> wrote:
> Hi Ryan,
>
> I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
>
> If it is working for you then could you please gives steps and suggestions to achieve it.


See
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html

that's what helped me.

You will need to download the skins plugin and do a mvn
-updateReleaseInfo=true install on it.


>
> Thanking you.
>
> Vijay
>
>
> ________________________________
>
> From: Ryan Wynn [mailto:bigwynnr@gmail.com]
> Sent: Fri 4/21/2006 1:32 PM
> To: Maven Users List
> Subject: Re: Support for Multi-project Web Sites
>
>
>
> On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> > Hi -
> >
> > See
> > http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> > and see if that doesn't help!
> >
>
> Thanks, that help worked.  I needed to use install with
> -updateReleaseInfo=true instead of install-file.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: Support for Multi-project Web Sites

Posted by Vijay Shanker <vs...@comframe.com>.
Hi Ryan,
 
I am facing the same problem while building reports for multiple modules. Parent report does not include links of child modules' reports.
 
If it is working for you then could you please gives steps and suggestions to achieve it.
 
Thanking you.
 
Vijay
 

________________________________

From: Ryan Wynn [mailto:bigwynnr@gmail.com]
Sent: Fri 4/21/2006 1:32 PM
To: Maven Users List
Subject: Re: Support for Multi-project Web Sites



On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> Hi -
>
> See
> http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> and see if that doesn't help!
>

Thanks, that help worked.  I needed to use install with
-updateReleaseInfo=true instead of install-file.




Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/21/06, Elliot Metsger <em...@jhu.edu> wrote:
> Hi -
>
> See
> http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html
> and see if that doesn't help!
>

Thanks, that help worked.  I needed to use install with
-updateReleaseInfo=true instead of install-file.

Re: Support for Multi-project Web Sites

Posted by Elliot Metsger <em...@jhu.edu>.
Hi -

See 
http://www.nabble.com/Running-maven-site-plugin-from-svn-p3953978.html 
and see if that doesn't help!

Elliot

Ryan Wynn wrote:
> On 4/21/06, Henry S. Isidro <hi...@exist.com> wrote:
> 
>>On Friday 21 April 2006 11:38 pm, Ryan Wynn wrote:
>>
>>>Do you know if I need to install the skin manually and if so how I can do
>>>it?
>>>
>>>Thanks.
>>
>>
>>Get it from here: https://svn.apache.org/repos/asf/maven/skins/trunk and then
>>install it.
> 
> 
> Thanks, Henry.  I installed it from 
> https://svn.apache.org/repos/asf/maven/skins/trunk
> using
> 
> E:\>mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven
> -site-skin -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=SkinPlugin.jar
> 
> and my site.xml includes
> 
> <skin>
> 		<groupId>org.apache.maven.skins</groupId>
> 		<artifactId>maven-site-skin</artifactId>
> 		<version>1.0-SNAPSHOT</version>
>     </skin>
> 
> and now the complaint is
> 
> [INFO] The skin does not exist: Unable to determine the release version
> 
> Try downloading the file manually from the project website.
> 
> Then, install it using the command:
>     mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven
> -default-skin \
>         -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> 
> 
>   org.apache.maven.skins:maven-default-skin:jar:RELEASE
> 
> I do not reference 
> org.apache.maven.skins:maven-default-skin:jar:RELEASE in my pom.xml or
> site.xml so the site plugin must be initiating this.
> 
> Any ideas what might be wrong?

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


Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/21/06, Henry S. Isidro <hi...@exist.com> wrote:
> On Friday 21 April 2006 11:38 pm, Ryan Wynn wrote:
> > Do you know if I need to install the skin manually and if so how I can do
> > it?
> >
> > Thanks.
>
>
> Get it from here: https://svn.apache.org/repos/asf/maven/skins/trunk and then
> install it.

Thanks, Henry.  I installed it from 
https://svn.apache.org/repos/asf/maven/skins/trunk
using

E:\>mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven
-site-skin -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=SkinPlugin.jar

and my site.xml includes

<skin>
		<groupId>org.apache.maven.skins</groupId>
		<artifactId>maven-site-skin</artifactId>
		<version>1.0-SNAPSHOT</version>
    </skin>

and now the complaint is

[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven
-default-skin \
        -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE

I do not reference 
org.apache.maven.skins:maven-default-skin:jar:RELEASE in my pom.xml or
site.xml so the site plugin must be initiating this.

Any ideas what might be wrong?

Re: Support for Multi-project Web Sites

Posted by "Henry S. Isidro" <hi...@exist.com>.
On Friday 21 April 2006 11:38 pm, Ryan Wynn wrote:
> Do you know if I need to install the skin manually and if so how I can do
> it?
>
> Thanks.


Get it from here: https://svn.apache.org/repos/asf/maven/skins/trunk and then 
install it.

HTH,

Henry

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


Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/21/06, Alexandre Poitras <al...@gmail.com> wrote:
> Yeah I think you're right! Now that you mention it I think you have to
> use the lastest snapshot built which is way better anyway. The site
> plugin hasn't seen a new release in a long time. Just add the Maven
> snapshots repository to your pom and declares the use of the
> 2.0-SNAPSHOT site plugin.

That help got me further, but now it is complaining about the skins.  I added
<skin>
		<groupId>org.apache.maven.skins</groupId>
		<artifactId>maven-site-skin</artifactId>
		<version>1.0-SNAPSHOT</version>
	</skin>

to my site.xml
and now I get the following error

[INFO] The skin does not exist: Unable to download the artifact from any reposit
ory

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven
-site-skin \
        -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-site-skin:jar:1.0-SNAPSHOT

from the specified remote repositories:
  Maven Snapshots (http://snapshots.maven.codehaus.org/maven2/),
  central (http://deva3.cde.ace.cbp.dhs.gov/repository/),
  Maven Snapshots 2 (http://cvs.apache.org/maven-snapshot-repository/)

Do you know if I need to install the skin manually and if so how I can do it?

Thanks.

Re: Support for Multi-project Web Sites

Posted by Alexandre Poitras <al...@gmail.com>.
Yeah I think you're right! Now that you mention it I think you have to
use the lastest snapshot built which is way better anyway. The site
plugin hasn't seen a new release in a long time. Just add the Maven
snapshots repository to your pom and declares the use of the
2.0-SNAPSHOT site plugin.

On 4/21/06, Geoffrey De Smet <ge...@gmail.com> wrote:
> $modules and <skin> etc are for the next release of the site plugin I
> believe
>
> Aaron Freeman wrote:
> > I tried using ${modules} in the site.xml of my parent project, just
> > like you did, but it didn't seem to do anything for me either.
> >
> >
> > On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> >> On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> >>> On 4/20/06, Alexandre Poitras <al...@gmail.com> wrote:
> >>>> ${modules} should definitely work. What your site.xml file looks like?
> >>> The parent site.xml is pretty basic.  The reports are showing but no
> >>> links to the modules.
> >>>
> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
> >>> <project name="PCS">
> >>>        <bannerLeft>
> >>>                <name>PCS</name>
> >>>                <src>
> >>>                        images/pcs.png
> >>>                </src>
> >>>                <href>http://maven.apache.org/</href>
> >>>        </bannerLeft>
> >>>        <bannerRight>
> >>>                <src>
> >>>                        http://localhost/images/logo.png
> >>>                </src>
> >>>        </bannerRight>
> >>>        <body>
> >>>                <links>
> >>>                        <item name="Shale"
> >>>                                href="http://struts.apache.org/struts-shale/" />
> >>>                        <item name="Myfaces" href="http://myfaces.apache.org/" />
> >>>                </links>
> >>>                <menu name="PCS">
> >>>                        <item name="Home" href="index.html" />
> >>>                </menu>
> >>>
> >>>
> >>>                ${modules}
> >>>                ${reports}
> >>>
> >>>        </body>
> >>> </project>
> >>>
> >> the site plugin is 2.0-beta-4
> >>
>
> --
> With kind regards,
> Geoffrey De Smet
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 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


Re: Support for Multi-project Web Sites

Posted by Geoffrey De Smet <ge...@gmail.com>.
$modules and <skin> etc are for the next release of the site plugin I 
believe

Aaron Freeman wrote:
> I tried using ${modules} in the site.xml of my parent project, just
> like you did, but it didn't seem to do anything for me either.
> 
> 
> On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
>> On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
>>> On 4/20/06, Alexandre Poitras <al...@gmail.com> wrote:
>>>> ${modules} should definitely work. What your site.xml file looks like?
>>> The parent site.xml is pretty basic.  The reports are showing but no
>>> links to the modules.
>>>
>>> <?xml version="1.0" encoding="ISO-8859-1"?>
>>> <project name="PCS">
>>>        <bannerLeft>
>>>                <name>PCS</name>
>>>                <src>
>>>                        images/pcs.png
>>>                </src>
>>>                <href>http://maven.apache.org/</href>
>>>        </bannerLeft>
>>>        <bannerRight>
>>>                <src>
>>>                        http://localhost/images/logo.png
>>>                </src>
>>>        </bannerRight>
>>>        <body>
>>>                <links>
>>>                        <item name="Shale"
>>>                                href="http://struts.apache.org/struts-shale/" />
>>>                        <item name="Myfaces" href="http://myfaces.apache.org/" />
>>>                </links>
>>>                <menu name="PCS">
>>>                        <item name="Home" href="index.html" />
>>>                </menu>
>>>
>>>
>>>                ${modules}
>>>                ${reports}
>>>
>>>        </body>
>>> </project>
>>>
>> the site plugin is 2.0-beta-4
>>

-- 
With kind regards,
Geoffrey De Smet


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


Re: Support for Multi-project Web Sites

Posted by Aaron Freeman <aa...@gmail.com>.
I tried using ${modules} in the site.xml of my parent project, just
like you did, but it didn't seem to do anything for me either.


On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> > On 4/20/06, Alexandre Poitras <al...@gmail.com> wrote:
> > > ${modules} should definitely work. What your site.xml file looks like?
> >
> > The parent site.xml is pretty basic.  The reports are showing but no
> > links to the modules.
> >
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> > <project name="PCS">
> >        <bannerLeft>
> >                <name>PCS</name>
> >                <src>
> >                        images/pcs.png
> >                </src>
> >                <href>http://maven.apache.org/</href>
> >        </bannerLeft>
> >        <bannerRight>
> >                <src>
> >                        http://localhost/images/logo.png
> >                </src>
> >        </bannerRight>
> >        <body>
> >                <links>
> >                        <item name="Shale"
> >                                href="http://struts.apache.org/struts-shale/" />
> >                        <item name="Myfaces" href="http://myfaces.apache.org/" />
> >                </links>
> >                <menu name="PCS">
> >                        <item name="Home" href="index.html" />
> >                </menu>
> >
> >
> >                ${modules}
> >                ${reports}
> >
> >        </body>
> > </project>
> >
>
> the site plugin is 2.0-beta-4
>

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


Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> On 4/20/06, Alexandre Poitras <al...@gmail.com> wrote:
> > ${modules} should definitely work. What your site.xml file looks like?
>
> The parent site.xml is pretty basic.  The reports are showing but no
> links to the modules.
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <project name="PCS">
>        <bannerLeft>
>                <name>PCS</name>
>                <src>
>                        images/pcs.png
>                </src>
>                <href>http://maven.apache.org/</href>
>        </bannerLeft>
>        <bannerRight>
>                <src>
>                        http://localhost/images/logo.png
>                </src>
>        </bannerRight>
>        <body>
>                <links>
>                        <item name="Shale"
>                                href="http://struts.apache.org/struts-shale/" />
>                        <item name="Myfaces" href="http://myfaces.apache.org/" />
>                </links>
>                <menu name="PCS">
>                        <item name="Home" href="index.html" />
>                </menu>
>
>
>                ${modules}
>                ${reports}
>
>        </body>
> </project>
>

the site plugin is 2.0-beta-4

Re: Support for Multi-project Web Sites

Posted by Ryan Wynn <bi...@gmail.com>.
On 4/20/06, Alexandre Poitras <al...@gmail.com> wrote:
> ${modules} should definitely work. What your site.xml file looks like?

The parent site.xml is pretty basic.  The reports are showing but no
links to the modules.

<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="PCS">
	<bannerLeft>
		<name>PCS</name>
		<src>
			images/pcs.png
		</src>
		<href>http://maven.apache.org/</href>
	</bannerLeft>
	<bannerRight>
		<src>
			http://localhost/images/logo.png
		</src>
	</bannerRight>
	<body>
		<links>
			<item name="Shale"
				href="http://struts.apache.org/struts-shale/" />
			<item name="Myfaces" href="http://myfaces.apache.org/" />
		</links>
		<menu name="PCS">
			<item name="Home" href="index.html" />
		</menu>

		
		${modules}
		${reports}
		
	</body>
</project>

Re: Support for Multi-project Web Sites

Posted by Alexandre Poitras <al...@gmail.com>.
${modules} should definitely work. What your site.xml file looks like?

On 4/20/06, Ryan Wynn <bi...@gmail.com> wrote:
> I haven't been able to find maven2 documentation on how to create a
> parent site that automatically includes links to all the modules under
> it.  Has a solution for this been developed yet, and if so where can I
> find documentation on it?  Maven is invoking site:site on all the
> reactor projects but the parent site does not include the links.
>
> Using ${modules} in the site.xml for the parent but not sure if this
> is even currently supported.
>
> Any help would be appreciated.
>
> Thanks,
> Ryan
>

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