hello all,
i want to mock a final class, for that i need to use jdave
to do so i need to
launch your tests with the following vm parameter:
-javaagent:/path/to/workspace/jdave-unfinalizer/target/jdave-unfinalizer-jar-name.jar
i did a search and the maven-test-plugin can do this ( i dont under
On 28 October 2010 23:20, Martin Gainty wrote:
>
> Folks
>
> originally i was using 2.5 version of maven-surefire-plugin as seen here
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.5
>
> this caused massive grief by DefaultPlexusContainer lookup which
> incorrectly parsed the roleHint
> s
Folks
originally i was using 2.5 version of maven-surefire-plugin as seen here
org.apache.maven.plugins
maven-surefire-plugin
2.5
this caused massive grief by DefaultPlexusContainer lookup which incorrectly
parsed the roleHint
so i backed all my dependencies of maven-surefire-plugin down to v
All I can suggest is to look at the source of that maven-hudson-project. I've
written a number of Maven plugins, but I believe that's the case where I used
AbstractMojoTestCase the most.
It's been a while, but I seem to remember figuring out AbstractMojoTestCase by
looking at other plugins whic
Thank you so very much for the reply Justin.
I'll go ahead and provide an implementation stub in the project tab to a class
that extends "MavenProjectStub"; following your example for Hudson. This setup
is just for the AbstractMojoTestCase, right? Presumably, normal poms don't
need this stub
hello all,
i want to mock a final class, for that i need to use jdave
to do so i need to
launch your tests with the following vm parameter:
-javaagent:/path/to/workspace/jdave-unfinalizer/target/jdave-unfinalizer-jar-name.jar
i did a search and the maven-test-plugin can do this ( i dont under
On Oct 28, 2010, at 5:04 PM, Olivier Gaudin wrote:
>
> The Sonar Team is pleased to announce the release of Sonar 2.2. This version
> ships with several new features :
^^
2.3 release :-)
> it is now possible to activate several times the Checkstyle rule "Illegal
> Regular Expression" with diff
I don't think 2.2 is out yet, however he can try snapshots, as described in
the issue.
2010/10/28 John Singleton
> It appears this was fixed in version 2.2 of m-w-p, try updating.
>
> http://jira.codehaus.org/browse/MWAR-235
>
> Cheers,
> John
>
> 2010/10/28 Marcin Trościańczyk
>
> > Hi,
> >
>
Hi Jörg,
> Did you see this:
> http://maven.apache.org/plugins/maven-shade-plugin/shade-
> mojo.html#keepDependenciesWithProvidedScope
I did, but it doesn't do what I need; my understanding is that it
changes the scope of the compile-scoped deps to :provided in the
shaded jar's pom.
Antonio, Way
It appears this was fixed in version 2.2 of m-w-p, try updating.
http://jira.codehaus.org/browse/MWAR-235
Cheers,
John
2010/10/28 Marcin Trościańczyk
> Hi,
>
> I have a problem with maven-war-plugin version 2.1. Below, I paste build
> section fragment from my pom.xml:
>
>
>
>
>
IIRC, you need to declare the project field and provide an implementation class.
See, for example,
http://github.com/justinedelson/maven-hudson-plugin/blob/master/src/test/resources/unit/pom-with-local-ci.xml
That code worked at some point...
HTH,
Justin
On Oct 28, 2010, at 11:19 AM, Andrew W
Yup, it's in ASF svn, and if the project isn't willing to own it, they
should attic it.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On 28/10/2010 9:35 AM, Martijn Dashorst wrote:
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
wrote:
It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.
maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plu
2010/10/28 Marcin Trościańczyk :
> Unfotunetly, generated artifact (war) contains two web.xml. When I use
> maven-war-plugin version 2.0.1 all works fine (generated war archive
> contains one web.xml). How can I solve this problem.
This is strange, do you see two WEB-INF/web.xml entries in the war
I'm not sure if this is the right forum for this, but I thought I would try
here first.
I have a plugin that I am trying to develop that wants to resolve a set of
groupId/artifactId pairs to resolved artifacts in the MavenProject it is
executing from. I have annotated the dependent field in t
I agree, there are many plugins that Maven developers just don't look after and
they should be ejected and taken out of the org.maven.plugins name space.
Anything there people assume are maintained which simply is not the case.
On Oct 28, 2010, at 10:58 AM, Antonio Petrelli wrote:
> 2010/10/28
The Sonar Team is pleased to announce the release of Sonar 2.2. This version
ships with several new features :
it is now possible to activate several times the Checkstyle rule "Illegal
Regular Expression" with different parameters and priority or the PMD rule
"XPath" with different XPath expressi
2010/10/28 Wayne Fay :
So how does one get ownership of the plugin? I've contributed 2
>
> This is open source so no one is stopping you from creating a fork.
Sorry to jump in but, in the Apache Committers' FAQ I read:
http://www.apache.org/dev/committers.html#committer-responsibilities
App
Hi,
I have a problem with maven-war-plugin version 2.1. Below, I paste build
section fragment from my pom.xml:
org.apache.maven.plugins
maven-compiler-plugin
1.6
1.6
org.apache.maven.plugins
ma
> m-e-p works better than M2ECLIPSE in many cases. Further, you have no
> proof here that I can see that the m-e-p is dead. To quote the plugin
I am the one who said "for all intents, m-e-p is dead" based entirely
on JIRA activity and releases, as well as the existence of newer (and
largely percei
Wrong person.
I was not the person claiming that patches were not being deployed.
Ron
On 28/10/2010 9:36 AM, Benson Margulies wrote:
Ron,
m-e-p works better than M2ECLIPSE in many cases. Further, you have no
proof here that I can see that the m-e-p is dead. To quote the plugin
site:
Last Publ
Hello,
I recently discovered some confusing Maven behavior related to snapshots. I'm
not sure whether this is expected behavior of Maven or Artifactory
or a bug in one of them.
Setup:
- Maven 2.2.1
- Artifactory 2.2.5
- Artifactory snapshot repo is libs-snapshots-local.
Maven Snapshot Version
We're not stopping you from taking it. Put it in Github and hack away.
On Oct 28, 2010, at 5:13 AM, Martijn Dashorst wrote:
> So how does one get ownership of the plugin? I've contributed 2
> patches with an implied promise that they would be included when the
> failing ITs on Barrie's workspace
Ron,
m-e-p works better than M2ECLIPSE in many cases. Further, you have no
proof here that I can see that the m-e-p is dead. To quote the plugin
site:
Last Published: 2010-02-25 | Version: 2.8
If someone posts a patch, I don't think there/s much evidence that it
will be ignored.
--benson
On
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
wrote:
> It is hard to get enthusiastic about maintaining old software that has been
> replaced by better stuff that is free.
maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plugin fails miserably with our maven project setu
Hi All,
I am receiving the below exception while using .
Please advise.
[INFO] Failed to configure plugin parameters for: org.codehaus.mojo:emma-maven-p
lugin:1.0-alpha-2
(found static expression: 'C:/maven.repo/test/TestProject1/0.0.1-SNAPSHOT/*.
jar' which may act as a default value).
On 28/10/2010 5:13 AM, Martijn Dashorst wrote:
So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.
I guess that you could take a
Thank you for your responses :-).
There are two ideas here:
1) have the configuration pick the right version, using
${project.parent.version}
2) refactor the parent into two parts, to avoid duplication.
1) is like the previous suggestion, but gets around the issue of having children
at differe
Hi All,
I am trying to get the code coverage for the maven dependent jars. I tried
the below plugin, however it is able to provide code coverage only if the
source files that are present in the project. It is unable to instrument the
jars if the source files are in the form of jars, tha
I had encounter that few days back.
And what I did is the location of the parent folder contains the pom.xml
into the relativePath just like
nl.topicus.onderwijs
onderwijs-project-parent
1.3
On Thu, Oct 28, 2010 at 5:22 P
Is this a known issue?
A new company parent pom release was not downloaded by maven 3, and
hence failed to do anything with my project. Running maven 2.2.1 on
the project successfully downloaded the parent pom.
Running maven 3 gave the following output:
$ mvn -X help:effective-pom
Apache Maven 3
So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.
Why the constant commercials for the m2eclipse plugin? Instead why not
ask for
The common project parent-pom and build-resources-bundle project, yes,
however the children (each project) won't have the same version.
2010/10/28 Anders Hammar
> The subject suggests that the projects will be release together, hence very
> likely have the same version.
>
> /Anders
>
> On Thu, O
Hi, we're using the jar-with-dependencies descriptor to assemble our
artifacts.
Now when we're switching from 3.0-beta-1 to 3.0 of Maven we are
experience a change of behavior of the assembly process. Before, the
resources of the assembled project would be assembled before any other
dependency
Hi,
Why not simply use scm apis ? (you can have a look at the checkout
mojo to understand how it works).
The mojo is simply a kind of wrapper around the scm apis (all the
stuff is done in the scm apis).
2010/10/28 Jared Prestwich :
> I'm writting a plugin that checks the dependencies and seperates
35 matches
Mail list logo
