Description of problem: The jboss eap zipped maven repositories are missing maven artifact metadata, notably used by our tooling (JBoss Tools/JBDS) to detect available versions of artifacts. This causes https://issues.jboss.org/browse/JBIDE-15295, where we're unable to check a *-redhat* version of org.jboss.spec:jboss-javaee-web-6.0 is available, displaying a incorrect warning to the user Version-Release number of selected component (if applicable): 6.1, 6.1.1, 6.2 How reproducible: Always. See https://issues.jboss.org/browse/JBIDE-15295 Steps to Reproduce: 0. Have a vanilla install: settings.xml file with no profiles; clean repositories/ directory; a clean install of JBDS 7.0.0. 1. Start JBDS. 2. Configure maven for EAP 6.1: Window > Preferences > JBoss Tools > JBoss Maven Integration; click 'Configure Maven Repositories'; click 'Add repository'; click 'Recognize JBoss Maven Enterprise Repositories'; locate EAP 6.1 maven repo directory; click 'OK' to add the repo; click 'Finish' and 'OK' to update settings.xml 3. Create EAP 6.1 server: Window > Preferences > JBoss Tools > JBoss Runtime Detection; click 'Add'; locate EAP 6.1 install directory; click 'OK' to create EAP 6.1 runtime 4. Start Java EE Web Project wizard: Click 'Java EE Web Project'; for Target Runtime select 'EAP 6.1 runtime' Actual results: Warning message about no enterprise maven repo is displayed Expected results: No warning should be displayed Additional info:
Fred Bricon <fbricon> made a comment on jira JBIDE-15295 I opened https://bugzilla.redhat.com/show_bug.cgi?id=1028053 for the EAP maven repo
Fred Bricon <fbricon> made a comment on jira JBIDE-15295 We're gonna hard code specific dependency version checks for repos with missing metadata, since we can't use version ranges for those.
Fred Bricon <fbricon> updated the status of jira JBIDE-15295 to Coding In Progress
Fred Bricon <fbricon> made a comment on jira JBIDE-15295 The check for enterprise maven repo availability was blocking the UI (bad), Checking resolution of discrete versions takes even longer (booh!). so the check is now done asynchronously in a background job. while we wait for the result, a the following message is displayed : "Checking enterprise maven repository availability..."
Fred Bricon <fbricon> made a comment on jira JBIDE-15295 The check for enterprise maven repo availability was blocking the UI (bad), Checking resolution of discrete versions takes even longer (booh!). so the check is now done asynchronously in a background job. while we wait for the result, the following message is displayed : "Checking enterprise maven repository availability..."
Fred Bricon <fbricon> made a comment on jira JBIDE-15295 Applied in master and jbosstools-4.1.x. The new job is cancelled when the page is disposed. UI components are checked for disposed state upon job completion
Rastislav Wagner <rawagner> updated the status of jira JBIDE-15295 to Closed
Rastislav Wagner <rawagner> made a comment on jira JBIDE-15295 verified in JBDS 7.1.0.CR1-v20131124-0717-B560