On 30/12/2007, at 2:44 PM, Brian E. Fox wrote:
Hi Nick, I'm working on fixing these issues. I was unaware that the
harness got moved to a new tlp "plugin-tools"
They all now have a common version, so it's more complicated to
release
this. Anyone know why this was moved? (Brett?)
Just thou
In preparation for some plugin releases, I'd like to release the next
version of maven-plugin-testing-tools (1.0-alpha-3)
It is staged at: http://people.apache.org/~brianf/staging-repository
NOTE: This is dependent on the passing of the maven-test-tools
1.0-alpha-2 release.
Vote i
Hi Nick, I'm working on fixing these issues. I was unaware that the
harness got moved to a new tlp "plugin-tools"
They all now have a common version, so it's more complicated to release
this. Anyone know why this was moved? (Brett?) Why not the
plugin-testing-tools too?
--Brian
-Original Me
In preparation for some plugin releases, I'd like to release the next
version of maven-test-tools (1.0-alpha-2)
It is staged at: http://people.apache.org/~brianf/staging-repository
Vote is open for 72hrs.
+1
If I use maven-archiver in a application without any p-c-a dependency.
This will cause java.lang.NoClassDefFoundError:
org/codehaus/plexus/logging/AbstractLogEnabled
IMHO, we must leave this pom as it and add exclusions in the maven
plugins which will use maven-archiver (as in jar plugin).
Becau
I will be out of the office starting 29.12.2007 and will not return until
09.01.2008.
I will respond to your message when I return.
Happy New Year and Merry Christmas!!!
May I repeat this question? I am absolutely undecided how to handle MOJO-866
without a helpful reply.
Jochen Wiedmann wrote:
>
> Hi,
>
> I have a question regarding MOJO-866. Hopefully, someone can help me.
>
> In this bug report, someone is invoking the rat:rat goal from the
> command line.
Thanks Brian.
Brian E. Fox wrote:
> Just exclude the api jar. I had to do this in maven-dependency and I
> setup an enforcer rule to alert me if the jar creeps back in so I can
> stamp it out. Take a look at the mdep pom to see.
>
> -Original Message-
> From: Dennis Lundberg [mailto:[EMAI
I was busy with writing a Enforcer rule to check whether you the latest
super pom (company pom, or what ever name you give it).
First time coding with Maven internals and after a while I came with this:
MavenProject superPom = getSuperParent( project );
MavenSessio
Carlos Sanchez schrieb:
> that's right, I still have to polish the eclipse plugin to generate
> the Eclipse repo using some "conventions"
>
I tried to build 'my' repo for the eclipse-3.3.1.1 version using
maven-eclipse-plugin build from trunk with mvn
eclipse:to-maven. All worked well and the ar
10 matches
Mail list logo
