Hello, Dion!
dion XSD doesn't seem to handle arbitrary content as far as I can tell, and
dion hence we haven't got the properties in there
How about somthing like this?
xsd:element name=properties type=xsd:anyType/
I haven't looked at XSD closely yet, in fact I do not speak
XSD at all
I know that...
But if jnlp, for example, is part of the standard distribution of
plugins (does this exist?) then its tags should be fed as well.
An alternate route could be to have, at registration time, the plugins
add elements to the schema... and have a validate:generate-xsd task.
Paul
On
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 4:16 AM
To: Maven Users List
Subject: Re: Distinguishing between runtime and compile time
dependencies
On Thu, 4 Sep 2003 [EMAIL PROTECTED] wrote:
Henri Yandell [EMAIL
:56 PM:
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 4:16 AM
To: Maven Users List
Subject: Re: Distinguishing between runtime and compile time
dependencies
On Thu, 4 Sep 2003 [EMAIL PROTECTED] wrote
Is there a magic flag to identify a runtime dependency from a compile
time dependency? For example, Xerces and Xalan may be needed to compile
some aspects of a project (some people use it to generate java source
code), but never needed at run time.
This will allow a number of things:
* The
On Wed, 2003-09-03 at 10:07, Berin Loritsch wrote:
Is there a magic flag to identify a runtime dependency from a compile
time dependency? For example, Xerces and Xalan may be needed to compile
some aspects of a project (some people use it to generate java source
code), but never needed at run
Why aren't the compile time dependencies, code generators etc in a
separate plugin similar to the way the antlr plugin is? That way the
project doesn't need to list those jars as dependencies.
You could always add a property to the dependency (like the war and ear
plugins do) and use that in
Jason van Zyl wrote:
On Wed, 2003-09-03 at 10:07, Berin Loritsch wrote:
Is there a magic flag to identify a runtime dependency from a compile
time dependency? For example, Xerces and Xalan may be needed to compile
some aspects of a project (some people use it to generate java source
code), but
You can specify properties for the dependency to indicate if it is
runtime or not, then use that information to collect your runtime
dependencies.
Example:
dependency
idcommons-logging/id
version1.0.3/version
urlhttp://jakarta.apache.org/commons/logging/url
On 3 Sep 2003, Jason van Zyl wrote:
There is no facility yet. But we've talked about it for a long time and
we do have working code for it in experimental versions of Maven but the
real crux of the problem is collecting POMs in the repositories so we
can build the necessary graphs. In this
On Wed, 2003-09-03 at 11:09, Berin Loritsch wrote:
Jason van Zyl wrote:
Are you trying to assemble a container runtime?
yes.
You may want to look at the Plexus plugin. Most of the work is done
there already and you can just take what you like. It assumes the
presence of POMs in the repo
properties
typeruntime/type
/properties
D'oh! That should be:
properties
runtimetrue/runtime
/properties
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Paul Libbrecht wrote:
j:forEach var=artifact items=${pom.artifacts}
j:set var=dependency value=${artifact.dependency}/
j:if test=${dependency.getProperty('runtime') == 'true'}
ant:echoProcessing dependency: ${dependency.id}/ant:echo
ant:mkdir
13 matches
Mail list logo
