Bug 1019854 - JAR without pom.xml cannot be uploaded into asset repository
Summary: JAR without pom.xml cannot be uploaded into asset repository
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Toni Rikkola
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On: 1012483 1018220
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 13:50 UTC by Radovan Synek
Modified: 2014-08-06 20:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:17:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
mode JAR (8.35 KB, application/x-java-archive)
2013-10-16 13:50 UTC, Radovan Synek 		no flags Details
the interesting part of a server log (27.25 KB, text/x-log)
2013-10-16 13:53 UTC, Radovan Synek 		no flags Details
View All

Description Radovan Synek 2013-10-16 13:50:22 UTC 
Created attachment 812935 [details]
mode JAR

Description of problem:
Uploading JAR without pom.xml ends up with an error message with NPE, server log gives better advice: "Could not find pom.xml from the jar."

Version-Release number of selected component (if applicable):
BRMS-6.0.0.ER4

Steps to Reproduce:
1. open Asset Repository and try to upload attached JAR
2. see the error msg and server log

Expected results:
I can remember previous builds enabled typing GAV when pom.xml was not available in the JAR.
Comment 1 Radovan Synek 2013-10-16 13:53:46 UTC 
Created attachment 812938 [details]
the interesting part of a server log
Comment 2 manstis 2013-10-17 08:51:16 UTC 
This was fixed (probably!) by https://bugzilla.redhat.com/show_bug.cgi?id=1018220. I have tested with "master" code-base and problem does not exist (you are asked to enter the GAV details as you remembered).
Comment 4 Radovan Synek 2013-12-03 14:36:04 UTC 
Verified on BRMS-6.0.0.ER5
Note You need to log in before you can comment on or make changes to this bug.