That looks like my first experience with the properties not being
inherited. Check if you have a sub project that rely on the
maven.repo.remote property being inherited from the parent
project.properties . In wich cases, ibilio repository will be used
instead of your repository, jars originnally
=.maven/repository
-Original Message-
From: Jean-Marc Lavoie [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 11:31 AM
To: Maven Users List
Subject: RE: Problems downloading dependencies in 1.0.1
That looks like my first experience with the properties not being
inherited. Check
I have jus install maven 1.0.1, Thanks a lot to the team.
I discovered that something seam to be working differently with
inheritance. I got some subproject that extends from a project file in
the parent directory. The parent directory contains a project.xml file
which is used to generate the
I'm not 100% certain on that, but maybe it's Eclipse who generate those
classes. I started getting thoses when we switch to Eclipse 3.0.1. Probably the
generated .class is present and maven won't compile it again. Javac do not use
the same taget folder, so it won't see the .class file and try
When running the multiproject, theere seem to be only one JVM, so the
current directory is the root folder, and it does not change. If you try
to find log4J in the current directory it won't find it because youre
searching one level higher.
You cans place a copy of the ifle in the root project
I use maven-1.0-rc1 and have tested the maven-jar-plugin with
version 1.3 and 1.4.
1.3, I had to patch my version to make it work
1.4, They add the feature (same code I added to my 1.3 version), but
accoriding to the jelly script, you must add the property
jar.manifest.classpath in your
.
-Original Message-
From: Jean-Marc Lavoie [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 18:25
To: Maven Users List
Subject: RE: Download of SNAPSHOT-Plugins
This make sense as you can be working on a branch to release
a maintenance version.
Let say your team released gizmosoft
Try using:
call maven clean
-Original Message-
From: Oliver Nölle [mailto:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 8:08 AM
To: Maven Users List
Subject: maven-call exits windows batch file: feature or bug?
When I write the followin lines in a batch file:
cd
I was curious, there is nice stuff in there :)
ear an ejb jelly script use the artifact:deploy ... goal to deploy, this goal call
some java code.
The jar plugin act differently and uses some jelly scripts to do the job, in a unix
maner.
There are some isues in Jira that may be caused by that
elsewhere. You will have to modify the MANIFEST.MF files of your
modules (ejb, war, etc.) to load classes from the specific jars. Not
sure, but am willing to bet a nickle that Maven can do the manifest
stuff for you. (NOTE: I have no specific experience using the ear
plugin, just
This make sense as you can be working on a branch to release a maintenance version.
Let say your team released gizmosoft 1.0, and you work on new and improved version 1.1
so you have 1.1-rc1-SNAPSHOT (or whatever you like: b1, b2 instead of rc1). Then you
must apply a fix to 1.0, you branch to
is there some way to override this location?
Setting the maven.repo.local properties does the job
It is briefly documented in the jar plugin.
http://maven.apache.org/reference/plugins/jar/properties.html
You may also consider using jar:install to deploy your myjar jar locally to this
location
12 matches
Mail list logo