ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-488) Upload of Artifact fails w/ null message
Date Thu, 23 Oct 2014 15:10:37 GMT

    [ https://issues.apache.org/jira/browse/ACE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181435#comment-14181435
] 

Marcel Offermans commented on ACE-488:
--------------------------------------

Checked the jar file, and its structure looks okay: the manifest is the first entry.

Checked the manifest, and what I miss is a header that indicates the "version" of the manifest
(introduced in OSGi R4):
{code}
Bundle-ManifestVersion: 2
{code}

I think that could be the reason why the UI complains. If you use the shell, there are different
ways to "upload" an artifact and depending on the way you choose, you can "circumvent" the
file type checks that the UI always performs. That explains why you can make it work with
the shell.

[~bjoern.petri], could you take a look if this is indeed the issue?

> Upload of Artifact fails w/ null message
> ----------------------------------------
>
>                 Key: ACE-488
>                 URL: https://issues.apache.org/jira/browse/ACE-488
>             Project: ACE
>          Issue Type: Bug
>            Reporter: Bjoern Petri
>         Attachments: remote_service_admin_http.jar, screenshot.png
>
>
> The upload of the attached artifact fails with an error message saying "All 1 Artifacts
failed - null". I am not sure what is different from this artifact than from other artifacts
- but it would already help to get a proper error message. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message