Hi all. I've written a plugin which allows you to do atomic multi-module
builds. It's beta at the moment, but should work for simple cases. Usage
is available on the home page. Bug reports enhancement requests welcome!
http://code.google.com/p/maven-deferred-deploy-plugin/
i can deploy an artifact into our repository, and have verified that it
deployed correct by checking the copy on disk, however when i attempt to
browse to the artifact i get the following error in the browser:
Error 404 Not Found
The following resource does not exist:
there are a couple of reasons why this is not a maven plugin.
1. we found it much easier to understand the dependency tree when it was
displayed in a GUI (ie being able open and close branches, see paths being
highlighted etc). if this were to be a plugin it would need to display
text
i am trying to bind assembly:assembly to the package phase in one of my
parent poms parent-1, the other parent is parent-2 which does not have
an assembly bound. the assembly plugin is the 2.0.x svn version.
this works as expected when i check out a single project and install it.
ie the assembly
.
child-assembly
pom.xml bind assembly:attached to package phase ( you need
to
get the assembly plugin from svn and build it your self )
On 5/5/06, Jake Pezaro [EMAIL PROTECTED] wrote:
thanks dan. my assembly config is in a parent pom, and when i try to
configure the binding
We have a number of projects which we build nightly using maven. I have
grouped these together using modules so that i can build deploy them
all at once with one command (mvn assembly:assembly deploy).
The problem is that the build fails because the assembly:assembly target
requires all
I want to add my assembly task to one of my parent poms, as follows:
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdcom.vcint.pom/groupId
artifactIdserver-app/artifactId
version0.0.1-SNAPSHOT/version
packagingpom/packaging
build
assembly, bind assembly:attached to the package
phase, then you run
maven deploy
-D
On 5/5/06, Jake Pezaro [EMAIL PROTECTED] wrote:
We have a number of projects which we build nightly using maven. I have
grouped these together using modules so that i can build deploy them
all at once
we do a nightly snapshot build deploy of all our apps and our
repository is growing rapidly. are there any tools or recommended
settings available to control the the size? we are using maven version
2.0.2
thanks
jake
__
This
to get the source into your repository then you need to attache the
source plugin to the package phase as below. this will then
automatically generate the sources and deploy them.
plugin
artifactIdmaven-source-plugin/artifactId
version2.0/version
executions
the project in question does not fail when run from the command line,
however when run from eclipse it produces the following error:
is there a way to get the eclipse pluging to show what the error is or
do run it in debug mode?
Compiling 918 source files to
i need to do some memory-intensive java compilation (918 files, 678 in
one directory alone, largest .java file is around 500K). setting the
-J-Xmx argument should fix it. the problems i encountered are:
- i must fork the process in order to do it as the maven compiler will
not accept this
i have written a new plugin. however, no matter what dependencies are
defined by the calling pom, my pluging has only 2 jars on it's
classpath. they are:
when running maven from the command line:
.../maven-2.0.2/core/boot/classworlds-1.1.jar
when running maven from eclipse:
i want to deploy a 3rd party jar (which is already in my local
repository) to the remote repository that we have set up on one of our
servers. what command should i use to do this?
__
This email has been scanned by the
14 matches
Mail list logo
