Re: [jbosside-dev] packaging API?
by Ole Matzura
Thanks Rob,
I'll check with Marshall on the status of this API..
regards!
/Ole
-----Original Message-----
From: Rob Stryker [mailto:rob.stryker@jboss.com]
Sent: Sunday, September 24, 2006 03:23 AM
To: 'Ole Matzura'
Cc: jbosside-dev(a)lists.jboss.org
Subject: Re: [jbosside-dev] packaging API?
Marshall has some packaging API underway... I dont even think wtp has any good packaging API available.
On 9/23/06, Ole Matzura <ole(a)eviware.com> wrote:Hello all,
maybe I missed this in some previous discussion, but I remember some
talks about a "new" packaging API that would replace the "old" one.. has
this happened? Will it happen? Or should packaging be done in some
"WTP-dictated" way?
thanks for any clarifications!
regards,
/Ole
eviware.com
_______________________________________________
jbosside-dev mailing list
jbosside-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosside-dev
18 years, 5 months
RE: [jbosside-dev] Call for tags...
by Koen Aers
For jbpm, best is to use the old tag (jbpm_gpd_3_0_11) unless the
release of jbpm 3.2 alpha (with the the 3.0.12 gpd) is before JBossIDE
2.0.0.Beta2. In that case there will be a jbpm_gpd_3_0_12 available.
Regards,
Koen
________________________________
From: jbosside-dev-bounces(a)lists.jboss.org
[mailto:jbosside-dev-bounces@lists.jboss.org] On Behalf Of Marshall
Culpepper
Sent: vrijdag 22 september 2006 4:23
To: Max Andersen
Cc: Kris Verlaenen; jbosside-dev(a)lists.jboss.org; Michael Neale
Subject: Re: [jbosside-dev] Call for tags...
Yes of course integration builds are the first part of the
process but we need tags for that =)
On 9/21/06, Max Rydahl Andersen < max.andersen(a)jboss.com
<mailto:max.andersen@jboss.com> > wrote:
On Wed, 20 Sep 2006 21:16:30 +0200, Marshall Culpepper
<marshall.culpepper(a)jboss.com> wrote:
> Well the release build is supposed to be on Friday,
but we can postpone
> until Monday if needed (I'd rather not though)
I assume you mean integration build ? Because we need
testing (the
amount of basic startup questions on the forum proved it
again ;)
I just completed my work and everything is in HEAD at
the moment.
I got caught up doing support with respect to
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2093
so would need to work on the documentation tomorrow for
inclusion in the
release.
/max
>
> On 9/20/06, Max Rydahl Andersen
<max.andersen(a)jboss.com> wrote:
>>
>>
>> for when ?
>>
>> > Hey guys...
>> >
>> > I need CVS/Subversion tags for JBossIDE 2.0.0.Beta2
>> >
>>
>>
>>
>> --
>> --
>> 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
>>
>
>
>
--
--
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
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
18 years, 5 months
RE: [jbosside-dev] Re: jBPM Designer feature.xml needs to be updated
by Koen Aers
Great! I am in Paris for a jBPM training now but I will include this
ASAP
________________________________
From: marshall.jboss(a)gmail.com [mailto:marshall.jboss@gmail.com]
On Behalf Of Marshall Culpepper
Sent: dinsdag 19 september 2006 18:12
To: Koen Aers
Cc: Dev - JBoss IDE; jbosside-dev(a)lists.jboss.org
Subject: Re: [jbosside-dev] Re: jBPM Designer feature.xml needs
to be updated
OK Koen.. I've uploaded a JAR to the repository under
eclipse/releng/jbosside-releng-tasks.jar. This includes the
CalculateFeatureDependenciesTask, and the antlib.xml is also included.
On 9/14/06, Koen Aers <koen.aers(a)jboss.com> wrote:
No I meant actually to CC jbosside-dev :-))
________________________________
From: marshall.jboss(a)gmail.com
[mailto:marshall.jboss@gmail.com] On Behalf Of Marshall Culpepper
Sent: donderdag 14 september 2006 19:16
To: Dev - JBoss IDE
Subject: Fwd: [jbosside-dev] Re: jBPM Designer
feature.xml needs to be updated
I think you meant to CC dev-jbosside on this one
---------- Forwarded message ----------
From: Koen Aers < koen.aers(a)jboss.com
<mailto:koen.aers@jboss.com> >
Date: Sep 14, 2006 6:59 AM
Subject: RE: [jbosside-dev] Re: jBPM Designer
feature.xml needs to be updated
To: Marshall Culpepper <marshall.culpepper(a)jboss.com >
I am pretty much OK with doing things the way they
should be done, no problem with that.
Btw, are you talking about the meeting when I was in
India? I cannot remember discussing this, but this might be due to some
kind of jetlag ;-). Anyway, we are in the process of releasing jBPM 3.2
alpha1 so the release has my number one attention at present. And as I
mentioned earlier, the good way to reuse the tag that Marshall has
written would be to bundle it in a library that resides in the
repository to avoid duplication. Or am I wrong about this?
Regards,
Koen
________________________________
From: marshall.jboss(a)gmail.com [mailto:
marshall.jboss(a)gmail.com <mailto:marshall.jboss@gmail.com> ] On Behalf
Of Marshall Culpepper
Sent: woensdag 13 september 2006 22:31
To: Max Andersen
Cc: Koen Aers; jbosside-dev(a)lists.jboss.org
Subject: Re: [jbosside-dev] Re: jBPM Designer
feature.xml needs to be updated
Yes, this is what we decided on our meeting.. we are
moving all dependencies to be included the "right" way, and retrofitting
the build system to calculate feature dependencies based on those
entries, instead of counting on eclipse PDE to auto-bundle things that
are listed as <plugin>.
On 9/13/06, Max Rydahl Andersen <max.andersen(a)jboss.com>
wrote:
just to be clear:
Our old/current way of bundling things are
*wrong* in context of
integrating with the rest of
the eclipse ecosystem. you should only have
<plugin> for plugins that is
actually part of the plugin
everything else is <import> of either plugin's
or feature's.
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
18 years, 5 months
RE: [jbosside-dev] Re: jBPM Designer feature.xml needs to be updated
by Koen Aers
No I meant actually to CC jbosside-dev :-))
________________________________
From: marshall.jboss(a)gmail.com [mailto:marshall.jboss@gmail.com]
On Behalf Of Marshall Culpepper
Sent: donderdag 14 september 2006 19:16
To: Dev - JBoss IDE
Subject: Fwd: [jbosside-dev] Re: jBPM Designer feature.xml needs
to be updated
I think you meant to CC dev-jbosside on this one
---------- Forwarded message ----------
From: Koen Aers <koen.aers(a)jboss.com >
Date: Sep 14, 2006 6:59 AM
Subject: RE: [jbosside-dev] Re: jBPM Designer feature.xml needs
to be updated
To: Marshall Culpepper <marshall.culpepper(a)jboss.com >
I am pretty much OK with doing things the way they should be
done, no problem with that.
Btw, are you talking about the meeting when I was in India? I
cannot remember discussing this, but this might be due to some kind of
jetlag ;-). Anyway, we are in the process of releasing jBPM 3.2 alpha1
so the release has my number one attention at present. And as I
mentioned earlier, the good way to reuse the tag that Marshall has
written would be to bundle it in a library that resides in the
repository to avoid duplication. Or am I wrong about this?
Regards,
Koen
________________________________
From: marshall.jboss(a)gmail.com
[mailto:marshall.jboss@gmail.com] On Behalf Of Marshall Culpepper
Sent: woensdag 13 september 2006 22:31
To: Max Andersen
Cc: Koen Aers; jbosside-dev(a)lists.jboss.org
Subject: Re: [jbosside-dev] Re: jBPM Designer
feature.xml needs to be updated
Yes, this is what we decided on our meeting.. we are moving all
dependencies to be included the "right" way, and retrofitting the build
system to calculate feature dependencies based on those entries, instead
of counting on eclipse PDE to auto-bundle things that are listed as
<plugin>.
On 9/13/06, Max Rydahl Andersen <max.andersen(a)jboss.com> wrote:
just to be clear:
Our old/current way of bundling things are *wrong* in
context of
integrating with the rest of
the eclipse ecosystem. you should only have <plugin> for
plugins that is
actually part of the plugin
everything else is <import> of either plugin's or
feature's.
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
18 years, 5 months