Yep, that is one of the many pages I had looked at also. I was also
considering the stage-deploy target as I think that actually does have a
property for URL, but was not sure what other side affects it would have
since it might be deemed a mis-use of that feature. I need to
understand it a little better and its original intent and how that maps
to our local process.
I also tried setting just a named property in settings.xml and
referencing that property in the <site><url> tag but since the URL tag
behavior is to append in a parent-child pom setup, it gets confused.
Disappointingly, when I look at the effective POM in Eclipse, it looks
exactly they way I want. When it actually runs though, it fails.
Robert Kuropkat
P.S. I am currently using the jackrabbit webdav wagon, but that's just
because it was the first one I got to work.
On 03/20/2014 04:42 PM, Mirko Friedenhagen wrote:
Hello Robert,
reading the information at
https://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html I
do not think there is an easy way to do this and probably never will
be.
1) AFAIK there is no (central) server available which hosts sites by default.
2) As stated on above page, there are a lot of different means to
deploy the site via wagon (ftp, http, ssh)
3) As a workaround you might think about using the site:stage-deploy
goal instead for your "local" builds.
Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Thu, Mar 20, 2014 at 8:29 PM, Robert Kuropkat
<[email protected]> wrote:
So is there an equivalent to altReleaseDeploymentRepository and
altSnapshotDeploymentRepository for the Site Deployment information also?
Since all three are in the Distribution Management directive, I was hoping I
could define this last one in the settings.xml also.
Robert Kuropkat
On 03/19/2014 05:15 PM, Mirko Friedenhagen wrote:
Hello Eric,
as outlined in
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
in your settings.xml you might define properties
altReleaseDeploymentRepository and altSnapshotDeploymentRepository in
a profile internal-repository which is activated by default while you
do not define any repository at all in your pom.
Now while developing you just invoke mvn deploy and everything should
go to your local Nexus.
When invoking mvn -P!internal-repository everything should go to central.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
