Probably helpfull by are you sure of your URL ?
Couldn't get you!
By the way, someone could enumerate the main properties in a project if there is no way to view available properties ?
Interesting, i don't know of a direct or a neat way to do that, but I have a link to the cvs for someone how wanna see.
And you can even make an xdoc for your properties. I have a xdoc for my project's properties also but I havan't give the
dependency URL as my xdoc but you can.
-----Original Message-----
From: Olivier CHAMPAGNE [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 08, 2004 9:33 PM
To: Maven Users List
Subject: Réf. : RE: Viewing all properties available
Probably helpfull by are you sure of your URL ?
By the way, someone could enumerate the main properties in a project if
there is no way to view available properties ?
Olivier Champagne @ EADS, Labège
(\(\ "Regular _expression_
( ~.) are to strings what
o((")(") math is to numbers"
"Verma, Nitin
(GECP, OTHER, Pour : Maven Users List <[EMAIL PROTECTED]>
529706)" cc :
<[EMAIL PROTECTED] Objet : RE: Viewing all properties available
PL.GE.COM>
08/01/04 15:05
Veuillez
répondre à
"Maven Users
List"
I make a properties jar for projects global properties files.
Then you can use it as an artifact.
<dependency>
<groupId>myProject</groupId>
<artifactId>properties</artifactId>
<version>2.1</version>
<url>http://cvs.my.com/myProject</url>
</dependency>
Hope this helps you!
-----Original Message-----
From: Olivier CHAMPAGNE [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 08, 2004 3:05 PM
To: [EMAIL PROTECTED]
Subject: Viewing all properties available
Sorry for this newbie's question (Maven related but probably java too) but
I would like to known if there is a way to view/browse all properties
available/set in a target.
In fact, I would like at least to output some revealant informations during
build process like :
- current artifact
- current version(s)
- goal's description
- current pathname
- ...
and so on
(I think "properties" in means of pom.*, maven.*, ...)
< context >
In the project (prototype), Maven is used as a build framework with ordered
and dependant (sometimes interactive) steps, not as a "super-Makefile" to
build Java projects/subprojects.
I mean Maven (and its project definition) can be viewed as a generic build
process coherency guardian which asks intermediate questions to generate a
final product (CD distribution) from an initial description of the global
system made by user (hardware environnement, dynamic flows and software
components/functionnalities needed for computing) through intermediate
tasks (viewed as goals).
I actually work on these intermediate and generic steps needed to guide
final users in the generation of there own system.
< / context >
Thanks in advance.
Olivier Champagne @ EADS, Labège
(\(\ "Regular _expression_
( ~.) are to strings what
o((")(") math is to numbers"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
