Although not a real solution, but I have a workaround for some of the
use cases. Some parameters of the plugins similar to ${parameter} can
be configured inside settings.xml... just use properties.
^_^
Tomasz Pik wrote:
Hello,
It's currently not possible but generally I think it would
Hi,
thanks a lot for the feedback, Hermod. I have just filed a bug on jira and
submitted the patch at http://jira.codehaus.org/browse/MNG-2347.
Let's see what happens...
Greets,
Ovidio
[EMAIL PROTECTED] wrote:
Hi
Your patch worked great :). Could you please file this in jira so that it
I'm working on MJAR-38 and I don't like how Maven adds some arbitrary
manifest entries. Specifically I'm referring to Specification-Title and
Specification-Vendor. The patch for this issue allows the user to
override these entries defined by Maven but I would actually just like
to remove them so
Could someone update the jar plugin site? It's 7-8 months old now and
contains next to no docs at all.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Just wanted to say that my conversion of a fairly large project (tapestry )
to maven2 has been pretty easy so far.. The only thing that I really had to
look hard for was how to create a custom skin, everything else pretty much
just worked as expected...So, thanks! :)
--
Jesse Kuhnert
+1
Stéphane
On 6/6/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a while, but with the re-introduction of xerces
into the core and the upcoming dom4j upgrade (which it should be
compatible
Lukas,
I would really like to try this version out on Jakarta Commons
components, but I won't have enough time to do it until Sunday.
--
Dennis Lundberg
Lukas Theussl wrote:
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a while,
Well, as far as they go under the maven group should be ok. the only
problem I think is the confusion, so description in pom should be
clear
On 6/6/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Hi devs,
Maven 1.1-beta-3 is almost ready but still waiting for some external
library releases that
No problem Dennis, I guess I can wait those few more days, too. ;)
I'd certainly appreciate the feedback though.
Cheers,
-Lukas
Dennis Lundberg wrote:
Lukas,
I would really like to try this version out on Jakarta Commons
components, but I won't have enough time to do it until Sunday.
You mean groupId=maven, artifactId=dom4j-1.7-20060507 or something like
that?
-Lukas
Carlos Sanchez wrote:
Well, as far as they go under the maven group should be ok. the only
problem I think is the confusion, so description in pom should be
clear
On 6/6/06, Lukas Theussl [EMAIL PROTECTED]
I'll vote based on whether it works in Commons.
Lukas Theussl wrote:
No problem Dennis, I guess I can wait those few more days, too. ;)
I'd certainly appreciate the feedback though.
Cheers,
-Lukas
Dennis Lundberg wrote:
Lukas,
I would really like to try this version out on Jakarta Commons
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (36 issues)
Subscriber: mavendevlist
Key Summary
MEV-408 Missing POMs for Spring 2.0-m5
http://jira.codehaus.org/browse/MEV-408
MEV-407 Missing POM for spring-support 2.0-m4
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (25 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-938Upload MySQL Connector/MXJ 5.0.2 beta
http://jira.codehaus.org/browse/MAVENUPLOAD-938
MAVENUPLOAD-937Upload MySQL Connector/MXJ 1.1.6
FYI We have been running this snapshot for weeks/months without problem (and
it fixes a couple of problems we experienced).
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 12:45 PM
To: Maven Developers List
Subject: [vote] [m1] release
14 matches
Mail list logo
