[ https://issues.jboss.org/browse/JBDS-2375?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2375: ----------------------------- Description: When diffing the features on JBDS Core site between Beta1c and Beta2: {code:title=Beta1c (left) vs. Beta2 (right)} com.jboss.jbds.product.feature.source_6.0.0.Beta1-v20121024-2 < {code} When diffing the features on JBDS Extras site between Beta1c and Beta2: {code:title=Beta1c (left) vs. Beta2 (right)} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar < org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar < org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-si < {code} was: When diffing the features on JBDS Core site between Beta1c and Beta2: {code:label=Beta1c (left) vs. Beta2 (right)} com.jboss.jbds.product.feature.source_6.0.0.Beta1-v20121024-2 < {code} When diffing the features on JBDS Extras site between Beta1c and Beta2: {code:label=Beta1c (left) vs. Beta2 (right)} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar < org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar < org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-si < {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2375?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2375: ----------------------------- Description: When diffing the features on JBDS Core site between Beta1c and Beta2: {code:title=Core Features: Beta1c (left) vs. Beta2 (right)} com.jboss.jbds.product.feature.source_6.0.0.Beta1-v20121024-2 < {code} When diffing the features on JBDS Extras site between Beta1c and Beta2: {code:title=Extras Features: Beta1c (left) vs. Beta2 (right)} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar < org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar < org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-si < {code} And in terms of plugins for core: {code:title=Core Plugins: Beta1c (left) vs. Beta2 (right)} com.jboss.jbds.usage.branding.source_6.0.0.Beta1-v20121024-20 < {code} and extras: {code:title=Extras Plugins: Beta1c (left) vs. Beta2 (right)} ch.qos.logback.classic_1.0.0.v20111214-2030.jar < ch.qos.logback.core_1.0.0.v20111214-2030.jar < ch.qos.logback.slf4j_1.0.0.v20120123-1500.jar < com.ning.async-http-client_1.6.5.20120903-0645.jar < org.eclipse.equinox.p2.discovery_1.0.200.v20120524-1717.jar < org.eclipse.equinox.p2.discovery.compatibility_1.0.101.v20120 < org.eclipse.equinox.p2.ui.discovery_1.0.0.v20110808-1657.jar < org.eclipse.m2e.archetype.common_1.2.0.20120903-0645.jar < org.eclipse.m2e.core_1.2.0.20120903-1050.jar < org.eclipse.m2e.core.ui_1.2.0.20120903-1050.jar < org.eclipse.m2e.discovery_1.2.0.20120903-1050.jar < org.eclipse.m2e.editor_1.2.0.20120903-1050.jar < org.eclipse.m2e.editor.xml_1.2.0.20120903-1050.jar < org.eclipse.m2e.jdt_1.2.0.20120903-1050.jar < org.eclipse.m2e.launching_1.2.0.20120903-1050.jar < org.eclipse.m2e.lifecyclemapping.defaults_1.2.0.20120903-1050 < org.eclipse.m2e.maven.indexer_1.2.0.20120903-0645.jar < org.eclipse.m2e.maven.runtime_1.2.0.20120903-0645.jar < org.eclipse.m2e.model.edit_1.2.0.20120903-1050.jar < org.eclipse.m2e.refactoring_1.2.0.20120903-1050.jar < org.eclipse.m2e.scm_1.2.0.20120903-1050.jar < org.eclipse.m2e.wtp_0.16.0.20120914-0945.jar < org.eclipse.m2e.wtp.overlay_0.16.0.20120914-0945.jar < org.eclipse.m2e.wtp.overlay.ui_0.16.0.20120914-0945.jar < org.hamcrest.core_1.1.0.v20090501071000.jar < org.jboss.netty_3.2.5.Final-20120903-0645.jar < org.slf4j.api_1.6.4.v20120130-2120.jar < org.sonatype.m2e.mavenarchiver_0.15.0.201207090125-signed-201 < {code} was: When diffing the features on JBDS Core site between Beta1c and Beta2: {code:title=Beta1c (left) vs. Beta2 (right)} com.jboss.jbds.product.feature.source_6.0.0.Beta1-v20121024-2 < {code} When diffing the features on JBDS Extras site between Beta1c and Beta2: {code:title=Beta1c (left) vs. Beta2 (right)} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar < org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar < org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-si < {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2375?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2375 at 11/8/12 12:49 AM: ------------------------------------------------------------ Complete diffs: [^JBDS.core.Beta1c.vs.Beta2.diff.txt] [^JBDS.extras.Beta1c.vs.Beta2.diff.txt] [^JBDS.core.plugins.Beta1c.vs.Beta2.diff-only.txt] [^JBDS.extras.plugins.Beta1c.vs.Beta2.diff-only.txt] was (Author: nickboldt): Complete diffs: [^JBDS.core.Beta1c.vs.Beta2.diff.txt] [^JBDS.extras.Beta1c.vs.Beta2.diff.txt] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2375?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2375 at 11/14/12 1:18 PM: ------------------------------------------------------------ With B102 build, org.eclipse.m2e.feature, org.eclipse.m2e.wtp.feature and org.sonatype.m2e.mavenarchiver.feature are already included in JBDS installer, so they don't need to be in the Extras site. Same goes for all the missing plugins - they're now in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... instead of in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... so no problem here either. Only stuff missing from extras and product site are also in the TP, so again we're fine: {code} $➔ find . -name "*ch.qos*" ./plugins/ch.qos.logback.classic_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.core_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.slf4j_1.0.0.v20120123-1500.jar {code} --- JBDS source features in product are still missing: * com.jboss.jbds.product.feature.source * com.jboss.jbds.usage.branding.source was (Author: nickboldt): With B102 build, org.eclipse.m2e.feature, org.eclipse.m2e.wtp.feature and org.sonatype.m2e.mavenarchiver.feature are already included in JBDS installer, so they don't need to be in the Extras site. Same goes for all the missing plugins - they're now in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... instead of in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... so no problem here either. Only stuff missing from extras and product site are also in the TP, so again we're fine: {code} $➔ find . -name "*ch.qos*" ./plugins/ch.qos.logback.classic_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.core_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.slf4j_1.0.0.v20120123-1500.jar {code} --- JBDS source features in product are still missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2375?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2375 at 11/14/12 1:23 PM: ------------------------------------------------------------ With B102 build, org.eclipse.m2e.feature, org.eclipse.m2e.wtp.feature and org.sonatype.m2e.mavenarchiver.feature are already included in JBDS installer, so they don't need to be in the Extras site. Same goes for all the missing plugins - they're now in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... instead of in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... so no problem here either. Only stuff missing from extras and product site are also in the TP, so again we're fine: {code} $➔ find . -name "*ch.qos*" ./plugins/ch.qos.logback.classic_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.core_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.slf4j_1.0.0.v20120123-1500.jar {code} --- JBDS source feature in product is back (com.jboss.jbds.product.feature.source). However, com.jboss.jbds.usage.branding.source is gone, because it's been folded into com.jboss.jbds.product.feature/feature.xml and com.jboss.jbds.product.feature.source/feature.xml was (Author: nickboldt): With B102 build, org.eclipse.m2e.feature, org.eclipse.m2e.wtp.feature and org.sonatype.m2e.mavenarchiver.feature are already included in JBDS installer, so they don't need to be in the Extras site. Same goes for all the missing plugins - they're now in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... instead of in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... so no problem here either. Only stuff missing from extras and product site are also in the TP, so again we're fine: {code} $➔ find . -name "*ch.qos*" ./plugins/ch.qos.logback.classic_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.core_1.0.0.v20111214-2030.jar ./plugins/ch.qos.logback.slf4j_1.0.0.v20120123-1500.jar {code} --- JBDS source features in product are still missing: * com.jboss.jbds.product.feature.source * com.jboss.jbds.usage.branding.source -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira