[jira] Created: (MNG-3651) mvn.bat returns an incorrect error code
mvn.bat returns an incorrect error code --- Key: MNG-3651 URL: http://jira.codehaus.org/browse/MNG-3651 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.9 Reporter: Napoleon Esmundo C. Ramirez In a number of instances, mvn.bat returns zero when it should be non-zero due to a build error. -- 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] Updated: (MNG-3651) mvn.bat returns an incorrect error code
[ http://jira.codehaus.org/browse/MNG-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MNG-3651: - Attachment: MNG-3651-apache-maven.patch mvn.bat returns an incorrect error code --- Key: MNG-3651 URL: http://jira.codehaus.org/browse/MNG-3651 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.9 Reporter: Napoleon Esmundo C. Ramirez Attachments: MNG-3651-apache-maven.patch In a number of instances, mvn.bat returns zero when it should be non-zero due to a build error. -- 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] Updated: (NMAVEN-112) Unable to generate solution file from test project
[
http://jira.codehaus.org/browse/NMAVEN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated NMAVEN-112:
---
Description:
To reproduce:
mvn archetype:create -DgroupId=NMaven -DartifactId=NMaven.Test
-DarchetypeArtifactId=maven-archetype-dotnet-simple
-DarchetypeGroupId=org.apache.maven.dotnet -DarchetypeVersion=0.14
cd NMaven.Test
mvn install
mvn clean
mvn org.apache.maven.dotnet.plugins:maven-vsinstaller-plugin:install
mvn NMaven.Plugins:NMaven.Plugin.Solution.JavaBinding:Solution
This results in some build output, then an error/debug dialog:
NMaven.Plugin.Loader has encountered a problem and needs to close
Console output:
{code}
[INFO] [NMaven.Plugin.Solution.JavaBinding:Solution]
NMAVEN: Start Process = 12/10/2007 2:35:19 PM
parameterFile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml assemblyFile=C
:\Documents and Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14-mae
stro-1.5-M3__NMaven.Plugins\NMaven.Plugin.Solution.dll mojoName=NMaven.Plugin.
Solution.SolutionMojo startProcessAssembly=C:\Documents and Settings\wsmoak\.m
2\pab\gac_msil\NMaven.Plugin.Loader\0.14__NMaven.Plugin\NMaven.Pl
ugin.Loader.exe
NMAVEN: End Process = 12/10/2007 2:35:19 PM
Creating Plugin Domain Manager
ParamFile = C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml, AssemblyFile = C:\
Documents and Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14-maest
ro-1.5-M3__NMaven.Plugins\NMaven.Plugin.Solution.dll, MojoName = NMaven.Plugin.S
olution.SolutionMojo
Loading Plugin: C:\Documents and Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.
Solution\0.14__NMaven.Plugins
Creating Plugin Domain Manager
System.String:NMaven.Model.Pom.Model
System.String:System.String
NMaven.Model.Pom.Model:NMaven.Model.Pom.Model
System.String:NMaven.Model.Pom.Model
System.String:System.String
[ERROR]
[ERROR] Unhandled Exception: System.IO.FileNotFoundException: Could not load fil
e or assembly 'NMaven.Solution, Version=0.14.0.0, Culture=neutral, PublicKeyToke
n=null' or one of its dependencies. The system cannot find the file specified.
[ERROR] File name: 'NMaven.Solution, Version=0.14.0.0, Culture=neutral, PublicKe
yToken=null'
[ERROR]at NMaven.Plugin.Solution.SolutionMojo.Execute()
[ERROR]at NMaven.Plugin.AbstractMojo.Execute()
[ERROR]at NMaven.Plugin.Loader.PluginLoader.Main(String[] args)
[ERROR]
[ERROR] WRN: Assembly binding logging is turned OFF.
[ERROR] To enable assembly bind failure logging, set the registry value [HKLM\So
ftware\Microsoft\Fusion!EnableLog] (DWORD) to 1.
[ERROR] Note: There is some performance penalty associated with assembly bind
failure logging.
[ERROR] To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].
[ERROR]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] NMAVEN-xxx-000
Embedded error: NMAVEN-063-000: Execution Path = C:\Documents and Settings\wsmoa
k\.m2\pab\gac_msil\NMaven.Plugin.Runner\0.14__NMaven.Plugin, Comm
and = [parameterFile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml, assemblyF
ile=C:\Documents and Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.1
4__NMaven.Plugins\NMaven.Plugin.Solution.dll, mojoName=NMaven.Plu
gin.Solution.SolutionMojo, startProcessAssembly=C:\Documents and Settings\wsmoak
\.m2\pab\gac_msil\NMaven.Plugin.Loader\0.14__NMaven.Plugin\NMaven
.Plugin.Loader.exe]
NMAVEN-040-001: Could not execute: Command = NMaven.Plugin.Runner.exe parameterF
ile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml assemblyFile=C:\Documents
and Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14_
_NMaven.Plugins\NMaven.Plugin.Solution.dll mojoName=NMaven.Plugin.Solution.Solu
tionMojo startProcessAssembly=C:\Documents and Settings\wsmoak\.m2\pab\gac_msil
\NMaven.Plugin.Loader\0.14__NMaven.Plugin\NMaven.Plugin.Loader.ex
e, Result = 0
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 24 seconds
[INFO] Finished at: Mon Dec 10 14:36:15 MST 2007
[INFO] Final Memory: 5M/12M
[INFO]
C:\Temp\NMaven.Test
{code}
was:
To reproduce:
mvn archetype:create -DgroupId=NMaven -DartifactId=NMaven.Test
-DarchetypeArtifactId=maven-archetype-dotnet-simple
-DarchetypeGroupId=org.apache.maven.dotnet
-DarchetypeVersion=0.14-maestro-1.5-M3
cd NMaven.Test
mvn install
mvn clean
mvn org.apache.maven.dotnet.plugins:maven-vsinstaller-plugin:install
mvn NMaven.Plugins:NMaven.Plugin.Solution.JavaBinding:Solution
This results in some build output, then an error/debug dialog:
NMaven.Plugin.Loader has encountered a
[jira] Created: (MRELEASE-340) Don't store the scm password in plaintext in release.properties
Don't store the scm password in plaintext in release.properties --- Key: MRELEASE-340 URL: http://jira.codehaus.org/browse/MRELEASE-340 Project: Maven 2.x Release Plugin Issue Type: Improvement Reporter: Napoleon Esmundo C. Ramirez Priority: Minor The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time. -- 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] Updated: (MRM-694) Virtual repositories or repository grouping
[ http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-694: Attachment: MRM-694-archiva-configuration.patch patch containing a utility method for getting the repository groups as a MapString repositoryId, RepositoryGroupConfiguration Virtual repositories or repository grouping --- Key: MRM-694 URL: http://jira.codehaus.org/browse/MRM-694 Project: Archiva Issue Type: New Feature Components: repository interface Reporter: Maria Odea Ching Fix For: 1.1 Attachments: MRM-694-archiva-configuration.patch, MRM-694-web-interface.patch A number of managed repositories can be grouped together with that group having only one url. So you only need to specify that url in the settings.xml file and when Archiva receives a request via that url, it would look for that artifact from the repositories belonging to that group. More details are dicussed here: http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879 -- 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: (MRM-694) Virtual repositories or repository grouping
[ http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131880#action_131880 ] Napoleon Esmundo C. Ramirez commented on MRM-694: - The following test cases are handled: 1. Accessing a valid repository group root url (e.g. http://machine.com/repository/repository-group/) returns a Bad Request (HTTP 400) 2. Accessing an invalid repository group root url is forwarded to managed repository checking 3. Accessing an artifact in a valid repository group will iterate over the managed repositories in the repository group 3.a. If an invalid managed repository is encountered (managed repository doesn't exist), a Not Found (HTTP 404) is returned and the iteration is broken 3.b. If an artifact is not found in a valid managed repository (after proxying, etc.), a Not Found (HTTP 404) is set but not returned yet, the iteration continues to the next managed repository. The Not Found (HTTP 404) is returned after exhausting all valid managed repositories 3.c. If an artifact is found in a valid managed repository, the artifact is returned, the iteration is broken and any Not Found (HTTP 404) is disregarded 4. Accessing a valid repository group with any http write method returns a Bad Request (HTTP 400) Virtual repositories or repository grouping --- Key: MRM-694 URL: http://jira.codehaus.org/browse/MRM-694 Project: Archiva Issue Type: New Feature Components: repository interface Reporter: Maria Odea Ching Fix For: 1.1 Attachments: MRM-694-archiva-configuration.patch, MRM-694-archiva-webapp.patch, MRM-694-archiva-webdav.patch, MRM-694-web-interface.patch A number of managed repositories can be grouped together with that group having only one url. So you only need to specify that url in the settings.xml file and when Archiva receives a request via that url, it would look for that artifact from the repositories belonging to that group. More details are dicussed here: http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879 -- 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] Issue Comment Edited: (MRM-694) Virtual repositories or repository grouping
[ http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131880#action_131880 ] nramirez edited comment on MRM-694 at 4/23/08 8:35 AM: -- The following test cases are handled: 1. Accessing a valid repository group root url (e.g. http://machine.com/repository/repository-group/) returns a Bad Request (HTTP 400) 2. Accessing an invalid repository group root url is forwarded to managed repository checking 3. Accessing an artifact in a valid repository group will iterate over the managed repositories in the repository group 3.a. If an invalid managed repository is encountered (managed repository doesn't exist), a Not Found (HTTP 404) is returned and the iteration is broken 3.b. If an artifact is not found in a valid managed repository (after proxying, etc.), a Not Found (HTTP 404) is set but not returned yet, the iteration continues to the next managed repository. The Not Found (HTTP 404) is returned after exhausting all valid managed repositories 3.c. If an artifact is found in a valid managed repository, the artifact is returned, the iteration is broken and any Not Found (HTTP 404) is disregarded 4. Accessing a valid repository group with any http write method returns a Bad Request (HTTP 400) was (Author: nramirez): The following test cases are handled: 1. Accessing a valid repository group root url (e.g. http://machine.com/repository/repository-group/) returns a Bad Request (HTTP 400) 2. Accessing an invalid repository group root url is forwarded to managed repository checking 3. Accessing an artifact in a valid repository group will iterate over the managed repositories in the repository group 3.a. If an invalid managed repository is encountered (managed repository doesn't exist), a Not Found (HTTP 404) is returned and the iteration is broken 3.b. If an artifact is not found in a valid managed repository (after proxying, etc.), a Not Found (HTTP 404) is set but not returned yet, the iteration continues to the next managed repository. The Not Found (HTTP 404) is returned after exhausting all valid managed repositories 3.c. If an artifact is found in a valid managed repository, the artifact is returned, the iteration is broken and any Not Found (HTTP 404) is disregarded 4. Accessing a valid repository group with any http write method returns a Bad Request (HTTP 400) Virtual repositories or repository grouping --- Key: MRM-694 URL: http://jira.codehaus.org/browse/MRM-694 Project: Archiva Issue Type: New Feature Components: repository interface Reporter: Maria Odea Ching Fix For: 1.1 Attachments: MRM-694-archiva-configuration.patch, MRM-694-archiva-webapp.patch, MRM-694-archiva-webdav.patch, MRM-694-web-interface.patch A number of managed repositories can be grouped together with that group having only one url. So you only need to specify that url in the settings.xml file and when Archiva receives a request via that url, it would look for that artifact from the repositories belonging to that group. More details are dicussed here: http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879 -- 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] Updated: (NMAVEN-117) The project generated by the NMaven netexecutable archetype defaults to version 0.14-incubating-SNAPSHOT when it should be 1.0-SNAPSHOT
[ http://jira.codehaus.org/browse/NMAVEN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-117: --- Summary: The project generated by the NMaven netexecutable archetype defaults to version 0.14-incubating-SNAPSHOT when it should be 1.0-SNAPSHOT (was: The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT) The project generated by the NMaven netexecutable archetype defaults to version 0.14-incubating-SNAPSHOT when it should be 1.0-SNAPSHOT --- Key: NMAVEN-117 URL: http://jira.codehaus.org/browse/NMAVEN-117 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-117.patch The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT. It should probably be filtered out. -- 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] Created: (NMAVEN-114) Jetty is pulled out by plugins, even if it isn't needed
Jetty is pulled out by plugins, even if it isn't needed --- Key: NMAVEN-114 URL: http://jira.codehaus.org/browse/NMAVEN-114 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Jetty isn't necessary in most of the plugins, but it is still downloaded as a dependency of the plugins. -- 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] Updated: (NMAVEN-114) Jetty is pulled out by plugins, even if it isn't needed
[ http://jira.codehaus.org/browse/NMAVEN-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-114: --- Attachment: NMAVEN-114.patch The patch removes the jetty dependency from the plugins as it isn't necessary at all. Diff'd against the STABLE-2007-12-16 tag. Jetty is pulled out by plugins, even if it isn't needed --- Key: NMAVEN-114 URL: http://jira.codehaus.org/browse/NMAVEN-114 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: NMAVEN-114.patch Jetty isn't necessary in most of the plugins, but it is still downloaded as a dependency of the plugins. -- 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] Created: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
Using the systemPath element in a dependecy doesn't work Key: NMAVEN-115 URL: http://jira.codehaus.org/browse/NMAVEN-115 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Using a system scope w/ a systemPath element in a dependency won't work, NMaven always points to local repo. -- 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] Updated: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
[ http://jira.codehaus.org/browse/NMAVEN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-115: --- Attachment: NMAVEN-115.patch Patch implements the systemPath element in the dependency element. Using the systemPath element in a dependecy doesn't work Key: NMAVEN-115 URL: http://jira.codehaus.org/browse/NMAVEN-115 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-115.patch Using a system scope w/ a systemPath element in a dependency won't work, NMaven always points to local repo. -- 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] Updated: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
[ http://jira.codehaus.org/browse/NMAVEN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-115: --- Attachment: NMAVEN-115-vs-support.patch The patch implements the systemPath element for the VS support. Using the systemPath element in a dependecy doesn't work Key: NMAVEN-115 URL: http://jira.codehaus.org/browse/NMAVEN-115 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-115-vs-support.patch, NMAVEN-115.patch Using a system scope w/ a systemPath element in a dependency won't work, NMaven always points to local repo. -- 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] Created: (NMAVEN-116) Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory --- Key: NMAVEN-116 URL: http://jira.codehaus.org/browse/NMAVEN-116 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez If *.resx file is found in the source directory of nmaven project, Solution.JavaBinding will generate the reference entry in *.csproj/.*vbproj file. -- 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] Updated: (NMAVEN-117) The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT
[ http://jira.codehaus.org/browse/NMAVEN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-117: --- Attachment: NMAVEN-117.patch The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT --- Key: NMAVEN-117 URL: http://jira.codehaus.org/browse/NMAVEN-117 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-117.patch The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT. It should probably be filtered out. -- 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] Created: (NMAVEN-117) The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT
The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT --- Key: NMAVEN-117 URL: http://jira.codehaus.org/browse/NMAVEN-117 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT. It should probably be filtered out. -- 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] Updated: (NMAVEN-116) Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
[ http://jira.codehaus.org/browse/NMAVEN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-116: --- Attachment: NMAVEN-116.patch Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory --- Key: NMAVEN-116 URL: http://jira.codehaus.org/browse/NMAVEN-116 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-116.patch If *.resx file is found in the source directory of nmaven project, Solution.JavaBinding will generate the reference entry in *.csproj/.*vbproj file. -- 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] Updated: (NMAVEN-118) Errors from .NET plugins are not recognized
[ http://jira.codehaus.org/browse/NMAVEN-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-118: --- Attachment: NMAVEN-118.patch Patch used p.WaitForExit() to allow process to finish. Errors from .NET plugins are not recognized --- Key: NMAVEN-118 URL: http://jira.codehaus.org/browse/NMAVEN-118 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Attachments: NMAVEN-118.patch Errors are not detected because the process isn't allowed to finish. -- 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] Created: (NMAVEN-118) Errors from .NET plugins are not recognized
Errors from .NET plugins are not recognized --- Key: NMAVEN-118 URL: http://jira.codehaus.org/browse/NMAVEN-118 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Errors are not detected because the process isn't allowed to finish. -- 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] Created: (MPATCH-1) Support deletion of empty files after the patches have been applied
Support deletion of empty files after the patches have been applied --- Key: MPATCH-1 URL: http://jira.codehaus.org/browse/MPATCH-1 Project: Maven 2.x Patch Plugin Issue Type: New Feature Reporter: Napoleon Esmundo C. Ramirez Priority: Minor By default, the patch command does not delete empty files after the patches have been applied. Compilation breaks on empty java sources. According to the man pages, as a workaround, the to be deleted could be compared to an empty file dated the Epoch (1970-01-01 00:00:00 UTC) if it conforms to POSIX. Or better yet, use the -E or --remove-empty-files option to be sure. -- 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] Updated: (MPATCH-1) Support deletion of empty files after the patches have been applied
[
http://jira.codehaus.org/browse/MPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated MPATCH-1:
-
Attachment: MPATCH-1.patch
Attached MPATCH-1.patch. It adds support to the -E option and can be used as:
{code}
plugin
artifactIdmaven-patch-plugin/artifactId
configuration
...
removeEmptyFilestrue/removeEmptyFiles
...
/configuration
/plugin
{code}
Support deletion of empty files after the patches have been applied
---
Key: MPATCH-1
URL: http://jira.codehaus.org/browse/MPATCH-1
Project: Maven 2.x Patch Plugin
Issue Type: New Feature
Reporter: Napoleon Esmundo C. Ramirez
Priority: Minor
Attachments: MPATCH-1.patch
By default, the patch command does not delete empty files after the patches
have been applied. Compilation breaks on empty java sources. According to
the man pages, as a workaround, the to be deleted could be compared to an
empty file dated the Epoch (1970-01-01 00:00:00 UTC) if it conforms to POSIX.
Or better yet, use the -E or --remove-empty-files option to be sure.
--
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] Updated: (CONTINUUM-1644) Test failures occur in tagged sources
[
http://jira.codehaus.org/browse/CONTINUUM-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated CONTINUUM-1644:
---
Attachment: CONTINUUM-1644.patch
This patch locks the version of the maven-surefire-plugin used.
Test failures occur in tagged sources
-
Key: CONTINUUM-1644
URL: http://jira.codehaus.org/browse/CONTINUUM-1644
Project: Continuum
Issue Type: Bug
Affects Versions: 1.1
Reporter: Napoleon Esmundo C. Ramirez
Attachments: CONTINUUM-1644.patch
I checked out the sources of continuum 1.1 and tried to build it, but I
encountered a test failure in continuum-api:
{code}
$ svn co http://svn.apache.org/repos/asf/maven/continuum/tags/continuum-1.1
$ cd continuum-1.1
$ mvn clean install
{code}
{code}
[INFO]
[INFO] Building Continuum API
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/nramirez/src/continuum-1.1/continuum-api/target
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 37 source files to
/home/nramirez/src/continuum-1.1/continuum-api/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 2 source files to
/home/nramirez/src/continuum-1.1/continuum-api/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/nramirez/src/continuum-1.1/continuum-api/target/surefire-reports
---
T E S T S
---
Running
org.apache.maven.continuum.project.builder.AbstractContinuumProjectBuilderTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec
FAILURE!
Running org.apache.maven.continuum.utils.ContinuumUtilsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Results :
Failed tests:
warning(junit.framework.TestSuite$1)
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to
/home/nramirez/src/continuum-1.1/continuum-api/target/surefire-reports for
the individual test results.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 21 seconds
[INFO] Finished at: Fri Feb 01 17:19:29 PHT 2008
[INFO] Final Memory: 28M/115M
[INFO]
{code}
I think this was caused by using maven-surefire-plugin:2.4, when it builds
with version 2.3 before.
--
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] Created: (MRM-669) Test failure occurs when building the bundled sources of archiva
Test failure occurs when building the bundled sources of archiva
Key: MRM-669
URL: http://jira.codehaus.org/browse/MRM-669
Project: Archiva
Issue Type: Bug
Components: build
Affects Versions: 1.0
Environment: Fedora 8, JDK 1.5, Maven 2.0.7
Reporter: Napoleon Esmundo C. Ramirez
Attachments: archiva.log
I downloaded the bundled sources of archiva from
http://maven.apache.org/archiva and extracted it in some directory. After
that, I executed `mvn clean install` inside the extracted source directory,
then I encountered a test failure somewhere in the archiva-repository-layer:
{code}
---
Test set: org.apache.maven.archiva.repository.scanner.RepositoryScannerTest
---
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.535 sec
FAILURE!
testDefaultRepositoryScanner(org.apache.maven.archiva.repository.scanner.RepositoryScannerTest)
Time elapsed: 0.11 sec FAILURE!
junit.framework.AssertionFailedError: Processed Count (of invalid items)
expected:6 but was:5
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:201)
at
org.apache.maven.archiva.repository.scanner.RepositoryScannerTest.testDefaultRepositoryScanner(RepositoryScannerTest.java:219)
{code}
I attached my build log as well.
--
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: (MRM-598) Validation error on new repository creation
[ http://jira.codehaus.org/browse/MRM-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114201 ] Napoleon Esmundo C. Ramirez commented on MRM-598: - I can't replicate this issue too. Maybe you can provide us the exact steps you did and the values you used when you encountered this problem? Validation error on new repository creation --- Key: MRM-598 URL: http://jira.codehaus.org/browse/MRM-598 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-4 Environment: Win Server 2003 Reporter: Federico Dal Maso Assignee: Maria Odea Ching Fix For: 1.0 When I try to create a new snapshot repository by web interface I obtain this validation error: Repository Purge By Days Older Than needs to be between 0 and 1000. even if field is correctly set to 30 It is impossible to create a new repository! -- 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] Updated: (CONTINUUM-761) Ability to delete results
[ http://jira.codehaus.org/browse/CONTINUUM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated CONTINUUM-761: -- Attachment: CONTINUUM-761-nramirez.patch The patch was implemented on trunk r555168. Multiple BuildResults can now be deleted in the Build Results page and individually in the Build Result page. Ability to delete results - Key: CONTINUUM-761 URL: http://jira.codehaus.org/browse/CONTINUUM-761 Project: Continuum Issue Type: New Feature Components: Core system Affects Versions: 1.0.3 Reporter: Srinivas Pavani Fix For: 1.1-beta-2 Attachments: CONTINUUM-761-nramirez.patch There needs to be a way to delete old results. Especially useful when doing frequent builds and for cleaning up failed build results. -- 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] Work stopped: (MRM-358) Update Consumers button in Database - Artifact Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-358 stopped by Napoleon Esmundo C. Ramirez. Update Consumers button in Database - Artifact Scanning doesn't work Key: MRM-358 URL: http://jira.codehaus.org/browse/MRM-358 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 1) Log in as admin. 2) Click the Database button in the left menu under Administration. 3) In Database - Unprocessed Artifacts Scanning, uncheck validate-repository-metadata to disable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-repository-metadata is still enabled. Note: Try the same procedure in Database - Artifact Cleanup Scanning. The changes made will not be saved. -- 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] Updated: (MRM-358) Update Consumers button in Database - Artifact Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-358: Attachment: MRM-358-archiva-webapp.patch The code in trunk doesn't do anything yet. The patch includes working stuff, updates the cron and consumers. Dunno what the Update Database button does. Update Consumers button in Database - Artifact Scanning doesn't work Key: MRM-358 URL: http://jira.codehaus.org/browse/MRM-358 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 Attachments: MRM-358-archiva-webapp.patch 1) Log in as admin. 2) Click the Database button in the left menu under Administration. 3) In Database - Unprocessed Artifacts Scanning, uncheck validate-repository-metadata to disable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-repository-metadata is still enabled. Note: Try the same procedure in Database - Artifact Cleanup Scanning. The changes made will not be saved. -- 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] Work started: (MRM-357) Update Consumers button in Repository Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-357 started by Napoleon Esmundo C. Ramirez. Update Consumers button in Repository Scanning doesn't work --- Key: MRM-357 URL: http://jira.codehaus.org/browse/MRM-357 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 1) Log in as admin. 2) Click the Repository Scanning button in the left menu under Administration. 3) In Repository Scanning - Consumers of Known Content, check validate-checksums to enable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-checksums is still disabled. -- 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] Updated: (MRM-357) Update Consumers button in Repository Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-357: Attachment: MRM-357-archiva-webapp.patch Patch contains the fix that updates the consumers in the Repository Scanning page. Update Consumers button in Repository Scanning doesn't work --- Key: MRM-357 URL: http://jira.codehaus.org/browse/MRM-357 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 Attachments: MRM-357-archiva-webapp.patch 1) Log in as admin. 2) Click the Repository Scanning button in the left menu under Administration. 3) In Repository Scanning - Consumers of Known Content, check validate-checksums to enable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-checksums is still disabled. -- 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] Work stopped: (MRM-357) Update Consumers button in Repository Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-357 stopped by Napoleon Esmundo C. Ramirez. Update Consumers button in Repository Scanning doesn't work --- Key: MRM-357 URL: http://jira.codehaus.org/browse/MRM-357 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 Attachments: MRM-357-archiva-webapp.patch 1) Log in as admin. 2) Click the Repository Scanning button in the left menu under Administration. 3) In Repository Scanning - Consumers of Known Content, check validate-checksums to enable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-checksums is still disabled. -- 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] Work started: (MRM-358) Update Consumers button in Database - Artifact Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-358 started by Napoleon Esmundo C. Ramirez. Update Consumers button in Database - Artifact Scanning doesn't work Key: MRM-358 URL: http://jira.codehaus.org/browse/MRM-358 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Dawn Angelito Assignee: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.0-alpha-2 1) Log in as admin. 2) Click the Database button in the left menu under Administration. 3) In Database - Unprocessed Artifacts Scanning, uncheck validate-repository-metadata to disable it. 4) Click the Update Consumers button. Once the page is refreshed, notice that validate-repository-metadata is still enabled. Note: Try the same procedure in Database - Artifact Cleanup Scanning. The changes made will not be saved. -- 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] Created: (CONTINUUM-1290) Project ID is not validated when adding a Project Group
Project ID is not validated when adding a Project Group --- Key: CONTINUUM-1290 URL: http://jira.codehaus.org/browse/CONTINUUM-1290 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Napoleon Esmundo C. Ramirez Steps to reproduce: 1. Go to Continuum. 2. Add a Project Group. 3. Use only spaces in Project Group Name and Id. 4. Hit Save. -- 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] Updated: (CONTINUUM-1290) Project ID is not validated when adding a Project Group
[ http://jira.codehaus.org/browse/CONTINUUM-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1290: --- Attachment: CONTINUUM-1290-continuum-webapp.patch The patch validates the Project Group ID for spaces, an illegal value. Project ID is not validated when adding a Project Group --- Key: CONTINUUM-1290 URL: http://jira.codehaus.org/browse/CONTINUUM-1290 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-1290-continuum-webapp.patch Steps to reproduce: 1. Go to Continuum. 2. Add a Project Group. 3. Use only spaces in Project Group Name and Id. 4. Hit Save. -- 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] Created: (CONTINUUM-1289) Sorting Usernames in Build Management's Project Group member list does not work in Firefox 2
Sorting Usernames in Build Management's Project Group member list does not work in Firefox 2 Key: CONTINUUM-1289 URL: http://jira.codehaus.org/browse/CONTINUUM-1289 Project: Continuum Issue Type: Bug Components: Web interface Environment: Firefox 2 Reporter: Napoleon Esmundo C. Ramirez -- 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] Updated: (CONTINUUM-1289) Sorting Usernames in Build Management's Project Group member list does not work in Firefox 2
[ http://jira.codehaus.org/browse/CONTINUUM-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1289: --- Attachment: CONTINUUM-1289-continuum-webapp.patch The patch replaces sortlist.submit() with the more standard document.forms['sortlist'].submit() Sorting Usernames in Build Management's Project Group member list does not work in Firefox 2 Key: CONTINUUM-1289 URL: http://jira.codehaus.org/browse/CONTINUUM-1289 Project: Continuum Issue Type: Bug Components: Web interface Environment: Firefox 2 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-1289-continuum-webapp.patch -- 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] Created: (CONTINUUM-1264) Editing a Project Group's name to an empty string generates an exception
Editing a Project Group's name to an empty string generates an exception Key: CONTINUUM-1264 URL: http://jira.codehaus.org/browse/CONTINUUM-1264 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Napoleon Esmundo C. Ramirez To replicate (assuming the user has sufficient roles): 1. Create a project group (name=asdf, id=asdf) 2. Edit a project group, change name into Result: Caused by: org.codehaus.plexus.rbac.profile.RoleProfileException: invalid role at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:405) at org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.renameDynamicRole(DefaultRoleProfileManager.java:134) at org.apache.maven.continuum.web.action.ProjectGroupAction.save(ProjectGroupAction.java:262) ... 78 more Caused by: org.codehaus.plexus.security.rbac.RbacObjectInvalidException: Resource.identifier must not be empty. at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:123) at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:110) at org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.saveResource(JdoRbacManager.java:458) at org.codehaus.plexus.security.authorization.rbac.store.cached.CachedRbacManager.saveResource(CachedRbacManager.java:662) at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:381) ... 80 more -- 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] Updated: (CONTINUUM-1264) Editing a Project Group's name to an empty string generates an exception
[ http://jira.codehaus.org/browse/CONTINUUM-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1264: --- Attachment: CONTINUUM-1264-continuum-webapp.patch Attached patch contains a quick fix for validating the empty string. Editing a Project Group's name to an empty string generates an exception Key: CONTINUUM-1264 URL: http://jira.codehaus.org/browse/CONTINUUM-1264 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-1264-continuum-webapp.patch To replicate (assuming the user has sufficient roles): 1. Create a project group (name=asdf, id=asdf) 2. Edit a project group, change name into Result: Caused by: org.codehaus.plexus.rbac.profile.RoleProfileException: invalid role at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:405) at org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.renameDynamicRole(DefaultRoleProfileManager.java:134) at org.apache.maven.continuum.web.action.ProjectGroupAction.save(ProjectGroupAction.java:262) ... 78 more Caused by: org.codehaus.plexus.security.rbac.RbacObjectInvalidException: Resource.identifier must not be empty. at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:123) at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:110) at org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.saveResource(JdoRbacManager.java:458) at org.codehaus.plexus.security.authorization.rbac.store.cached.CachedRbacManager.saveResource(CachedRbacManager.java:662) at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:381) ... 80 more -- 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: (CONTINUUM-1264) Editing a Project Group's name to an empty string generates an exception
[ http://jira.codehaus.org/browse/CONTINUUM-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95454 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-1264: I forgot to paste the main exception, here it is: org.apache.maven.continuum.ContinuumException: unable to rename the project group at org.apache.maven.continuum.web.action.ProjectGroupAction.save(ProjectGroupAction.java:270) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) Editing a Project Group's name to an empty string generates an exception Key: CONTINUUM-1264 URL: http://jira.codehaus.org/browse/CONTINUUM-1264 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-1264-continuum-webapp.patch To replicate (assuming the user has sufficient roles): 1. Create a project group (name=asdf, id=asdf) 2. Edit a project group, change name into Result: Caused by: org.codehaus.plexus.rbac.profile.RoleProfileException: invalid role at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:405) at org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.renameDynamicRole(DefaultRoleProfileManager.java:134) at org.apache.maven.continuum.web.action.ProjectGroupAction.save(ProjectGroupAction.java:262) ... 78 more Caused by: org.codehaus.plexus.security.rbac.RbacObjectInvalidException: Resource.identifier must not be empty. at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:123) at org.codehaus.plexus.security.rbac.RBACObjectAssertions.assertValid(RBACObjectAssertions.java:110) at org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.saveResource(JdoRbacManager.java:458) at org.codehaus.plexus.security.authorization.rbac.store.cached.CachedRbacManager.saveResource(CachedRbacManager.java:662) at org.codehaus.plexus.rbac.profile.AbstractDynamicRoleProfile.renameRole(AbstractDynamicRoleProfile.java:381) ... 80 more -- 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: (MRM-326) Adding/Editing repositories doesn't have validation
[ http://jira.codehaus.org/browse/MRM-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95372 ] Napoleon Esmundo C. Ramirez commented on MRM-326: - Though adding a repository using invalid values appears to be harmless, no repository added, it should still notify the user of invalid inputs. Adding/Editing repositories doesn't have validation --- Key: MRM-326 URL: http://jira.codehaus.org/browse/MRM-326 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: A. Adding a repository 1. Click the Repositories link in the left navigation menu 2. Click the Add Repository link in the upper right part of the page 3. Enter invalid values in Identifier, Name, Directory or URL, empty Strings 4. Click the Add Repository button Result: Repositories Administration page is displayed, no repository is added Expected Result: Validation errors B. Editing a repository 1. Click the Repositories link in the left navigation menu 2. Click the Edit Repository link in the same row as the repository's header 3. Enter invalid values in Name, Directory or URL, empty Strings and using default values for Type and Cron 4. Click the Update Repository button Result: Repositories Administration page displayed, repository is updated Expected Result: Validation errors -- 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] Created: (MRM-327) Adding/Editing network proxies doesn't have validation
Adding/Editing network proxies doesn't have validation -- Key: MRM-327 URL: http://jira.codehaus.org/browse/MRM-327 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: A. Adding a network proxy 1. Click the Network Proxies link in the left navigation menu 2. Click the Add Network Proxy link in the upper right part of the page 3. Enter invalid values in Identifier, Protocol, Hostname and Port, empty Strings 4. Click the Add Network Proxy button Result: Network Proxies Administration page displayed, network proxy (identifier=, protocol=, hostname=, port=8080) added Expected Result: Validation errors B. Editing a network proxy 1. Click the Network Proxies link in the left navigation menu 2. Click the Edit Network Proxy link in the same row as the network proxy's header 3. Enter invalid values in Protocol, Hostname and Port, empty Strings 4. Click the Save Network Proxy button Result: Network Proxies Administration page displayed, network proxy updated into (protocol=, hostname=, port=8080) Expected Result: Validation errors -- 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] Created: (MRM-328) Unable to delete network proxies
Unable to delete network proxies Key: MRM-328 URL: http://jira.codehaus.org/browse/MRM-328 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: 1. Click the Network Proxies link in the left navigation menu 2. Click on the Delete Network Proxy link in the same row as the repository's header 3. Click the Delete button Result: Nothing happens, user stays at the same page. Expected Result: Network Proxies Administration page displayed, network proxy deleted -- 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] Created: (MRM-329) The Reports link gives an HTTP 500
The Reports link gives an HTTP 500 -- Key: MRM-329 URL: http://jira.codehaus.org/browse/MRM-329 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez Clicking the Reports link in the side navigation menu displays the following (edited/snipped stacktrace): HTTP ERROR: 500 RequestURI=/admin/reports.action Caused by: javax.el.PropertyNotFoundException: The class 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have the property 'groupId'. at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) at com.sun.el.parser.AstValue.getValue(AstValue.java:118) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) at org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) at org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) at org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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] Created: (MRM-330) Searching gives an HTTP 500
Searching gives an HTTP 500 --- Key: MRM-330 URL: http://jira.codehaus.org/browse/MRM-330 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: 1. Click the Search link in the left navigation menu 2. Enter any input valid or invalid 3. Click the Submit button Result (snipped): HTTP ERROR: 500 RequestURI=/quickSearch.action java.lang.IllegalArgumentException: Only supports managed repositories. at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndexFactory.toIndexDir(LuceneRepositoryContentIndexFactory.java:77) at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndexFactory.createBytecodeIndex(LuceneRepositoryContentIndexFactory.java:50) at org.apache.maven.archiva.indexer.search.DefaultCrossRepositorySearch.getBytecodeIndexes(DefaultCrossRepositorySearch.java:173) at org.apache.maven.archiva.indexer.search.DefaultCrossRepositorySearch.searchForTerm(DefaultCrossRepositorySearch.java:91) at org.apache.maven.archiva.web.action.SearchAction.quickSearch(SearchAction.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) -- 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] Created: (MRM-331) Finding an Artifact gives an HTTP 500
Finding an Artifact gives an HTTP 500 - Key: MRM-331 URL: http://jira.codehaus.org/browse/MRM-331 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: A. Using any existing file 1. Click the Find Artifact link in the left navigation menu 2. Enter a valid input in Search for text area, existing file 3. Click the Go! button B. Using any checksum 1. Click the Find Artifact link in the left navigation menu 2. Enter valid/invalid input in Checksum text area 3. Click the Go! button Result (snipped): HTTP ERROR: 500 RequestURI=/checksumSearch.action java.lang.NullPointerException at org.apache.maven.archiva.web.action.SearchAction.findArtifact(SearchAction.java:103) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) -- 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] Created: (MRM-332) Adding a Proxy Connector displays a blank page
Adding a Proxy Connector displays a blank page -- Key: MRM-332 URL: http://jira.codehaus.org/browse/MRM-332 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: 1. Click the Proxy Connectors link in the left navigation menu 2. Click the Add Proxy Connector link in the upper right part of the page Result: A blank archiva page -- 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: (MRM-332) Adding a Proxy Connector displays a blank page
[ http://jira.codehaus.org/browse/MRM-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95375 ] Napoleon Esmundo C. Ramirez commented on MRM-332: - Nothing shows up in the logs either. Adding a Proxy Connector displays a blank page -- Key: MRM-332 URL: http://jira.codehaus.org/browse/MRM-332 Project: Archiva Issue Type: Bug Components: web application Reporter: Napoleon Esmundo C. Ramirez To replicate: 1. Click the Proxy Connectors link in the left navigation menu 2. Click the Add Proxy Connector link in the upper right part of the page Result: A blank archiva page -- 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] Updated: (CONTINUUM-1229) com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Invalid default value for 'SCM_USE_CACHE'
[ http://jira.codehaus.org/browse/CONTINUUM-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1229: --- Attachment: CONTINUUM-1229-continuum-model.patch com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Invalid default value for 'SCM_USE_CACHE' -- Key: CONTINUUM-1229 URL: http://jira.codehaus.org/browse/CONTINUUM-1229 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-1 Environment: Windows XP / JDK 1.5.0_10-b03 / Tomcat 5.5.20 / MySQL 5.0.27 Reporter: Arnaud Heritier Attachments: CONTINUUM-1229-continuum-model.patch, stdout_20070328.log The change in the model (r507778) creates the error described in the subject and in the attached logs if I use continuum with MySQL. If I remove jpox.nullValue=default for the field scmUseCache, the tests in the core fail. -- 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: (CONTINUUM-1112) Unable to use DB without username and password
[ http://jira.codehaus.org/browse/CONTINUUM-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94421 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-1112: Oh I see, the database received a connection request from null when it should've been . Btw, I tried it using the code from trunk, but I can't seem to reproduce the issue. Is there anything else to consider? Unable to use DB without username and password -- Key: CONTINUUM-1112 URL: http://jira.codehaus.org/browse/CONTINUUM-1112 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-1 Environment: mysql jdbc driver 5.0.3, mysql server 5.0.24 Reporter: Carlos Sanchez Fix For: 1.1-alpha-# Attachments: log.txt Changed plexus.conf database definition to use mysql db that anyone can access (no user / no password) and got an error because it's trying to use a null username. java.sql.SQLException: Access denied for user 'null'@'localhost' (using password: YES) resource namejdbc/continuum/name typejavax.sql.DataSource/type properties property namedriverClassName/name valuecom.mysql.jdbc.Driver/value /property property nameurl/name valuejdbc:mysql://localhost/test/value /property property nameusername/name value/value /property property namepassword/name value/ /property /properties /resource -- 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: (CONTINUUM-1112) Unable to use DB without username and password
[ http://jira.codehaus.org/browse/CONTINUUM-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94395 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-1112: This isn't a Continuum issue. To enable null users, or more known as anonymous users, privileges on the database must be granted to it. To make your configuration work, you'll have to do something like: mysql GRANT ALL PRIVILEGES ON test TO ''@'localhost'; mysql FLUSH PRIVILEGES; Unable to use DB without username and password -- Key: CONTINUUM-1112 URL: http://jira.codehaus.org/browse/CONTINUUM-1112 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-1 Environment: mysql jdbc driver 5.0.3, mysql server 5.0.24 Reporter: Carlos Sanchez Fix For: 1.1-alpha-# Attachments: log.txt Changed plexus.conf database definition to use mysql db that anyone can access (no user / no password) and got an error because it's trying to use a null username. java.sql.SQLException: Access denied for user 'null'@'localhost' (using password: YES) resource namejdbc/continuum/name typejavax.sql.DataSource/type properties property namedriverClassName/name valuecom.mysql.jdbc.Driver/value /property property nameurl/name valuejdbc:mysql://localhost/test/value /property property nameusername/name value/value /property property namepassword/name value/ /property /properties /resource -- 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] Updated: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test-2.patch This patch contains tweaks to the pom.xml, updating the ant task that copies test resources to the appropriate locations. The AbstractArchivaTestCase is also updated of the resources' names. Web UI tests for Archiva - Browse - Key: MRM-317 URL: http://jira.codehaus.org/browse/MRM-317 Project: Archiva Issue Type: Test Components: web application Environment: Linux FC6, JDK 1.5, Maven 2.0.6 Reporter: Napoleon Esmundo C. Ramirez Attachments: MRM-317-archiva-webapp-test-2.patch, MRM-317-archiva-webapp-test.patch, MRM-317-archiva-webapp-test.tar.gz -- 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] Updated: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test-x.tar.gz Web UI tests for Archiva - Browse - Key: MRM-317 URL: http://jira.codehaus.org/browse/MRM-317 Project: Archiva Issue Type: Test Components: web application Environment: Linux FC6, JDK 1.5, Maven 2.0.6 Reporter: Napoleon Esmundo C. Ramirez Attachments: MRM-317-archiva-webapp-test-x.patch, MRM-317-archiva-webapp-test-x.tar.gz -- 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] Created: (MRM-321) Web UI tests for Archiva - Managed Repositories Configuration
Web UI tests for Archiva - Managed Repositories Configuration - Key: MRM-321 URL: http://jira.codehaus.org/browse/MRM-321 Project: Archiva Issue Type: Test Components: web application Reporter: Napoleon Esmundo C. Ramirez -- 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] Updated: (MRM-321) Web UI tests for Archiva - Managed Repositories Configuration
[ http://jira.codehaus.org/browse/MRM-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-321: Attachment: MRM-321-archiva-webapp-test.patch Attached a patch for testing the configuration of managed repositories. On toggling the Show POM snippet: The POM snippet cannot be verified not to be present using the assertTextNotPresent() method as the POM snippet is always present, just hidden. Web UI tests for Archiva - Managed Repositories Configuration - Key: MRM-321 URL: http://jira.codehaus.org/browse/MRM-321 Project: Archiva Issue Type: Test Components: web application Reporter: Napoleon Esmundo C. Ramirez Attachments: MRM-321-archiva-webapp-test.patch -- 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] Created: (MRM-315) Selenium test cases fail due to an HTTP 500
Selenium test cases fail due to an HTTP 500
---
Key: MRM-315
URL: http://jira.codehaus.org/browse/MRM-315
Project: Archiva
Issue Type: Bug
Components: web application
Environment: Linux FC6, JDK 1.5, Maven 2.0.6
Reporter: Napoleon Esmundo C. Ramirez
The selenium tests fail because an HTTP 500 is encountered. This is caused by
the missing archiva.xml in the ${appserver-base} 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
[jira] Updated: (MRM-315) Selenium test cases fail due to an HTTP 500
[
http://jira.codehaus.org/browse/MRM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated MRM-315:
Attachment: MRM-315-archiva-webapp-test.patch
The patch includes the fix to the HTTP 500 encountered on selenium tests. It
also includes a trivial fix to AbstractArchivaTestCase--it creates
archiva-webapp-testtarget/ a directory over the archiva-webapp-test/.
Selenium test cases fail due to an HTTP 500
---
Key: MRM-315
URL: http://jira.codehaus.org/browse/MRM-315
Project: Archiva
Issue Type: Bug
Components: web application
Environment: Linux FC6, JDK 1.5, Maven 2.0.6
Reporter: Napoleon Esmundo C. Ramirez
Attachments: MRM-315-archiva-webapp-test.patch
The selenium tests fail because an HTTP 500 is encountered. This is caused
by the missing archiva.xml in the ${appserver-base} 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
[jira] Updated: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test.tar.gz MRM-317-archiva-webapp-test.tar.gz contains a test repository and an index for testing the 'browse' functionality of Archiva webapp. To be used in conjunction with MRM-317-archiva-webapp-test.patch Web UI tests for Archiva - Browse - Key: MRM-317 URL: http://jira.codehaus.org/browse/MRM-317 Project: Archiva Issue Type: Test Components: web application Environment: Linux FC6, JDK 1.5, Maven 2.0.6 Reporter: Napoleon Esmundo C. Ramirez Attachments: MRM-317-archiva-webapp-test.patch, MRM-317-archiva-webapp-test.tar.gz -- 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] Closed: (MRM-314) Webapp tests are not working because of missing derby dependency
[ http://jira.codehaus.org/browse/MRM-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez closed MRM-314. --- Resolution: Duplicate Issue duplicates MRM-310 Webapp tests are not working because of missing derby dependency Key: MRM-314 URL: http://jira.codehaus.org/browse/MRM-314 Project: Archiva Issue Type: Bug Reporter: Maria Odea Ching -- 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] Updated: (MRM-310) Selenium test cases do not run
[
http://jira.codehaus.org/browse/MRM-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated MRM-310:
Attachment: MRM-310-archiva-webapp-test-2.patch
Here's another patch fixing the same issue, but something consistent with the
one in continuum-webapp-test.
Selenium test cases do not run
--
Key: MRM-310
URL: http://jira.codehaus.org/browse/MRM-310
Project: Archiva
Issue Type: Test
Components: web application
Affects Versions: 1.0
Environment: Linux FC6, JDK1.5, Maven2.0.5
Reporter: Napoleon Esmundo C. Ramirez
Assignee: Napoleon Esmundo C. Ramirez
Attachments: MRM-310-archiva-webapp-test-2.patch,
MRM-310-archiva-webapp-test.patch
Selenium test cases located at the project
${maven}/archiva/archiva-webapp-test do not run due to an undeployed
archiva-webapp. Stacktrace follows.
[INFO] [antrun:run {execution: check-archiva-loaded}]
[INFO] Executing tasks
[get] Getting: http://localhost:9696/archiva/
[get] To:
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
--
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] Created: (MRM-310) Selenium test cases do not run
Selenium test cases do not run
--
Key: MRM-310
URL: http://jira.codehaus.org/browse/MRM-310
Project: Archiva
Issue Type: Test
Components: web application
Affects Versions: 1.0
Environment: Linux FC6, JDK1.5, Maven2.0.5
Reporter: Napoleon Esmundo C. Ramirez
Selenium test cases located at the project ${maven}/archiva/archiva-webapp-test
do not run due to an undeployed archiva-webapp. Stacktrace follows.
[INFO] [antrun:run {execution: check-archiva-loaded}]
[INFO] Executing tasks
[get] Getting: http://localhost:9696/archiva/
[get] To:
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
--
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] Updated: (MRM-310) Selenium test cases do not run
[
http://jira.codehaus.org/browse/MRM-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Napoleon Esmundo C. Ramirez updated MRM-310:
Attachment: MRM-310-archiva-webapp-test.patch
This patch fixes the archiva-webapp loading problems as described in
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat .
src/test/tomcat5x/conf/Catalina/localhost/archiva.xml
- added the resources needed by archiva-webapp
pom.xml
- upgraded the dependency from the codehaus version into the apache version
- changed the ant task that copies archiva-webapp's provided dependencies
into the container's common/lib into a dependency mojo that copies them to the
container's common/lib, because the ant task copies from
archiva-webapp/WEB-INF/lib and provided dependencies are not included that
directory
Selenium test cases do not run
--
Key: MRM-310
URL: http://jira.codehaus.org/browse/MRM-310
Project: Archiva
Issue Type: Test
Components: web application
Affects Versions: 1.0
Environment: Linux FC6, JDK1.5, Maven2.0.5
Reporter: Napoleon Esmundo C. Ramirez
Assigned To: Napoleon Esmundo C. Ramirez
Attachments: MRM-310-archiva-webapp-test.patch
Selenium test cases located at the project
${maven}/archiva/archiva-webapp-test do not run due to an undeployed
archiva-webapp. Stacktrace follows.
[INFO] [antrun:run {execution: check-archiva-loaded}]
[INFO] Executing tasks
[get] Getting: http://localhost:9696/archiva/
[get] To:
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Error opening connection java.io.IOException: Server returned
HTTP response code: 500 for URL: http://localhost:9696/archiva/index.action
[get] Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Can't get http://localhost:9696/archiva/ to
/home/nramirez/src/maven/archiva/archiva-webapp-test/target/index.html
--
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] Updated: (CONTINUUM-1099) Consistency in confirmation message
[ http://jira.codehaus.org/browse/CONTINUUM-1099?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1099: --- Attachment: CONTINUUM-1099-continuum-webapp.patch In the patch, the confirmation.jsp is no longer used in xwork.xml (individual confirmation pages are used instead), the confirmGroupRemoval.jsp and confirmScheduleRemoval.jsp and their respective actions are modified to follow a consistent confirmation message found in Continuum.properties Consistency in confirmation message --- Key: CONTINUUM-1099 URL: http://jira.codehaus.org/browse/CONTINUUM-1099 Project: Continuum Issue Type: Improvement Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1099-continuum-webapp.patch -- 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] Created: (CONTINUUM-1099) Consistency in confirmation message
Consistency in confirmation message --- Key: CONTINUUM-1099 URL: http://jira.codehaus.org/browse/CONTINUUM-1099 Project: Continuum Issue Type: Improvement Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor -- 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] Created: (CONTINUUM-1072) Release icon doesn't appear in the legend
Release icon doesn't appear in the legend - Key: CONTINUUM-1072 URL: http://jira.codehaus.org/browse/CONTINUUM-1072 Project: Continuum Issue Type: Bug Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4, Firefox2.0 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1072-continuum-webapp.patch -- 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] Updated: (CONTINUUM-1072) Release icon doesn't appear in the legend
[ http://jira.codehaus.org/browse/CONTINUUM-1072?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1072: --- Attachment: CONTINUUM-1072-continuum-webapp.patch The patch only includes the changes in the text files (tigris.css, Menu.jsp). This does not include the changes for legendbg.gif Release icon doesn't appear in the legend - Key: CONTINUUM-1072 URL: http://jira.codehaus.org/browse/CONTINUUM-1072 Project: Continuum Issue Type: Bug Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4, Firefox2.0 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1072-continuum-webapp.patch -- 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] Updated: (CONTINUUM-1072) Release icon doesn't appear in the legend
[ http://jira.codehaus.org/browse/CONTINUUM-1072?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1072: --- Attachment: legendbg.gif This image file has the changes corresponding to the attached patch. Release icon doesn't appear in the legend - Key: CONTINUUM-1072 URL: http://jira.codehaus.org/browse/CONTINUUM-1072 Project: Continuum Issue Type: Bug Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4, Firefox2.0 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1072-continuum-webapp.patch, legendbg.gif -- 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] Updated: (CONTINUUM-1061) Deleting a project should go back to the project group, not the group summary
[ http://jira.codehaus.org/browse/CONTINUUM-1061?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1061: --- Attachment: CONTINUUM-1061-continuum-webapp.patch Modified the xwork.xml to redirect to the Project Group Summary page after deleting a project. Deleting a project should go back to the project group, not the group summary - Key: CONTINUUM-1061 URL: http://jira.codehaus.org/browse/CONTINUUM-1061 Project: Continuum Issue Type: Bug Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1061-continuum-webapp.patch -- 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] Updated: (CONTINUUM-1061) Deleting a project should go back to the project group, not the group summary
[ http://jira.codehaus.org/browse/CONTINUUM-1061?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1061: --- Attachment: CONTINUUM-1061-2-continuum-webapp.patch This patch contains the necessary parameters the first patch was lacking. Please use this patch instead. Deleting a project should go back to the project group, not the group summary - Key: CONTINUUM-1061 URL: http://jira.codehaus.org/browse/CONTINUUM-1061 Project: Continuum Issue Type: Bug Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1061-2-continuum-webapp.patch, CONTINUUM-1061-continuum-webapp.patch -- 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] Created: (CONTINUUM-1071) Schedules list should use Edit/Remove icons instead of test links
Schedules list should use Edit/Remove icons instead of test links - Key: CONTINUUM-1071 URL: http://jira.codehaus.org/browse/CONTINUUM-1071 Project: Continuum Issue Type: Improvement Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor -- 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] Updated: (CONTINUUM-1071) Schedules list should use Edit/Remove icons instead of test links
[ http://jira.codehaus.org/browse/CONTINUUM-1071?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1071: --- Attachment: CONTINUUM-1071-continuum-webapp.patch This patch replaces the Edit/Remove text links into their respective icons. Schedules list should use Edit/Remove icons instead of test links - Key: CONTINUUM-1071 URL: http://jira.codehaus.org/browse/CONTINUUM-1071 Project: Continuum Issue Type: Improvement Components: Web interface Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: CONTINUUM-1071-continuum-webapp.patch -- 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] Updated: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=all ] Napoleon Esmundo C. Ramirez updated MRM-242: Attachment: MRM-242-archiva-2.patch I revised the 1st patch and fixed the artifact file extension used in the download url. Please use the 2nd patch. Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.0-beta-1 Attachments: MRM-242-archiva-2.patch, MRM-242-archiva.patch When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- 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: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=comments#action_82249 ] Napoleon Esmundo C. Ramirez commented on MRM-242: - Jesse, The second patch fixes the download url of the artifact. Anyway, regarding the authz thingy, the browser still prompts me for username password though Joakim told me he has this working already. Probably some trouble bridging the SecuritySystem's authn/authz to the HttpAuthenticator. Can you verify this please? Cheers! Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.0-beta-1 Attachments: MRM-242-archiva-2.patch, MRM-242-archiva.patch When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- 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: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=comments#action_81961 ] Napoleon Esmundo C. Ramirez commented on MRM-242: - Ok, I'll revise my patch for that. I'll try to include a fix for the authz if I happen to pass along the code. Thanks! :) Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Assigned To: Jesse McConnell Fix For: 1.0-beta-1 Attachments: MRM-242-archiva.patch When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- 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: (CONTINUUM-1022) Validaiton Email not working
[ http://jira.codehaus.org/browse/CONTINUUM-1022?page=comments#action_81381 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-1022: The validation mail now uses JNDI to locate the mail service. However the codes at the trunk isn't configured yet to make jetty:run work. Validaiton Email not working Key: CONTINUUM-1022 URL: http://jira.codehaus.org/browse/CONTINUUM-1022 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Franz Allan Valencia See The validation email sent when you register is not working. -- 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: (CONTINUUM-1022) Validaiton Email not working
[ http://jira.codehaus.org/browse/CONTINUUM-1022?page=comments#action_81382
]
Napoleon Esmundo C. Ramirez commented on CONTINUUM-1022:
The validation mail now uses JNDI to locate the mail service. However the
codes at the trunk isn't configured yet to make jetty:run work.
To configure continuum to use the JNDI mail resource, I added the following in
continuum-webapp/src/jetty-env.xml:
New id=validation_mail class=org.mortbay.jetty.plus.naming.Resource
Argmail/Session/Arg
Arg
New class=org.mortbay.naming.factories.MailSessionReference
Set name=userusername/Set
Set name=passwordpassword/Set
Set name=properties
New class=java.util.Properties
Put name=mail.smtp.hostsmtp.host.org/Put
Put name=mail.from[EMAIL PROTECTED]/Put
Put name=mail.senderNameContinuum/Put
Put name=mail.debugtrue/Put
/New
/Set
/New
/Arg
/New
I also added the following in continuum-webapp/src/main/webapp/WEB-INF/web.xml:
resource-ref
res-ref-namemail/Session/res-ref-name
res-typejavax.mail.Session/res-type
res-authContainer/res-auth
/resource-ref
Which led me to another problem described by the following stack trace:
DEBUG: JavaMail version 1.4ea
DEBUG: java.io.FileNotFoundException:
/usr/share/jdk1.5.0_06/jre/lib/javamail.providers (No such file or directory)
DEBUG: !anyLoaded
DEBUG: not loading resource: /META-INF/javamail.providers
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name:
{com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun
Microsystems, Inc],
com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc],
com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc],
com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun
Microsystems, Inc],
com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun
Microsystems, Inc],
com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun
Microsystems, Inc]}
DEBUG: Providers Listed By Protocol:
{imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc],
imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun
Microsystems, Inc],
smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun
Microsystems, Inc],
pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun
Microsystems, Inc],
pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun
Microsystems, Inc],
smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: !anyLoaded
DEBUG: not loading resource: /META-INF/javamail.address.map
DEBUG: java.io.FileNotFoundException:
/usr/share/jdk1.5.0_06/jre/lib/javamail.address.map (No such file or directory)
2006-11-29 16:26:29,745 [btpool0-4] ERROR Mailer -
Unable to generate email for template
'org/codehaus/plexus/security/ui/web/mail/template/newAccountValidationEmail.vm':
javax.mail.Session
java.lang.ClassCastException: javax.mail.Session
at
org.codehaus.plexus.mailsender.javamail.JndiJavamailMailSender.getSession(JndiJavamailMailSender.java:52)
at
org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:62)
at
org.codehaus.plexus.security.ui.web.mail.Mailer.sendMessage(Mailer.java:237)
at
org.codehaus.plexus.security.ui.web.mail.Mailer.sendVelocityEmail(Mailer.java:165)
at
org.codehaus.plexus.security.ui.web.mail.Mailer.sendAccountValidationEmail(Mailer.java:108)
at
org.codehaus.plexus.security.ui.web.action.RegisterAction.register(RegisterAction.java:183)
Any ideas about this? Or did I miss on some configuration?
Validaiton Email not working
Key: CONTINUUM-1022
URL: http://jira.codehaus.org/browse/CONTINUUM-1022
Project: Continuum
Issue Type: Bug
Components: Web interface
Reporter: Franz Allan Valencia See
The validation email sent when you register is not working.
--
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] Updated: (CONTINUUM-1022) Validaiton Email not working
[ http://jira.codehaus.org/browse/CONTINUUM-1022?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-1022: --- Comment: was deleted Validaiton Email not working Key: CONTINUUM-1022 URL: http://jira.codehaus.org/browse/CONTINUUM-1022 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Franz Allan Valencia See The validation email sent when you register is not working. -- 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] Created: (MRM-242) Replace the proxy url of the Download link into the absolute url
Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- 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] Updated: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=all ] Napoleon Esmundo C. Ramirez updated MRM-242: Attachment: MRM-242-archiva.patch This patch replaces the proxy url into the absolute url used in the Download link when browsing for artifacts in archiva. Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez Attachments: MRM-242-archiva.patch When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- 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] Created: (MRM-233) Add 'Edit user info' link in the side navigation
Add 'Edit user info' link in the side navigation Key: MRM-233 URL: http://jira.codehaus.org/browse/MRM-233 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK 1.5, Maven 2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Add 'Edit user info' link similar to that of continuum. -- 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] Updated: (MRM-233) Add 'Edit user info' link in the side navigation
[ http://jira.codehaus.org/browse/MRM-233?page=all ] Napoleon Esmundo C. Ramirez updated MRM-233: Attachment: MRM-233-archiva-webapp.patch This patch adds the 'Edit user info' link in the side navigation menu. Add 'Edit user info' link in the side navigation Key: MRM-233 URL: http://jira.codehaus.org/browse/MRM-233 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK 1.5, Maven 2.0.4 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Attachments: MRM-233-archiva-webapp.patch Add 'Edit user info' link similar to that of continuum. -- 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] Created: (CONTINUUM-929) The value in the Description field of the Edit User Group page is truncated until the first comma symbol
The value in the Description field of the Edit User Group page is truncated until the first comma symbol Key: CONTINUUM-929 URL: http://jira.codehaus.org/browse/CONTINUUM-929 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, JDK1.5, Maven 2.0.4, Jetty 6.0.0beta17 Reporter: Napoleon Esmundo C. Ramirez When adding or editing the Description field of the User Group, the value is truncated on the first occurence of the comma symbol. -- 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] Created: (CONTINUUM-906) Accessing the release pages cause a server error because of missing extremecomponents taglib
Accessing the release pages cause a server error because of missing extremecomponents taglib Key: CONTINUUM-906 URL: http://jira.codehaus.org/browse/CONTINUUM-906 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux Fc4, Jetty6.0.0beta17, Maven 2.0.4, JDK1.5 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-906-continuum-webapp.patch The release pages use the uri /tld/extremecomponents instead of http://www.extremecomponents.org -- 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] Updated: (CONTINUUM-906) Accessing the release pages cause a server error because of missing extremecomponents taglib
[ http://jira.codehaus.org/browse/CONTINUUM-906?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-906: -- Attachment: (was: CONTINUUM-907-continuum-webapp.patch) Accessing the release pages cause a server error because of missing extremecomponents taglib Key: CONTINUUM-906 URL: http://jira.codehaus.org/browse/CONTINUUM-906 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux Fc4, Jetty6.0.0beta17, Maven 2.0.4, JDK1.5 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-906-continuum-webapp.patch The release pages use the uri /tld/extremecomponents instead of http://www.extremecomponents.org -- 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] Updated: (CONTINUUM-906) Accessing the release pages cause a server error because of missing extremecomponents taglib
[ http://jira.codehaus.org/browse/CONTINUUM-906?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-906: -- Attachment: CONTINUUM-906-continuum-webapp.patch Accessing the release pages cause a server error because of missing extremecomponents taglib Key: CONTINUUM-906 URL: http://jira.codehaus.org/browse/CONTINUUM-906 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux Fc4, Jetty6.0.0beta17, Maven 2.0.4, JDK1.5 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-906-continuum-webapp.patch The release pages use the uri /tld/extremecomponents instead of http://www.extremecomponents.org -- 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] Created: (CONTINUUM-908) Submitting in the Preparing Project Release Page gives a server error
Submitting in the Preparing Project Release Page gives a server error - Key: CONTINUUM-908 URL: http://jira.codehaus.org/browse/CONTINUUM-908 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, JDK1.5, Maven 2.0.4, Jetty 6.0.0beta17 Reporter: Napoleon Esmundo C. Ramirez After submitting in the Preparing Project Release page, the following error occurs: ...the server is redirecting the request for this address in a way that will never complete. -- 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: (CONTINUUM-867) User edit page is missing fields
[ http://jira.codehaus.org/browse/CONTINUUM-867?page=comments#action_74722 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-867: --- The Full Name and lock fields were added in the add/edit user form. The lock of the user's account can be toggled--using a checkbox. User edit page is missing fields Key: CONTINUUM-867 URL: http://jira.codehaus.org/browse/CONTINUUM-867 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.1 It needs other fields like user name and specially the feature to unlock an user account -- 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] Closed: (CONTINUUM-867) User edit page is missing fields
[ http://jira.codehaus.org/browse/CONTINUUM-867?page=all ] Napoleon Esmundo C. Ramirez closed CONTINUUM-867. - Resolution: Fixed User edit page is missing fields Key: CONTINUUM-867 URL: http://jira.codehaus.org/browse/CONTINUUM-867 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Priority: Critical Fix For: 1.1 It needs other fields like user name and specially the feature to unlock an user account -- 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: (CONTINUUM-875) projectEdit page validates before submit
[ http://jira.codehaus.org/browse/CONTINUUM-875?page=comments#action_74741 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-875: --- projectEdit.doEdit() is invoked in this link. Added doEdit() in the list of methods that do not need validation the first time the page is loaded projectEdit page validates before submit Key: CONTINUUM-875 URL: http://jira.codehaus.org/browse/CONTINUUM-875 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 projectEdit (linked from projectView) shows the validation errors with empty fields, is the same as another error that Nap Ramirez solved this week -- 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] Closed: (CONTINUUM-875) projectEdit page validates before submit
[ http://jira.codehaus.org/browse/CONTINUUM-875?page=all ] Napoleon Esmundo C. Ramirez closed CONTINUUM-875. - Resolution: Fixed projectEdit page validates before submit Key: CONTINUUM-875 URL: http://jira.codehaus.org/browse/CONTINUUM-875 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 projectEdit (linked from projectView) shows the validation errors with empty fields, is the same as another error that Nap Ramirez solved this week -- 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: (CONTINUUM-852) Configuration page shows en error in the form the first time is accessed
[ http://jira.codehaus.org/browse/CONTINUUM-852?page=comments#action_74567 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-852: --- Dropped the idea of having the default value for baseUrl. The validation-before-submit error is now fixed in the branch. As suspected, this undesired behavior was due to the lacking configuration in some interceptors overridden in xwork.xml. The reason why validation occurs even before submit (as opposed to the default behavior) is because the validation workflow interceptors were overridden with empty configuration (excluded methods). [Reference: http://forums.opensymphony.com/thread.jspa?messageID=27367#27367] Is there any reason for having a custom interceptor stack aside from the exception logging? If not, maybe we can reuse the defaultStack beside the defaultContinuumStack. Just a thought... Configuration page shows en error in the form the first time is accessed Key: CONTINUUM-852 URL: http://jira.codehaus.org/browse/CONTINUUM-852 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: acegi-branch Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 Now that the configuration step is back in place, when login the first time you get redirected to http://localhost:8080/continuum/configuration!input.action That page shows You must define a URL. for the BaseURL, seems that it's doing validation *before* submit. Also the css is bad and the message is missaligned -- 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: (CONTINUUM-852) Configuration page shows en error in the form the first time is accessed
[ http://jira.codehaus.org/browse/CONTINUUM-852?page=comments#action_74471 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-852: --- Is it ok to just use a default value for the baseUrl to avoid the validation errors before submitting the configuration? Btw, in the branch, the companyUrl can now be saved. Configuration page shows en error in the form the first time is accessed Key: CONTINUUM-852 URL: http://jira.codehaus.org/browse/CONTINUUM-852 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: acegi-branch Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 Now that the configuration step is back in place, when login the first time you get redirected to http://localhost:8080/continuum/configuration!input.action That page shows You must define a URL. for the BaseURL, seems that it's doing validation *before* submit. Also the css is bad and the message is missaligned -- 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: (CONTINUUM-843) Add user form for self editing user details
[ http://jira.codehaus.org/browse/CONTINUUM-843?page=comments#action_74327 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-843: --- Factored the userForm out of the edit page. Created another edit screen for the normal user aside from the page used by the admin. The edit actions are split into 2 but still uses the same action class. Add user form for self editing user details --- Key: CONTINUUM-843 URL: http://jira.codehaus.org/browse/CONTINUUM-843 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 Users should be able to edit its own details (like email) and change their password Of course thay can't edit their permissions or username Reuse as much as possible the edit user page already done for administrators Make sure the user id / username is not passed as argument anywhere, it must be retrieved by the UserManager object, to avoid dependency on acegi in maven-user-core i'm gonna create an interface there and add an implementation in maven-user-acegi -- 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: (CONTINUUM-843) Add user form for self editing user details
[ http://jira.codehaus.org/browse/CONTINUUM-843?page=comments#action_74174 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-843: --- For now, disabling the username field is fixed in CONTINUUM-842. I added a menu item in the navigation that will hold the link to editing the user's own account. Now that I think of it, what roles would be needed for authorization? And where is the list of roles for acegi located? Add user form for self editing user details --- Key: CONTINUUM-843 URL: http://jira.codehaus.org/browse/CONTINUUM-843 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Napoleon Esmundo C. Ramirez Fix For: 1.1 Users should be able to edit its own details (like email) and change their password Of course thay can't edit their permissions or username Reuse as much as possible the edit user page already done for administrators Make sure the user id / username is not passed as argument anywhere, it must be retrieved by the UserManager object, to avoid dependency on acegi in maven-user-core i'm gonna create an interface there and add an implementation in maven-user-acegi -- 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: (CONTINUUM-842) Maven-user improvements
[ http://jira.codehaus.org/browse/CONTINUUM-842?page=comments#action_74217 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-842: --- The unhidden password fields seem to be fixed in the apache trunk. Thanks for pointing out. :) Maven-user improvements --- Key: CONTINUUM-842 URL: http://jira.codehaus.org/browse/CONTINUUM-842 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Lester Ecarma Fix For: 1.1 - user list page shows user.username user.email - when adding a user, the roles list shouldn't show up, only on editing -- 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: (CONTINUUM-843) Add user form for self editing user details
[ http://jira.codehaus.org/browse/CONTINUUM-843?page=comments#action_74104 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-843: --- I'm thinking that, to reuse the same edit.jsp page in maven-user-webapp, we could use the authz taglib to disable the username text field and disable the stuff for editing the permissions. But wouldn't that tie acegi up with maven-user-webapp too much? Or am I just missing something? Add user form for self editing user details --- Key: CONTINUUM-843 URL: http://jira.codehaus.org/browse/CONTINUUM-843 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Fix For: 1.1 Users should be able to edit its own details (like email) and change their password Of course thay can't edit their permissions or username Reuse as much as possible the edit user page already done for administrators Make sure the user id / username is not passed as argument anywhere, it must be retrieved by the UserManager object, to avoid dependency on acegi in maven-user-core i'm gonna create an interface there and add an implementation in maven-user-acegi -- 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: (CONTINUUM-842) Maven-user improvements
[ http://jira.codehaus.org/browse/CONTINUUM-842?page=comments#action_74021 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-842: --- The password fields in the General Configuration do not hide the entered passwords. Maven-user improvements --- Key: CONTINUUM-842 URL: http://jira.codehaus.org/browse/CONTINUUM-842 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Henry S. Isidro Fix For: 1.1 - user list page shows user.username user.email - when adding a user, the roles list shouldn't show up, only on editing -- 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: (CONTINUUM-842) Maven-user improvements
[ http://jira.codehaus.org/browse/CONTINUUM-842?page=comments#action_74022 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-842: --- The password fields when adding new users do not hide the entered passwords too. Maven-user improvements --- Key: CONTINUUM-842 URL: http://jira.codehaus.org/browse/CONTINUUM-842 Project: Continuum Issue Type: Sub-task Components: Web interface Reporter: Carlos Sanchez Assigned To: Henry S. Isidro Fix For: 1.1 - user list page shows user.username user.email - when adding a user, the roles list shouldn't show up, only on editing -- 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] Updated: (CONTINUUM-818) Catch ContinuumObjectNotFoundException in buildResult.action
[ http://jira.codehaus.org/browse/CONTINUUM-818?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-818: -- Attachment: CONTINUUM-818-3.patch Thanks Carlos, I missed that part. Catch ContinuumObjectNotFoundException in buildResult.action Key: CONTINUUM-818 URL: http://jira.codehaus.org/browse/CONTINUUM-818 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, Maven 2.0.4, JDK 1.5 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-818-2.patch, CONTINUUM-818-3.patch, CONTINUUM-818.patch ContinuumObjectNotFoundException is thrown by the buildResult.action if a project isn't built yet. -- 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] Created: (CONTINUUM-817) The generated output in the Working Copy page displays the wrong content
The generated output in the Working Copy page displays the wrong content Key: CONTINUUM-817 URL: http://jira.codehaus.org/browse/CONTINUUM-817 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, Maven 2.0.4, JDK 1.5 Reporter: Napoleon Esmundo C. Ramirez The Working Copy page displays html codes (which it shouldn't). In the page source, nbsp; is generated as amp;nbsp; and so on... -- 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] Created: (CONTINUUM-818) Catch ContinuumObjectNotFoundException in buildResult.action
Catch ContinuumObjectNotFoundException in buildResult.action Key: CONTINUUM-818 URL: http://jira.codehaus.org/browse/CONTINUUM-818 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, Maven 2.0.4, JDK 1.5 Reporter: Napoleon Esmundo C. Ramirez ContinuumObjectNotFoundException is thrown by the buildResult.action if a project isn't built yet. -- 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] Updated: (CONTINUUM-818) Catch ContinuumObjectNotFoundException in buildResult.action
[ http://jira.codehaus.org/browse/CONTINUUM-818?page=all ] Napoleon Esmundo C. Ramirez updated CONTINUUM-818: -- Attachment: CONTINUUM-818.patch Catches ContinuumObjectNotFoundException in the buildResult.action Catch ContinuumObjectNotFoundException in buildResult.action Key: CONTINUUM-818 URL: http://jira.codehaus.org/browse/CONTINUUM-818 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, Maven 2.0.4, JDK 1.5 Reporter: Napoleon Esmundo C. Ramirez Attachments: CONTINUUM-818.patch ContinuumObjectNotFoundException is thrown by the buildResult.action if a project isn't built yet. -- 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
