What I like in particular is that you change the element 'build' into set.
The name build gives the impression it is an action that is described, while
it is actually a structure of a project, upon which the generic actions are
based.
Gino.
> -Original Message-
> Hi,
>
> Based on the dis
Guys,
please upgrade Apache Jakarta Commons Codec from 1.0-dev to 1.1
Download from http://jakarta.apache.org/site/sourceindex.cgi
into http://www.ibiblio.org/maven/commons-codec/jars/
thanx
Martin
-
This mail sent through IMP: http://horde.org/i
On Thu, 2003-06-05 at 04:04, Rafal Krzewski wrote:
> Jason van Zyl wrote:
>
> > Document it and it will more than likely be followed.
>
> I wish it would be so simple. Humans are lazy and forgetful, even the
> best documenation won't change that. The most common case is that some
> a person wants
--- [EMAIL PROTECTED] wrote:
> Hi all,
>
> I know it's the wrong list to send this info to, but
> hopefully some people with
> a better link to the xdoclet guys read this and
> forward to a xdoclet committer..
> ..
We read this lost too.
> I had my problems with the maven xdoclet plugin
> (w
Hi all,
I know it's the wrong list to send this info to, but hopefully some people with
a better link to the xdoclet guys read this and forward to a xdoclet committer..
..
I had my problems with the maven xdoclet plugin (wanted to generate
output) because I missed to configure the "xdoclet+jb
Mark H. Wilkinson wrote:
Either that, or leave this file as plain text and convert it to dos line
endings during the build...
-Mark.
Yeah I like that idea the best. Thanks,
-Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
On Thu, 2003-06-05 at 08:33, [EMAIL PROTECTED] wrote:
> plynch 2003/06/05 00:33:24
>
> Modified:src/bin maven.bat
> Log:
> o did the ole' unix2dos maven.bat to convert the line endings of
> this file to dos type
You might need to do 'cvs admin -kb maven.bat' to make sure the line
Jason van Zyl wrote:
> Document it and it will more than likely be followed.
I wish it would be so simple. Humans are lazy and forgetful, even the
best documenation won't change that. The most common case is that some
a person wants to apply just a tiny little fix to a plugin.
I think that publi
plynch 2003/06/05 00:33:24
Modified:src/bin maven.bat
Log:
o did the ole' unix2dos maven.bat to convert the line endings of this file to dos
type
Revision ChangesPath
1.37 +160 -160 maven/src/bin/maven.bat
Index: maven.bat
=
I myself have bumped into this some days ago trying to integrate the webtest
plugin (hosted on SF) into my Maven. Something was not working as I'd
expected and I pulled out the Ant docos. Surprise-surprise, :)
Yours,
Florin
- Original Message -
From: "Vincent Massol" <[EMAIL PROTECTE
Ah right, I understand now. I have learnt something today! :-) (I hadn't
realized this).
Thanks
-Vincent
> -Original Message-
> From: Florin Vancea [mailto:[EMAIL PROTECTED]
> Sent: 05 June 2003 07:10
> To: Maven Developers List
> Subject: Re: cvs commit: maven/src/plugins-build/checkstyl
Fixed for Cactus and Checkstyle.
Thanks
-Vincent
> -Original Message-
> From: Florin Vancea [mailto:[EMAIL PROTECTED]
> Sent: 05 June 2003 07:24
> To: Maven Developers List
> Subject: Re: cvs commit: maven/src/plugins-build/checkstyle
plugin.jelly
>
> P.S.: I did a quick search for 'incl
vmassol 2003/06/04 22:38:00
Modified:src/plugins-build/checkstyle plugin.jelly
Log:
Correctly apply Thomas patch (Thanks to Florin): Fix fileset include/exclude so that
comma separated list are supported.
Revision ChangesPath
1.8 +3 -4 maven/src/plugins-build/
vmassol 2003/06/04 22:35:33
Modified:src/plugins-build/cactus plugin.jelly
Log:
Applied Florin's patch for Fileset include/exclude so that comma separated list are
supported.
Revision ChangesPath
1.18 +9 -12 maven/src/plugins-build/cactus/plugin.jelly
Index
P.S.: I did a quick search for 'include name="${' in the sources and I
suspect the same issue also appears in the following plugins:
cactus, ejb, jalopy, war,
eventually with different potential of getting transformed into a
significant bug. Usually these properties are left untouched by the
"end
Vincent, I think you missed what Thomas really meant, and catched another
bug (actually a typo).
The element may have in the name attribute _just_one_
pattern, therefore if the property contains several patterns, as the
property name suggests, then something will go wrong.
Thomas suggested to us
The JXR plugin kept dying on us with a "Too many
open files" problem that we tracked down to a
FileReader not being closed properly.
Attached is a patch that addresses this issue (we've
been using it for the past couple weeks now.).
Vince.
---
Attached is a patch for deploy plugin. It fixes the following problem:
When is invoked more than once and two types of artifacts are
deployed, all the artifacts are deployed to the directory of the first type.
The problem is caused by .
does not set for the second time. It is replaced by
--
On Wed, 2003-06-04 at 05:47, Aslak Hellesøy wrote:
> Sorry if this has been brought up before, but I have an idea about how
> to make the reactor smarter/quicker.
>
> I have a project with lots of subprojects that are built with reactor. I
> want to reduce the build time by making the reactor sm
On Wed, 2003-06-04 at 08:49, Vincent Massol wrote:
> Hi,
>
> What do you think about the following process for making changes to a
> plugin (and for accepting patches):
>
> 1/ Update xdocs/changes.xml (create it if it does not exist) and
> describe the change
> 2/ Update the goals.xml/properties.
Hi Peter,
Can you check if it's correct now? Looks ok to me.
Actually it seems to me the opposite happened. It previously had unix
line endings (that's what my UltraEdit said at least). Not sure though
:-)
-Vincent
> -Original Message-
> From: Peter Lynch [mailto:[EMAIL PROTECTED]
> Se
vmassol 2003/06/04 12:49:32
Modified:src/bin maven.bat
Log:
Trying to fix end of line chars... Has it worked?
Revision ChangesPath
1.36 +1 -1 maven/src/bin/maven.bat
Index: maven.bat
===
R
Hi Thomas,
- I have applied the patch for issue 1.
- I don't understand issue 2.
- For issues 3 and 4 you seem to be modifying the checkstyle framework
itself? If this is so your patch should be sent to the checkstyle dev
mailing list. There is no java source code in the checkstyle plugin.
Thank
vmassol 2003/06/04 12:24:58
Modified:src/plugins-build/checkstyle project.xml
Log:
Added Thomas as a contributor. Thanks Thomas!
Revision ChangesPath
1.14 +6 -1 maven/src/plugins-build/checkstyle/project.xml
Index: project.xml
vmassol 2003/06/04 12:23:03
Modified:src/plugins-build/checkstyle plugin.jelly
Log:
Fixed "exclude" bug. Thanks to Thomas Diesler.
Revision ChangesPath
1.7 +1 -1 maven/src/plugins-build/checkstyle/plugin.jelly
Index: plugin.jelly
Vincent,
Looks like you comitted with unix line endings with this file. Could you
fix that please? Thanks.
-Peter
[EMAIL PROTECTED] wrote:
vmassol 2003/06/04 01:47:36
Modified:src/bin maven.bat
Log:
Applied Matt Johnson's patch to let users use the JVM -Xmx settings in MAVEN_OPT
> -Original Message-
> From: Charles Chan [mailto:[EMAIL PROTECTED]
> Sent: 04 June 2003 19:33
> To: maven-dev
> Subject: MAVEN_OPTS bug
>
> Hi, can we put a similar fix into Linux shell script?
Sure. Please send me the patch and I'll apply it.
Thanks
-Vincent
> Thanks
> Charles
>
>
Hi, can we put a similar fix into Linux shell script?
Thanks
Charles
vmassol 2003/06/04 01:47:36
Modified:src/bin maven.bat
Log:
Applied Matt Johnson's patch to let users use the
JVM -Xmx settings in MAVEN_OPTS environment variable.
Revision ChangesPath
1.35 +160
vmassol 2003/06/04 10:26:52
Modified:src/plugins-build/examples/simple-java README.txt
project.xml
Added:
src/plugins-build/examples/simple-java/src/test/org/apache/maven/examples/simplejava
TestSimpleJava.java
Log:
Added a jun
vmassol 2003/06/04 10:23:21
maven/src/plugins-build/examples/simple-java/src/test/org/apache/maven/examples/simplejava
- New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PR
On Wed, 2003-06-04 at 02:45, [EMAIL PROTECTED] wrote:
>
> I completely agree that standards are so much better then custom made
> solutions. That is the reason why we are investigating the use of Maven
> in the first place. But we simply have got no choice but to use a
> completely custom repos
On Wed, 2003-06-04 at 02:34, [EMAIL PROTECTED] wrote:
> Jason,
>
> > Maybe you should think about what your company policy is. What is your
> > company policy on the use of software components? Do you use your own
> > standard or something like a J2EE or Avalon standard? I think in most
> > cases
32 matches
Mail list logo
