[jira] Commented: (MASSEMBLY-545) While loading multiple Filter files, already known filter values are not applied (see MSHARED-177)
[ http://jira.codehaus.org/browse/MASSEMBLY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255012#action_255012 ] Daniel Mohni commented on MASSEMBLY-545: Another maven magic happend here. I can not reproduce the problem even with version 2.2 I tracked the problem and found out that it didn't work with beta-4. From beta-5 it is working, looks like there is workaround for my fix on maven-filtering somewhere else. Basicly the problem occured because the version was not specified in the pom, and maven 2.2.1 has beta-1 defined in the pluginManagment. Switching to maven3 would also solve the problem as it uses beta-5. > While loading multiple Filter files, already known filter values are not > applied (see MSHARED-177) > -- > > Key: MASSEMBLY-545 > URL: http://jira.codehaus.org/browse/MASSEMBLY-545 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Daniel Mohni > Fix For: 2.2.1 > > > Fix has been submitted to maven-filtering project. > MASSEMBLY shoud update to new version as soon it is released -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
[ http://jira.codehaus.org/browse/MSHARED-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Mohni updated MSHARED-177: - Attachment: DefaultMavenFileFilter.patch I created another patch that will fix the problem on the DefaultMavenFileFilter. The PropertyUtils Patches are obsolete and should not be used. I don't know how to delete the already attached files. TestCase with FilterFiles is included > Filter files are not filtered with already known filter values > -- > > Key: MSHARED-177 > URL: http://jira.codehaus.org/browse/MSHARED-177 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Environment: all >Reporter: Daniel Mohni >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0 > > Attachments: DefaultMavenFileFilter.patch, PropertyUtils.patch, > PropertyUtilsTest.patch > > > While loading multiple Filter files the current file is filtered but the > combined filter properties are not updated. > The problem is related that the current filter properties are combined before > they are filterd. > The copmbined values are not updated after filtering... > Attached is a patch that will also update the value in the combinedProperties -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
[ http://jira.codehaus.org/browse/MSHARED-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253612#action_253612 ] Daniel Mohni commented on MSHARED-177: -- Unfortunatly this correct. As there is no acces to the combinedProperties this can not be verified. I think that the problem should be fixed somewhere else. Looking deeper thru the code I don't understand why my patch worked I'l try to find a better patch > Filter files are not filtered with already known filter values > -- > > Key: MSHARED-177 > URL: http://jira.codehaus.org/browse/MSHARED-177 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Environment: all >Reporter: Daniel Mohni >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0 > > Attachments: PropertyUtils.patch, PropertyUtilsTest.patch > > > While loading multiple Filter files the current file is filtered but the > combined filter properties are not updated. > The problem is related that the current filter properties are combined before > they are filterd. > The copmbined values are not updated after filtering... > Attached is a patch that will also update the value in the combinedProperties -- 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: (MASSEMBLY-545) While loading multiple Filter files, already known filter values are not applied (see MSHARED-177)
While loading multiple Filter files, already known filter values are not applied (see MSHARED-177) -- Key: MASSEMBLY-545 URL: http://jira.codehaus.org/browse/MASSEMBLY-545 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Reporter: Daniel Mohni Fix has been submitted to maven-filtering project. MASSEMBLY shoud update to new version as soon it is released -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
[ http://jira.codehaus.org/browse/MSHARED-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253553#action_253553 ] Daniel Mohni edited comment on MSHARED-177 at 1/31/11 2:05 AM: --- Created UnitTest to check if already known filters are applied was (Author: mohnid): UnitTest to check if already known filters are applied > Filter files are not filtered with already known filter values > -- > > Key: MSHARED-177 > URL: http://jira.codehaus.org/browse/MSHARED-177 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Environment: all >Reporter: Daniel Mohni >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0 > > Attachments: PropertyUtils.patch, PropertyUtilsTest.patch > > > While loading multiple Filter files the current file is filtered but the > combined filter properties are not updated. > The problem is related that the current filter properties are combined before > they are filterd. > The copmbined values are not updated after filtering... > Attached is a patch that will also update the value in the combinedProperties -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
[ http://jira.codehaus.org/browse/MSHARED-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Mohni updated MSHARED-177: - Attachment: PropertyUtilsTest.patch UnitTest to check if already known filters are applied > Filter files are not filtered with already known filter values > -- > > Key: MSHARED-177 > URL: http://jira.codehaus.org/browse/MSHARED-177 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Environment: all >Reporter: Daniel Mohni >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0 > > Attachments: PropertyUtils.patch, PropertyUtilsTest.patch > > > While loading multiple Filter files the current file is filtered but the > combined filter properties are not updated. > The problem is related that the current filter properties are combined before > they are filterd. > The copmbined values are not updated after filtering... > Attached is a patch that will also update the value in the combinedProperties -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
[ http://jira.codehaus.org/browse/MSHARED-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249634#action_249634 ] Daniel Mohni commented on MSHARED-177: -- I will create a unit test for this issue when I am back from holiday, but this will have to wait until end of January when I get back to work... I faced the problem working on a customer site project, using the assembly-plugin version 2.2, we used multiple filter files to create environment specific configurations. Filter File A contains portions of a value of Filter File B, using the key of File B to replace a value in a resource file still contained the key of File A... > Filter files are not filtered with already known filter values > -- > > Key: MSHARED-177 > URL: http://jira.codehaus.org/browse/MSHARED-177 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Environment: all >Reporter: Daniel Mohni > Attachments: PropertyUtils.patch > > > While loading multiple Filter files the current file is filtered but the > combined filter properties are not updated. > The problem is related that the current filter properties are combined before > they are filterd. > The copmbined values are not updated after filtering... > Attached is a patch that will also update the value in the combinedProperties -- 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: (MSHARED-177) Filter files are not filtered with already known filter values
Filter files are not filtered with already known filter values -- Key: MSHARED-177 URL: http://jira.codehaus.org/browse/MSHARED-177 Project: Maven Shared Components Issue Type: Bug Components: maven-filtering Environment: all Reporter: Daniel Mohni Attachments: PropertyUtils.patch While loading multiple Filter files the current file is filtered but the combined filter properties are not updated. The problem is related that the current filter properties are combined before they are filterd. The copmbined values are not updated after filtering... Attached is a patch that will also update the value in the combinedProperties -- 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-228) Archiva Client Configuration Howto
Archiva Client Configuration Howto -- Key: MRM-228 URL: http://jira.codehaus.org/browse/MRM-228 Project: Archiva Issue Type: Improvement Affects Versions: 1.0-beta-1 Environment: Archiva Running on Tomcat 5.5.17 Reporter: Daniel Mohni Priority: Trivial Attachments: archiva_client_config.patch I created a Client Configuration Page where I discribe how the Client should be configured to use archiva as maven proxy -- 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-223) Download Artefact Button is not working
Download Artefact Button is not working --- Key: MRM-223 URL: http://jira.codehaus.org/browse/MRM-223 Project: Archiva Issue Type: Bug Components: web application Reporter: Daniel Mohni Priority: Minor I have setup more than one proxied repository and a few non proxied repositories When I use the 'Browse' function I can see all artefacts in the different repositories, but when I want to download the artefact is not found. When I change the url generated from http://archiva/proxy/net.sf.ehcache/ehcache/1.2/ehcache-1.2.jar to (adding the repository_id) http://archiva/proxy/maven_release/net.sf.ehcache/ehcache/1.2/ehcache-1.2.jar the download works, for artefacts in non proxied repositories you also have to change from /proxy// to /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] Created: (MRM-222) dav:http repository access with dot in url is not working
dav:http repository access with dot in url is not working -- Key: MRM-222 URL: http://jira.codehaus.org/browse/MRM-222 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Environment: Windows 2003 Server Reporter: Daniel Mohni tests done on daily build of 20061115 If I try to access an artifact in the archiva repository and have a 'dot' in the url the artefact is not found -> ../repository/3p_release/net.sf.ehcache/ehcache/1.2/ehcache-1.2.jar this works with the proxy access -> ../proxy/maven_release/net.sf.ehcache/ehcache/1.2/ehcache-1.2.jar this can have an impact on the download button in the webapp -- 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
