Hi,
Currently for releasing to a staging directory we have documented
each developer specifying one, but do we want to have a shared
directory where we stage releases?
Simple use case might be I stage a release and then someone else does
the final approval and merging to the production re
Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
This is pretty tricky, because the versions are selected based on the
interpolated POM, and it's possible (but unlikely) something like
this might happen:
project.version=1.0-alpha-1-SNAPSHOT
module1: ${project.version}
module2: ${project.version}
and then we select:
module1: 1.0-alpha-1
mod
Hi,
You might see some junk flying by, I've done some preliminary tests
on file based repos and some fake svn repos but I'm going to do a few
passes at a real plugin so I'm sure it won't work the first couple
times so I'll probably be nuking some stuff. I'll try not to pull a
Classworlds
Good day to you, Aaron,
add @parameter to your mojos field so that it can be configured in the pom.
/**
* @parameter
*/
private String test;
add "expression=${...}" to @parameter so that it can be referenced as
a property ( i.e from the commandline )
/**
* @parameter expression=${test}
*/
priv
Hi all, a few weeks ago I wrote my own JUnit4.x plugin which has been working
perfectly. But yesterday I added cobertura to a pom and the plugin stopped
working. Whenever cobertura is added the Junit4 plugin's classloader claims
it cannot locate the compiled/instrumented classes. Turning on debug
Here's the content of the proposal from:
http://docs.codehaus.org/display/MAVEN/Suppression%2C+Ordering%2C+and+Replacement+of+Plugins+and+Mojos+Bindings
Thanks,
-john
content follows:
==
[PROPOSAL] Support for Relative Ordering, Replacement, and Suppression of
Mojos 1. Backgro
Hi everyone,
I wanted to start a discussion about the current drawbacks involved with:
* suppression of inherited/injected/packaging-mapped mojo bindings
* ordering of new mojo bindings within a phase that already contains other
bindings
* replacement of one mojo binding with another
As we've a
I've cleaned them all up.
On 01/02/2007, at 7:05 PM, Trygve Laugstøl wrote:
[EMAIL PROTECTED] wrote:
Author: jmcconnell
Date: Tue Jan 30 14:59:27 2007
New Revision: 501627
URL: http://svn.apache.org/viewvc?view=rev&rev=501627
Log:
added $ back into the expressions, was throwing NPE in the test
Seems to make sense - please file it as a JIRA issue.
- Brett
On 01/02/2007, at 9:43 PM, Loic Jay wrote:
Hi,
I am using the Maven Antlib 2.0.4 with Ant 1.7.0 and when using the
task with the pathId attribute:
...
I get the following error:
[maven:dependencie
Yeah, apparently there are versions of the rpm command that are buggy at the
db-locking step...for instance, on RHEL3.
As far as doing the install action, sometimes this is pretty hard to avoid,
since you may need to use an rpm as a compile-time dependency for another
project in the reactor. In t
You have to set a mojo parameter and use the @expression tag to specify
a variable. Take a look at some of the other mojos. I'm not sure if you
can directly read all the params.
-Original Message-
From: Aaron Digulla [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 8:51 AM
To:
Hello,
I have a mojo which has dynamic parameters/properties which have to be
specified via the commandline.
When I'm in my execute() method, what do I have to call to see "value"
when I call mvn with "-Dtest=value"?
They aren't in MavenProject/Model.getProperties()...
Regards,
--
Aaron
Hi,
I am using the Maven Antlib 2.0.4 with Ant 1.7.0 and when using the
task with the pathId attribute:
...
I get the following error:
[maven:dependencies] An error has occurred while processing the Maven
artifact tasks.
[maven:dependencies] Diagnosis:
[maven:
Please see:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/plexus/security/plexus-security/1.0-alpha-8/plexus-security-1.0-alpha-8.pom
Its clear that the release manager failed to update the expression
definition of the dependency versions. Fixing this bug will be easy if
only the
+1, sounds very interesting and I already face this "issue" a couple of times.
Stéphane
On 1/31/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
The assembly plugin has proven to be very valuable, and used very often.
Can we create a new type for "assembly" that defaults a set
of values, and eve
Or in the Maven sandbox, that'd be a more appropriate place :-)
(I'm only talking about the "standardized report" framework that Joakim
introduced, of course)
On 1/31/07, Garvin LeClaire <[EMAIL PROTECTED]> wrote:
Let me fix my over zealeous typing ;-o)
Why don't we put the code in the Plugin
[EMAIL PROTECTED] wrote:
Author: jmcconnell
Date: Tue Jan 30 14:59:27 2007
New Revision: 501627
URL: http://svn.apache.org/viewvc?view=rev&rev=501627
Log:
added $ back into the expressions, was throwing NPE in the test cases on the
jarArchiver
[snip]
/**
* Jar archiver.
- *
18 matches
Mail list logo
