[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- Got this working for Eclipse BPEL editor. See: http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.bpel/features/org.e... http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.bpel/features/pom.x... http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.bpel/site/site.xml?... etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8838: --------------------------------------- Fix Version/s: 3.3.0.M3 (was: 3.3.0.M2) Priority: Critical (was: Major) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8838: --------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-8838: ------------------------------ Fix Version/s: 3.3.0.M4 (was: 3.3.0.M3) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 9/29/11 1:48 AM: ------------------------------------------------------------ A. CLEANUP (PDE cruft): 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files B. CONTAINMENT (feature in maven reactor for building and site for publishing): 3. add .sdk.feature to features/pom.xml 4. add .sdk.feature to site/site.xml C. OUTPUT (define source feature contents): 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} source.. = src/ output.. = bin/ bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png src.includes = about.*,\ build.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ src/,\ icons/,\ jboss_about.png {code} D. CONTAINMENT (SDK feature's contents - other features + source plugins): 6. add component.feature, component.test.feature to sdk.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to sdk.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} E. AGGREGATION (JBT and jBDS update sites): 8. add new sdk feature to aggregate/**/site.xml (JBT Core, SOA Tooling, Web Tools, Bot Tests) 9. add new sdk feature to JBDS Core, Extras, SOA Tooling) was (Author: nickboldt): CLEANUP: 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files AGGREGATION: 3. add .sdk.feature to features/pom.xml 4. add .sdk.feature to site/site.xml (and to other aggregate/**/site.xml or JBDS/**/site.xml files GENERATION: 5. add component.feature, component.test.feature to sdk.feature/feature.xml (<includes>) 6. add component.ui.source, component.core.source, component.test.source, etc. to sdk.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} DEFINE OUTPUT: 7. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} source.. = src/ output.. = bin/ bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png src.includes = about.*,\ build.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ src/,\ icons/,\ jboss_about.png {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 9/29/11 2:11 AM: ------------------------------------------------------------ A. CLEANUP (PDE cruft): 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files B. CONTAINMENT (feature in maven reactor for building and site for publishing): 3. add .sdk.feature to features/pom.xml 4. add .sdk.feature to site/site.xml C. OUTPUT (define source feature contents): 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} source.. = src/ output.. = bin/ bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png src.includes = * src.excludes = src {code} D. CONTAINMENT (SDK feature's contents - other features + source plugins): 6. add component.feature, component.test.feature to sdk.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to sdk.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} E. AGGREGATION (JBT and jBDS update sites): 8. add new sdk feature to 1 or more JBT sites (JBT Core, SOA Tooling, Web Tools, Bot Tests): jbt/build/ggregate/**/site.xml 9. add new sdk feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml was (Author: nickboldt): A. CLEANUP (PDE cruft): 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files B. CONTAINMENT (feature in maven reactor for building and site for publishing): 3. add .sdk.feature to features/pom.xml 4. add .sdk.feature to site/site.xml C. OUTPUT (define source feature contents): 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} source.. = src/ output.. = bin/ bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png src.includes = * src.excludes = src {code} D. CONTAINMENT (SDK feature's contents - other features + source plugins): 6. add component.feature, component.test.feature to sdk.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to sdk.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} E. AGGREGATION (JBT and jBDS update sites): 8. add new sdk feature to aggregate/**/site.xml (JBT Core, SOA Tooling, Web Tools, Bot Tests) 9. add new sdk feature to JBDS Core, Extras, SOA Tooling) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 10/7/11 3:58 PM: ------------------------------------------------------------ **UPDATED: now using .source.feature and .test.source.feature instead of .sdk.feature** A. CLEANUP (PDE cruft): 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files B. CONTAINMENT (feature in maven reactor for building and site for publishing): 3. add .source.feature to features/pom.xml 4. add .source.feature to site/site.xml C. OUTPUT (define source feature contents): 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} D. CONTAINMENT (source feature's contents: source plugins): 6. add component.feature, component.test.feature to source.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to source.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} E. AGGREGATION (JBT and JBDS update sites): 8. add new source.feature to 1 or more JBT sites (JBT Core, SOA Tooling): jbt/build/aggregate/**/site.xml 9. add new source.feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml ?. add new test.source.feature to Bot Tests site: jbt/build/aggregate/bottests-site/site/site.xml was (Author: nickboldt): A. CLEANUP (PDE cruft): 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files B. CONTAINMENT (feature in maven reactor for building and site for publishing): 3. add .sdk.feature to features/pom.xml 4. add .sdk.feature to site/site.xml C. OUTPUT (define source feature contents): 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} D. CONTAINMENT (SDK feature's contents - other features + source plugins): 6. add component.feature, component.test.feature to sdk.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to sdk.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} E. AGGREGATION (JBT and jBDS update sites): 8. add new sdk feature to 1 or more JBT sites (JBT Core, SOA Tooling, Web Tools, Bot Tests): jbt/build/ggregate/**/site.xml 9. add new sdk feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 10/7/11 4:19 PM: ------------------------------------------------------------ *{color:red}UPDATED: now using .source.feature and .test.source.feature instead of .sdk.feature{color}* *A. CLEANUP (PDE cruft):* 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files *B. CONTAINMENT (feature in maven reactor for building and site for publishing):* 3. add .source.feature and .test.source.feature to features/pom.xml 4. add .source.feature and .test.source.feature to site/site.xml *C. OUTPUT (define source feature contents):* 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} *D. CONTAINMENT (source feature contains source plugins):* 6. add component.core.source, component.ui.source, etc. to source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} 7. add component.core.test.source, component.ui.test.source, etc. to test.source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} *E. AGGREGATION (JBT and JBDS update sites):* 8. add new source.feature to 1 or more JBT sites (JBT Core, SOA Tooling): jbt/build/aggregate/**/site.xml 9. add new source.feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml ?. add new test.source.feature to Bot Tests site: jbt/build/aggregate/bottests-site/site/site.xml was (Author: nickboldt): *{color:red}UPDATED: now using .source.feature and .test.source.feature instead of .sdk.feature{color}* *A. CLEANUP (PDE cruft):* 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files *B. CONTAINMENT (feature in maven reactor for building and site for publishing):* 3. add .source.feature to features/pom.xml 4. add .source.feature to site/site.xml *C. OUTPUT (define source feature contents):* 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} *D. CONTAINMENT (source feature's contents: source plugins):* 6. add component.feature, component.test.feature to source.feature/feature.xml (<includes>) 7. add component.ui.source, component.core.source, component.test.source, etc. to source.feature/feature.xml (<plugin>) {code} <includes id="org.jboss.tools.jmx.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <includes id="org.jboss.tools.jmx.test.feature" version="0.0.0"/> <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} *E. AGGREGATION (JBT and JBDS update sites):* 8. add new source.feature to 1 or more JBT sites (JBT Core, SOA Tooling): jbt/build/aggregate/**/site.xml 9. add new source.feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml ?. add new test.source.feature to Bot Tests site: jbt/build/aggregate/bottests-site/site/site.xml -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 10/7/11 7:49 PM: ------------------------------------------------------------ Completed Steps A-D for these components (Step E will follow after they're all done in JBIDE-9869 and JBIDE-9870): {code} jmx archives tests common as birt {code} was (Author: nickboldt): Completed Steps A-D for these components (Step E will follow after they're all done in JBIDE-9869 and JBIDE-9870): {code} tests common jmx archives as {code} -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 12/1/11 10:23 AM: ------------------------------------------------------------- Completed Steps A-D for these components (Step E will follow after they're all done in JBIDE-9869 and JBIDE-9870): {code} archives as birt bpel - SOA common jmx openshift tests - tests {code} was (Author: nickboldt): Completed Steps A-D for these components (Step E will follow after they're all done in JBIDE-9869 and JBIDE-9870): {code} jmx archives tests common as birt {code} -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 12/1/11 10:27 AM: ------------------------------------------------------------- *{color:red}UPDATED: now using .source.feature and .test.source.feature instead of .sdk.feature{color}* *A. CLEANUP (PDE cruft):* 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files *B. CONTAINMENT (feature in maven reactor for building and site for publishing):* 3. add .source.feature and .test.source.feature to features/pom.xml 4. add .source.feature and .test.source.feature to site/site.xml *C. OUTPUT (define source feature contents):* 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} *D. CONTAINMENT (source feature contains source plugins):* 6. add component.core.source, component.ui.source, etc. to source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} 7. add component.core.test.source, component.ui.test.source, etc. to test.source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} *E. AGGREGATION (JBT and JBDS update sites):* 8. add new source.feature to 1 or more NEW JBT source sites (JBT Core, SOA Tooling): jbt/build/aggregate/**/sources/site.xml 9. add new source.feature to 1 or more NEW JBDS source sites (Core, Extras, SOA Tooling): jbds/**/site.xml 10. add new test.source.features to NEW Test sources site: jbt/build/aggregate/bottests-site/site/sources/site.xml *F. COMPOSITING (JBT and JBDS update sites):* 11. composite binary and source sites together for JBT (Core, SOA, Tests) and JBDS (Core) was (Author: nickboldt): *{color:red}UPDATED: now using .source.feature and .test.source.feature instead of .sdk.feature{color}* *A. CLEANUP (PDE cruft):* 1. remove any rootfiles or sourceTemplatePlugin or sourceTemplateFeature folders within a feature folder 2. remove any generate.feature or generate.plugin entries from build.properties files *B. CONTAINMENT (feature in maven reactor for building and site for publishing):* 3. add .source.feature and .test.source.feature to features/pom.xml 4. add .source.feature and .test.source.feature to site/site.xml *C. OUTPUT (define source feature contents):* 5. ensure component plugins have build.properties which state BOTH bin.includes and src.includes directives. {code} bin.includes = about.*,\ plugin.*,\ schema/,\ META-INF/,\ .,\ icons/,\ jboss_about.png output.. = bin/ source.. = src/ src.includes = * src.excludes = src {code} *D. CONTAINMENT (source feature contains source plugins):* 6. add component.core.source, component.ui.source, etc. to source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} 7. add component.core.test.source, component.ui.test.source, etc. to test.source.feature/feature.xml (<plugin>) {code} <plugin id="org.jboss.tools.jmx.core.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.jboss.tools.jmx.ui.test.source" download-size="0" install-size="0" version="0.0.0" unpack="false"/> {code} *E. AGGREGATION (JBT and JBDS update sites):* 8. add new source.feature to 1 or more JBT sites (JBT Core, SOA Tooling): jbt/build/aggregate/**/site.xml 9. add new source.feature to 1 or more JBDS sites (Core, Extras, SOA Tooling): jbds/**/site.xml ?. add new test.source.feature to Bot Tests site: jbt/build/aggregate/bottests-site/site/site.xml -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-8838: ------------------------------ Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.M5) Slip to 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

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- Not being produced as an exploded site, only as a zip. http://download.jboss.org/jbosstools/builds/nightly/core/trunk/latest/all... I notice too the md5 file is missing. Crap. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- Well for now the sites are separate. Once they are published, they can be composited together. Have a look at the site's contents and we can decide if re-categorization is needed. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=345234 suggests that Tycho 0.14 will allow us to generate source features from regular features w/o having to maintain manually-created versions of them. We should test 0.14.0-SNAPSHOT to see if that works. If not, it's prolly worth pushing this out to CR1 and waiting for 0.14.0 to be released. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8838: -------------------------------------------- btw. https://bugs.eclipse.org/bugs/show_bug.cgi?id=345234#c24 indicates they force the binary feature into the source feature :( -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- Is this a problem? They asked on the bug whether this approach was an issue for some use-case and nobody complained about it. Who would like to have sources without having binary? The output of build of feature A is a feature A and a feature A.source containing feature A, then you are sure your source feature will install correctly together with the right version of binary feature. IMHO, this is rather a very nice implementation than a :( -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- what "EPP feature" ? -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- Does JBoss Tools really use EPP? I don't see any reason why such features could not be installed. The only case when the installation could fail is when you have a newer version of a binary feature F1 installed (let's say version 1.3), and that you want to install a F1.sdk in version 1.2: since F1.sdk 1.2 includes F1 1.2, and that you already have 1.3, then it will fail. But if you have F1 1.3 and you want to install F1.sdk 1.3, it will be OK. If you don't have F1, and want to install F1.sdk 1.3, it will be OK. As a result, you'll have F1 1.3 + F1.sdk 1.3 installed. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- It's gonna be the "built with Tycho" way, so that's probably what most Eclipse projects will use. I don't think it makes a difference on footprint. We'll need to ensure this 3 use-cases are working well, but in theory, they should -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- Seems like the plugins to generate source features cannot be factorized into parent: when using it on eclipse-plugin, the p2-plugin makes build crash. So it has to be copy-pasted on 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- I produced twice the same update-sites with this source-feature Tycho plugin. Will try various configurations for installations, and report whether everything is fine. I actively report progress and issues met on this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=345234 , this issue included. Tycho guys are now aware we are giving a try to it. They'll probably pay attention on feedback since we are probably the first ones to try this in a real case. As for getting it to work (currently): * Remove committed source features * In each eclipse-feature pom.xml add the plugin invocation as explained in bug * in each eclipse-feature folder, add a "sourceTemplateFeature" * in site.xml, replace name of source feature. For a given feature A.feature, the source feature is now called A.feature.source. Tested and working for "common" module. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- It is just a folder to create which acts like a switch. It can be empty, the Tycho plugin will generate the right source feature. Then there is no more maintainance or update of source features necessary. I thought about it. This change, if name cannot be overriden, would require to fix some featureIds or patterns in downstream aggregators or mirrors. Do you think this would be a blocking point? By reading at the Mojo code (http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-so... ), I would say no. But that could be contributed. What makes more sense/cost less: adapting new patterns in downstream builds, or contributing a "sourceFeatureName" option to this plugin. I estimate writing the contribution to 15 minutes + half a day of serious negociations to get it integrated into the master. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8838: -------------------------------------------- Nick - since we don't have any source integration stuff setup yet - shouldn't we be ok following whatever naming convention tycho applies ? -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-8838 at 2/6/12 1:42 PM: ----------------------------------------------------------- Probably will be fine to adopt this new convention... but we may need to redo some xslt or other regex pattern downstream. **shrug** I was just curious if the pattern could be changed easily. Scanning through Indigo, looks like the current convention is in fact .source or .feature.source. I did find 1 hits for ".source.feature", but that's out of 264 source features... so, yeah. Don't bother submitting anything to upstream. :) If the sourceTemplateFeature folder can be empty, then that's certainly better than building an actual source feature! was (Author: nickboldt): Probably will be fine to adopt this new convention... but we may need to redo some xslt or other regex pattern downstream. *shrug* I was just curious if the pattern could be changed easily. Scanning through Indigo, looks like the current convention is in fact .source or .feature.source. I did find 1 hits for ".source.feature", but that's out of 264 source features... so, yeah. Don't bother submitting anything to upstream. :) If the sourceTemplateFeature folder can be empty, then that's certainly better than building an actual source feature! -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8838: --------------------------------------- Fix Version/s: 3.3.0.Beta2 3.3.0.CR1 (was: 3.3.0.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

[ https://issues.jboss.org/browse/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- Committed generation and consumption of source features for simplest components: Some that will be part of a 2nd round of commit since they have "include" dependencies on some bundles generated by other components: * AS depends on JMX * JBPM depends on Flow * JSF depends on JMX * VPE depends on XulRunner Some "weirdos" that will require some more specific work: * BPEL includes feature and bundles from Eclipse.org in its feature * BPMN has no output site * Central has to remain an Eclipse-update-site and then we cannot include source features in it ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=371504 ) * Drools * Forge has a bundle with no source * GWT has an inclusion of an external GWT feature in its feature, this GWT feature does not provide sources * Runtime depends on Drools * -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- Forget Drools: ~/trunk/drools/ does nothing anymore -- all the relevant content has been moved to github EXCEPT the docs. Forget BPMN: that one never got off the ground. Instead there's a bpmn2 modeler project at Eclipse. (There are also several defunct projects there & in github too.) https://git.eclipse.org/c/bpmn2-modeler/org.eclipse.bpmn2-modeler.git/ Runtime's dependency on drools should just be the runtime detection plugin, which is supposed to be moving OUT of Runtime and into Runtime-SOA, so it can be built downstream of Runtime and Drools. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-8838: --------------------------------------- Included features cause real troubles to Tycho-source-feature-plugin. https://bugs.eclipse.org/bugs/show_bug.cgi?id=374663 This is blocking for us. Except if we remove included features and rely on bundle dependency rather than on feature inclusion. Included feature are not safe because only 1 version of a feature can be installed at a time. Dependencies are much better. -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8838: ----------------------------------- Have added a bunch of new features/plugins to the collect that generate source bundles. See also JBIDE-11077, JBIDE-11390 -- 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/JBIDE-8838?page=com.atlassian.jira.plugin... ] Vlado Pakan commented on JBIDE-8838: ------------------------------------ Please verify and close this Jira. -- 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