[
https://jira.codehaus.org/browse/MRM-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309649#comment-309649
]
Chris Harris commented on MRM-1673:
-----------------------------------
Olivier,
I think you meant to provide a hyperlink to another issue.
O.K. I've spent about the last 3 hours trying to recreate this bug. I've
gotten inconsistent behavior every time I've tried to upload the .jar and .pom,
which always results in undesirable results.
The problems start upon the 1st upload attempt of the .jar & .pom. I can
successfully upload the .jar & .pom, but, when I inspect the uploaded artifacts
via Browse, I see either just a .jar and no .pom.
So, I try manually deleting group Id packages on the "Browse" page (*that's a
whole other problem).
Upon subsequent upload attempts after deletion, I see:
a.) 2 .jar's (the .pom has been uploaded as a .jar)
b.) a messed-up looking group Id that contains no artifacts inside of it.
This brings to light the question, "How exactly do you upload a .jar & .pom?
The instructions at
http://archiva.apache.org/docs/1.4-M3-SNAPSHOT/userguide/deploy.html are nice,
but they don't explicitly state whether I have to declare a packing of pom when
I pick a pom for "Choose File" and upload it. I'm also not sure whether or not
I'm supposed to check "pom file" (I assume that I do). I'm also not sure what
to do with Classifier. I'm including screen shots on a subsequent attempt
after my 1st upload attempt & deletion.
*Manually deleting can be a pain. I keep deleting a parent package, and I'm
told that the artifact was deleted after I press "ok". Once the screen
refreshes, I'm still staring at the package that I supposedly just deleted.
Furthermore, when item b from above happens, I'll delete a Group Id package,
and then the package chain will shrink by one package. I'll delete the next
package, and the previous package comes back. This back and forth continues.
The only way that I can overcome both of these scenarios is if I log out, hold
the shift key while I refresh the page, and then log back in and ACTUALLY
delete the Group Id packages. Sometimes, it takes 2 times of logging
out/logging in to be able to actually delete the Group Id packages. I'll
attach screen shots for this as well. They'll be appropriately labeled.
> 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
> Attachments: screenshot-1.jpg
>
>
> 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
