[
http://jira.codehaus.org/browse/MRM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-663:
-----------------------------
Fix Version/s: (was: 1.0.2)
1.1
Summary: Make type to extension mapping configurable (was:
Configuring types problem)
the EJB bug is fixed (linked), but to work for "apps" we would need to make the
type list configurable in ArtifactExtensionMapping
moving to 1.1
> Make type to extension mapping configurable
> -------------------------------------------
>
> Key: MRM-663
> URL: http://jira.codehaus.org/browse/MRM-663
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Linux FC6, archiva 1.0, jdk 1.6.0
> Reporter: Fabien DUBRON
> Fix For: 1.1
>
>
> I'm working on a multi-project application and i encountered a problem.
> One of my sub-project is having the type ejb. Also, when i deploy it with
> maven, it's placed in a folder called "ejbs".
> The problem is that when i'm browsing this folder, i can see the jar created
> in my "ejbs" folder but when i try to download it, archiva gives me an error
> 404 with a message in which the part of the path "ejbs" is replaced by "jars".
> The url of the page is "http://xxx/repository/xxx/ejbs/Ejb-xxx.jar"; and the
> message is :
> Error 404 Not Found
> The following resource does not exist:
> http://xxx/repository/xxx/jars/Ejb-xxx.jar";
> And the problem happens for the type "zip" replaced by "distribution" (???).
--
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
