Hello
Option a) is probably something we can solve with an extension mechanism in
maven3. If you have time to load an issue ?.
Btw some ci server handles this case.
--
Olivier
Le 17 oct. 2011 01:22, Michael L. Hartery michael.hart...@kinek.com a
écrit :
Hi all. We have a medium size maven
Hi,
a) Run the entire mvn build with just the clean and deploy, but
deploy ONLY if all projects build and pass the tests properly
b) Run the other installs, but when it comes to the deploy, not to
run the install again, just deploy what is already there.
Have a look at
Hi all. We have a medium size maven deployment. There are about 30 or
40 projects that the reactor finds in the initial scan. I run the build
in Hudson in 4 steps:
1) Mvn clean
2) mvn install -Dmaven.test.skip=true
This finds any bad code and stops the build before going to far, no
Hi Maven gurus,
Looks like mvn deploy is deploying artifact from the target directory
to remote maven repo. Is it possible to configure mvn deploy to
deploy artifact from the local maven repo. Also, is it possible to skip
all the lifecyle phases before deploy (validate, compile, test,
Hi,
See
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Also note that modern MRM have a page that features this exact upload.
Cheers.
2009/5/20 Jane Young jane.yo...@sun.com
Hi Maven gurus,
Looks like mvn deploy is deploying artifact from the target directory to
Thanks for the link.
I do not want to deploy individual artifacts. I want to deploy
artifacts from a project. Is it possible to do this with
deploy:deploy-file?
Baptiste MATHUS wrote:
Hi,
See
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Also note that
Well, I'm finally not sure I understand what you want to do.
Did you look at the provided link?
Some goals (bound to the standard lifecycle that you should be aware of:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics
)
* package will create
Hi,
Thanks for responding.
In our project, we first do mvn install to produce the artifact and
then run QA tests to make sure the artifacts are good before deploying
to the remote maven repository. When executing mvn deploy, it will go
through preceding lifecycle phases (compile, package,
You need to stage the deploy, i.e. deploy to an intermediate repository and
then move them from there.
I know that the pro version of Nexus has support built in for this, but
given that we have not purchased it I cannot attest to it's workability.
Alternatively there is a stage mojo on one of
mvn deploy -DaltDeploymentRepository=http://stage.repo.url/
mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \
-Dwagon.source=http://stage.repo.url \
-Dwagon.target=http://deploy.repo.url \
-Djava.io.tmpdir=target
2009/5/20 Stephen Connolly
sorry that should be
mvn deploy -DaltDeploymentRepository=stage::default::http://stage.repo.url/
http://stage.repo.url/
mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \
-Dwagon.source=http://stage.repo.url \
-Dwagon.target=http://deploy.repo.url \
Thanks, Stephen.
This may work for us.
Stephen Connolly wrote:
sorry that should be
mvn deploy -DaltDeploymentRepository=stage::default::http://stage.repo.url/
http://stage.repo.url/
mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \
12 matches
Mail list logo