That's what it was...anybody know a better way to get the parent build dir
than

${project.build.directory}/../../target/

-Dave

On Fri, Apr 10, 2009 at 12:47 PM, David Hoffer <[email protected]> wrote:

> Perhaps my macro is wrong.
>
> How can I get parent's .${project.build.directory} in child?
>
> -Dave
>
>
> On Fri, Apr 10, 2009 at 12:28 PM, David Hoffer <[email protected]> wrote:
>
>> I think I forgot something, mvn site-deploy should deploy site to URL
>> specified in site section right?
>>
>> The parent project does deploy here correctly.  However the child modules
>> do not.  So I figured each child pom must need its own site configuration to
>> append its module name to the URL, like:
>>
>> <site>
>>             <id>website</id>
>>             <url>${website-root}/${project.artifactId}</url>
>> </site>
>>
>> However this still doesn't work, the children keep putting their output in
>> their own target/website folder.
>>
>> How can I enable the children to use the children's site URL?
>>
>> -Dave
>>
>>
>>
>>
>> On Fri, Apr 10, 2009 at 11:11 AM, David Hoffer <[email protected]>wrote:
>>
>>> That doesn't really help it just overrides
>>> <url>file://${basedir}/target/website</url>
>>>
>>> It still puts the content at %stagingDirectory%localhost/[SVN check out
>>> folder]/target/website/[website content here]
>>>
>>> I need a fixed location relative to %stagingDirectory%.  I don't want
>>> [SVN check out folder] to be part of the destination because it isn't
>>> constent.
>>>
>>> -Dave
>>>
>>>
>>> On Fri, Apr 10, 2009 at 10:56 AM, Stevo Slavić <[email protected]>wrote:
>>>
>>>> Use "mvn %some_other_goal% site:stage
>>>> -DstagingDirectory=%desired_site_dir%"
>>>>
>>>> Regards,
>>>> Stevo.
>>>>
>>>> On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer <[email protected]>
>>>> wrote:
>>>>
>>>> > Can someone help with a simple site plugin question?
>>>> >
>>>> > I am just trying to build a site of a multi-module project and want to
>>>> > publish it to my local hard drive.  Here is my pom.
>>>> >
>>>> > <plugins>
>>>> > <plugin>
>>>> >                <groupId>org.apache.maven.plugins</groupId>
>>>> >                <artifactId>maven-site-plugin</artifactId>
>>>> >                <version>2.0</version>
>>>> > </plugin>
>>>> > </plugins>
>>>> > <distributionManagement>
>>>> >       ...
>>>> >        <site>
>>>> >            <id>website</id>
>>>> >            <url>file://${basedir}/target/website</url>
>>>> >        </site>
>>>> >    </distributionManagement>
>>>> >
>>>> > If I run mvn site:deploy it creates only part of the site at
>>>> > ${basedir}/target/website, the root content is there and just one
>>>> project
>>>> > module, it's like it just quit!
>>>> >
>>>> > If I run mvn site:stage it creates a valid site with all links working
>>>> but
>>>> > at a project specific staging location.
>>>> >
>>>> > If I run mvn site:stage-deploy it creates a valid site but all links
>>>> are
>>>> > back up to the original module target locations.
>>>> >
>>>> > None of these options create a valid web site under the specified URL
>>>> > location.  How can I do this?
>>>> >
>>>>
>>>
>>>
>>
>

Reply via email to