I am still new to Maven after using it for 3 years with 20+ projects.
I recently installed the Nexus repository manager, community (free) version.
It is a great help and I would heartily recommend installing it if you
are moving to Maven.
It makes the whole process much more visible.
We use th
2010/1/24 Manuel Grau
> Is exactly what I'm doing. I only build the project I'm working on. The
> dependencies are pulled from my local repository. Run mvn clean package
> install from your jars.
FYI, since install includes all the phases up to install, and package is <
install, mvn package ins
I think I get what you are saying. So each project should have dependencies
on its jars, and I just choose to build each project if I want, otherwise
the dependencies will be resolved from the jars.
josh
On Sun, Jan 24, 2010 at 2:28 PM, Manuel Grau wrote:
> Is exactly what I'm doing. I only bui
Just configure Maven settings.xml file to pull from the organization repo
(the one populated by CI builds).
The deps in the projects you are working on will get pulled from the repo.
-Original Message-
From: Josh Stone [mailto:pacesysj...@gmail.com]
Sent: Sunday, January 24, 2010 4:18 PM
Is exactly what I'm doing. I only build the project I'm working on. The
dependencies are pulled from my local repository. Run mvn clean package
install from your jars. Only if you change any of them, you execute mvn
package install. I'm not sure if you understand me.
2010/1/24 Josh Stone
> Thank
Thanks for the response. Allow me to try and explain again:
Since our stack is so large and consists of many projects, developers don't
build the entire stack from source, they only build the specific projects
that they work on. Dependencies on other projects in our stack should be
resolved from j
Let me introduce what I'm doing in my company. We have some
maven-java-simple projects used in other projects. These projects are
considered common code. Then, our projects are all maven-j2ee-simple
projects. These projects have a root pom. Then, we have inside a folder
called servlets, with at lea
On Sun, Jan 24, 2010 at 2:55 PM, Josh Stone wrote:
> Since any given project could be built locally from source or from jars, do
> I need two poms for each project, one to serve as a "build" pom and one to
> reference jars?
No, you don't need two poms. What do you mean by building from source
o
I'm in the process of moving our company over to Maven, and am not sure of
the best way to organize our existing projects. Currently our application
stack consists of two dozen projects with various dependencies on each
other. For projects that a developer is actively working on, these should be
bu
you might be right, i'll look into it.
i've already used GMaven to use some groovy code in a pom file, and it is
quite easy.
thanks for the idea.
E.
On Sun, Jan 24, 2010 at 6:45 PM, Wayne Fay wrote:
> > is it possible to tell maven to add a classpathPrefix that will include
> the
> > artifact
> is it possible to tell maven to add a classpathPrefix that will include the
> artifactId Subdirectory?
>
> i'm using 'copy dependencies' plugin, and i want to keep each artifact in
> its own dir:
I really think you need to just write your own plugin to do all this
custom file location business r
is it possible to tell maven to add a classpathPrefix that will include the
artifactId Subdirectory?
i'm using 'copy dependencies' plugin, and i want to keep each artifact in
its own dir:
org.apache.maven.plugins
maven-dependency-plugin
12 matches
Mail list logo
