me too!
2008/5/8 Keith Bonawitz <[EMAIL PROTECTED]>:
> Thanks, this is just what I wanted. I look forward to seeing it on
> central :-)
> Keith
>
> 2008/5/4 Sherali Karimov <[EMAIL PROTECTED]>:
> > Just a clarification:
> > Download - will download (and optionally deploy to maven repo) licenses
We have a similar structure, we release the super-pom and the poms of the
subsystems always only have a released version of the parent.
Nicole
On 24/04/2008, Eugene Batogov <[EMAIL PROTECTED]> wrote:
>
> Hello !
> I am trying to use maven-release-plugin.
>
> Our project is consist of 3 levels.
Hi,
I have read that when there are conflicting versions, maven chooses
the version highest in the dependency tree. If I remember right if
there are serveral version at the same level the choosen version is
randomly one of those 3 (I remember this form etter Bilds with Maven).
Nicole
On 13/03/
Hi,
What you are trying to do sounds like a very bad idea. It is better
to increase the snapshot version. The common practice is that the
version of a snapshop x.y.z-SNAPSHOT will be released to x.y.z. Your
approach seems to suggest that you will release a new different 2.1.0?
Hopefully maven
Hi,
Try deleting the release.properties file.
Nicole
On 06/03/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I've been working with the release plugin for the first time and
> encountering build failures that I've gradually been able to resolve to
> the point where I'm prompted for the d
> > BUT:
> > only
> > mvn eclipse:eclipse
> > now just wants to download the jar.
> >
> > mit freundlichen Grüßen/best regards
> >
> > Wolfgang Schrecker
> >
> >
> >
> > "Nicole L
Hi Wolfgang,
Make sure that in the pom that contains the dependencies has right
. It should be pom, if you don't mention packaging the default
is jar. When you depend on this artifact you need to mention type, I am not
sure what you put here? Maybe pom too? We have the same sort of thing, but
w
Hi,
I recommend reading chapter 7, Team Collaboration with Maven, from Better
Builds with Maven.
Nicole
On 07/02/2008, simon <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 2008-02-06 at 09:47 -0500, Edelson, Justin wrote:
> > > 1) During the development process within an iteration, how to make
> > > s
Hi Steven,
I had a sort of similar problem. Maven expects certain things from the unit
tests, that eclipse doesn't, the reason being that surefire uses reflection
to lance the unit tests. One thing is that all classes are required to have
public constructors with either no-arg or String name. The
Hi Benoit,
Yes I think so. Well I know you can release from a tag made with the
release prepare. The command is
mvn release:perform -DconnectionUrl=scm:svn:file://your-url-here/tag-name
Look at page 224 of better builds with maven for more details
Nicole
On 06/02/2008, Benoit Decherf <[EMAIL
Hi,
Does this (Have all sources for all modules in the parent src folder) work
with the release plugin? I would be very surprised if it did... Since the
release plugin checks out a tagged version of everything to a different
folder anything relative is lost.
Another option would be to have an a
Hi,
It's quite hard to understand your mail...
The site plugin generates html pages from stuff it finds in the
site/src/apt, site/src/fml, site/src/resources, etc. You then
reference things starting from there. For you this would mean your link to
href="/xxx-project/index.html" points
to src/sit
Murali
I think you need to also install the jars of the sub-modules in the local
repository. Then you can either depend directly on the sub-modules in
Project B. Or better yet make a new sub-project of Project A that makes the
zip, leaving Project A to be just an aggregate pom. This new sub proj
Please don't address the list as gentlemen! It isn't nice for the
gentlewomen who are on the list too :-)
Nicole
On 26/11/2007, Eugeny N Dzhurinsky <[EMAIL PROTECTED]> wrote:
>
> Hello, gentlemen, we are using Artifactory to hold the modules we're using
> in
> Maven, for some weird reason we can
Hi Christian,
If you want to depend on another artifact you must define the artifact in
the depencencies section in the pom of the project that needs the dependecy,
not its parent. You can have a dependency management section in a project's
parent pom where you declare the version number, so that
Hi Ross,
I think what you want to do is download all the stuff you need, then use the
maven deploy plugin goal, deploy-file to put it in your repository. Read
the details of the plugin, but you give it a groupId, artifactId and
version, and if there isn't a pom file, one will be created and deplo
of module A (0.0.1). I have both modules as part of the
> module-tag in the root pom.xml and a normal install works fine.
>
> What parameters are you using when calling release:prepare? How did you
> configure the plugin?
>
> - Original Message
> From: Nicole Lacoste <[
Hi,
Don't put ANY versions in child poms EXCEPT for the parent version. If
module B depends on module A, declare the version of module A and B in the
common parent pom dependency management section (your main project if I
understand right), with ${project.version}. There should only be one
*** i
Hi Maarten,
We had the same problem and here's how we fixed it. WARNING this is
probably not a best practice, more of a twisting mavens arm to get it to do
what we want.
0. Prerequisite is that all the artifacts have the same version, the
version of the highest parent.
1. We declare all the
7;s the usual way to filter files you want copied in maven?
>
> Thanks,
> Yaakov.
>
> On 10/28/07, Nicole Lacoste <[EMAIL PROTECTED]> wrote:
> > Hi Yaakov,
> >
> > Do I understand right that the ${project.build.directory} in in a file
> that
> > is no
leNotFoundException cites the
> literal string: ${project.build.directory} and not the absolute path.
>
> Yaakov.
>
> On 10/28/07, Nicole Lacoste <[EMAIL PROTECTED]> wrote:
> > Hi Yaakov,
> >
> > Not sure if this is your problem, but
> >
> >
Hi Yaakov,
Not sure if this is your problem, but
${project.build.directory} refers to the target directory.
${project.directory} refers to the directory that contains the src
directory. Also I am wondering why you have the context.xml file where you
do in src/resources, and not in src/main/resou
You might want to look into cutting a real release. You only have your
artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release
plugin to cut release in non snapshot version (1.0). The release prepare
goal creates the 1.0 version and tags the source code in your scm. You then
crea
You can add sources to the dependency. If you need
the classes jar too, then you should have the dependency twice in your
dependency list.
Nicole
On 10/22/07, Paul Gier <[EMAIL PROTECTED]> wrote:
>
> Hi Everyone,
> Is there a way to tell maven to download source jars by default? I didn't
> se
24 matches
Mail list logo
