[jira] (DOXIA-513) Add support for {color}

Borut Bolcina created DOXIA-513: --- Summary: Add support for {color} Key: DOXIA-513 URL: https://jira.codehaus.org/browse/DOXIA-513 Project: Maven Doxia Issue Type: Improvement Report

[jira] Created: (MEV-639) log4j bad metadata

log4j bad metadata -- Key: MEV-639 URL: http://jira.codehaus.org/browse/MEV-639 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Borut Bolcina why there are no 1.2.14 an

[jira] Commented: (MJAVADOC-218) Ignoring links element in the configuration

[ http://jira.codehaus.org/browse/MJAVADOC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150303#action_150303 ] Borut Bolcina commented on MJAVADOC-218: I tried now by explicitly stating

[jira] Created: (MJAVADOC-218) Ignoring links element in the configuration

Ignoring links element in the configuration --- Key: MJAVADOC-218 URL: http://jira.codehaus.org/browse/MJAVADOC-218 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Reporter: Borut Bolcina

[jira] Created: (MNG-3784) Failed to validate POM for project ... at ...\release-pom.xml

Failed to validate POM for project ... at ...\release-pom.xml - Key: MNG-3784 URL: http://jira.codehaus.org/browse/MNG-3784 Project: Maven 2 Issue Type: Bug Affects Versions: 2.

[jira] Commented: (MNG-3685) Dependency can't be resolved but has been found in the reactor.

[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150291#action_150291 ] Borut Bolcina commented on MNG-3685: We are having this issue too. When doing mvn release:prepare a

[jira] Created: (MNG-3752) Preparing release fails with svn client 1.5.1 and 1.5.2

Preparing release fails with svn client 1.5.1 and 1.5.2 --- Key: MNG-3752 URL: http://jira.codehaus.org/browse/MNG-3752 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9

[jira] Commented: (WAGON-57) Error deploying 3rd party jar to company webdav repository

[ http://jira.codehaus.org/browse/WAGON-57?page=comments#action_70808 ] Borut Bolcina commented on WAGON-57: Thanks for your input Carlos. I added one more jar (commons-logging) and it works now. During upload I got lots of this messages (IN

[jira] Commented: (WAGON-57) Error deploying 3rd party jar to company webdav repository

[ http://jira.codehaus.org/browse/WAGON-57?page=comments#action_70800 ] Borut Bolcina commented on WAGON-57: I copied jakarta-slide-webdavlib-2.1.jar commons-httpclient-3.0.jar Now I am getting [ERROR] BUILD ERROR [INFO] -

[jira] Created: (WAGON-57) Error deploying 3rd party jar to company webdav repository

Error deploying 3rd party jar to company webdav repository -- Key: WAGON-57 URL: http://jira.codehaus.org/browse/WAGON-57 Project: wagon Issue Type: Bug Components: wagon-webd

[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"

[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66575 ] Borut Bolcina commented on MSITE-145: - I managed to deploy my site with scp. > Deploying site with sftp or scp creates directory with name "-p" > ---

[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"

[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66534 ] Borut Bolcina commented on MSITE-145: - With ftp and added org.apache.maven.wagon wagon-ftp under , I get C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn site

[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"

[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66451 ] Borut Bolcina commented on MSITE-145: - This is not true! I can make make directories just fine. Please read the issue carefully. The directory with name of the first parameter gets

[jira] Created: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"

Deploying site with sftp or scp creates directory with name "-p" Key: MSITE-145 URL: http://jira.codehaus.org/browse/MSITE-145 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-5 Env

[jira] Commented: (MSITE-104) There is no way to specify the input encoding of site documents

[ http://jira.codehaus.org/browse/MSITE-104?page=comments#action_65485 ] Borut Bolcina commented on MSITE-104: - I was eagerly awaiting this feature. Thanks! Writing documentation in UTF-8 works now, ... but menu items in site.xml still don't work. X

[jira] Created: (MEV-393) Published artifacts should not depend on snapshot repos & artifacts

Published artifacts should not depend on snapshot repos & artifacts --- Key: MEV-393 URL: http://jira.codehaus.org/browse/MEV-393 Project: Maven Evangelism Type: Bug Components: Invalid POM Repo

[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies as project J2EE Module Dependencies

[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_64494 ] Borut Bolcina commented on MNGECLIPSE-105: -- Hello, I am using Eclipse 3.2 RC2 with the latest (also RC2) Callisto update site modules (Web Standard Tools Version: 1.5.0.