On Tue, 2003-01-21 at 09:04, [EMAIL PROTECTED] wrote: > Great! I think something about the function of Touchstone should be added > to the Wiki... I was wondering what it was. > > Okay, I updated to CVS Head, and now touchstone-goal-C and touchstone-goal-D > are failing. I went and looked at it, and it seems to be a test of getting > variables from other plugins. So, if this is only failing for me, then it > must be my setup. Is anyone else out there in Maven land finding this > plugin failing? If not, I will send the stack trace of the error.
Behaviour of this not working is evident in some stuff Bob and I were trying to do. I can get drools to build on my machine (it uses some preGoal trickery) but Bob can't. And the tests all pass for me but not for you. So we've got a subtle problem somewhere and I believe it's the order in which the plugins are processed. The inodes on my machine are giving a different plugin loading order than you or Bob. So I'll make the loading order deterministic and then track down the problem. I'm certain it's in the caching code that I've been farting around with. Thanks for being patient. > Eric > > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 20, 2003 4:12 PM > To: Turbine Maven Users List > Subject: RE: How to reference properties set in other plugins > > > On Mon, 2003-01-20 at 13:31, [EMAIL PROTECTED] wrote: > > I tried testing this: > > > > <goal name="test"> > > <j:set var="testval" > > > value="${pom.getPluginContext('maven-war-plugin').getVariable('maven.war.src > > ')}" /> > > <j:set var="genDocs" > > > value="${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.gen.do > > cs')}" /> > > <echo> > > Here is maven.war.src: > > ${pom.getPluginContext('war').getVariable('maven.war.src')} > > Here is test 2: ${testval} > > Here is test genDocs: ${genDocs} > > </echo> > > > > </goal> > > > > > > But what I get is : > > > > test: > > [echo] > > Here is maven.war.src: > > Here is test 2: > > Here is test genDocs: > > > > It doesn't seem to be populating the plugin.. I just rebuilt maven from > CVS > > HEAD a couple minutes ago... > > Again, I will repeat this for those who didn't catch it the first time. > If you find a failure make it reproducible in the touchstone so there is > a failure we can work with. > > It's here: > > http://cvs.apache.org/viewcvs.cgi/jakarta-turbine-maven/src/test/touchstone- > build/ > > I'm sure users are frustrated, but I get just as frustrated when I'm > given little to work with or expected to go digging for errors with > little snippets of purported test code with no context. I set up the > touchstone so users can put the failures somewhere we can find them. > Your reported failure may very well exist but I have no idea what your > setup is. The touchstone may very well have errors that make me think > what you're reporting is erroneous but we have to be on the same page if > I'm going to see what you see. > > I have added some simple instructions to the touchstone's maven.xml file > to try and explain how it is working. It's currently not a very scalable > setup but it's what's there right now. I will try to isolate each of the > tests in a separate jelly file that can be imported to make things > easier. > > > Eric Pugh > > > > -----Original Message----- > > From: Michal Maczka [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 20, 2003 10:47 AM > > To: 'Turbine Maven Users List' > > Subject: RE: How to reference properties set in other plugins > > > > > > I think that it is something like: > > > > > > > > > ${pom.getPluginContext('name-of-the-plugin').getVariable('name-of-variable') > > } > > > > > > Michal > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, January 20, 2003 3:33 PM > > > To: [EMAIL PROTECTED] > > > Subject: How to reference properties set in other plugins > > > > > > > > > Hi all, > > > > > > I used to be able in my maven.xml to have a proerty like this: > > > maven.war.build.dir, however, not with CVS head, I can't. > > > > > > I believe this has to do with the whole plugin namespace > > > seperation. If I > > > want to reference another plugin's properties, what is the > > > correct manner to > > > do this? > > > > > > Eric Pugh > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
