Dear All,
This might not be directly related to maven, but I believe maven project is
responsible for http://www.ibiblio.org/maven.
Please note that asm 3.0 (released November 2006) is not found in
http://www.ibiblio.org/maven/asm/jars/
If this is out of topic, then can someone point out
The maven project is not responsible for ibiblio, asm-3.0 is available
from the central m2 repo: http://repo1.maven.org/maven2/asm/asm/3.0/
where also m1 requests get forwarded to.
HTH,
-Lukas
Ahmed Ashour wrote:
Dear All,
This might not be directly related to maven, but I believe maven
As I mentioned I used @phase pre-site but it does not work.
It looks like I should explicitly attach my mojo to site lifecycle. I
guess the mojo belongs to default lifecycle. So question is HOW TO ATTACH
MOJO to *SITE LIFECYCLE*!
There is really nobody who tried to execute mojo in *pre-site*
Hi,
I use the m2 cobertura plugin.
It works fine.
For information I had to add the following in order to make it works:
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
Perhaps posting the actual code will help. When it comes to
classloading many loaders such as eclipse
are very liberal whereas the surefire loader is more strict to the
java spec.
Andy
On 27 Jun 2007, at 14:05, Erik Ruisma wrote:
Hello,
I've been trying out several options on the
I would look at the cargo plugin.
Andy
On 29 Jun 2007, at 18:56, crinu wrote:
I need some help...
when we change some some static files like jsp, properties.. etc..
is there
any way that i can just copy them to target server deployment
directly..
The reason why i need is ,, when i
On 7/1/07, Libor Kramoliš [EMAIL PROTECTED] wrote:
As I mentioned I used @phase pre-site but it does not work.
My suggestion was to try it in quotes - but was a bad thought anyway,
forget it.
It looks like I should explicitly attach my mojo to site lifecycle. I
guess the mojo belongs to
Frederick N. Brier wrote:
I followed the link you provided. Please correct me if I am wrong, but
the capability in Maven 1 IDEA plugin to turn off exclusion of the
target directory tree is missing.
http://maven.apache.org/plugins/maven-idea-plugin/idea-mojo.html#exclude
Seems to suggest
Is there a difinitive list of built-in m2 lifecycles? Does lifecycle ==
packaging type? Also is there a way to discover the phases that a given
lifecycle processes?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
In pom below the objective is to copy the specialres resources
directory from src to target.
If the resources section of build is commented out as shown nothing
gets copied although resources:resources runs twice. The log shows that
the execution named resource-copy ran first.
If the
On 7/1/07, Paul Copeland [EMAIL PROTECTED] wrote:
Is there a difinitive list of built-in m2 lifecycles? Does lifecycle ==
packaging type? Also is there a way to discover the phases that a given
lifecycle processes?
The default lifecycle is here:
Hm - following that link (which I had seen) there is a heading named
Packaging. So if you examine the pom there is a packaging element
(jar, war, pom, what are the others?) which is different from the
package phase. Apparently there is some kind of mapping between
packaging and lifecycle.
On 7/1/07, Paul Copeland [EMAIL PROTECTED] wrote:
Hm - following that link (which I had seen) there is a heading named
Packaging. So if you examine the pom there is a packaging element
(jar, war, pom, what are the others?) which is different from the
package phase. Apparently there is some kind
Stefan Prange wrote:
I'd like to test Maven2's ability to build eclipse plugin projects.
Therefore I built a little sample project as described on the home page of
the pde-maven-plugin (see here:
http://mojo.codehaus.org/pde-maven-plugin/examples/simple_plugin.html).
But unfortunately every
14 matches
Mail list logo
