]
Max Rydahl Andersen commented on JBDS-1878:
-------------------------------------------
we've got a quickfix now for -redhat-* and other missing dependencies which includes
option for locating disk based repo
Find a way to set up / install EAP6/WFK repos (automatically)
-------------------------------------------------------------
Key: JBDS-1878
URL:
https://issues.jboss.org/browse/JBDS-1878
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: installer, maven
Affects Versions: 5.0.0.M2
Reporter: Fred Bricon
Assignee: Burr Sutter
Priority: Critical
Labels: eap6, installation, maven, repository, wfk
Fix For: 5.0.0.CR1
We need to find a way to let users easily use the EAP6 / WFK maven repos.
Basically, it boils down to 2 use cases :
1 - The user wants to use the repos from his enterprise repository manager
2 - The user wants to install the repos locally
Installation / configuration of the repos can be done either via the JBDS installer
(Burr's idea) or a JBDS plugin (Max's idea).
1 - If the user chooses to use a remote repo, then may be open a page detailing the
required steps to install EAP6/WFK on nexus/artifactory/archiva. I'm not sure this
would be necessary since Joe developper will probably won't have the rights to manage
his enterprise repo management app. So we might as well bail and assume he has everything
configured.
2 - The user chooses to install the repos locally.
We can detect if the repos are already configured before continuing : Check if one remote
repository already contains specific jars only available in EAP6/WFK repos or look for a
specific snippet in the user / global settingsea.
- if nothing is found, unzip and either ask the user to change his settings manually
(showing him the right xml snippet) or do it automatically for him (by adding a new
profile activated by default)
Question is : where are the repos coming from? will they be publicly available, i.e.
easily downloadable?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: