Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1144272

Summary: eap-local-maven-repository doesn't contains all artifacts required for offline testsuite run
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: Maven RepositoryAssignee: Vladimir Dosoudil <dosoudil>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bsutter, jmartisk, mkopecky, myarboro, nziakova, pgier, pslavice
Target Milestone: CR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:44:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
build output none

Description Petr Kremensky 2014-09-19 06:38:46 UTC
Created attachment 939102 [details]
build output

Description of problem:
 eap-testsuite-local-repository lacks some artifacts required for offline running of EAP testsuite.

Version-Release number of selected component (if applicable):
 EAP 6.4.0.DR1.1

How reproducible:
 Always

Steps to Reproduce:
 unzip -q jboss-eap-6.4.0.DR1.1-src.zip
 cd jboss-eap-6.4-src
 unzip -q jboss-eap-6.4.0.DR1.1-testsuite-local-repository.zip
 REPO=`pwd`/eap-local-maven-repository
 ./build.sh -Dmaven.repo.local=$REPO -DallTests -DskipTests -o -fae

Actual results:
 ...
WildFly Test Suite: Integration - Role Based Access Control  FAILURE
JBoss Application Server Test Suite: Integration - Manual Mode Tests  FAILURE
JBoss Application Server Test Suite: Integration - PicketLink  FAILURE
...
Expected results:
eap-testsuite-local-repository contains all artifacts required for offline testsuite run

Additional info:
 This is not a serious issue (cannot impact customer directly) however it breaks our automation.
 See attachment for full build log

Comment 2 Hynek Mlnarik 2015-02-25 13:46:00 UTC
EC2 cannot be certified due to this bug, increasing severity, requesting blocker flag.

Comment 4 Vladimir Dosoudil 2015-03-02 13:06:48 UTC
There's new resolution from local repository coming with Maven 3.x which was confusing, so a new CLI argument for using Maven 2 Legacy Local Repository came with Maven 3.1.0 [MNG-5181] (-llr,--legacy-local-repository). It could be also activated with -Dmaven.legacyLocalRepo=true to ignore _maven.repositories and _remote.repositories and use only local artifacts without checking remote repositories, see http://maven.apache.org/ref/3.1.0/maven-embedder/cli.html

Those metafiles could be removed in next EAP 6.4.0 Maven repository zips to avoid activating legacy behaviour of local repository resolving.

Comment 6 Vladimir Dosoudil 2015-03-03 13:16:39 UTC
Pre-tested, local testsuite maven repository zip is going to be metafiles-free in ER4/CR1. Jenkins job jboss-eap-6.4.x-server creating local testsuite maven repository zip has been modified to remove metafiles before creating the zip file.

Comment 7 Petr Kremensky 2015-03-18 11:18:20 UTC
Offline build of all modules using just testsuite local repo succeeded.

$ unzip jboss-eap-6.4.0.CR1-testsuite-local-repository.zip -d $MAVEN_REPO_LOCAL
$ ./build.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -DallTests -DskipTests -o -fae -Dmaven.test.failure.ignore=true

Verified on EAP 6.4.0.CR1