[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2033: ------------------------------ Affects Version/s: 5.0.0.Beta1 (was: 5.0.0.M5) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2033: ----------------------------------- Changes committed. Do you wait for the builds to complete before resolving the issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2033: ---------------------------------- Verify thus: {color:red}*PENDING*{color} ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml --> When trunk respins to get Central H409 Beta2 bits (http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....) or newer, then this site will include new JBoss Maven JPA Configurator and Maven Profile Management UI connectors, which will *NOT BE INSTALLABLE* because they're only on the trunk site and not yet on http://devstudio.jboss.com/updates/5.0/staging/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-2033 at 2/29/12 3:59 AM: ------------------------------------------------------------ I'm using JBDS v20120227-2324-H78-Beta1 and these 2 maven features are missing. Using -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml, I don't even see them. Changes are in rev 8568, committed friday 24/02/2012 at 16:50 CEST (for some reason JIRA doesn't link to them) was (Author: fbricon): I'm using JBDS v20120227-2324-H78-Beta1 and these 2 maven features are missing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-2033 at 2/29/12 4:05 AM: ------------------------------------------------------------ I'm using JBDS v20120227-2324-H78-Beta1 and these 2 maven features are missing. Using -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml, I don't even see them. Changes are in rev 8568, committed friday 24/02/2012 at 16:50 CEST (for some reason JIRA doesn't link to them) but com.jboss.jbds.central.discovery_1.0.0.v20120224-1412-H1692-Beta1.jar doesn't contain the reference to the JPA or Profiles features. That makes sense if the build id uses the GMT time value, but that still means H78 contains a 3 days old plugin. was (Author: fbricon): I'm using JBDS v20120227-2324-H78-Beta1 and these 2 maven features are missing. Using -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml, I don't even see them. Changes are in rev 8568, committed friday 24/02/2012 at 16:50 CEST (for some reason JIRA doesn't link to them) but com.jboss.jbds.central.discovery_1.0.0.v20120224-1412-H1692-Beta1.jar doesn't contain the reference to the JPA or Profiles features. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2033: ---------------------------------- Looks fine when run like this: ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml However, it can't be installed... because the URL from which it's sourced does not YET have the bits: http://download.jboss.org/jbosstools/updates/development/indigo won't have the Beta1 bits until AFTER QE approves the bits and I publish them there. So, this JIRA will have to stay open until then. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2033: ---------------------------------- Did you also apply your patch here? https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.0.Beta1/prod... I see the two new entries in trunk, but not in the branch. Was this meant to be applied in JBDS for Beta1 branch too? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2033: ----------------------------------- No it wasn't. Me sad panda. I just applied the patch to the Beta1 branch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-2033. --------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2033?page=com.atlassian.jira.plugin.... ] Rastislav Wagner closed JBDS-2033. ---------------------------------- verified in jbdevstudio-product-universal-5.0.0.v201203081830M-H105-Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira