Ah! http://jira.codehaus.org/**browse/MSITE-600<http://jira.codehaus.org/browse/MSITE-600> http://maven.apache.org/**plugins/maven-site-plugin/faq.**html#Use_of_url<http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url> http://maven.apache.org/**plugins/maven-site-plugin/faq.** html#Why_do_my_absolute_links_**get_translated_into_relative_**links<http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_do_my_absolute_links_get_translated_into_relative_links>
All sound like potential causes of what I am seeing. That will be the first thing I check when I get back. One more question possibly in relation to http://jira.codehaus.org/** browse/MSITE-600 <http://jira.codehaus.org/browse/MSITE-600>. In a few of the cases I tried, I'd end up with site:stage attempting to place files in target/staging/../../mysite/morestuff (ie. in the base directory of my aggregator) or even farther up the directory tree.. How would you feel about having site:stage verify all the staging files actually went into the staging directory and erroring out otherwise? Having maven place files in non-target directories makes me really nervous (even if my configuration might be to blame). Thanks for all the help! Mike On Thu, Sep 8, 2011 at 12:29 PM, Lukas Theussl <ltheu...@apache.org> wrote: > > > Michael Haefele wrote: > >> Third time trying to send this... I keep getting spam blocked..... >> >> "Technical details of permanent failure: >> Google tried to deliver your message, but it was rejected by the recipient >> domain. We recommend contacting the other email provider for further >> information about the cause of this error. The error that the other server >> returned was: 552 552 spam score (5.3) exceeded threshold >> (HTML_MESSAGE,RCVD_IN_DNSWL_**LOW,SPF_NEUTRAL,URI_OBFU_WWW (state 18)." >> >> >> The long and the short of it is I need to come up with a set of test >> projects to verify what I am seeing. >> >> If I'm reading this right, there are a few expected behaviors.. >> 1. mvn site:site site:stage should work. >> > > It should work up to http://maven.apache.org/** > plugins/maven-site-plugin/faq.**html#What_is_the_difference_** > between_mvn_site_and_mvn_site:**site<http://maven.apache.org/plugins/maven-site-plugin/faq.html#What_is_the_difference_between_mvn_site_and_mvn_site:site> > > > 2. The<distributionManagement><**site><url> is important. >> > > Only in a multi-module build and/or if you want to stage/deploy your site. > > > * It can be in the form of file://mysite/ or scp://mysite/ >> > > it should be a valid URL (and to make sense it should be an absolute URL, > even though in practice a relative one will probably work too, as in the > example you have shown in your previous email). > > > * It will be inherited by child modules (as in hierarchy, not >> aggregator/directory children) and appended with that child artifactId. >> > > yes, unless you explicitly override it in the inheriting child. However, > note > http://jira.codehaus.org/**browse/MSITE-600<http://jira.codehaus.org/browse/MSITE-600>which > I still haven't managed to fix in a satisfactory manner. > > > ** This will not work if the module directory does not match the >> artifactId. >> 3. Does the<project><url> tag matter? >> > > See > http://maven.apache.org/**plugins/maven-site-plugin/faq.**html#Use_of_url<http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url> > http://maven.apache.org/**plugins/maven-site-plugin/faq.** > html#Why_do_my_absolute_links_**get_translated_into_relative_**links<http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_do_my_absolute_links_get_translated_into_relative_links> > > > > >> What I would like to do is add >> <site> >> <id>anId</id> >> <url>scp://mysite/</url> >> </site> >> to my corporate pom and have that be inherited down to the children, >> grandchildren, etc nodes.. >> >> So, for example, if I have a hierarchy >> corp->my-grandparent->my-**parent->my-module >> and an aggregator root module >> corp->my-aggregator which aggregates my-grandparent, my-parent and >> my-module >> >> my-aggregator/ >> my-aggregator/my-grandparent >> my-aggregator/my-parent >> my-aggregator/my-module >> >> If only corp has a url defined, >> I would expect the my-module url to be >> scp://mysite/my-grandparent/**my-parent/my-module/ ? >> > > yes > > > And the following structure for my-aggregator/staging ? >> target/staging/corp/my-**aggregator >> target/staging/corp/my-**grandparent >> target/staging/corp/my-**grandparent/my-parent >> target/staging/corp/my-**grandparent/my-parent/my-**grandparent >> > > yes > > > >> And all the links properly navigate this structure. >> > > hopefully ;) > > > Cheers, > -Lukas > > > > >> I've got a bit of vacation coming up, but after that I will try to come up >> with some simple test projects to confirm what I am seeing on our main >> project (or perhaps expose that I'm doing something non-maveny that i can >> fix). >> >> Thanks! >> Mike >> >> > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.org> > For additional commands, e-mail: users-h...@maven.apache.org > >
