That's great!. I applied the macrodef usage in my situation and it worked
very well. Finally we get rid of the code that mojo plugin doesn't
work very well with.
Thanks Pete.
--
View this message in context:
http://www.nabble.com/-m2--problem-w--antcall-in-ANT-based-mojo-t1307160.html#a5011671
Thanks Pete, that sounds very promising. Could you also post a piece of
sample code? Thanks a lot.
--
View this message in context:
http://www.nabble.com/-m2--problem-w--antcall-in-ANT-based-mojo-t1307160.html#a4956130
Sent from the Maven - Users forum at Nabble.com.
---
The only work-around to this issue is to add a line of ant script in the
target before you invoke the task, like this
so that there is always a build.xml available in the directory by the time
is executed. But you will always need to remember the
"mymojo.build.xml" is the real one for you
Hi guys, this might be a stupid question, but...
Can I simply call an existing ANT's build.xml file explicitly from Maven2
POM without wrinting any mojo plugin?
Probably like this:
/path/build.xml
I just try to confirm my conclusion that the only way to make use of ant
targets in an existing b
Hi Mark,
I have read through all conversations within this thread and it still looks
like we still have to go to each individual project to modify the version
number when parent pom updates its version.
I have posted the exact same question in a separate thread
http://www.nabble.com/Inheriting
Is there a way that the maven2 build can skip the test phase even if the
src/test/java/* is in the folder structure?
Thanks.
--
View this message in context:
http://www.nabble.com/Skipping-Test-Phase.-t1741757.html#a4733181
Sent from the Maven - Users forum at Nabble.com.
-
We have a few 3rd-party jar files that are not in central repository, e.g.
ibiblio.org. So we had to manually install them to our local repository
using the following command.
mvn install:install-file -Dfile= -DgroupId= \
-DartifactId= -Dversion= -Dpackaging=
However, this command only insta
Now, I have 20 or so POM's that are all taking a top level POM as the parent
shown below:
com.mycompay.apps
BaseApp
9.5-SNAPSHOT
../BaseApp
Now the question is - if we later on change the version of the BaseApp, we
will have to modify the section in ea
Hi Tatiana, I had the exactly the same error as you got. Here is what I found
when running mvn with -X option (debug mode). In fact, maven still looking
for my webapp directory in src/main/webapp even though I had specified
different warSourceDirectory in the plugin configuration.
See if you see
Pete, this is still a problem as of today. I am having exactly the same
situation as you did. Haven't found any solution yet.
Folks, please share some tips on this if you know any.
--
View this message in context:
http://www.nabble.com/-m2-+problem+w-+antcall+in+ANT-based+mojo-t1307160.html#a4
We had some Jelly script similar to the following in our Maven1 projects. Now
we need to migrate everything into Maven2. It was suggested that we should
write some mojo/ant plugin for the equivalent constructs. Does anyone know
how we replace the jelly's "forEach" construct in maven2??? -- Many Th
Very nice, Edwin.
It works in the way I wanted. This is the answer I've been looking for.
Thanks very much.
--
View this message in context:
http://www.nabble.com/attach+mojo+plugin+to+the+build+lifecycle-t1682566.html#a4627843
Sent from the Maven - Users forum at Nabble.com.
---
Hi, I had a test mojo plugin which I tried to attach it to the compile phase
of the lifecycle. I did all these following the guide at this link:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
So, I was able to run the command "mvn compile" - I can see the sample
hello:
Hi folks, we have some jelly scripts in maven1's maven.xml. Now we are moving
to maven2. The question is how we are going replicate this customized
behavior in maven2 by knowing that m2 will not use jelly any more?
Please advise. Thanks in advance.
Signing jar for J
14 matches
Mail list logo
