[jira] Created: (CONTINUUM-607) Working directory uses numbers instead of project names which is confusing because they change

: Continuum Type: Improvement Components: Core system Versions: 1.0.2 Reporter: Michael Mattox This is causing us problems for the website and also for our source paths (a project uses a src/main/config from another project). Each time we regenerate the working directory we

[jira] Commented: (MEV-345) POM for dom4j-1.4-dev-8 is invalid

[ http://jira.codehaus.org/browse/MEV-345?page=comments#action_59352 ] Michael Mattox commented on MEV-345: I didn't think of that. It must have been invalid a month or so ago when I downloaded it for the first time. I wish maven would have given

[jira] Commented: (MEV-346) xpp3 filename invalid

[ http://jira.codehaus.org/browse/MEV-346?page=comments#action_59351 ] Michael Mattox commented on MEV-346: Sorry, didn't know about maven classifiers. Must be new for 2.0. > xpp3 filename invalid > - > >

[jira] Commented: (MEV-346) xpp3 filename invalid

[ http://jira.codehaus.org/browse/MEV-346?page=comments#action_59335 ] Michael Mattox commented on MEV-346: That's not the point of this issue, the point is there is a version deployed to ibiblio which is invalid. I thought fixing it would only t

[jira] Commented: (MEV-346) xpp3 filename invalid

[ http://jira.codehaus.org/browse/MEV-346?page=comments#action_59322 ] Michael Mattox commented on MEV-346: yep I got it working with 1.1.3.4.O (that's a letter O not a number, weird naming system). I hope they implement some kind of meth

[jira] Created: (MEV-346) xpp3 filename invalid

xpp3 filename invalid - Key: MEV-346 URL: http://jira.codehaus.org/browse/MEV-346 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Michael Mattox The filename contains -RC8_min which doesn't match the version

[jira] Created: (MEV-345) POM for dom4j-1.4-dev-8 is invalid

POM for dom4j-1.4-dev-8 is invalid -- Key: MEV-345 URL: http://jira.codehaus.org/browse/MEV-345 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Michael Mattox I get this error: [WARNING] POM for

[jira] Commented: (MPCRUISECONTROL-34) FileNotFoundException with EmailPublisher

[ http://jira.codehaus.org/browse/MPCRUISECONTROL-34?page=comments#action_59102 ] Michael Mattox commented on MPCRUISECONTROL-34: --- This issue is so old I don't think it should remain open. We're using Continuum with Maven2 so for me

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_58925 ] Michael Mattox commented on MNGECLIPSE-59: -- We're really stuck on this. So far the only solution we have is to have two pom.xml, a pom.xml for the maven eclipse p

[jira] Commented: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

[ http://jira.codehaus.org/browse/MNG-1797?page=comments#action_56339 ] Michael Mattox commented on MNG-1797: - I just found this issue after running into this bug myself. I think it's pretty serious, I'm very surprised that this hasn't

[jira] Commented: (MEV-309) PicoContainer 1.0 POM invalid

[ http://jira.codehaus.org/browse/MEV-309?page=comments#action_56338 ] Michael Mattox commented on MEV-309: There is a second logo for the organization which is breaking the build too. I got it working by removing all that and putting it in my internal

[jira] Created: (MEV-309) PicoContainer 1.0 POM invalid

PicoContainer 1.0 POM invalid - Key: MEV-309 URL: http://jira.codehaus.org/browse/MEV-309 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Michael Mattox the pom contains /images/pico-logo.png which

[jira] Created: (MPCRUISECONTROL-34) FileNotFoundException with EmailPublisher

plugin 1.7 linux Reporter: Michael Mattox Attachments: config.xml, cruisecontrol.log When I use the config.xml generated by the plugin I get the attached config.xml & the output contains FileNotFoundExceptions. I searched the mailing list and found one other person with these except

RE: Looking for ideas for Maven presentation at Javapolis

This is great news that you'll be presenting Maven to Javapolis. There are two issues that I'm very interested in: - Integration with Eclipse. Last time I tried (several months ago) the eclipse plugin didn't work. As a result, we launch maven goals to copy jars into our eclipse workspace. It g