9:53 a.m.
Notes from today's meeting:
- Moved Beta2 release back 3 weeks to account for EclipseWorld, Consulting
gig for Max (Sept 22nd)
- We should add a new "ALL" file bundle that includes all of our plugins but
no Eclipse dependencies.
- Investigate the following things:
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
10:03 a.m.
New subject: [jbosside-dev] Re: 8/28 team meeting notes
Sorry, got cut off in the middle of writing this =) Here's the rest:
- Moved Beta2 release back 3 weeks to account for EclipseWorld, Consulting
gig for Max (Sept 22nd)
- We should add a new "ALL" file bundle that includes all of our plugins but
no Eclipse dependencies.
- Everyone needs to make sure their feature.xml uses "import" instead of
"include" for any plugin that is not in your feature (i.e. all eclipse
dependencies)
- Everyone also needs to perform "code cleanup" to make sure we are catching
Exceptions correctly etc. Please reference Max's JIRA task here for
comments:
http://jira.jboss.com/jira/browse/JBIDE-351
- Marshall will look into standardizing on facets for providing runtime /
classpath containers to the user.
- We need to collaborate on a presentation for November's JBWorld Europe.
Friday is the deadline for submission..
On 8/28/06, Marshall Culpepper <marshall.culpepper(a)jboss.com> wrote:
Notes from today's meeting:
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
10:54 a.m.
New subject: [jbosside-dev] Re: 8/28 team meeting notes
- Moved Beta2 release back 3 weeks to account for EclipseWorld,
Consulting gig for Max (Sept 22nd)
Ok.
- We should add a new "ALL" file bundle that includes all
of our plugins
but no Eclipse dependencies.
I thought about this and i think most of my comments on it went lost in
the skype echo, so here is what I suggested:
Keep the same downloads as we have now under the JBoss-IDE 2.0.0.Beta1
category.
add a new category called JBoss-IDE 2.0.0.Beta1-nodeps (or something) that
simply is the exact same plugins but *without*
any external plugins.
...and may I suggest to move all the MD5 files to a seperate category ?
They are the main reason for all the clutter imo (and it is downloaded by
*very* few people)
..and even move the test builds out of the way too.
The result would be something like:
JBoss-IDE 2.0.0.Beta1
HibernateTools-3.2.0.beta7.zip
HibernateTools-Tests-2.0.0.Beta1.zip
JBossIDE-2.0.0.Beta1-ALL.zip
JBossIDE-2.0.0.Beta1-Bundle-linux-gtk.tar.gz
JBossIDE-2.0.0.Beta1-Bundle-win32.zip
JBossIDE-AOP-Developer-1.2.0.Beta1.zip
JBossIDE-Core-2.0.0.Beta1.zip
JBossIDE-Drools-3.0.4.zip
JBossIDE-EJB3-Tools-1.1.0.Beta1.zip
JBossIDE-FreeMarker-1.0.0.Beta1.zip
JBossIDE-JBossAS-Tools-1.0.0.Beta1.zip
JBossIDE-JBossCacheIDE-2.0.0.Beta1.zip
JBossIDE-JBossWS-0.3.2.zip
jBPM-Designer-3.0.11.zip
JBoss-IDE 2.0.0.Beta1-nodeps
HibernateTools-3.2.0.beta7-nodeps.zip
HibernateTools-Tests-2.0.0.Beta1-nodeps.zip
JBossIDE-2.0.0.Beta1-ALL-nodeps.zip
...
JBoss-IDE 2.0.0.Beta1-aux
<all of the above>.MD5
<the tests plugins>.zip
That makes it alot simpler IMO.
Thing to consider is:
a) what about source builds ?
b) should we provide a jbosside-alldeps.zip as a download under the
-nodeps?
- Everyone needs to make sure their feature.xml uses
"import" instead of
"include" for any plugin that is not in your feature (i.e. all eclipse
dependencies)
does the feature.xml in any way control what gets into the .zip file ?
or is that controlled by something else ?
The next step after is to consider simply depending on features instead of
individual plugins..
- We need to collaborate on a presentation for November's JBWorld
Europe.
If i understood correctly here is what we are planning to submit
indivdually:
Koen: Hands-on JBPM which uses the desginer
Olav: 2(?) talks about soapui and the jbosside plugin
Max: Hibernate Tools
(...and someone (Thomas Heute) might also do things in context of Seam)
What I suggest is that we can do a jbosside-BOF or something where we walk
through some of the features of the authors who will be at JBW and then let
people ask questions/suggestions etc. I'll find out who I should contact
inside
JBoss to email them directly instead of a "normal" submission.
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
11:36 a.m.
New subject: [jbosside-dev] Re: 8/28 team meeting notes
Comments below..
- We should add a new "ALL" file bundle that includes all
of our plugins
> but no Eclipse dependencies.
I thought about this and i think most of my comments on it went lost in
the skype echo, so here is what I suggested:
Keep the same downloads as we have now under the JBoss-IDE 2.0.0.Beta1
category.
add a new category called JBoss-IDE 2.0.0.Beta1-nodeps (or something) that
simply is the exact same plugins but *without*
any external plugins.
...and may I suggest to move all the MD5 files to a seperate category ?
They are the main reason for all the clutter imo (and it is downloaded by
*very* few people)
..and even move the test builds out of the way too.
The result would be something like:
<snip>
My only beef with this approach is that we won't have a single sourceforge
release to link to from our downloads page. That being said, we have
complete freedom over our download links and their layout, so given enough
creativity we can probably make this painless for the user..
Thing to consider is:
a) what about source builds ?
My opinion is we should go the JBossAS route and just make one big source
build with all of our source code.. this won't include any JARs or anything
so it should be relatively small yes?
b) should we provide a jbosside-alldeps.zip as a download under the
-nodeps?
Not a bad idea and would pretty easy to do..
- Everyone needs to make sure their feature.xml uses
"import" instead of
> "include" for any plugin that is not in your feature (i.e. all eclipse
> dependencies)
does the feature.xml in any way control what gets into the .zip file ?
or is that controlled by something else ?
IIRC "include" tells eclipse to bundle the plugin and "import"
doesn't. Our
build system lets you bundle arbitrary plugins w/ your zip as well.
The next step after is to consider simply depending on features instead of
individual plugins..
Yes, this would be ideal..
- We need to collaborate on a presentation for November's JBWorld
Europe.
If i understood correctly here is what we are planning to submit
indivdually:
Koen: Hands-on JBPM which uses the desginer
Olav: 2(?) talks about soapui and the jbosside plugin
His name is Ole .. you can blame my terrible American pronunciation skills
=)
Max: Hibernate Tools
(...and someone (Thomas Heute) might also do things in context of Seam)
What I suggest is that we can do a jbosside-BOF or something where we walk
through some of the features of the authors who will be at JBW and then
let
people ask questions/suggestions etc. I'll find out who I should contact
inside
JBoss to email them directly instead of a "normal" submission.
I think a BOF format would be great for our type of presentation, 2-3 hours
minimum, IMO. We ate up 2+ hours at Vegas like pie...
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
2:28 p.m.
New subject: [jbosside-dev] Re: 8/28 team meeting notes
My only beef with this approach is that we won't have a single
sourceforge
release to link to from our downloads page. That being said, we have
complete freedom over our download links and their layout, so given
enough creativity we can probably make this painless for the user..
We would just point to the same link as before - the categories would be
visible
there still...or is that not the case ?
> a) what about source builds ?
My opinion is we should go the JBossAS route and just make one big source
build with all of our source code.. this won't include any JARs or
anything so it should be relatively small yes?
and that is something users can just copy into the plugins directory and
sourcelookups
etc. will work automatically when e.g. debugging via eclipse PDE ?
IIRC "include" tells eclipse to bundle the plugin and
"import" doesn't.
Our
build system lets you bundle arbitrary plugins w/ your zip as well.
nice.
> Olav: 2(?) talks about soapui and the jbosside plugin
His name is Ole .. you can blame my terrible American pronunciation
skills
hehe - sorry Ole; I should know not to listen to American's pronouncing
scandinavian names.
I think a BOF format would be great for our type of presentation, 2-3
hours minimum, IMO. We ate up 2+ hours at Vegas like pie...
yes.
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
10:59 a.m.
New subject: [jbosside-dev] Re: 8/28 team meeting notes
One bullet item you forgot ;)
Each plugin should try and create a new-and-noteworthy for each release.
(I'll suggest doing that for current features today too....it's a fast
and simple way of communicating what is new without too much effort)
For an example see:
http://www.hibernate.org/hib_docs/tools/eclipse/newandnoteworthy/hibernat...
..and notice the "Previous" link at the top.
This format is a total rip-off from what eclipse normally does...but it
works ;)
/max
Sorry, got cut off in the middle of writing this =) Here's the
rest:
- Moved Beta2 release back 3 weeks to account for EclipseWorld,
Consulting
gig for Max (Sept 22nd)
- We should add a new "ALL" file bundle that includes all of our plugins
but
no Eclipse dependencies.
- Everyone needs to make sure their feature.xml uses "import" instead of
"include" for any plugin that is not in your feature (i.e. all eclipse
dependencies)
- Everyone also needs to perform "code cleanup" to make sure we are
catching
Exceptions correctly etc. Please reference Max's JIRA task here for
comments:
http://jira.jboss.com/jira/browse/JBIDE-351
- Marshall will look into standardizing on facets for providing runtime /
classpath containers to the user.
- We need to collaborate on a presentation for November's JBWorld Europe.
Friday is the deadline for submission..
On 8/28/06, Marshall Culpepper <marshall.culpepper(a)jboss.com> wrote:
>
> Notes from today's meeting:
>
>
>
>
>
> --
> Marshall Culpepper
> marshall.culpepper(a)jboss.com
> JBoss Eclipse IDE Lead, JBoss Inc.
>
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
6680
days inactive
6680
days old
jbosstools-dev@lists.jboss.org
5 comments
2 participants
participants (2)
-
Marshall Culpepper -
Max Rydahl Andersen