plugin.jelly in test plugin:
j:if
test=${!context.getVariable('maven.junit.fork').toString().trim().equalsIgnoreCase('no')}
pathelement path=${plugin.getDependencyPath('xml-apis')}/
pathelement path=${plugin.getDependencyPath('xerces')}/
/j:if
this
How can I use different plugin version? I want to override some plugin for our
company, but don't know how to.
or, please remove xml parser dependency from test plugin. it is useless. let
the user select parser!!
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
To: Maven
How's it going? would xml parser setting be removed? answer plz
- Original Message -
From: Pak, Young-rok [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]; Brett Porter [EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 10:17 AM
Subject: Re: xerces
I'm interested in why you
it helps in some cases, but I still want to change xml parser for maven. I want to use
JVM's default parser. why maven specifies XML Parser? I think this is bad. users must
be able to choose their own parser without modifying maven script and classpath.
- Original Message -
From: John
The reason is simple - the crimson parser bundled with the JDK's through
1.4.2(?) is complete crap. Additionally, even older JDK's don't have a
parser bundled, which means you'd have to create multiple maven distros
(one for parser-bundled JDKs and another which accounted for the xml
I'm interested in why you need MS949 for project.xml. The reason I ask
is that we intend to switch to a smaller, faster XML parser in Maven
1.1, however it is likely to support fewer encodings and xml features
- but still supports everything required to correctly operate Maven
that we have
jelly is good scripting language but still restricted than real script language.
groovy-ant scripting can overcome such restriction. instead of maven.xml, how about
using maven.groovy?
I defined dependecy like this:
dependency
groupIdibatis/groupId
artifactIdibatis-nhn/artifactId
versionSNAPSHOT/version
jaribatis-2.jar/jar
typejar/type
properties
war.bundletrue/war.bundle
|-+
| | Pak, Young-rok |
| | [EMAIL PROTECTED]|
| | o.co.kr |
| ||
| ||
| | 22/09/2004 10:54 |
| | Please respond
I want to deploy some files to repository without modifying filename when deploying
jar. for example, there is file to deploy in my project like this:
src/tld/mytag.tld
and, I want to deploy to my repository like this:
mygroup/tlds/mytag.tld
so, I tried to use maven.xml like this:
in the
repository, especially with new features coming in Maven.
What problems will this cause you?
- Brett
On Wed, 22 Sep 2004 20:10:17 +0900, Pak, Young-rok
[EMAIL PROTECTED] wrote:
I want to deploy some files to repository without modifying filename when
deploying jar. for example
after deploying maven-based project, jar and pom is deployed to repository. can I use
that pom file to extend in other project?
12 matches
Mail list logo
