Chris Harris created MRM-1673:
---------------------------------
Summary: Cannot manually upload certain artifacts or Archiva says
you can't but you can
Key: MRM-1673
URL: https://jira.codehaus.org/browse/MRM-1673
Project: Archiva
Issue Type: Bug
Components: Design, Web Interface
Affects Versions: 1.4-M3
Environment: Windows XP, Firefox 15.0.1, Apache 2.2 w/ mod_proxy,
Tomcat 7.0.26 (base separated from installation and running as Windows
service), MySQL 5.5 as FileSystem, DataStore, and PM.
Reporter: Chris Harris
Priority: Critical
Unfortunately, I'm stuck having to make Production deployments to WebSphere 6.1
until Winter (in NA). A particular JSF 1.2 project I'm maintaining uses
RichFaces 3.3.3.Final. To resolve a horrendous memory leak problem involving
capping the number of logical views it can generate and another problem
involving IE9 and also adding a tooltip feature to the RichFaces calendar, I
downloaded the source, modified it, and generated my own custom artifacts.
I now need to upload them to Archiva so they can be included in the next
Production release, or my head will roll when the WAS 6.1 cluster goes down due
to logical views getting created out the wazoo.
Three artifacts are produced when building RichFaces 3.3.3.Final's source using
Maven 2 and -P jsf2:
richfaces-api-3.3.3.Final.jar (has no .pom)
richfaces-impl-jsf2-3.3.3.Final.jar (has a .pom)
richfaces-ui-3.3.3.Final.jar (has a .pom)
Archiva seems to upload the ui .jar just fine. However, two oddball things
happened for the other two .jars.
First:
I accidentally had selected the Snapshots repository when I tried to upload the
api .jar. I received the error message that I can't overwrite artifacts to
that repository. So, I selected a managed repository that I created. I still
received the same error message. Upon inspection of the repo via "Browse", I
was able to verify that the artifact had indeed been uploaded successfully.
Second:
I tried uploading the impl .jar but was promptly denied by the same error
message as before. Once again, it was successfully uploaded to the repo.
I find that, to get this section to actually work, I have to do a lot postbacks
(navigate to another section in Archiva do a refresh, shift + refresh, or even
log out and refresh and then log back in - argh).
Additionally, I can't upload these release artifacts to the default "internal"
repo? Why? I'd like to simply upload them there and set it to where they're
never updated by the artifacts present Central. Please advise.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
