I understand that a SNAPSHOT dependency will be pulled from my local
repository, and once a day maven will make a check for a newer version in
remote repositories known to the build. Is this behavior the same if the
SNAPSHOT dependency in local was built and installed from a local build?
The magic is inside maven-metadata.xml that will be generated while uploading.
And who is responsible for generating the meta-data . . . the repository? Or
Maven itself?
-
To unsubscribe, e-mail:
After handcrafting an assembly to set my permissions just write, I then pull
that assembly artifact, a zip file, down into another build. This build uses
the dependency plugin to unpack the zip. But when it does so, it loses my
permissions . . . is this supposed to be happening? What can I
I can't seem to figure out how to configure the clean plugin to delete a
fileset in a directory defined with an absolute path. I have to have the path
relative to the build, it seems. Is there a way to configure the clean plugin
to delete stuff at arbitrary location that isn't relative to the
Nevermind. I'm not sure what was going on here. It works as advertised.
-Original Message-
From: chad.da...@emc.com [mailto:chad.da...@emc.com]
Sent: Thursday, July 05, 2012 2:07 PM
To: users@maven.apache.org
Subject: clean execution with absolute path
I can't seem to figure out
I'm beginning to sense that the structure of your build, e.g. the choices you
make in grouping certain builds into multi-module builds and how you structure
your directories in source control, have huge impacts on the ease of doing
software lifecycle things like branches and future releases.
Is it possible to have a merge of files that exist in both wars?
Is it possible to have a merge of files that exist in both wars?
I'm not quite sure how that would work. You'd have to write pretty
smart code to handle the various types of files and merges which are
possible.
How do people manage source files that are additive between overlay wars
What are the general reasons for having the pom deployed into the META-INF?
What kind of use cases leverage this info?
I've got multiple jdk's installed. I'm trying to force maven to use my java 7.
I invoke mvn with a JAVA_HOME value that points to my desired jdk, but then
the compile plugin complains about 1.7 not being a valid source setting . . .
seems like the JAVA_HOME doesn't control the execution of
Hi Martin.
I saw that actually. It seems kind of hacky to me . . . like, a workaround for
my local java installations, and I don't want to modify the build for my own
dev situation.
It seems like if I set the JAVA_HOME for mvn, it should use the java I'm
telling it to . . . do you have any
Run whereis java (where java in Windows) to find out how many java
executable you might have in PATH and which one is listed first. That's where
I'd start.
I'm beyond that phase already, but thanks. I'm on linux, and the mvn start up
script checks
JAVA_HOME to see which version of java
You should check the effective pom. I think that's a part of the maven help
plugin.
-Original Message-
From: Hartzman, Les X. -ND [mailto:les.x.hartzman@disney.com]
Sent: Friday, June 01, 2012 10:35 AM
To: users@maven.apache.org
Subject: Central repository not being hit
Hi,
I'm a relative newbie to Maven. When you say effective pom are you
referring to the project's pom or a global pom for Maven? If global, where
would it be located?
The effective pom is your pom plus all the stuff it inherits from parent poms
it declares, and from the Maven super pom. The
We're having problems with a build not being able to download snapshots from
nexus. We use timestamped snapshots, but I noticed that there are also
non-timestamped, i.e. they just say myArtifact-1.0.0-SNAPSHOT.jar, in there. I
belive these came from someone doing a redploy artifacts from an
I think it's more of a Nexus question as it depends on what's in the maven-
metadata.xml file. Maven never scraps the folders but uses the metadata.
What error do you get? Why not just remove the non-timestamped
Snapshots? Or, just wipe all the Snapshots and issue new build of them
Is it possible to change the name of the folder into which the dependency is
unpacked? Seems like there is no equivalent to the non-unpacked
outputFileNameMapping?
My question wasn't all that clear.
My problem is this. I have a zip dependency that I'm unpacking into my
assembly. I'd like to trim out the root folder of that zip's contents, so I
can just dump the contents of that root folder into my output directory. I'm
having trouble figuring anyway
So your problem is with the unzip stage where it is creating a top level
directory and putting the files in it instead of exporting just the files
into the
output directory?
Perhaps you want to share your current method of doing that?
Hey Ron. It's not that it's creating a top level
Our build has a dependency on the JRE. In order to build our final
distribution artifact, we need a JRE. To me, this means that the JRE
should be managed as a maven artifact in nexus. Otherwise,
I don't understand the use case. Please describe it in more detail.
My installer is
You are not alone in that. Especially since the most valuable single bit of
advice one can give a new Maven user is: if you don't do things Maven's
way, Maven will fight you and Maven will win.
People extol the virtues of convention over configuration, but where is the
compact definitive
Especially since the most valuable single
bit of advice one can give a new Maven user is: if you don't do
things Maven's way, Maven will fight you and Maven will win.
I disagree that it is the most valuable single bit of advice. It is
repeated far
too frequently, often in cases
Good read.
Thanks.
I think it says something that it has not been done yet. While everyone says
it would be great to have, clearly no one has felt strongly enough about it
(yet) to make it happen. It is more of a very nice to have than a hard and
fast
requirement.
I'm tackling the
Our build has a dependency on the JRE. In order to build our final
distribution artifact, we need a JRE. To me, this means that the JRE should be
managed as a maven artifact in nexus. Otherwise, I can't use the assembly
plugin to build my distribution. I can't really find much on this on
I'm wondering if I can preserve a timestamp on an artifact in my assembly so
that it stays equal to when it was originally built, i.e. the build time, or at
least the deploy to nexus time - very similar timestamps obviously.
My scenario and observations. I'm using an assembly to prepare a
You might also want to switch from Eclipse to Eclipse STS from the Spring
guys.
This gives you Eclipse and Maven in the IDE all from a single download.
We have used it for a few years now and it is much better than Eclipse on its
own.
Is that packaged with m2e as the maven plugin, or does
I'm using the attach-artifact to attach a binary installer that I build.
Everything works great, but I don't quite understand the sequencing
requirements. For instance, it appears to work okay if I run the
attach-artifact prior to the exec:exec mojo that actually creates the
installer. Is
Not good.
Dependency versions should be deterministic. For the same reason avoid
version ranges.
That's pretty definitive, and I think I agree on a gut level. Can you
articulate any specific issues? I'd appreciate it if you could.
Well, kinda - that only allows you to adjust extension and classifier.
I _know_, we're swimming up stream here a bit.
I'm pulling down the code for the buildhelper - I'd like to be able to control
final name or artifactId at least :-/
I would suggest that controlling the name of the
Are there issues with the re-use of the same repository id across the various
repository declarations? As identifiers, it seems like they should each be
unique. Is there anything wrong with the following . . .
repositories
repository
So, the id is only used to match the credential declarations ?
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, February 27, 2012 9:44 AM
To: Maven Users List
Subject: Re: repository id question
if they all use the same credentials,
Hi,
I'm trying to set up a WAR project which uses NetBeans Lookup to find
services in external JAR files. Right now, I define an interface in the WAR
and
the implementations in a couple of JAR projects. I tried adding a dependency
on the WAR to the JAR poms, but mvn clean package
So basically i have to use deploy plugin to deploy the stuffs at repository
and
over there i can define what components i want to publish or deployed.
Sometimes the definitions are kind of vague in the maven literature. A
repository is simply the thing that holds your maven artifacts.
P.S. I think screwing around with the Maven snapshot naming scheme is
asking for trouble. Putting it in the manifest seems safer to me.
Unfortunately, you didn't elaborate on *why* you want to do this, so we
can't really comment on any alternative solutions.
Oh, I can elaborate ;) This is
I'm trying to figure out a way to get my Hudson build number onto my snapshot
artifact names. I noticed that the timestamp in the snapshot unique version
number is followed by a build number. Is there way to inject my own value
here, the Hudson build number for instance.
I'd like to have a better understanding of classifiers and package types.
The packaging type is supposed to indicate the package type of the artifact.
Simple enough. But does this carry through to any extra artifacts that I might
attach to the pom? Or is this purely for the primary artifact.
I'm wondering what the difference would be between the following two ways of
handling copying of a certain type of maven dependency. The dependency I'm
talking about is something like, for instance, a self-extracting installer that
I want to bundle with my custom assembly. I've deployed this
I'm trying to figure out how to best handle a .run binary as a maven artifact.
My build produces a single binary executable, a .run file. Currently this is
done with a maven exec plugin firing off an script, all tied to the install
phase. The package type of the pom is pom. So, this, to my
2) How do I go about getting my .run binary installed into nexus by maven,
i.e. by the deploy phase? Note, I've already figured out how to get my build
to put the .run file into the target directory, so I really just need to
figure out
how to get maven to deploy it, right? Thanks!
Use
Chad, instead of
typerun/type
I think you use -
classifierrun/classifier
Hey, Wes! How are things? Thanks for the info.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands,
Are there supposed to be timestamp uniquely named snapshot artifacts in my
local repo? I'm investigating the uniqueVersion = false setting to solve a
disks space problem, but I read some threads here and there that expressed
disagreement on whether there should actually be an accumulation of
I'm using the maven-exec-plugin to run a process that produces a binary
executable, let's call it myBin.run I would like to treat this as my maven
artifact, i.e. have it deployed to my nexus repository during the deploy phase.
What's the best way to do this?
The deploy:deploy mojo seems like
When I build a jar file, the compile dependencies are not packaged into the
jar. So, this means that they are expected to be provided somewhere else in
the run time environment, doesn't it? Which means that it doesn't seem like
there's a difference between compile and provided . . . am I
43 matches
Mail list logo
