When I set the value of maven.final.name in a jar:jar preGoal, it has
the correct value there and in the jar:jar postGoal. But for some
reason it contains an earlier value in the jar:jar goal.
I've put echo tags in a few pre/post goals, as well as a couple in the
jar plugin's plugin.jelly file to
I'm using the jelly junit tags. I have a file called suite.jelly and a
test case which subclasses
org.apache.commons.jelly.tags.junit.JellyTestSuite.
Obviously the jelly test case don't know about maven as it's part of jelly.
The suite.jelly I'm using is below. The pipeline generates some code
Can you show us how you're running the tests.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Bert van Brakel <[EMAIL PROTECTED]> wrote on 08/12/2003 08:57:57 AM:
> thanks but unfortunately that doesn't work ( I'd already tried that ).
> From what I can
Run maven plugin:install on your modified plugin. It will remove the old one
and add your new one. Make sure to change to 1.4-SNAPSHOT and work off the
CVS copy if you are going to contribute changes.
There is some documentation on developing plugins on the web site and the
wiki.
Cheers,
Brett
>
thanks but unfortunately that doesn't work ( I'd already tried that ).
From what I can see the context created for the jelly script unit
tests is completely fresh with only the basedir ( and possibly other
system properties) being included.
At this stage I'll look at using a custom tag to proc
Hi,
When I upgraded to RC1, I kept ketting the following checkstyle error:
BUILD FAILED
File.. file:/J:/Documents and
Settings/Administrator/.maven/plugins/maven-checkstyle-plugin-2.0/
Element... ant:checkstyle
Line.. 127
Column 65
Unable to create a Checker: cannot initialize module
On Windows this is your \Documents and Settings\userid\.maven dir.
I just installed RC1 on a different machine, DIDN'T delete anything under
.maven, and I didn't have the problem (hrefs worked).
Don't know what the problem was on the other machine. I will try it again.
Thanks to everyone for t
classpathref="maven.dependency.classpath" on your javac task.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Bert van Brakel <[EMAIL PROTECTED]> wrote on 07/12/2003 08:43:18 PM:
> I'm using jelly junit to run some of my tests which include using the
> a
Hi,
I'm using Maven RC1 which comes with maven-jboss-plugin-1.3. I'm about
to make modifications to the plugin (and have the diff available to the
public). How do I override the built-in dependency that rc1 has to
version 1.3 of the jboss plugin? That is how to use my own SNAPSHOT
version of the
You seem to be on the right track. A shortcut to getting all of your
dependencies into the classpath so that Ant can find them is:
You're doing this in a more manual way, but I can't see any apparent
problems. Maybe try the way that I've suggested and see if it makes a
difference?
I know t
I have a jar:jar preGoal in my master maven.xml file that sets the
maven.final.name property as such:
I then run install-snapshot using multiproject, and echo the value of
maven.final.name immediately after setting it. It is correct. But when
I echo it from within the jar:jar goal, maven.final
I had been using reactor directly from my maven.xml, and decided to
try multiproject again a couple days ago, and it worked. I no longer
get the unknown multiproject goal message. I removed my maven.xml
thinking maybe something there had "fixed" my problem, but it still
worked fine.
I would docume
I'm using jelly junit to run some of my tests which include using the
ant:javac task to compile some generated code and I'm wondering how to
include all the project dependencies in javac's classpath. If anyone
could point me in the right direction it would be most appreciated, as I
haven't been
13 matches
Mail list logo
