How to play with 2 repositories ?
I have a repository at work that is only accessible from our intranet. This repository is configured in my personal setting as a repository (for some company artefact) and as a mirror for all other repository. When I'm home, I use an other settings file without this repository and the mirror config. But when I launch a build, it seems that he need to redownload all plugin and dependencies. I also have difficulties to launch build with option -o because some plugin are not found in my local repository altought they are there (but maybe donwloaded from the miror). How can I configure my settings files so that when I switch the config I keep my entire local repository useable, independantly of the place from where I downloaded it. - Gilles Scokart -- View this message in context: http://maven.40175.n5.nabble.com/How-to-play-with-2-repositories-tp5748541.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Use of ${version} in published pom
The pom :
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/cargo/cargo-core-api-generic/0.9/cargo-core-api-generic-0.9.pom
Contains some ${version}. I looked in the parent poms, but there is no
explicit property with this name.
Where does this value comes from? Is it a standard property implicitely
defined?
Gilles Scokart
--
View this message in context:
http://www.nabble.com/Use-of-%24%7Bversion%7D-in-published-pom-tf3790660s177.html#a10720048
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven users in the industry
Hi, Next week I have to make a presentation to my collegues. I will try to 'sell' maven, and I would like to say something like "Look, Maven is now very used in the industry, It's for instance used by ...". Did you know any companies using Maven, more particularily in Belgium and Europe, but worlwide would be ok also? Thanks for your help. Gilles -- View this message in context: http://www.nabble.com/Maven-users-in-the-industry-tf3557876s177.html#a9934912 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Building tool community feedback
Everywhere i go, i see that there is a lot of people (like me) thinking that the existing build tools are extremely useful (maven in first;-) ). But still, a lot of people think that something else should be possible. I have thus started a forum in order to collect info from the "builder community": http://phoebus.tigris.org/servlets/ProjectForumView If you want to share expertise, lesson learned or ideas, please join this forum. I hope the result of this discussion will be a better knowledge of the build problems, and some ideas on how to solve them (with good practices, enhancement of the existing tools or with some new tools). Thanks, Gilles Scokart -- View this message in context: http://www.nabble.com/Building-tool-community-feedback-tf2450373.html#a6829671 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Build Notification
You can use the antrun plugin to send mail at a given phase of your build. But I don't think you can have this when your build fails. When the maven build fail, it stop. I don't think there is any listener. Did you search in jira to see if there is a feature request? If not, you should maybe introduce it. Gilles -- View this message in context: http://www.nabble.com/Maven-Build-Notification-tf1995888.html#a5480753 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Expansion of maven variables
${project.classpathElements} can be used when your parameter is a List .
Here you want to place it in a String.
Moreover, I think that the expension done into the pom, and the things done
in the plugin is different. So, there is maybe some differences.
--
View this message in context:
http://www.nabble.com/Expansion-of-maven-variables-tf1996470.html#a5480707
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Release Plugin Version Problem
Actually, to find a workaround, you don't need to deploy on a company repository. You limit it to an local install. What I could suggest you is to bind the install plugin to the latest phase (integration-test I think) of the build launched by the release plugin. But I'm not sure it would work. Indeed, maven has to find the dependencies before it launch the build (to know in wich order to build). I have already build some times ago a project with a similar structure, and what I did was to release on module at a time (but there is maybe an better solution with more recent versions). Note that when there is no dependencies between submodules, the release plugin works correctly with multi-module project. By the way, did you tried similar things with only 1 level? In that case, the maven is maybe able to find sibbling module. Gilles Scokart -- View this message in context: http://www.nabble.com/Maven-Release-Plugin-Version-Problem-tf1902125.html#a5205412 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly and multi-levels multi-modules
baerrach wrote: > > > My file layout looks like: > ROOT > - pom.xml > - module1 > - modulen > - build > - pom.xml > > Where the build/pom.xml will contain the assembly of everything that > is needed from the other modules. > > I don't think putting the assembly plugin and descriptor in the > ROOT/pom.xml is correct as then it will be inherited by all the > modules. So the correct place to put together an aggregation is > build/target. > > Any one else doing this and have some hints? > > If the inheritance is a problem, you can use the inherited tag when configuring your plugin. Gilles Scokart -- View this message in context: http://www.nabble.com/Assembly-and-multi-levels-multi-modules-tf1747056.html#a5178340 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: acces to svn.apache.org
I did, without success. Thanks for your answer anyway. It means something is wrong on my side. I will try with an other network connection when I have the oportunity (in a few days, unfortunately). Thanks, Gilles Scokart -- View this message in context: http://www.nabble.com/acces-to-svn.apache.org-tf1871896.html#a5120476 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
acces to svn.apache.org
When I try to get the source, I got an HTTP 302 error. : / $ svn ls http://svn.apache.org/repos/asf/maven svn: PROPFIND request failed on '/repos/asf/maven' svn: PROPFIND of '/repos/asf/maven': 302 Found (http://svn.apache.org) I tried with https, I updated my svn client (I use Windows client), I tried with the cygwin client, and with Torvoise (those two are older verions). I always get the same answer. By sniffing the request, I have seen the 302 redirect to http://people.apache.org. I tried there, but then I get a "405 Method Not Allowed". Can someone help me? I'm I the only one to have this problem (since yesterday. It worked 2 or 3 months ago). Thanks, Gilles Scokart -- View this message in context: http://www.nabble.com/acces-to-svn.apache.org-tf1871896.html#a5116494 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 How to add generated source to the compilation path from a new pl
See http://maven.apache.org/guides/mini/guide-generating-sources.html Namely : project.addCompileSourceRoot( outputDirectory ); at the end of the code sample. Gilles Scokart -- View this message in context: http://www.nabble.com/m2-How-to-add-generated-source-to-the-compilation-path-from-a-new-plugin-t1471998.html#a3985251 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Does runtime dependencies really exist ?
In Maven 2, compile dependencies are transitive. It means that the libraries called from the library I use are included in the compile path. And so transitively... At the end, if all libraries are build and distributed with maven, all the libraries I need at runtime will transitivelly be in the compile path! Am I wrong? I understand the reasons for which 'compile' stay transitively 'compile': It's easier when you use inheritance accross modules. However, I regret the choice made in maven. The alternative was to say = "Well, if you use a class of a module B which extends a class of module C... You are actually using the interface exposed by C, and you should place C as a compile depency." I mean, It's only if the dependencies of my dependencies are included in runtime by default that the runtime dependencies make sense. One of the bad consequence of this choice has already been presented in this thread : http://www.nabble.com/forum/ViewPost.jtp?post=1045013 To sumarize, the question was "When I write a module B for which I use a module C, how can I prevent the module A to use directly the module C ?". The answer was not given, but it was : "You must say it in the pom of the module A". The author wanted to put that in the pom of the module B because A has no reason to know that B use C. An other problem I see with the choice that was made is "How did I know precisely which module is really used directly (I mean at compile time) by my module?". Now, ok this choice has been made and can not be changed. But maybe things could be adapted. We can imagine to add an XML tag to the dependency block to say how to export a compile dependency. By default it can stay "compile", but with the possibility to say "runtime". How do you feel it? -- View this message in context: http://www.nabble.com/-M2-Does-runtime-dependencies-really-exist--t1330012.html#a3551082 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what is used for?
No, it is possible. Just declare your dependencies in the parent pom (directly into dependencies not in dependencyManagment) and they will be inherited in all subproject. Could be usefull for some libraries like junit or log4j used accross all modules of an entire product. From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: users@maven.apache.org Subject: Re: what is used for? Date: Thu, 22 Dec 2005 11:19:05 -0600 (CST) nope, each subproject needs to declare what it uses, but can be seeded version wise from the parent On 12/22/05, Mick Knutson <[EMAIL PROTECTED]> wrote: > > That sounds great, but what if I am using multiple sub projects and they > all > require some standard libs? Is there a way to just declare them in the > root > pom instead of having to re-declare them in each sub pom? > > > > Thanks > Mick Knutson > > http://www.BASELogic.com > http://www.MickKnutson.com > > MSN Messenger: [EMAIL PROTECTED] > > > > - Original Message - > From: \"Jesse McConnell\" <[EMAIL PROTECTED]> > To: \"Maven Users List\" ; \"Mick Knutson\" > <[EMAIL PROTECTED]> > Sent: Thursday, December 22, 2005 8:18 AM > Subject: Re: [m2] what is used for? > > > it lets you set all of the scopes and versions of dependencies in one > place, > and then child poms don\'t need to specify versions in their dependencies, > they get inherited from the parent pom. > > then if you up the version for something, you can update it only in one > place. > > > > On 12/22/05, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > what is used for? > > > > > > > > > > > Thanks > > Mick Knutson > > > > http://www.BASELogic.com > > http://www.MickKnutson.com > > > > MSN Messenger: [EMAIL PROTECTED] > > > > > > > > > > > > -- > jesse mcconnell > -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Guideline to test Pojo
I have written a pojo, and I would like to know what is the best method to test it. I have some unit test of it, but I would like to test his integration inside maven. The aproach I have used is to use my own pojo inside the pom.xml of my project. That provide me a test of a concrete case. However it introduce a kind of cycle (the project need to be deployed in order to build). An other aproach would be to create dummy project using my plugin. But this seams heavy. What are the good practice to test a mojo? _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] eclipse plugin and generated sources
When you have a project using a code generator plugin, how can we add the generated sources in the list of eclipse source directory? This problematic was seemingly handled in Mavane 1.x (As I read on http://maven.apache.org/maven-1.x/reference/plugins/eclipse/), but there is no similar things on Maven 2. I know it is possible to a plugin to add a source directory for the following plugins (expl: a plugin executed in generate-test-sources phase can add test source directory for the following phases, incuding test-compile). But (as I understand) the eclipse plugin is not executed at a particular phase. So how can we do? Thanks, Gilles Scokart _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] install plugin
Thanks for your response. I find the problem. My project was a pure pom, but had the packaging jar. "m2 install" produced an empty jar, a maven-metadata-local file, but the pom was not installed. (And no errors nor warnings where produced). Gilles you're certain that there isn't a file alongside the jar named something similar to: -.pom If that's missing, there's a problem. 'm2 install' should handle installing the primary artifact, attached artifacts, and metadata - including the POM. - -john Gilles Scokart wrote: | When I try to use the install plugin, I see that the jar are installed | in the local respository, but not the pom.xml. | | Is it normal? Did I miss somthing? Should I use an other plugin to | install the pom.xml ? | | Thanks, | | Gilles Scokart | _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] install plugin
When I try to use the install plugin, I see that the jar are installed in the local respository, but not the pom.xml. Is it normal? Did I miss somthing? Should I use an other plugin to install the pom.xml ? Thanks, Gilles Scokart _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Extensions, module and cycle
Usually this happens when a plugin project uses itself to build itself. Might also be because you define a dependency to the plugin AND the plugin itself (using build/plugins/plugin). -- Kenney Indeed, I 'import' the module as a dependency AND as an extension. Is it the problem? Is there a good reason for which it is not allowed ? _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Extensions, module and cycle
I have written a code genrator that has an ant interface. In order to test
it, I have a separate module that use ant run. In order to be able to call
my owns task, I have to use the extensions.
The problem is that I receive a cycle error.
The structure is this :
- I have my parent project with 2 modules : ant-generator and test.
- test try to load the extension 'ant-generator' into the test module
I regularly receive an error :
[INFO] Reason: Edge between 'Vertex{label='org.nextmock:ant-generator'}' and
'Vertex{label='org.nextmock:ant-generator'}
' introduces to cycle in the graph org.nextmock:ant-generator -->
org.nextmock:ant-generator
But I don't see why there is a cycle. It should not be a problem.
generator can be built alone, but test or the parent project can not be
build. Why ? Any idea ?
Thanks,
Gilles Scokart
_
Protégez votre boîte de réception: Phishing : comment l'identifier, le
signaler et l'empêcher http://www.fr.msn.be/security/phishing/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logging/tracing conventions
Thanks, but what are the guidelines on when to log at which level ? I guess it's a good idea that all plugins follow the same guidelines. What is the best practice for that ? And what if our mojo call external code that is not (and should not be) aware of running into a maven plugin ? > When writting a Mojo, what are the standard convention to trace/log [debug] > messages ? getLog().info( "Hey yo!" ); -- Trygve _ Protégez votre boîte de réception: Phishing : comment l'identifier, le signaler et l'empêcher http://www.fr.msn.be/security/phishing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Logging/tracing conventions
When writting a Mojo, what are the standard convention to trace/log [debug] messages ? Gilles Scokart _ Protégez votre boîte de réception: Phishing : comment l'identifier, le signaler et l'empêcher http://www.fr.msn.be/security/phishing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Mojo, subproject and self-reference
I'm writting a mock generator and I need advice on how to organise my project. Amongst other module, I have : - The genrator itself - The runtime library used by the genrated code - The Mojo that will launch the genrator from + All the unit test. I wonder how to organise this into modules? I guess that the decomposition I have should be nice, but I have a problem for my unit tests. Indeed, I would like to be self-testing. I mean that I would like to use my mock generator to make my tests. One solution I have seen is to place the unit test into a separated module. But I don't really like it. An other one is to rely an a previous version of the mock generator being already deployed on the repository. Did you have already encounter similar problem ? What is the best practice ? Other question, maybe related : How did you make to test a plugin like sure-fire? Or how do you generate site docs for the site plugin ? _ Protégez votre boîte de réception: Phishing : comment l'identifier, le signaler et l'empêcher http://www.fr.msn.be/security/phishing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] site:deploy behind a proxy
Hmm, it seems that the plugin doesn't use the proxy at all. I put the ip adress in my host file, and now I just have Connection time-out. I fear that's because the proxy is not used. Can anyone confirm ? Is it changed in the Beta release ? I have now found why it works with putty. In putty, there is an option "Do DNS lookup at proxy end". This option is set to auto by default. If I set it to "no", it doesn't work. Is it possible to configure a similar option with the maven plugin ? From: "Gilles Scokart" <[EMAIL PROTECTED]> Reply-To: "Maven Users List" To: users@maven.apache.org Subject: [m2] site:deploy behind a proxy Date: Fri, 16 Sep 2005 10:27:28 +0200 I try to use site:deploy behind a proxy, but I receive an UnknownHostException. I have verified if the hostname was accessible from my machine by using putty, and it works. I just had to configure the HTTP Proxy in putty. I use the maven 2-alpha 3 version. I have very poor knowledge in network protocols behind a proxy. Did the plugin look at the proxy configuration of the settings.xml file ? How works the hostname resolution when we are behind a firewall ? _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] site:deploy behind a proxy
I have now found why it works with putty. In putty, there is an option "Do DNS lookup at proxy end". This option is set to auto by default. If I set it to "no", it doesn't work. Is it possible to configure a similar option with the maven plugin ? From: "Gilles Scokart" <[EMAIL PROTECTED]> Reply-To: "Maven Users List" To: users@maven.apache.org Subject: [m2] site:deploy behind a proxy Date: Fri, 16 Sep 2005 10:27:28 +0200 I try to use site:deploy behind a proxy, but I receive an UnknownHostException. I have verified if the hostname was accessible from my machine by using putty, and it works. I just had to configure the HTTP Proxy in putty. I use the maven 2-alpha 3 version. I have very poor knowledge in network protocols behind a proxy. Did the plugin look at the proxy configuration of the settings.xml file ? How works the hostname resolution when we are behind a firewall ? _ Protégez votre boîte de réception: Phishing : comment l'identifier, le signaler et l'empêcher http://www.fr.msn.be/security/phishing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Créez gratuitement votre espace perso en ligne avec MSN Spaces ! http://spaces.msn.com/?mkt=fr-be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] site:deploy behind a proxy
I try to use site:deploy behind a proxy, but I receive an UnknownHostException. I have verified if the hostname was accessible from my machine by using putty, and it works. I just had to configure the HTTP Proxy in putty. I use the maven 2-alpha 3 version. I have very poor knowledge in network protocols behind a proxy. Did the plugin look at the proxy configuration of the settings.xml file ? How works the hostname resolution when we are behind a firewall ? _ Protégez votre boîte de réception: Phishing : comment l'identifier, le signaler et l'empêcher http://www.fr.msn.be/security/phishing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Launching plugin with non default configuration
Hello,
I try [unsuccessfully] to launch a plugin with a non default configuration.
My project generates mock source code by analysing .class files. In order
to test it, I have written some classes that must be compiled before I
launch my generator.
Thus, I would like to launch a compiler on a specific directory at the
beginning of the generate-test-sources phase.
I use the alpha-3 version. I have tried different things like that,
maven-compiler-plugin
mockable_compile
generate-test-sources
src/test/mockable-src
${project.build.testOutputDirectory}
testCompile
But, this compiles both src/test/mockable-src and my src/test.
When I use the goal compile, it is even worse. It compile all my
src/main/java files, and place the result in the project.build.output
directory.
Everything happen like if the configuration that I put comes after (or on
top) of the default configuration.
Can we change this behaviour ?
Can we compile 2 source directory at different states without writing a
plugin ?
SCOKART Gilles
_
Protégez votre boîte de réception: Phishing : comment l'identifier, le
signaler et l'empêcher http://www.fr.msn.be/security/phishing/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Use variables in configuration of a plug in
Here is a sample pom.xml
When I execute it, I actually obtain this in the result.txt file :
runtimeclasspath =
C:\Dev\cygwin\home\ScokartG\project\testantrun\target\classes;C:\dev\data\maven2_repository\log4j\log
4j\1.2.11\log4j-1.2.11.jar;C:\dev\data\maven2_repository\ant\ant\1.6\ant-1.6.jar;C:\dev\data\maven2_repository\velocity\
velocity\1.4\velocity-1.4.jar
compileclasspath =
C:\dev\data\maven2_repository\log4j\log4j\1.2.11\log4j-1.2.11.jar;C:\dev\data\maven2_repository\ant\a
nt\1.6\ant-1.6.jar;C:\dev\data\maven2_repository\velocity\velocity\1.4\velocity-1.4.jar
The runtime classpth contains target/classes + all other jar contained in
compilepath, but doesn't contains the velocity-dep jar.
_
Créez gratuitement votre espace perso en ligne avec MSN Spaces !
http://spaces.msn.com/?mkt=fr-be
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
testing
testantrun
jar
0.1-SNAPSHOT
TestAntRun
org.apache.maven.plugins
maven-project-info-reports-plugin
src/main/java
src/test/java
maven-antrun-plugin
1.0-SNAPSHOT
generate-test-sources
runtimeclasspath = ${project.runtimeClasspathElements}
compileclasspath = ${project.compileClasspathElements}
runtimeclasspath = ${runtimeclasspath}
compileclasspath = ${compileclasspath}
run
nemonics_rep
Neonics
http://www.neonics.com/maven2/
junit
junit
3.8.1
test
velocity
velocity
1.4
compile
velocity
velocity-dep
1.4
runtime
jmock
jmock
1.0.1
test
jmock
jmock-cglib
1.0.1
test
ant
ant
1.6
compile
ant
ant-launcher
1.6
test
ant
ant-apache-log4j
1.6.5
test
log4j
log4j
1.2.11
compile
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Use variables in configuration of a plug in
> I have tried to use ${project.compileClasspathElements} into the
> configuration tag of a plugin (antrun), and it seems to work.
How did you use it? Could you post the pom.xml?
I will try to clean it a little bit, then I will post it here.
> But when I use ${project.runtimeClasspathElements}, I only have the same
> result. The pure runtime dependencies are not present in the list.
That's because all compile time dependencies are also runtime
dependencies. See
http://maven.apache.org/maven2/dependency-mechanism.html#dependency_scope
Yes, but runtime class path should contain more. It should contain the
compile + pure runtime dependencies.
> Is it a general behaviour that can be used in any plugin or is it
specific
> to antrun ?
It's general behaviour.
Does it mean that we can use $project.xxx in the configuration of other
plugin. Is there other variable than $project. For instance, I have tried
(unsuccessfully) to found a varaible that map to the local repository.
I'm really curious how you intend to use this.. AFAIK it'll return
something like "[/path/to/a.jar,/path/to/b.jar]".
That's exactly what I receive. I use it because I have a project that build
an ant task, and I want to test this ant task by executing it from the pom,
in the testing phase.
I use this value, to set a classpath. I use a series of echo and relplace
to format it correctly.
_
Créez gratuitement votre espace perso en ligne avec MSN Spaces !
http://spaces.msn.com/?mkt=fr-be
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Use variables in configuration of a plug in
I have tried to use ${project.compileClasspathElements} into the
configuration tag of a plugin (antrun), and it seems to work.
But when I use ${project.runtimeClasspathElements}, I only have the same
result. The pure runtime dependencies are not present in the list.
Is it a general behaviour that can be used in any plugin or is it specific
to antrun ?
Where can we found the list of defined variables ?
Why is the project.runtimeClasspathElements not set correctly? Is it a bug?
Did I made something wrong?
Thanks,
Gilles Scokart
_
Créez gratuitement votre espace perso en ligne avec MSN Spaces !
http://spaces.msn.com/?mkt=fr-be
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
