September 2006 - jbosstools-dev - Jboss List Archives

[jbosside-dev] JBossIDE nightly build 200609110140-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] JBossIDE nightly build 200609100023-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] JBossIDE nightly build 200609081609-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] JBossIDE nightly build 200609080337-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] JBossIDE installer discussion

by Marshall Culpepper

Hey guys... Alex Pinkin started a thread for the JBossIDE installer that I never saw until now... let's make some noise so we can make this happen ;) http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970261#3970261 -- Marshall Culpepper marshall.culpepper(a)jboss.com JBoss Eclipse IDE Lead JBoss, a division of Red Hat

20 years, 1 month

1
0
0 / 0

[jbosside-dev] New splash screen

by Marshall Culpepper

Hey guys.. check out a screenshot of our new splash screen in action: http://jira.jboss.com/jira/secure/attachment/12312640/12312640_new_splash... FYI to get this all working I needed to create a product configuration (this probably should've been done a long time ago anyway), so now the user will see things like "JBossIDE for Eclipse" in their taskbar.. -- Marshall Culpepper marshall.culpepper(a)jboss.com JBoss Eclipse IDE Lead JBoss, a division of Red Hat

20 years, 1 month

3
2
0 / 0

[jbosside-dev] JBossIDE nightly build 200609052140-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] Bundling features/plugins in the build system

by Marshall Culpepper

Hey guys.. Over the past few days I've been playing with the build system trying to understand exactly how and what Eclipse bundles with a feature when it's being built.. I think I have a pretty clear understanding of what's going on now. I have implemented an ant task that can automate some of the places where pde build drops off, but I wanted to start a discussion about how things should work WRT our new distribution idea.. Things PDE build does/doesn't do: 1) If a plugin is listed as a <plugin> in your feature.xml, it will get bundled in the final ZIP file automatically (we were including 3rd party plugins to let eclipse do a lot of the bundling for us) 2) If a plugin is listed as an <import> in your feature.xml, no bundling will occur 3) If another feature is listed as an <include> in your feature.xml, no bundling will occur of that feature or it's plugins Things the old ant task did: 1) Took a list of plugins and added them to an arbitrary zip file. The old ant task was pretty annoying as you all probably know it required a list of plugins in a property file, which had to be synchronized every time one of our dependencies changed or one of our plugins changed it's needs. I have replaced the old task with a java-based task that recursively pulls requirements from your feature's feature.xml and corresponding plugin manifests. Things the new ant task current does: 1) Takes a name of a feature, and sets a property to a list of plugins that are not in the standard SDK that that feature depends on. This list is pulled from the <import> and <include> tags. With the new ant task we will be able now to automate bundling by just keeping our feature.xml's up to date. I am also thinking about making the new ant task make the "dependencies" it generates be not just plugins, but features also. That way our bundle contains not just plugins but features (which it probably should have all along). So, in short.. with the new ant task.. this will be the "new" behavior provided from our build system: 1) If a plugin is listed as a <plugin>, it gets auto-bundled just like in standard PDE build (no change). Anything here will be seen in both "bundle" and "nodeps" downloads. 2) If a plugin is listed as an <import>, that plugin and all of it's recursive dependencies will be auto-bundled (only for "bundle" downloads) 3) If a feature is listed as an <include>, that feature and all of it's plugins (and recursive dependencies) will be auto-bundled (again only in "bundle" downloads) Basically, I just want you guys to chime in if this is or isn't the expected behavior you think we should have for bundling... -- Marshall Culpepper marshall.culpepper(a)jboss.com JBoss Eclipse IDE Lead JBoss, a division of Red Hat

20 years, 1 month

3
8
0 / 0

[jbosside-dev] JBossIDE nightly build 200609050018-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

[jbosside-dev] JBossIDE nightly build 200609032339-nightly results

by jbosside-build＠jboss.org

20 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev September 2006