Issue Subscription
Filter: Design & Best Practices (28 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
Lukas Theussl wrote:
>
>
> Dennis Lundberg wrote:
>> ltheu...@apache.org wrote:
>>
>>> Author: ltheussl
>>> Date: Mon Jan 19 05:01:45 2009
>>> New Revision: 735679
>>>
>>> URL: http://svn.apache.org/viewvc?rev=735679&view=rev
>>> Log:
>>> Change doxia dep to 1.1 (beta-1 won't be released).
>>>
>>
On Wed, Jan 21, 2009 at 5:17 PM, Oleg Gusakov
wrote:
> Logistics were sorted out, here we go:
>
> This is iterative improvements release of Mercury.
The the tag was modified in r736525. Have the binaries been changed
since the vote started?
(The commit message on the tag could use an issue numb
Actually, I'm trying to catch the following situation:
https://svn.codehaus.org/mojo/trunk/mojo/versions-maven-plugin/src/it/it-103
Another situation I'm trying to catch is in it-104, which is briefly this:
4.0.0
localhost
it-104
1.0
pom
maven-clean
Inheritence happens first and then interpolation. So if you put it in
the parent, it's essentially the same as putting it in the child and it
will have the value defined in the child.
Now if you are simply trying to validate the property, take a look at
the requireProperty enforcer rule. You can v
2009/1/22 Stephen Connolly :
> Well would it help if I pointed out that these are snippets of the
> pom.xml file (or it's parents)... specifically, they're the
> tags from definitions!
>
> (It's the versions-maven-plugin) and I'm trying to ensure that
> ${plugin.version.install} evaluates correct
Well would it help if I pointed out that these are snippets of the
pom.xml file (or it's parents)... specifically, they're the
tags from definitions!
(It's the versions-maven-plugin) and I'm trying to ensure that
${plugin.version.install} evaluates correctly... of
course somebody might have forc
You're probably better getting the PluginParameterExpressionEvaluator
component and using that (it's not the same as the interpolator in the
POM unfortunately, but probably what you are looking for and more
accessible).
On 22/01/2009, at 6:55 AM, Stephen Connolly wrote:
I'm working on a m
I'm working on a mojo that needs to filter property and maven model
property-equivalents (i.e. ${project.parent.groupId}).
What is the preferred way to get these values?
My current theory is that I should use
http://maven.apache.org/ref/current/maven-project/xref/org/apache/maven/project/interpo
Thanks alot
Next thing is that , I am having a huge directory structure like
dempack/room/primitive/*.java
demapack/jmx/console/*.java
/rfg/pool/bevarage/*.java
/rfg/pool/bevarage/test/*Test.java
like this with lots of .java,.prejava, .properties, .h
10 matches
Mail list logo