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

Bug 900649 (JBPAPP6-1195)

Summary: Installer: Add support for a remote location in Maven Repo location
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Thomas Hauser <thauser>
Component: InstallerAssignee: Default User <jbpapp-maint>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: atangrin, msadhukh, pkremens, rsvoboda, thauser, tkirby
Target Milestone: ER6   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1195
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 17:01:33 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 953529    
Bug Blocks:    
Attachments:
Description Flags
mavenrepo_quickstarts.png
none
mavensettings-error none

Description Thomas Hauser 2012-06-19 15:33:28 UTC
project_key: JBPAPP6

Need to have the ability to specify a remote location for the maven repository's location in the relevant panel. This also means that the XSL file must take this into account, as well as the checking mechanism that the given location is a valid repository for the quickstarts and will contain all of the necessary artifacts.

Comment 1 Anne-Louise Tangring 2012-09-20 18:51:16 UTC
Please add Affects Version so that this issue can be triaged into the correct major version of EAP or EWS. Thanks!

Comment 2 Alex Szczuczko 2012-10-04 15:25:11 UTC
This feature exists in the 6.0.1 installer

Comment 3 Madhumita Sadhukhan 2012-11-02 10:23:12 UTC
I found option for specifying only local maven repository.Could you please attach screenshot or provide further details?
I am reopening this as I do not find this fix in EAP 6.0.1.ER3....please resolve with details or move the fix version to correct one.(attaching screenshot for what I see currently)

Comment 4 Madhumita Sadhukhan 2012-11-02 10:26:08 UTC
Attachment: Added: mavenrepo_quickstarts.png


Comment 5 Alex Szczuczko 2012-11-02 14:13:25 UTC
Specifying a URL as the location works transparently. Confirmed to work with the following values:

http://maven.repository.redhat.com/techpreview/all/
/tmp/example-settings.xml

We're looking at changing the text of the option to remove the  local  qualifier.

Comment 6 Misty Stanley-Jones 2012-11-05 05:08:32 UTC
Release Notes Docs Status: Added: Not Required


Comment 7 Anne-Louise Tangring 2012-11-13 20:43:51 UTC
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW 


Comment 8 Rostislav Svoboda 2013-02-21 11:40:06 UTC
We will check current status when installer is available, should be with ER1 or ER3.

Comment 9 Madhumita Sadhukhan 2013-03-05 14:18:42 UTC
I tried to enter remote location for existing file http://maven.repository.redhat.com/techpreview/all/example-settings.xml

However it always gives me error message that settings.xml does not exist.

However specifying a maven repository and settings.xml available on local works.

Is this fix in 6.1.0.ER1?

Comment 10 Madhumita Sadhukhan 2013-03-05 14:19:44 UTC
Created attachment 705460 [details]
mavensettings-error

Comment 11 Thomas Hauser 2013-03-05 16:37:20 UTC
Madhumita,

What this part of the installer does is add an active profile to the given (local) settings.xml with the location of the maven repository configured (the locaiton of the maven repo can be remote). This is to simplify the building of the quickstarts. One cannot specify a remote location for the settings.xml (the installer is modifying the file). 

Scenarios:
a) Local repo location, local settings.xml
  - Useful if the user has downloaded the JBoss maven repo, can specify the local location
b) Remote repo location, local settings.xml 
  - Useful if the user hosts their own maven repository, or for using the public JBoss repos
c) Local repo location, no settings.xml exists
  - Basic settings.xml will be created at the given local path
d) Remote repo location, no settings.xml exists
  - Same as above

So it seems like the issue you've described, we should prevent by making sure the user is not trying to specify a remote settings.xml location. Does that sound about right?

Thanks, 
Tom

Comment 12 Thomas Hauser 2013-03-05 17:00:12 UTC
Confirming that the basic settings.xml functionality is not present in ER1. This will be present in ER2.

Comment 13 Madhumita Sadhukhan 2013-03-12 15:37:49 UTC
Hi Thomas,

           Above scenarios proposed by you look good from my POV.Petr will verify if the changes are available with 6.1.0.ER2 installer

Comment 14 Petr Kremensky 2013-03-13 13:43:48 UTC
Hi Tom, I tried all four scenarios you mentioned and it works fine. I have just one really tiny note. In Maven Repository Setup screen we should remove word "local" in: Skip local maven-repository set up; as we can use also remote repo.

I also find that I am able to specify remote settings.xml location.
If I enter eg. http://google.com as settings.xml location I am asked whether I want to create settings.xml file at that location. At the end of installation, when the settings.xml should be actually created, Post processing error is thrown.

Comment 15 Petr Kremensky 2013-04-18 11:51:39 UTC
I cannot verify this, until BZ953529 is resolved.

Comment 16 Petr Kremensky 2013-04-29 14:25:58 UTC
Hi Tom, 
I can still specify remote settings.xml if using -console mode.

Comment 17 Thomas Hauser 2013-04-29 16:03:00 UTC
Will be in ER6.

Comment 18 Petr Kremensky 2013-05-03 12:38:19 UTC
Verified on EAP 6.1.0 ER6