My suggestion would be your second solution. Then each developer need only
define the property tools.jar in his/her build.properties file. Although,
you may want to consider using a version number in the property name (e.g.,
tools14.jar) just in case a developer also wants to point to version
This legend is only available in the CVS version of the maven-xdoc-plugin.
Arnaud.
-Message d'origine-
De : Michael Bolin [mailto:[EMAIL PROTECTED]
Envoyé : lundi 9 août 2004 08:50
À : [EMAIL PROTECTED]
Objet : Maven link legend
On the Maven home page, there is a nice legend
If I build Maven from CVS and use it, will the legend appear
automatically or do I have to add something to get it?
Thanks,
Michael
On Mon, 9 Aug 2004 08:58:34 +0200, Heritier Arnaud [EMAIL PROTECTED] wrote:
This legend is only available in the CVS version of the maven-xdoc-plugin.
Arnaud.
Yes, it will work if you build maven and maven-plugins from CVS.
If you want you can build only the maven-xdoc-plugin.
Arnaud
-Message d'origine-
De : Michael Bolin [mailto:[EMAIL PROTECTED]
Envoyé : lundi 9 août 2004 09:02
À : Maven Users List
Objet : Re: RE : Maven link legend
Maven defines tools.jar as a system property.
On Mon, 9 Aug 2004 07:54:39 +0100, Charles Daniels [EMAIL PROTECTED] wrote:
My suggestion would be your second solution. Then each developer need only
define the property tools.jar in his/her build.properties file. Although,
you may want to
It's posted [MAVEN-1420].
Thanks!
Am So, den 08.08.2004 schrieb Brett Porter um 14:33:
I'll try this out in a week when I have access to a samba share. If
you haven't already, can you post to JIRA?
Thanks,
Brett
On Thu, 05 Aug 2004 09:08:07 +0200, Christian Mouttet
[EMAIL PROTECTED]
Hi,
we have modularized our build by using Maven. However, because the build
runs into OutOfMemoryExceptions when we compile all modules within one Maven
Reactor call, we are using the reactor only to determine the build order and
call afterwards each module via the ant:exec call.
maven:reactor
I'm thinking about automating releasing tasks and building distributions.
I was about to check how maven release plugin works, but I saw that it
has just been deprecated.
What is a future of releasing?
Thanks,
Marcin
-
To
Hi,
To make releases you should use the scm:prepare-release and
scm:perform-release goals.
For distributions you can use the distribution plugin, if it suits your
needs.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-Original Message-
From:
Hello all,
I am trying to use the ftp ant task from maven. It dosent work! Running
the task straight from Ant works fine
Some have suggested a brute hack with a typedef and dependency on Ant 1.6.
Before trying this I would like to hear if anybody has a solution to the
problem or another
Hi,
I found the solution myself. Instead of calling 'cmd /c maven' I have to
call 'cmd /c call maven'. In this case the error code is corretly returned
and interpreted by Ant and the build aborts.
For completeness here the correct maven.xml section
maven:reactor
basedir=${basedir}
Hello,
please provide a property to set the cvs binary to be used: My PATH
environment variable contains nearly about 700 characters (more than 8
lines in the cmd window), so I'd prefer not to add a path element for
every helper application. I suggest to temporarily add the
path-to-cvs-binary
Hello,
is there a complete list of planned features for m2?
Kind regards
Peter Nabbefeld
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
Could you please raise an issue to JIRA
http://jira.codehaus.org/browse/MPSCM ?
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Peter Nabbefeld
Sent: Monday, August 09, 2004
Hi, when I run Multiproject:clean in my master project, it tries to find a jar file
that was not created yet.
I use an argument passed to Maven (mm_domain) to create the name of jar file.
Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find anything
about this error.
You typically need to do a multiproject:install or
multiproject:install-snapshot before using any other goals.
This places the dependent jars in the local repo.
On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro [EMAIL PROTECTED] wrote:
Hi, when I run Multiproject:clean in my master project, it
and what about the scenario when I do a multiproject clean the a
multiproject build which however failt mid-way.. a subsequent
multiproject clean failt, because it cannot resolve all dependencies..
is there a way out? it seems liuke one can only do a clean build after
successfully building the
AFAIK, the reactor (which multiproject uses), verifies projects before
calling goals on them.
This means, yes, you'll need all the dependent jars in the repo before
doing a multiproject:clean
On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint [EMAIL PROTECTED] wrote:
and what about the scenario
Dion Gillard wrote:
AFAIK, the reactor (which multiproject uses), verifies projects before
calling goals on them.
This means, yes, you'll need all the dependent jars in the repo before
doing a multiproject:clean
IMHO it shouldn't do it, at least for the the artifacts of the projects
included
Milos Kleint wrote on Monday, August 09, 2004 3:34 PM:
and what about the scenario when I do a multiproject clean the a
multiproject build which however failt mid-way.. a subsequent
multiproject clean failt, because it cannot resolve all
dependencies.. is there a way out? it seems liuke one
Hello
I have a plugin where I have declared a taglib by doing
define:taglib uri=myuri
define:tag name=yadayada
etc etc
I can do plugin:install fine
However, when I try and use it in my script, with
project xmlns:mine=myuri ...
goal. ...
mine:yadayada /
I get
Tag library requested
Hi,
It was the subject of a previous thread and I think there was a solution.
The issue is at http://jira.codehaus.org/browse/MAVEN-1270
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-Original Message-
From: Milos Kleint [mailto:[EMAIL PROTECTED]
My intentions running Multiproject:clean was, exactly, to clean target directory,
before building another project. So, how can I run Multiproject:install first? It
doesn't make sense. In fact, I run Multiproject:install after clean.
Well, what I'm going to do is, delete target directory using
Hello,
I want a specific plugin not to be updated (so -o does not work, as no
plugin would be updated) and provide a private version instead. Could
anybody help me, how to achieve this?
Kind regards
Peter Nabbefeld
-
To
You only need to make multiproject:install once, so you have dependent jars
in repo. Then you can run clean as many times as you want without running
multiproject:install (until you change your dependencies).
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
To resolve this problem I used the following solution:
The reactor has to be called using:
ignoreFailures=true (so it keeps going if there is a failure)
and then maven can be invoked using:
maven -o InfoBUS:clean (-o offline: this way maven ignores the central repo)
goal
It doesn't make sense Carlos, Running install, then clean to run install again.
I think clean could be used to delete the directories, only this. Why it looks for
the dependencies?
By the way, I'll delete target directory using ant.
Thank you a lot.
Regards,
Roberto de
What is the release of the Dashboard plugin? Currently v1.4 is in
development. I know additional aggregator have been added since 1.3.
Paul Spencer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
What is the release of the CruiseControl plugin? Currently v1.5 is in
development. I know report and dependent project support have been
added since 1.4.
Paul Spencer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
--- Nigel Magnay [EMAIL PROTECTED] wrote:
Hello
I have a plugin where I have declared a taglib by doing
define:taglib uri=myuri
define:tag name=yadayada
etc etc
I can do plugin:install fine
However, when I try and use it in my script, with
project xmlns:mine=myuri ...
goal.
Sounds like time to release it.
On Mon, 09 Aug 2004 11:10:29 -0400, Paul Spencer [EMAIL PROTECTED] wrote:
What is the release of the CruiseControl plugin? Currently v1.5 is in
development. I know report and dependent project support have been
added since 1.4.
Paul Spencer
Does
goal name=multiproject:clean
m:reactor basedir=${maven.multiproject.basedir}
banner=Gathering project list
includes=${maven.multiproject.includes}
excludes=${maven.multiproject.excludes}
On Mon, 9 Aug 2004 11:28:53 -0300, Roberto Castro [EMAIL PROTECTED] wrote:
My intentions running Multiproject:clean was, exactly, to clean target directory,
before building another project. So, how can I run Multiproject:install first? It
doesn't make sense. In fact, I run
On Mon, 9 Aug 2004 16:23:01 +0100 , Peter Bright
[EMAIL PROTECTED] wrote:
Does
goal name=multiproject:clean
m:reactor basedir=${maven.multiproject.basedir}
banner=Gathering project list
On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld
[EMAIL PROTECTED] wrote:
Hello,
I want a specific plugin not to be updated (so -o does not work, as no
plugin would be updated) and provide a private version instead. Could
anybody help me, how to achieve this?
Updated? By what?
--
Hi Paul,
I'll release it next week end for you.
Thanks
-Vincent
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]
Sent: lundi 9 août 2004 17:06
To: Maven Users List
Subject: Dashboard plugin release status?
What is the release of the Dashboard plugin? Currently
What does it do when it doesn't work?
For me, the -X switch showed that there was a CNF exception for an oro
FTP class. I had to put this in my project.xml:
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version20020829/version
/dependency
Hi Vincent,
If you don't want to make a release yet, you can deploy a SNAPSHOT to
http://cvs.apache.org/repository/maven/plugins/
Just use -Dmaven.repo.list=apachecvs
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-Original Message-
From: Vincent
Dion Gillard schrieb:
On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld
[EMAIL PROTECTED] wrote:
Hello,
I want a specific plugin not to be updated (so -o does not work, as no
plugin would be updated) and provide a private version instead. Could
anybody help me, how to achieve this?
Updated? By
How can I specify additional parameters with my remote repository url, For examlple,
if my remote repository is at
http://abc.com/viewcvs/RefLib/jars/configurator.jar?root=myroot
how would I pass the extra parameter (root=myroot) ?
Please help.
I'd rather we release early and often
On Mon, 9 Aug 2004 19:21:12 +0200, Carlos Sanchez
[EMAIL PROTECTED] wrote:
Hi Vincent,
If you don't want to make a release yet, you can deploy a SNAPSHOT to
http://cvs.apache.org/repository/maven/plugins/
Just use -Dmaven.repo.list=apachecvs
So you have a plugin, specified as a dependency, using SNAPSHOT as the
version and would like maven not to download it but use your version
instead?
Is that it?
On Mon, 09 Aug 2004 20:00:36 +0200, Peter Nabbefeld
[EMAIL PROTECTED] wrote:
Dion Gillard schrieb:
On Mon, 09 Aug 2004 16:36:15
or just plugin:install maven-plugins/xdoc from CVS.
On Mon, 9 Aug 2004 09:06:58 +0200, Heritier Arnaud [EMAIL PROTECTED] wrote:
Yes, it will work if you build maven and maven-plugins from CVS.
If you want you can build only the maven-xdoc-plugin.
Arnaud
-Message d'origine-
De
I strongly disagree.
I'd rather we fix all outstanding bugs (or at least scope out a
release) for any release of a plugin now. We too often let bugs slide
and have a bad reputation for it.
If people really need new features, build from CVS. Put a new version
on it when it is done and tested.
-
If you really want to use CVS (and I don't recommend it for this), you
need to URL rewrite a path name to the view CVS URL on the web server
I think.
- Brett
On Mon, 9 Aug 2004 16:42:40 -0400, Karan-Sahni (Contractor)
[EMAIL PROTECTED] wrote:
How can I specify additional parameters with my
Hi Charles Dion,
Thanks for your recommendations!
Here's what I did:
In my project's build.properties:
maven.doccheck.tools.jar = ${tools.jar}
maven.jar.override = on
maven.jar.javadoc = ${maven.doccheck.tools.jar}
By default, it uses the tools.jar maven uses. In case you are
On Mon, 9 Aug 2004 20:34:20 -0400, Brett Porter [EMAIL PROTECTED] wrote:
I strongly disagree.
So you'd rather not release early and often? That has nothing to do
with fixing bugs.
I'd rather we fix all outstanding bugs (or at least scope out a
release) for any release of a plugin now. We too
We weren't talking about bugs. We were talking about new features.
So you'd rather not release early and often? That has nothing to do
with fixing bugs.
But it has everything to do with not introducing new ones.
What if there are bugs fixed in the CVS version, critical ones even. I
don't
Sorry Malachi, I misunderstood your original question. I run javadocs
without checkstyle, but I'm using JDK1.4.
Jeff
On Mon, 09 Aug 2004, at 19:57:30 [GMT -0700] Malachi de AElfweald
wrote:
I had tried that; currently, I have the entire report section commented out.
Are you using JDK1.5
Dion Gillard schrieb:
So you have a plugin, specified as a dependency, using SNAPSHOT as the
version and would like maven not to download it but use your version
instead?
Is that it?
yes.
On Mon, 09 Aug 2004 20:00:36 +0200, Peter Nabbefeld
[EMAIL PROTECTED] wrote:
Dion Gillard schrieb:
On Mon, 09
50 matches
Mail list logo
