Hello,
I'm having a bit of a problem here !
I have a project that while not very big, does span a dependency tree a few
level deep and has many leaves of final deployed packages. I use maven not
only to build and all but to generate zip files that contain everything
(doc, runtime environment,
AFAIK, the execution of plugin goals within a phase is not configurable, at
least in Maven 2.0.x.
In order to make dependency:unpack happen before assembly:attached, just
execute dependency:unpack in an earlier lifecycle phase.
HTH,
Justin
From: Éric
I need to clarify my question.
The security people at my company certainly want the finest-grained
control possible over artifacts, that is, an ask-first model where they
approve each individually. I don't question that we can force Maven into
this mindset, but whether we can do so without
I don't see how you can have both an ask-first approach and not some business
process to handle it. The recommended setup we like to see is to let developers
have access to the repos, but keep the official builds behind the Nexus
Procurement repo so that you are sure what is officially built.
The order should follow the pom, with children always coming before the parent
definitions. User bound executions always come after the default ones for any
given phase.
-Original Message-
From: Edelson, Justin [mailto:justin.edel...@mtvstaff.com]
Sent: Sunday, February 01, 2009 12:12
I have to agree with Brian: letting developers use the proxy repo, but
CI/Releases the procured repo (which pulls its content from same proxy
repo that devs uses, but bureaucratic rules are applied). This IS a
supported scenario.
But, as with many things in our lives, you can play Unnatural Acts
We envision a process where we periodically reevaluate our needs,
gathering all artifacts we'll use until the next assessment.
In summary, that is simply impractical; we need a different approach.
Saying that at work lately, I've felt like Cassandra, but I'll be glad
to admit if I'm wrong...
you can stage the process
online hours Server1 pulls any/all necessary poms/jars/wars/ears/properties
8am server1 run every AntiVirus on the planet against downloaded files
9am server1 becomes accessible locally
Now you can set your localRepository to server1 e.g.
settings
Thanks Justin, sounds reasonable... there are so many phases to choose from
I guess the expanding of the package could very well be in the pre-package
phase.
@Brian.. That`s just it, when I put the assembly bits in the parent POM it
is systematically executed before anything in the children`s
Does anybody know of a good place to put some free-form documentation
files in the maven project/pom.xml?
I know the default location appears to be src/site, but I overrode the
default source location when creating our pom.xml (to minimize changes)
to be src. Therefore, stuffing docs into the
Take a look at:
http://www.sonatype.com/book
and http://www.maven.apache.org/plugins/
-Original Message-
From: Éric Daigneault [mailto:dai...@gmail.com]
Sent: Sunday, February 01, 2009 8:35 PM
To: Maven Users List
Subject: Re: POM element orders
Thanks Justin, sounds reasonable...
well, here's my settings.xml- couldn't send it earlier.
I'm just using the standard repositories which are configured in nexus.
Original-Nachricht
Datum: Thu, 29 Jan 2009 15:16:04 -0500
Von: Brian E. Fox bri...@reply.infinity.nu
An: Maven Users List users@maven.apache.org
the one as sourceforge is for maven 1, the one at codehaus is for maven 2
-D
On Sun, Feb 1, 2009 at 10:48 PM, Sahoo sa...@sun.com wrote:
I see two findbugs plugins:
maven-findbugs-plugin [1] and findbugs-maven-plugin [2]. Which one is
recommended? Looking at the activity, I see [1] is not
I see two findbugs plugins:
maven-findbugs-plugin [1] and findbugs-maven-plugin [2]. Which one is
recommended? Looking at the activity, I see [1] is not updated for a
long time, so does it mean [2] is the one to use?
Thanks,
Sahoo
[1]
14 matches
Mail list logo
