It should be being set relative to the project.xml being processed.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Paul Libbrecht [EMAIL PROTECTED] wrote on 08/11/2003 09:13:38 AM:
Hi
Why ?
I know it should be thus, it worked doing a symbolic link but the
program manipulating the parser should set the systemId and not only
give a stream to the parser!
Paul
[EMAIL PROTECTED] wrote:
It should be being set relative to the project.xml being processed.
--
dIon Gillard, Multitask
Seems it already is.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Alain Javier Guarnieri del Gesu [EMAIL PROTECTED] wrote on 08/11/2003
01:53:39 AM:
* [EMAIL PROTECTED] [EMAIL
Sorry, I did not mean I know it should be thus but I know it's
working this way but that it should not be thus.
Paul
Paul Libbrecht wrote:
Why ?
I know it should be thus, it worked doing a symbolic link but the
program manipulating the parser should set the systemId and not only
give a stream
Ok, I think I understand what you mean now. You want to have a
distributed workflow instead of a centralized one. So you want to move
from WKG to WKP (Well-Known Plugins).
What I don't like is that it means not all plugins will be equal, some
will be more equal than others ;-) It also means that
Hi Daniel,
It looks like it's a limitation of the Maven junit-report plugin. Could
you post a JIRA improvement report for the junit-report plugin. Although
I haven't tested it, I believe you'll also not see stack trace
information for pure junit tests when using Maven.
Thanks
-Vincent
Oops. Actually this may not be true. I had forgotten there was a
cactus.jsl file in the cactus plugin. I'll have a look and fix this.
Thanks
-Vincent
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: 08 November 2003 11:56
To: 'Maven Users List'
Cc: [EMAIL
Ok, I've had a better look. I was right. The cactus.jsl is an exact copy
of the junit-report's junit.jsl file which does not display stack trace.
So I'd say you should open a bug report against the junit-report plugin
and I'll make sure that I update Cactus's cactus.jsl file.
Thanks
-Vincent
Hi Scott
Scott Brickner [EMAIL PROTECTED] writes:
Maven is littering my project folders with maven.log files, none of
which say anything useful (just info on the running time). Is there
some officially supported way for me to make it put that log
somewhere else? Or to suppress it entirely
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 11:54 AM
To: 'Maven Users List'
Subject: RE: war plugin : [maven.caller.call.compile-java] is not defined
Ok, I think I understand what you mean now. You want to have a
Could someone point me to an example of how to setup a classpath from
using the dependencies so that it can be used with the ant:java tag?
TIA
-ScottTavares-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
never mind... I found it...
Scott Tavares wrote:
Could someone point me to an example of how to setup a classpath from
using the dependencies so that it can be used with the ant:java tag?
TIA
-ScottTavares-
-
To unsubscribe,
Hi,
I use Maven to generate an Ant file so people do not need
to install Maven to build a source distribution (those
crazy people :-). I recently added the 'maven.javadoc.links'
property to my project.properties. The issue is that when
I generate the Ant file there is no link child element of
Hi,
Is it possible to override configuration settings in the
current Checkstyle plugin like it was possible when
properties files were used? For example, I would like
to use the sun coding standard as the base for my
coding standard and I want to change some of the settings.
I notice that the
* Vikas Phonsa [EMAIL PROTECTED] [2003-11-07 21:19]:
Can I have the jar goal generate a jar that includes the source code file
also beside the .class files.
I've been asking about creating separate debug and release build
targets for some time now. A debug target would have a source jar.
This
* John Keyes [EMAIL PROTECTED] [2003-11-09 00:49]:
Hi,
Is it possible to override configuration settings in the
current Checkstyle plugin like it was possible when
properties files were used?
maven.checkstyle.properties=my-checkstyle.xml
For example, I would like to use the sun coding
Is it possible to override configuration settings in the
current Checkstyle plugin like it was possible when
properties files were used?
maven.checkstyle.properties=my-checkstyle.xml
Yes but I have to specify all of the rules again in that file. I
think it should be extensible.
For example, I
Yes but I have to specify all of the rules again in that file. I
think it should be extensible.
I don't see why. Its a configuration file. Create your own
configuration. It is just as easy to copy the file and edit it.
Of course you can. I just think its a step backwards in
comparison to the
Does this seem stupid to anyone else? I mean, the log files are there to
analyze maven when things go wrong, they aren't specific to the project
- so why should they end up in the project directory? ~/.maven would
make more sense, I'd think. And they shouldn't have *anything* unless
something does
Scott,
placing the log in ~/.maven makes sense, except when you run multiple
mavens simultaneously.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Scott Brickner [EMAIL PROTECTED] wrote on
Alain,
if you have an alternative checkstyle file for the sun_checks.xml, I'm
happy to replace the existing one.
Patches are always welcome.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Alain,
where did we get with this?
Last I remember, my suggest was to use the dist plugin, not the jar
plugin.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Alain Javier Guarnieri del Gesu
22 matches
Mail list logo