On 1/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: > This was a point of discussion on the design doc as to whether this > should be supported. Currently, it is not. I haven't yet captured that > in a JIRA entry but I think some solution to it is needed - perhaps if > we were to map a local path to a site location so that it can be built > in a location that mimics its final destination?
I think it's an important feature to have for site generation. Deployment step is supposed to be the deployment of what generated locally. However here it becomes more.. I would really like to have that capability. > - Brett > > On 1/22/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > For Maven 1.x we had a multiproject property: > > maven.multiproject.aggregateDir which was we were using as: > > > > maven.multiproject.aggregateDir = subprojects/ > > > > However as I understood we not longer have it for m2. > > > > While we do not have this feature i cannot see deployed sites on the > > local machine because I can only specify the subprojects/ directory in > > site deploy url. I can only see the effect after I deploy the whole > > site (ofcourse deploying to the local machine is a solution). How can > > I handle this with m2 with a more automatic way? > > > > On 1/22/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > Thanks Brett! The build is ok with the trunk version of the plugins. > > > > > > On 1/22/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > This is a different error - it is fixed in SVN for the > > > > maven-project-info-reports-plugin. > > > > > > > > So, I recommend: > > > > * install maven 2.0.2 > > > > * check out /repos/asf/maven/plugins/trunk > > > > * cd maven-site-plugin; mvn install > > > > * cd maven-project-info-reports-plugin; mvn install > > > > > > > > Both of these have upcoming releases that I mentioned earlier so the > > > > site will be stable by then. > > > > > > > > HTH, > > > > Brett > > > > > > > > On 1/21/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > > > > > On 1/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > I don't experience the problem on JDK 1.5. What version are you > > > > > > using? > > > > > > > > > > I'm using the latest version of JDK 1.5. When I do a "mvn site" in > > > > > "trunks/apacheds", lots of generation happens and finally I get: > > > > > ... > > > > > [INFO] Trace > > > > > java.lang.NullPointerException > > > > > at > > > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82) > > > > > at > > > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) > > > > > at > > > > > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:386) > > > > > ... > > > > > > - Brett > > > > > > > > > > What can be the problem? Can you please svn up and be sure to try with > > > > > the latest content? > > > > > > > > > > Thanks. > > > > > > > > > > > On 1/21/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > One of our three subprojects ApacheDS's site is causing problems > > > > > > > while > > > > > > > building. The problem is same again: > > > > > > > > > > > > > > [INFO] Trace > > > > > > > java.lang.NullPointerException > > > > > > > at > > > > > > > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.getParentPrefix(DefaultDecorationModelInheritanceAssembler.java:340) > > > > > > > at > > > > > > > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolvePath(DefaultDecorationModelInheritanceAssembler.java:149) > > > > > > > > > > > > > > This is generated when I do a "mvn site" in > > > > > > > "directory/trunks/apacheds". I use the latest version of the site > > > > > > > plugin but there still is the problem. > > > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > > On 1/21/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > > The main site and mina site is build and deployed successfully > > > > > > > > at: > > > > > > > > > > > > > > > > http://directory.apache.org/newsite > > > > > > > > > > > > > > > > Mina site does not conform to m2 conventions well but it works > > > > > > > > for now. > > > > > > > > > > > > > > > > The main site needs content and structure update. As Alex > > > > > > > > requested, > > > > > > > > we'll have only three project categories: ApacheDS, Naming and > > > > > > > > MINA. > > > > > > > > Other subproject documents will probably go under ApacheDS or > > > > > > > > will be > > > > > > > > deleted if no longer necessary. > > > > > > > > > > > > > > > > For the project information part we can use maven generated > > > > > > > > style or > > > > > > > > custom manual style. In other words, for example, we can have a > > > > > > > > svn.xml to describe svn stuff (as we currently have) or we can > > > > > > > > make > > > > > > > > maven generate it for us. The former was already setup but needs > > > > > > > > custum content update. Now I've also made maven generate them > > > > > > > > for us. > > > > > > > > For example: > > > > > > > > > > > > > > > > http://directory.apache.org/newsite/svn.html > > > > > > > > vs. > > > > > > > > http://directory.apache.org/newsite/source-repository.html > > > > > > > > > > > > > > > > We need to choose one. The former is custom and may be more > > > > > > > > verbose > > > > > > > > but needs maintanance. The latter is auto generated but may not > > > > > > > > be > > > > > > > > very user friendly. > > > > > > > > > > > > > > > > On 1/21/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > > > Ok, thanks. It seems to work with the latest version of the > > > > > > > > > plugin. > > > > > > > > > > > > > > > > > > On 1/20/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > > > This was a bug in SVN at one point. I've tested this with > > > > > > > > > > the latest > > > > > > > > > > release (2.0-beta-4) of the site plugin, and it works, as > > > > > > > > > > does the > > > > > > > > > > current SVN version. > > > > > > > > > > > > > > > > > > > > - Brett > > > > > > > > > > > > > > > > > > > > On 1/20/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > The main site migration goes promising but other > > > > > > > > > > > projects' sites are > > > > > > > > > > > problematic. I have the same problem I mentioned in the > > > > > > > > > > > other thread > > > > > > > > > > > which is: > > > > > > > > > > > > > > > > > > > > > > ... > > > > > > > > > > > [INFO] Trace > > > > > > > > > > > java.lang.NullPointerException > > > > > > > > > > > at > > > > > > > > > > > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.getParentPrefix(DefaultDecorationModelInheritanceAssembler.java:340) > > > > > > > > > > > at > > > > > > > > > > > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolvePath(DefaultDecorationModelInheritanceAssembler.java:149) > > > > > > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > I get this while I try to mvn site for asn1 project. I > > > > > > > > > > > think I have > > > > > > > > > > > done required changes for m2 but it does not build.. > > > > > > > > > > > > > > > > > > > > > > On 1/20/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Hi again, > > > > > > > > > > > > > > > > > > > > > > > > The new site looks more like the previous now. I fixed > > > > > > > > > > > > some problems > > > > > > > > > > > > which are both because of me and because of some new m2 > > > > > > > > > > > > conventions. I > > > > > > > > > > > > still get the same error I mentioned below. > > > > > > > > > > > > > > > > > > > > > > > > On 1/20/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > Sorry for opening a new thread about the same subject > > > > > > > > > > > > > but I did not > > > > > > > > > > > > > want to confuse you with the old discussion. Now I'm > > > > > > > > > > > > > trying to migrate > > > > > > > > > > > > > old site subproject to m2. The build (mvn site) again > > > > > > > > > > > > > fails but some > > > > > > > > > > > > > doco are generated. The most obvious problem is that > > > > > > > > > > > > > index.html is not > > > > > > > > > > > > > being generated. I get the following error during > > > > > > > > > > > > > site generation: > > > > > > > > > > > > > > > > > > > > > > > > > > [ERROR] VM #displayTree: error : too few arguments to > > > > > > > > > > > > > macro. Wanted 2 got 0 > > > > > > > > > > > > > [ERROR] VM #menuItem: error : too few arguments to > > > > > > > > > > > > > macro. Wanted 1 got 0 > > > > > > > > > > > > > > > > > > > > > > > > > > However the generating completes *successfully*. And > > > > > > > > > > > > > the generated site is here: > > > > > > > > > > > > > > > > > > > > > > > > > > http://directory.apache.org/newsite/ > > > > > > > > > > > > > > > > > > > > > > > > > > Does not seem very good now :-D > > > > > > > > > > > > > > > > > > > > > > > > > > We'll fix it of course. > > > > > > > > > > > > > > > > > > > > > > > > > > Any help is appreciated. > > > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Ersin > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Ersin > > > > > > > > > > > > > > > > > > -- > > > Ersin > > > > > > > > > -- > > Ersin > > > -- Ersin
