If you have done `mvn install` previously then it will copy that zip to the
site. The only risk is that you may have a stale zip in your local
repository, but since the release plugin will invoke `deploy site-deploy`
the released site will always be correct.
On 20 August 2012 06:46, Thomas
http://maven.apache.org/guides/mini/guide-default-execution-ids.html
On Sun, Aug 19, 2012 at 4:17 PM, Levin, Ilya ilya.le...@hp.com wrote:
HI,
Sometimes I want to override default execution goals, for example:
war:war goal. So what I do is simply add to the maven-war-plugin this:
Hi,
You may replace execution listener with your listener and delegate events
to the previous listener. You may inherit your listener from something like
this: [1].
BTW, I've never seen that Maven sets some default execution listener, it
was always null in my tests. Can someone confirm if it is
Why are you excluding things that you need to be in the jar?
Perhaps you can explain your real problem rather than the symptoms.
You are right about the use of the jar.
Where else could it get the classes from? Think about the answer to that
one!
Ron
On 20/08/2012 12:38 AM, omritt wrote:
I
Hi,
I would like to launch a build using a clean local repository. I have
already tried the following solutions:
- Use the maven.repo.local property [1] from Maven 1. I haven't
found a similar reference in Maven 2 3 documentation, so I don't
know it's safe to use.
- Specify a localRepository
Hi, htfv
Thanks for your reply.
I got a mail like your idea privately and I implemented the delegation
listener using Proxy.
I released the plugin to my maven repository.
https://github.com/kompiro/notification-maven-plugin
Regards,
Hiroki
On Mon, Aug 20, 2012 at 8:35 PM, Aliaksei Lahachou
It appears that gmaven is always recompiling groovy files even when valid
and up to date class files already exist. Is this the expected behavior or
do I need to alter my configuration? To clarify, if I execute mvn test
Most likely the groovy compiler simply does not have the functionality
The project uses 2 profiles - 'release' and 'debug', with 'release' being
the default profile.
...
Does anybody know what the problem is here?
Find a way to do what you need without involving a profile (more
modules is the general approach rather than profiles) and things will
most likely work
Hello Folks,
I am using mvn 2.2.1, and ran into this (known) issue with sources jar
deploying twice when releasing (mvn release:perform).
I see there have been some posts on this, but one solution (Peter Lynch’s link
below) which mentions setting up the pom.xml so the additional source-jar
Hi folks,
We need to deploy the war file to multiple servers from hudson. I tried
google search and experimenting a little with not much of luck. Normally
we execute
mvn -Ptrunk clean package cargo:redeploy -DskipTests=true
Internally in code hierarchy, we have a qa deployer module that is
As a by-product of some infrastructure work some time ago I hacked
together an Ant/Maven script for parallel deployment to Tomcat 7. I
just had a discussion about the parallel deployment feature last week
with a friend of mine so I figured publishing our script might be of
use to somebody:
Good morning to everyone.
I am quite new to Maven and I have a problem that I am not able to solve.
I have my project structured in this way:
main_module
|--- module_1
|--- module_2
|--- module_3
and for each module I have created its pom.xml file.
I have the following questions:
1) I saw that
Hi Mauro,
Perhaps I can shed some light on these questions:
1) I saw that in the main_module there is not any folder for putting
the source code file, but from the manual I read that it is right
because it has been created as main project. Is it right?
In the case you have described main_module
Hi Mauro,
You are very close, just need one dependency defined in the POM for module_2 to
module_1. So assuming you created everything with the Maven project
archetypes, you'll have some examples of dependencies in your POMs for jUnit,
just duplicate one of those in module_2 and change the
Thank you very much guys.
I've created a dependency in the pom.xml of the module_2 that uses the
package defined in the module_1 and it works well.
I don't know if it is the most efficient solution, but for now it is ok... ;)
This Maven is a bit complex at the beginning, but it is very
attractive
I'm still hitting this bug with 1.7.1 release.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Shade-Plugin-1-7-causes-project-basedir-to-point-to-the-build-dir-instead-of-where-the-pom-xmls-tp5711836p5717693.html
Sent from the Maven - Users mailing list archive at
On Mon, Aug 20, 2012 at 11:16 PM, Francesco Mari
mari.france...@gmail.com wrote:
Hi,
I would like to launch a build using a clean local repository. I have
already tried the following solutions:
Why?
What are you hoping to achieve?
The easiest is to delete your ~/.m2/repository directory, but
I have a couple of quick questions about plugins and their dependencies. I am
on a private network so it is sometimes difficult to get a plugin and all it's
dependencies.
1. I am trying to use the maven-release-plugin and during the deploy phase it
is looking for the maven-javadoc-plugin
I would aggregate all of your local plugins into a local-only pom.xml which
would identify your local repository as your 'primary repository'
when using the local-only pom you would always identify 2.8.1 as the only
maven-javadoc-plugin stored in local repository
the other poms will reference
This is very confusing to me. I have a remote repository (Archiva) where we
store all the plugins we bring in. This includes version 2.3.2 of the release
plugin. When I use the 2.3.2 release plugin it asks for 2.5 of the javadoc
plugin which I do not have in my internal remote repository.
Sent
Just ignore Martin's mail. It doesn't make any sense to me either.
To answer your questions, I'll start with #2 first:
The best solution to this problem is to get a repo manager (archiva in
your case) that has Internet access. It will be VERY difficult for you
to work with Maven unless you do
21 matches
Mail list logo
