[jira] Created: (CONTINUUM-607) Working directory uses numbers instead of project names which is confusing because they change
Working directory uses numbers instead of project names which is confusing because they change -- Key: CONTINUUM-607 URL: http://jira.codehaus.org/browse/CONTINUUM-607 Project: 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 have new numbers. So instead of "common" we have "147". I'm talking about resource files. They're not included in the jars we produce. So we have this: ../config/src/main/config for example to put our common config files in a single project. The other problem we have is the website: http://adclinux:9090/continuum/maven/working-directory/21/target/site/ You can see here 21 which should be "common". Since these change we can't bookmark the site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 more information like where it was getting the pom. Thanks for the analysis. > 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 > Assignee: Carlos Sanchez > > > I get this error: > [WARNING] POM for 'dom4j:dom4j:pom:1.4-dev-8' is invalid. It will be ignored > for > artifact resolution. Reason: Parse error reading POM. Reason: TEXT must be > imme > diately followed by END_TAG and not START_TAG (position: START_TAG seen > ... factId>junit... @47:36) > but what I don't understand is that when I look at line 47 of this file: > junit > IT'S CORRECT!!! Something really weird is going on here. I don't have any > mirrors defined so I have no idea what it is. The solution for me was to > copy these files exactly as-is from ibiblio to our local repository and it > works. Very strange. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 > - > > Key: MEV-346 > URL: http://jira.codehaus.org/browse/MEV-346 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Michael Mattox > Assignee: Carlos Sanchez > > > The filename contains -RC8_min which doesn't match the version # in the > directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 take a few seconds (less time than to debate this) and would save someone from getting stuck and having problems. > 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 > Assignee: Carlos Sanchez > > > The filename contains -RC8_min which doesn't match the version # in the > directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 method to prevent people from deploying invalid POM's. And I hope they fix the problem where that breaks the entire maven build. > 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 # in the > directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 # in the directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 'dom4j:dom4j:pom:1.4-dev-8' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: TEXT must be imme diately followed by END_TAG and not START_TAG (position: START_TAG seen ...junit... @47:36) but what I don't understand is that when I look at line 47 of this file: junit IT'S CORRECT!!! Something really weird is going on here. I don't have any mirrors defined so I have no idea what it is. The solution for me was to copy these files exactly as-is from ibiblio to our local repository and it works. Very strange. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 this issue can be closed. > FileNotFoundException with EmailPublisher > - > > Key: MPCRUISECONTROL-34 > URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-34 > Project: maven-cruisecontrol-plugin > Type: Bug > Versions: 1.7 > Environment: CC 2.2.1 maven 1.0.2 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 exceptions but no replies. > :( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 plugin and a pom-server.xml. The difference between the two is the pom.xml doesn't contain dependencies for the projects that are in the eclipse workspace. Is there a better solution? > Allow artifact resolution from workspace projects > - > > Key: MNGECLIPSE-59 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-59 > Project: Maven 2.x Extension for Eclipse > Type: New Feature > Components: Dependency Resolver > Versions: 0.0.4 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > Fix For: 1.0.0 > > > Provide artifact resolution from workspace projects, which override the same > artifact from the local or remote repositories. This would allow to work with > dependant Eclipse projects without specifying the Eclipse dependency manually. > The workspace artifact resolution would have to be specified manually, since > several Maven-Enabled projects in the same workspace could have the same > artifact and version Id. Or at least automatic resolution with an optional > override would be nice. > More comments here: > http://jira.codehaus.org/browse/MNGECLIPSE-58 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 been discussed on the mailing list. My solution was to put the excluded dependency (picocontainer) into my internal repository under a different groupId. Ugly but it works. I hope the patch can be integrated soon. > Dependency excludes apply to every subsequent dependency, not just the one it > is declared under. > > > Key: MNG-1797 > URL: http://jira.codehaus.org/browse/MNG-1797 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Reporter: David Hawkins > Attachments: MNG-1797-maven-project.patch > > > If you specify ANY dependency excludes, all dependencies after that one in > the pom will also exclude what you specified. They appear to be cumulative > on every dependency in that they bleed over into sibling dependencies. > It's easy to test if you add an exclusion to a random dependency. This > exclusion should exclude a required transitive dependency that is included by > a dependency lower in the list. You will find that the dependency lower in > the list no longer includes the required dependency because it is using the > filter you declared in the other dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 repo under a different group id due to another maven bug on the excludes being global. > 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 is invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 is invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCRUISECONTROL-34) FileNotFoundException with EmailPublisher
FileNotFoundException with EmailPublisher - Key: MPCRUISECONTROL-34 URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-34 Project: maven-cruisecontrol-plugin Type: Bug Versions: 1.7 Environment: CC 2.2.1 maven 1.0.2 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 exceptions but no replies. :( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
