ÿþbdudney: quick question - I'm trying to pass a property to surefire and its not being replaced, any idea what I'm doing wrong? pom bits are here; http://www.rafb.net/paste/results/9wCbdX32.html [10:14am] jorg: this character © comes out mangled after the archetype is extracted [10:14am] jorg: the velocity template substitution also barfs on binary files [10:15am] trygvis: bdudney: where in the pom do you have that? [10:15am] jorg: we need a switch to toggle template substitution [10:15am] bdudney: in 'build/plugins/plugin/configuration/systemProperties/property (plugin/artifactiId = maven-surefire-plugn) [10:16am] bdudney: trygvis that is (thanks BTW) [10:16am] bdudney: trygvis: http://www.rafb.net/paste/results/tIA2BG27.html has almost all of it [10:17am] bdudney: ${version} is making it into wadi.version but the ${projet.build.directory} is not being replaced... [10:17am] kenney: are you working on cargo? [10:18am] bdudney: kenney: working on wadi, trying to test with cargo [10:18am] bdudney: kenny: you do cargo? [10:18am] kenney: sure [10:18am] kenney: vincent's working on a cargo plugin, you might want to check that sometime [10:19am] bdudney: yeah, its great but does not allow wadi to extend TC so I'm usign the JavaAPI [10:19am] bdudney: I'm trying to convince Vincent to add the ability to extend Tomcat (i.e. supply my own server.xml so I can substitue the Mangaer class for Tomcat) but he is not quite there yet [10:20am] kenney: right.. [10:20am] kenney: you could just build a tomcat distro yourself and pass that to cargo, but it seems like you're already doing that now [10:22am] bdudney: well what I've done patched the AbstractTomcatLocalConfiguration to allow me to pass in the server.xml bits I need which allows wadi to replace the TC manager class then I copy all the wadi dependencies into the propert lib dirs (server/lib, shared/lib etc) then fire up the servers deploy a test app and make sure they are clustering propertly [10:22am] bdudney: its cool, I really like cargo, I'm an old cactus fan too so cargo is natural for me... [10:23am] bdudney: trygvis: any idea about the property? [10:25am] hohi: is there any JNI support in mvn or do I have to use ant-tasks <javah/> ? [10:26am] hohi: aehm antrun not ant-task ... [10:28am] trygvis: bdudney: sorry, no [10:28am] bdudney: trygvis: thanks anyway - know anywere that documents the properties that should be replacced? [10:33am] acabrera joined the chat room. [10:39am] raphael joined the chat room. [10:40am] gastaldi joined the chat room. [10:40am] gastaldi: hey [10:40am] gastaldi: If i create a project named "A" and a subproject named "B", this means that the jar produced by B will be "a-b-1.0.jar" ? [10:41am] gastaldi: ??? [10:43am] jesse: gastaldi: no [10:44am] gastaldi: what will the name be ? [10:44am] gastaldi: the name of the project ? [10:44am] gastaldi: in my case: "b-1.0.jar" ? [10:45am] gastaldi: artifactId + version ? [10:46am] jdcasey left the chat room. (Ping timeout) [10:48am] jdcasey joined the chat room. [10:49am] jesse: gastaldi: yes [10:49am] gastaldi: ok [10:56am] jorg left the chat room. (jorg) [10:57am] jallen: whats the score with new mojo naming? we going for maven-XXX-plugin or XXX-maven-plugin? [11:00am] evenisse: XXX-maven-plugin [11:01am] jallen: cool. [11:04am] jaylow: JAR will be empty - no content was marked for inclusion! [11:04am] jaylow: what does that mean? [11:07am] lukas joined the chat room. [11:07am] gastaldi left the chat room. [11:08am] jbossruel left the chat room. (CGI:IRC) [11:14am] jaylow: un my pom can i have multiple sourceDirectory? [11:14am] bdudney: trying to debug a problem with surefire, anyone know where it gets its systemProperties from? [11:14am] bdudney: specifically how to plugins get their properties set? [11:17am] jorg joined the chat room. [11:18am] jeremy joined the chat room. [11:20am] zuk007 joined the chat room. [11:20am] zuk007 left the chat room. (CGI:IRC) [11:35am] adamc: is there support for selecting a build profile based on an environment variable? [11:40am] jeremy left the chat room. (BitchX-1.1-final ýÿ 1996-2003 Colten Edwards) [11:40am] jeremy joined the chat room. [11:48am] evenisse left the chat room. (Client closed connection) [11:48am] evenisse joined the chat room. [11:48am] pikus joined the chat room. [11:48am] pikus: a question about sycying repos... [11:49am] pikus: in http://cvs.apache.org/maven-snapshot-repository/org/apache/ there're some 'not-SNAPSHOT' jars [11:49am] pikus: avalon/excalibur ones, I'm guessing it's a 'side effect' of cocoon maveniztion [11:49am] pikus: any chance to port those changes to ibiblio? [11:53am] jallen: anyone got an old school (ie. not eclipse) checkstyle.xml config file for the maven mojo style? [11:53am] SUNYMatt left the chat room. (CGI:IRC) [11:56am] bdudney: still trying to debug prob with surefire, I'd like to find out why some <systemProperties> are not be evaluated before being passed into my tests - any one have any idea where I could look for what's going wrong. [11:56am] bdudney: for example ${version} is replaced but ${project.build.directory} is not [12:01pm] adamc: bdudney: at least you're getting some things replaced ... I'm still trying to track down why it appears no filtering is working for me [12:02pm] bdudney: argh! [12:02pm] bdudney: don't yo ujust love it adamc [12:04pm] bdudney: adamc - have you written a plugin? Do you know where/how the properties are set? [12:04pm] adamc: no, sorry, total newb. [12:04pm] bdudney: figure that would be a place to start to look at why it does not work... [12:04pm] bdudney: ah well thanks anyway - good luck [12:04pm] jaylow: its probly an xml file of some sort [12:04pm] adamc: is the pattern consistent? Like, "top level" properties? [12:04pm] bdudney: adamc http://www.rafb.net/paste/results/tIA2BG27.html is my bit that works for ${version} [12:05pm] bdudney: no it seems that some properties are explicitly looked for and others are left... [12:05pm] adamc: ouch. [12:06pm] jaylow: why are some tomcat 50 and others tomcat 55 [12:06pm] jaylow: ? [12:06pm] adamc: they're all being set in the same place, in the same way? [12:06pm] bdudney: jaylow: tomcat50 and tomcat55 are two containers that wadi supports [12:07pm] bdudney: I'm tryng to test [12:07pm] bdudney: wadi that is [12:07pm] bdudney: with cargo [12:07pm] jaylow: gotcha [12:07pm] jaylow: with both tomcat 5. and 5. [12:07pm] jaylow: er .. 5.5 [12:07pm] jaylow: i mean [12:07pm] bdudney: jaylow: any ideas why ${project.build.dir} not being replaced? [12:07pm] jaylow: it works for some and not others? [12:08pm] bdudney: yes, wadi support 5 containers at the moment (tc5, tc55, jetty5, jetty6, jboss4) we are working on Geronimo and other but we need to test [12:08pm] bdudney: no it works for ${version} but not for ${project.build.directory} [12:08pm] adamc: are version and project.build.directory defined in the same place and set in the same way? [12:08pm] adamc: (and do you have independent verification that both are set?) [12:08pm] jaylow: man i dunno [12:08pm] bdudney: adamc: both are supposed to be comming from maven... not set by us [12:08pm] bdudney: ok thanks anyway jaylow [12:09pm] adamc: ahh ... why not ${pom.___} then? [12:09pm] bdudney: jaylow: you know where/when properties are set on plugins? [12:09pm] jaylow: other than, project.build.directory.. should change on each build righgt? [12:09pm] jaylow: doesn't that increment [12:09pm] jaylow: ? [12:09pm] bdudney: well ${p.b.d} should always be 'target/' unless overriden by the user with -D [12:09pm] bdudney: at thease that is how I understand it [12:10pm] bdudney: but I'm sort of new to m2 [12:12pm] jaylow: no worries.. i am too [12:12pm] jaylow: i'd help ya [12:12pm] jaylow: but i think you've gone past my abilities [12:12pm] bdudney: jaylow: it appears that PluginParameterExpressionEvaluatorTest might have some info as to how the properties are being placed into the System.getProperties space but... [12:12pm] bdudney: ok, well thanks anyway jaylow! [12:12pm] bdudney: adamc: you get your stuff working yet? bdudney: vmassol: got time for a quick Q? [1:23pm] vmassol: hi bill [1:23pm] vmassol: shoot! [1:23pm] bdudney: http://www.rafb.net/paste/results/tIA2BG27.html is part of POM [1:23pm] bdudney: thanks BTW! [1:23pm] bdudney: in my tests I have access to wadi.version (set to ${version}) as the correct value (2.0-SNAPSHOT) but I don't have the correct value for container.config.dir [1:23pm] bdudney: container.config.dir gets the unevaluated ${project.build.directory}/test-containeers [1:24pm] bdudney: any ideas why ${version} is being evaluated and ${project.build.properties} is not? [1:25pm] vmassol: hmm.... no idea [1:26pm] bdudney: argh! say it isn't so! nooooo [1:26pm] vmassol: try #maven they may some idea [1:26pm] bdudney: or rather [1:26pm] vmassol: oops this is #maven [1:26pm] bdudney: that's were we are [1:26pm] jaylow: lol [1:26pm] vmassol: I thought we were on #cargo [1:26pm] vmassol: hehe [1:26pm] bdudney: I've asked several times today and no answer [1:26pm] bdudney: I guess everyone thinks it should work [1:27pm] bdudney: so what I was trying to do was figure out how SurefirePlugin.systemProperties gets set? [1:27pm] bdudney: perhaps that would hlep me find the problem [1:27pm] vmassol: the problem is'nt there [1:27pm] jdcasey: bdudney: they're resolved as two separate processes...version is resolved via pom interpolation, while project.build.directory is resolved as a plugin parameter expression... [1:27pm] vmassol: I have coded that part and it's simply a System.setProperty() [1:27pm] jdcasey: ${project.build.properties} doesn't exist, tho [1:27pm] jdcasey: it's ${project.properties} [1:28pm] bdudney: jdcasey: thanks for the help, where does ${project.build.directory} get set? [1:28pm] bdudney: or come from? [1:28pm] jdcasey: bdudney: <project>...<build>...<directory>target</directory></build></project> [1:28pm] jdcasey: [1:29pm] bdudney: jdcasey: sorry I'm a newbie, so what you are saying is that the surefire plugin won't have access to that property (project.build.directory)? [1:29pm] jdcasey: try 'mvn help:effective-pom' to see what the default value is, if you haven't set it. [1:29pm] bdudney: yeah, I know the default, its target, prob is I don't want to hardcode [1:29pm] jdcasey: it should have access to it [1:29pm] bdudney: any idea why its not being substituted? [1:29pm] jdcasey: it should be resolved and injected right before themojo is called [1:30pm] vmassol: jdcasey: the surefire plugin does not resolve anything AFAIK [1:30pm] bdudney: did you see the rafb from earlier? [1:30pm] jdcasey: ?? [1:30pm] jdcasey: no [1:30pm] bdudney: http://www.rafb.net/paste/results/tIA2BG27.html [1:30pm] bdudney: so the top I'm setting wadi.version to ${version} in my test wadi.version evals to 2.0-SNAPSHOT [1:30pm] bdudney: which is what I expect [1:30pm] bdudney: container.config.dir should be target/test-containers [1:31pm] bdudney: but instead is ${project.build.directory}/test-containers [1:31pm] jdcasey: looks like the configuration handling code from plexus doesn't resolve that stuff before building the map...just a guess. [1:31pm] hohi left the chat room. (KVIrc 3.2.0 'Realia') [1:31pm] jdcasey: it should do [1:31pm] bdudney: ${project.build.directory} is nto being evaluated... [1:31pm] jdcasey: ...not sure, off hand [1:32pm] trygvis: brozow: you keep on sending mail from an address that's not subscribed [1:32pm] bdudney: so where would I stop plexus to see where/what is going wrong? [1:35pm] jdcasey: bdudney, if it were me, I'd attach a debugger and set a breakpoint in o.a.m.plugin.DefaultPluginManager.executeMojo(..) in maven-core [1:35pm] kenney: bdudney: what's the string after evaluation? "" or ${...} ? [1:35pm] kenney: you said about 4 hours earlier that ${version} _was_ resolved, right? [1:36pm] bdudney: thanks jdcasey - that is the hint I was looking for [1:36pm] bdudney: kenney: ${version} is ok but ${project.build.directory} is not [1:37pm] jdcasey: ${version} is resolved during model interpolation...it's a separate step in the build, called from the project builder... [1:38pm] jdcasey: IIRC [1:38pm] kenney: it's somewhere near the merging/inheritance, right? [1:38pm] bdudney: jdcasey: should I be using ${project.version} instead of ${version} [1:38pm] jdcasey: don't think so...either way should be fine [1:38pm] kenney: maybe ${build.directory} would work.. [1:39pm] bdudney: kenney: tried that no dice [1:39pm] kenney: good [1:39pm] kenney: are the servers up again? [1:39pm] kenney: why don't i check myself.. [1:39pm] kenney: yup [1:39pm] kenney: what was the problem, DDOS? [1:39pm] jdcasey: bdudney: think I found something...can you try ${x.project.build.directory}? [1:40pm] jdcasey: that will confirm a bug if it works [1:40pm] bdudney: sure, let me check [1:40pm] jdcasey: thanks [1:42pm] jdcasey: actually, that should work, which means I need to check in this change to the plexus-utils project. [1:42pm] bdudney: jdcasey: ${x.project.build.directory}/installs is the value [1:42pm] bdudney: that I get a runtime [1:42pm] bdudney: so it just passes it right through [1:43pm] SUNYMatt left the chat room. (CGI:IRC) [1:43pm] jdcasey: hmm, so that didn't work either...how about ${project.x.build.directory}? trying to understand this, and I think I told you wrong the first time. [1:43pm] bdudney: http://www.rafb.net/paste/results/OvBgmZ23.html is my pom as I chaned it [1:43pm] bdudney: ok, rerunning [1:43pm] jdcasey: thanks [1:44pm] bdudney: http://www.rafb.net/paste/results/IG6WBz21.html [1:44pm] bdudney: as changed [1:44pm] bdudney: and the value comes through as target/installs, woooo hooo! [1:45pm] jdcasey: hmm, works? [1:45pm] jdcasey: good, I'll incorporate this fix in the release of p-u I was about to cut [1:45pm] bdudney: great! [1:46pm] bdudney: so should I always be using project.x.build.directory? seems odd or is that just a workaround? [1:47pm] jdcasey: no, definitely not [1:47pm] jdcasey: just until I can get this release done [1:48pm] jdcasey: I'm doing a release in the next 5 mins. [1:48pm] jdcasey: I'll deploy a new snapshot first, to freshen that up too [1:49pm] jdcasey: bdudney: you'll probably have to re-bootstrap maven, though... [1:50pm] jdcasey: or somehow replace the plexus-utils in ${maven.home}/core with the new copy I'm uploading now. [1:51pm] bdudney: jdcasey: thanks, 're-bootstrap maven' is not something I'm familiar with... [1:51pm] bdudney: the upload will be on ibibilio? [1:51pm] jdcasey: ok, then slice the old copy of plexus-utils out, download the new one from snapshots.maven.codehaus.org/maven2, and put it in the old one's place [1:52pm] bdudney: will do, it is uploaded yet? [1:52pm] jdcasey: bdudney, it'll be in http://snapshots.maven.codehaus.org/maven2/org/codehaus/plexus/plexus-utils/1.0.5-SNAPSHOT [1:52pm] jdcasey: let me check [1:52pm] jdcasey: not yet [1:54pm] jdcasey: apparently my net connection is not the best today... [1:55pm] bdudney: isn't that always the way [1:55pm] jdcasey: *sigh* getting closer...one log message at a time [1:55pm] bdudney: while we are waiting, how painful is it to be on the head of m2? [1:56pm] jdcasey: there...the specific version is: 1.0.5-20051207.205025-8 [1:56pm] trygvis: bdudney: define painful [1:56pm] jdcasey: [1:56pm] bdudney: [1:56pm] bdudney: well I like pain so its not so bad if its a little painful [1:56pm] bdudney: [1:56pm] jdcasey: I think it's been relatively stable lately...but I spend most of my time developing maven, not using it [1:56pm] bdudney: there are several plugins that are not working quite like I'd like them to, surefire, clover and this prob [1:56pm] jdcasey: I mean, we don't use it to its full capabilities every day...site plugin and such [1:57pm] bdudney: if I move to head many might be fixed [1:57pm] jdcasey: what version are you on? [1:57pm] bdudney: 2.0 released version... [1:57pm] jdcasey: ah [1:57pm] jdcasey: hmm [1:57pm] bdudney: you guys push a nightly? sorry for being lazy [1:57pm] bdudney: I'v ejust not chedked [1:57pm] trygvis: but it is trivial switching between versions so it's often worth a shot [1:57pm] jdcasey: wonders how you ever saw that problem with the project.build.directory... [1:57pm] trygvis: 09:39 < trygvis> 10:15 < jorg> http://maven.zones.apache.org/~maven/builds/ [1:57pm] jdcasey: we haven't started pushing nightlies yet... [1:58pm] jdcasey: yeah? [1:58pm] jdcasey: didn't know we were doing that now... [1:58pm] jdcasey: [1:58pm] jdcasey: I guess the CI build counts [1:58pm] trygvis: we've always done that [1:58pm] jdcasey: decides to stop talking now... [1:58pm] bdudney: [1:58pm] trygvis: the CI is even better than a nighly, the CI is only built if the build was successful [1:59pm] jdcasey: releasing p-u 1.0.5...WHEEE! [1:59pm] jdcasey: true enough [1:59pm] jdcasey: of course, the definition of 'successful' is only as good as our tests [2:01pm] bdudney: jdcasey: just grabbed 1.0.5-20051207.205025-8 and same issue... [2:02pm] bdudney: project.build.directory is not being evaled [2:02pm] jdcasey: hmm [2:03pm] jdcasey: looking now [2:03pm] bdudney: dir http://www.rafb.net/paste/results/ySOzyE49.html [2:03pm] bdudney: thatis the correct version right? [2:08pm] bdudney: trygvis - will running the 2.0.1-snapshot and 2.0 against the same repo cause probs? [2:08pm] dain left the chat room. (Ping timeout) [2:08pm] trygvis: nope [2:08pm] bdudney: well then I'm moving to the bleeding edge... [2:08pm] evenisse left the chat room. (Client closed connection) [2:09pm] trygvis: lets not hope it's so painful that'll make you bleed [2:09pm] trygvis: then I'd feel kinda bad [2:09pm] bdudney: already doing that because of surefire and clover plugins [2:09pm] bdudney: so no prob... [2:10pm] jaylow left the chat room. (jaylow) [2:11pm] brozow: trygvis: sorry about the mail.. I'll change my subscription [2:11pm] trygvis: [2:12pm] dain joined the chat room. [2:12pm] evenisse joined the chat room. [2:13pm] brozow: trygvis: anyway I can tell which email I'm subscribed with? [2:15pm] trygvis: you can see it from the headers on the mail you receive [2:15pm] brozow: ok thanks [2:17pm] jaylow joined the chat room. [2:24pm] bdudney: jdcasey: I'll be back in 10 to 15, if you need me to test anything just say so I'd I'll download and try it out thanks again [2:25pm] jdcasey: I've got a test case here, so I can figure it out. [2:25pm] bdudney: great, thanks again [2:27pm] brozow: trygvis: I unsubscribe and subscribe from my usual address.. please let me know if you still have problems [2:28pm] trygvis: will do [2:31pm] user57 joined the chat room. [2:47pm] jaylow left the chat room. (jaylow) [2:50pm] vmassol left the chat room. (Ping timeout) [2:52pm] jdcasey: bdudney: yeah, I verified that the problem has been fixed in my latest release...but you may have to bootstrap to 2.0.1-SNAPSHOT [2:52pm] bdudney: ok, I've got 2.0.1-SNAPSHOT from yesterday [2:52pm] bdudney: do I need the ....-8 version of plexus-util? [2:53pm] jesse: pokes trygvis [2:53pm] jdcasey: bdudney: yes [2:53pm] bdudney: great thanks, I'll run right now and let you know [2:54pm] jdcasey: cool [2:56pm] bdudney: jdcasey, you have time for one more question on these props? [2:57pm] nb left the chat room. (Leaving) [2:57pm] jesse: jdcasey: you know how releasing mojos should work? [2:58pm] jdcasey: jesse: 'mvn clean release:prepare release:perform' ? [2:58pm] jdcasey: bdudney: what's up? [2:58pm] jesse: jdcasey: dunno...I'll give it a whirl I guess [2:59pm] bdudney: thanks, the prop is evaling to target/installs as it should - I'm running from the root of my project and I'd like to have a prop that would eval to the target of the subproject with the tests, is there a way to do that? [2:59pm] jdcasey: is that not happening now? [3:00pm] bdudney: yes [3:00pm] bdudney: sorry what? its currently evaling to target/installs [3:00pm] kenney: i remember this issue from looooooong ago... [3:00pm] bdudney: oh wait spoke too soon, its still hosed with out the .x [3:01pm] kenney: isn't it just easier to use ..>target/...</ ? [3:01pm] jdcasey: slaps kenney's hand [3:01pm] jdcasey: that breaks <build><directory/> configurability [3:01pm] kenney: i know, just kidding :0 [3:01pm] jdcasey: [3:02pm] bdudney: not sure if this helps but here is my version and the stuff in core [3:02pm] bdudney: http://www.rafb.net/paste/results/QKh8Tj13.html [3:02pm] jdcasey: bdudney: can you file it, and I'll look at it later? it'd be great if you could attach a stripped down test case (zip file, whatever)... [3:02pm] bdudney: will do [3:02pm] jdcasey: looking [3:02pm] kenney: gametime! l8r! [3:02pm] bdudney: mean time the .x will continue to work for 2.0 and 2.0.1 right? [3:02pm] jdcasey: yeah, you need to remove the old version of p-e [3:03pm] jdcasey: [3:03pm] jdcasey: kenney: later [3:03pm] bdudney: by kenny, thansk for the help! [3:03pm] jdcasey: bdudney: remove that old version, and it should work w/o .x [3:03pm] bdudney: I removed the .x and got the ${project.build.directory} instead of intsall [3:03pm] bdudney: or value [3:04pm] bdudney: the old plexus-utils is renamed to .gar instead of .jar should not be picked up right? [3:04pm] jdcasey: bdudney: did you remove the old copy of plexus-utils from /core yet? [3:05pm] jdcasey: prolly not [3:05pm] jdcasey: and it's still not working, once you've renamed that file? [3:05pm] bdudney: yep [3:05pm] bdudney: it still does not work [3:06pm] jdcasey: yeah, you'll have to file it, I guess. [3:06pm] jdcasey: I can't reproduce here... [3:06pm] jdcasey: I'm using that snippet that you rafb.net/paste'd in my test, too... [3:06pm] bdudney: what snapshot are you on? [3:06pm] jdcasey: of plexus-utils? [3:06pm] bdudney: of m2 [3:06pm] bdudney: ? [3:06pm] bdudney: i have root/modules/proj1/pom.xml [3:07pm] jdcasey: I bootstrapped from trunk yesterday [3:07pm] bdudney: that is where the snipit I pasted is [3:07pm] bdudney: then we should be on same snapshot [3:07pm] bdudney: of m2 [3:07pm] bdudney: then I'm running the test from root [3:07pm] bdudney: mvn -Dmaven.test.failure.ignore=true test [3:08pm] jdcasey: you have pom.xml at the root level which references <module>modules/proj1</module> or another pom.xml in the modules dir? [3:08pm] bdudney: it references modules/proj1 [3:08pm] jdcasey: ok [3:08pm] jdcasey: I'll give it another try [3:09pm] bdudney: thanks! [3:09pm] jdcasey: your root pom.xml is <packaging>pom</packaging>, right? [3:09pm] jdcasey: (just checking) [3:11pm] bdudney: yes, sorry, watching the test [3:11pm] jdcasey: np [3:11pm] bdudney: root pom http://www.rafb.net/paste/results/uAA0aq99.html [3:12pm] bdudney: module pom http://www.rafb.net/paste/results/dyQ30d76.html [3:14pm] trygvis: http://slacksite.com/images/humour/dilbert-unix.gif [3:14pm] bdudney: trygvis [3:15pm] jdcasey: bdudney: can you try re-running with 'package' phase? [3:15pm] bdudney: sure, get rid of the .x or keep it? [3:16pm] jdcasey: without .x [3:17pm] bdudney: running now... [3:21pm] bdudney: still get the property instead of the value [3:21pm] bdudney: I've got to go, I'll post a bug on maven jira or mojo? [3:21pm] jdcasey: jira bug on mng project [3:25pm] adamc left the chat room