Just an observation from today when RELEASE didn't work for us.
I was at someone's desk who normally build's the parent pom we are
trying to reference as RELEASE. His last build of the pom or perhaps
every build to his local repository is done without mvn install
-DupdateReleaseInfo=true (so
I thought I these two keywords LATEST and RELEASE were supported
versions that could be used in a pom.xml.
Does anyone know more about them, an I mistaken?
Jeff,
From my experience, using RELEASE as a version identifier
works for any kinds of artifacts given the fact that you
should have install or deployed the artifact using the
parameter updateReleaseInfo to true.
Thanks. That's very helpful! I was about to complain it does not work -
but
[Vickey wrote:]
I wonder how to refer to the path of local repository with a
${} variable in the pom.xml?
--
Try settings.localRepository
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
-
To unsubscribe,
I'm running into the issue documented here.
http://jira.codehaus.org/browse/MANTRUN-68
Actually I'm hitting it from maven-plugin-tools-ant.
Can anyone tell me if they have worked around this (without patching ant
to take an invalid uri.)
It seems to be fixed in Embedded 2.1 but I don't see how.
I wanted to see if others have addressed this requirement before and
what approaches they have taken:
We have certain artifacts which need to be built for multiple platforms.
For example, we may have j2ee artifacts that get deployed to Websphere 6
and Websphere 6.1. We use profiles to setup the
I don't think I'm understanding the docs here regarding how to use
import scope:
http://maven.apache.org/guides/introduction/introduction-to-dependency-m
echanism.html#Importing_Dependencies
Here is what I have - must be incorrect I think...
parent
+ testapp
+ testimports (not a module)
Wayne Fay wrote:
The real use case for import scope IMO is where a company
does not want to use a single shared corporate parent pom,
but they do want to enforce versions on all projects. So you
manage versions in the imported pom (one place), force all
your projects to import it (can
Hi Simon,
I'm aware of the difference btw dependencies and dependencyManagement.
When I first heard about the feature proposal I thought it was to inline
dependencies into poms. My line of thinking was of course into the
dependencies section.
When I read that you put that scope only in the
Can anyone tell me the best way to get the project classpath from with
a plug-in including transitive dependencies?
I've tried mavenProject.getCompileClasspath() but it doesn't seem to
have the transitive deps
Some problem with mavenProject.getDependencies()
I think I need
fyi, I just hit this issue as well. Thank you Mark for hitting this
before me ;-P
The research you provided save me hours and helped me understand to
close the project for now,
and probably move the dependency to a different workspace until
resolved.
I also voted for it getting resolved.
Is there additional information on Wagon besides
http://maven.apache.org/wagon ?
I have been working with wagon for the last couple of days. The best
I've personally have found is to read the code:
http://svn.apache.org/viewvc/maven/wagon/trunk/
If you have specific questions, maybe myself
I was wondering .. is there a way to skip building the sub-modules in a project
which is a parent pom and also an aggregator?
I don't really want to split the pom into parent and aggregator, but I can if
that's the only way. We don't want to skip modules very often.
Thanks!
[Patrick Schneider wrote]
mvn -N clean:install
On 7/27/07, Timothy Reilly [EMAIL PROTECTED] wrote:
I was wondering .. is there a way to skip building the sub-modules in a
project which is a parent pom and also an aggregator?
I don't really want to split the pom into parent
I am trying to add an additional classpath element to the manifest created by
the war plugin.
Is it possible to do this? I see how to add a manifest entry
and I see how to specify the war classpath should be generated,
but how to get this:
Manifest-Version: 1.0
Class-Path:
the information about the company's projects etc,
I usually have to create a new pom that shows the behavior.
Thanks,
Deng
Timothy Reilly wrote:
I am wondering how I can get to the bottom of this
exception/build error. I am already running the -e option:
[INFO] [war:war]
... Etc..
Thank
[Harish wrote:]
so can you find any other solution.
Here is how we are managing our application server libraries and server
shared libraries on my current project.
We have internal corporate repositories (several - one per environment.
E.g. unit, dev, test, release, etc.)
We have an additional
I am wondering how I can get to the bottom of this exception/build error. I am
already running the -e option:
[INFO] [war:war]
[INFO] Exploding webapp...
[INFO] Assembling webapp cmsl-war in
C:\Work3\cmsl-app\cmsl-war\target\cmsl-war-1.0-SNAPSHOT
[INFO] Copy webapp webResources to
I am having a couple of issues.
1) I am getting a NPE from the Surefire plugin. I have no test cases atm
- so it threw the NPE. Seems like a bug though.
[INFO] [surefire:test]
[INFO]
[ERROR] FATAL ERROR
[INFO]
I wrote:
Pls, disregard on both counts...
I am having a couple of issues.
1) I am getting a NPE from the Surefire plugin. I have no
test cases atm
- so it threw the NPE. Seems like a bug though.
Now I deleted my placeholder testcase and everything still runs fine,
So I can't
Wrt
2. If yes, how to force eclipse to use profile before it attempts to
download Bar's version from local maven repository.
Are you using m2eclipse plugin? If so, perhaps this posting on the
m2eclipse mailing list helps?:
http://www.nabble.com/RE%3A-Profile-dependencies-p11092303s177.html
Posting these back on the user list:
From: Eduardo [wrote:]
Sent: Monday, June 04, 2007 10:01 AM
To: Timothy Reilly
Subject: Daytrader doesn't compile
Hello Timothy,
I have the exact same error when trying to install the
daytrader application... Did you come to any conclussions
MojoFailureException or MojoExecutionException
I am wondering what the difference is between these two exception types?
The javadocs are identical. I am guessing the types are markers, but this
doesn't appear to be documented - or perhaps it is and I have missed it?
TIA
Has anyone run into the this problem that Better Builds with Maven code
sample (Chapter 4) the Daytrader build will not compile?
Starting with :
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
Hi Tyler,
I use RAD 7, but our .project is part of our archetypes and we are using
the M2Eclipse plugin which creates a classpath container instead of
individual classpath entries. Aside from this I don't see any major
differences. I ran eclipse:rad and compared the output to the orginal
.project
Based on this information http://maven.apache.org/settings.html
http://maven.apache.org/settings.html http://maven.apache.org/settings.html
http://maven.apache.org/settings.html
I thought that variables and variable expansion would be available anywhere in
a POM _and_ settings files?
Is this
I am getting some strange behavior from deploy:deploy-file goal.
1) I am using the -DgenerateChecksum=true option, but this option is not
documented here:
http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
I am
27 matches
Mail list logo