1:04 a.m.
I was checking if there are components that requires version update in
4.0.x branch and
It looks like some components should have version updated (see attached
txt file for component changes):
esb ( 1.5.0 - 1.5.1 )
forge ( 1.1.0 - 1.1.1 )
jbpm ( 4.5.0 - 4.5.1 )
openshift ( 2.4.0 - 2.4.1 )
vpe ( 3.4.0 - 3.4.1 )
server/archives ( 3.4.0 - 3.4.1 )
version is already updated in:
bpel ( 1.2.0 -> 1.2.1 )
server/as ( 2.4.0 - 2.4.1 )
not sure if it is really required:
runtime-soa - nick suggested it can be deleted, because all runtime
detection plugins moved to corresponding modules
Could component leads confirm if version update above is really required?
Thanks
Denis
3:03 a.m.
not sure if it is really required:
runtime-soa - nick suggested it can be deleted, because all runtime detection plugins
moved to corresponding modules
Since when ? where are the new homes/repos ?
jbosstools-4.0.x haven't had such changes and runtime-soa is still part of jboss soa
tooling 3.3.x afaik ?
I haven't seen any of these runtime detection plugins actually been picked up yet ?
ESB had some movement but was that followed through ?
Could component leads confirm if version update above is really
required?
If any change in the source repos then it is required. Pretty simple afaics.
/max
11:09 a.m.
New subject: Some modules in jbosstools-4.0.x require version update
I'm not sure why ESB would have changed in the past 5 days - Brian? Nick? Doug?
--Len
----- Original Message -----
From: "Max Rydahl Andersen"
<max.andersen(a)redhat.com>
To: "Denis Golovin" <dgolovin(a)exadel.com>
Cc: jbosstools-dev(a)lists.jboss.org
Sent: Wednesday, February 20, 2013 4:03:53 AM
Subject: Re: [jbosstools-dev] Some modules in jbosstools-4.0.x
require version update
>
> not sure if it is really required:
> runtime-soa - nick suggested it can be deleted, because all runtime
> detection plugins moved to corresponding modules
Since when ? where are the new homes/repos ?
jbosstools-4.0.x haven't had such changes and runtime-soa is still
part of jboss soa tooling 3.3.x afaik ?
I haven't seen any of these runtime detection plugins actually been
picked up yet ?
ESB had some movement but was that followed through ?
> Could component leads confirm if version update above is really
> required?
If any change in the source repos then it is required. Pretty simple
afaics.
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Len DiMaggio (ldimaggi(a)redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886 USA
tel: 978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
11:24 a.m.
New subject: Some modules in jbosstools-4.0.x require version update
Nick moved the ESB runtime detector out of the soa project into the esb project.
That's the only change I know about.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Len DiMaggio" <ldimaggi(a)redhat.com>
To: "Max Rydahl Andersen" <max.andersen(a)redhat.com>
Cc: jbosstools-dev(a)lists.jboss.org
Sent: Wednesday, February 20, 2013 10:09:09 AM
Subject: Re: [jbosstools-dev] Some modules in jbosstools-4.0.x require version update
I'm not sure why ESB would have changed in the past 5 days - Brian? Nick? Doug?
--Len
From: "Max Rydahl Andersen" <max.andersen(a)redhat.com>
To: "Denis Golovin" <dgolovin(a)exadel.com>
Cc: jbosstools-dev(a)lists.jboss.org
Sent: Wednesday, February 20, 2013 4:03:53 AM
Subject: Re: [jbosstools-dev] Some modules in jbosstools-4.0.x require version update
not sure if it is really required:
runtime-soa - nick suggested it can be deleted, because all runtime detection plugins
moved to corresponding modules
Since when ? where are the new homes/repos ?
jbosstools-4.0.x haven't had such changes and runtime-soa is still part of jboss soa
tooling 3.3.x afaik ?
I haven't seen any of these runtime detection plugins actually been picked up yet ?
ESB had some movement but was that followed through ?
Could component leads confirm if version update above is really
required?
If any change in the source repos then it is required. Pretty simple afaics.
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Len DiMaggio (ldimaggi(a)redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886 USA
tel: 978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
9:05 p.m.
New subject: Some modules in jbosstools-4.0.x require version update
>> runtime-soa - nick suggested it can be deleted, because all
runtime
detection plugins moved to corresponding modules
To be clear, this only applies to jbosstools-runtime-soa
4.0.x/4.1.0.Alpha1x/master branches in github. The older 3.3.x stuff in
SVN should not be touched as it's part of the JBDS SOA 5 stream. And I
meant it COULD be deleted once the migration of all three
plugins/features was complete.
I opened PRs to move the contents from that repo into ESB, jbpm, and
droolsjbpm, but the droolsjbpm stuff requires further changes as it
changes the way they build. With this change they will depend on JBT,
and therefore will need to retool they way they produce their update
site. They've also asked to upversion the feature/plugin to match their
release version (eg., 6.0.0).
Ref: https://github.com/droolsjbpm/droolsjbpm-tools/pull/14
See also: https://issues.jboss.org/browse/JBIDE-11098, 11099, 11100, 11101
N
On 02/20/2013 02:14 PM, Denis Golovin wrote:
... and jBPM was moved to jbpm module, runtime-soa still contains
original plugins for runtime esb and jbpm runtime detection.
Only drools runtime detector was not moved.
Denis
On 02/20/2013 09:24 AM, Brian Fitzpatrick wrote:
> Nick moved the ESB runtime detector out of the soa project into the esb project.
That's the only change I know about.
>
> _______________________________
> Brian Fitzpatrick (aka "Fitz")
> Senior Software Engineer, SOA-P
> JBoss by Red Hat
>
> ----- Original Message -----
> From: "Len DiMaggio"<ldimaggi(a)redhat.com>
> To: "Max Rydahl Andersen"<max.andersen(a)redhat.com>
> Cc:jbosstools-dev@lists.jboss.org
> Sent: Wednesday, February 20, 2013 10:09:09 AM
> Subject: Re: [jbosstools-dev] Some modules in jbosstools-4.0.x require version
update
>
>
>
> I'm not sure why ESB would have changed in the past 5 days - Brian? Nick? Doug?
>
>
> --Len
>
>
>
>
>
>
>
> From: "Max Rydahl Andersen"<max.andersen(a)redhat.com>
> To: "Denis Golovin"<dgolovin(a)exadel.com>
> Cc:jbosstools-dev@lists.jboss.org
> Sent: Wednesday, February 20, 2013 4:03:53 AM
> Subject: Re: [jbosstools-dev] Some modules in jbosstools-4.0.x require version
update
>
>> not sure if it is really required:
>> runtime-soa - nick suggested it can be deleted, because all runtime detection
plugins moved to corresponding modules
> Since when ? where are the new homes/repos ?
> jbosstools-4.0.x haven't had such changes and runtime-soa is still part of jboss
soa tooling 3.3.x afaik ?
> I haven't seen any of these runtime detection plugins actually been picked up yet
?
>
> ESB had some movement but was that followed through ?
>
>> Could component leads confirm if version update above is really required?
> If any change in the source repos then it is required. Pretty simple afaics.
>
> /max
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
3:52 a.m.
New subject: Some modules in jbosstools-4.0.x require version update
On 21 Feb 2013, at 04:05, Nick Boldt <nboldt(a)redhat.com> wrote:
>>> runtime-soa - nick suggested it can be deleted, because
all runtime
detection plugins moved to corresponding modules
To be clear, this only applies to jbosstools-runtime-soa
4.0.x/4.1.0.Alpha1x/master branches in github. The older 3.3.x stuff in
SVN should not be touched as it's part of the JBDS SOA 5 stream. And I
meant it COULD be deleted once the migration of all three
plugins/features was complete.
For me *move* of a runtime plugins means that the features are
A) The project owners taken ownership of these (just applying a PR blindly without
testing doesn't count does it ? ;)
B) setup and verified to build and be included properly in JBTIS
C) no longer present in
https://github.com/jbosstools/jbosstools-runtime-soa/tree/master/plugins
None o
I opened PRs to move the contents from that repo into ESB, jbpm, and
droolsjbpm, but the droolsjbpm stuff requires further changes as it
changes the way they build. With this change they will depend on JBT,
and therefore will need to retool they way they produce their update
site. They've also asked to upversion the feature/plugin to match their
release version (eg., 6.0.0).
Ref: https://github.com/droolsjbpm/droolsjbpm-tools/pull/14
Okey - if Drools pluginrefer to one of our sites is that stripped out when
composited/aggregated in JBTIS ?
Otherwise when user point to this site they will have jboss tools updatesite show up twice
with possible incompatible versions, right ?
/max
1:18 p.m.
New subject: Some modules in jbosstools-4.0.x require version update
On 02/21/2013 01:52 AM, Max Rydahl Andersen wrote:
On 21 Feb 2013, at 04:05, Nick Boldt <nboldt(a)redhat.com>
wrote:
>>>> runtime-soa - nick suggested it can be deleted, because all runtime
> detection plugins moved to corresponding modules
>
> To be clear, this only applies to jbosstools-runtime-soa
> 4.0.x/4.1.0.Alpha1x/master branches in github. The older 3.3.x stuff in
> SVN should not be touched as it's part of the JBDS SOA 5 stream. And I
> meant it COULD be deleted once the migration of all three
> plugins/features was complete.
For me *move* of a runtime plugins means that the features are
A) The project owners taken ownership of these (just applying a PR blindly without
testing doesn't count does it ? ;)
B) setup and verified to build and be included properly in JBTIS
C) no longer present in
https://github.com/jbosstools/jbosstools-runtime-soa/tree/master/plugins
"take ownership" means some changes in original runtime detector plugin,
like:
- change plugin/feature name to match module namespace;
- do the refactoring in plug-in's packages to match module namespace
It is good time to do so, because it is first development release.
Does that sound right?
Denis
None o
> I opened PRs to move the contents from that repo into ESB, jbpm, and
> droolsjbpm, but the droolsjbpm stuff requires further changes as it
> changes the way they build. With this change they will depend on JBT,
> and therefore will need to retool they way they produce their update
> site. They've also asked to upversion the feature/plugin to match their
> release version (eg., 6.0.0).
>
> Ref: https://github.com/droolsjbpm/droolsjbpm-tools/pull/14
Okey - if Drools pluginrefer to one of our sites is that stripped out when
composited/aggregated in JBTIS ?
Otherwise when user point to this site they will have jboss tools updatesite show up
twice with possible incompatible versions, right ?
/max
3:02 p.m.
New subject: Some modules in jbosstools-4.0.x require version update
No, I don't think changing bundle Ids are a requirement. Some of these could easily be
maintained separate from their "homes" IMO.
What I mean ownership is that someone will be developing and testing these in context of
eap,soap, JPP etc. and not just only individual runtime projects.
That's what the runtime detection is about - making the setup easy across runtimes and
versions.
/max (sent from my phone)
On 21/02/2013, at 20.18, Denis Golovin <dgolovin(a)exadel.com> wrote:
On 02/21/2013 01:52 AM, Max Rydahl Andersen wrote:
> On 21 Feb 2013, at 04:05, Nick Boldt <nboldt(a)redhat.com> wrote:
>
>>>>> runtime-soa - nick suggested it can be deleted, because all runtime
>> detection plugins moved to corresponding modules
>>
>> To be clear, this only applies to jbosstools-runtime-soa
>> 4.0.x/4.1.0.Alpha1x/master branches in github. The older 3.3.x stuff in
>> SVN should not be touched as it's part of the JBDS SOA 5 stream. And I
>> meant it COULD be deleted once the migration of all three
>> plugins/features was complete.
> For me *move* of a runtime plugins means that the features are
>
> A) The project owners taken ownership of these (just applying a PR blindly without
testing doesn't count does it ? ;)
> B) setup and verified to build and be included properly in JBTIS
> C) no longer present in
https://github.com/jbosstools/jbosstools-runtime-soa/tree/master/plugins
"take ownership" means some changes in original runtime detector plugin, like:
- change plugin/feature name to match module namespace;
- do the refactoring in plug-in's packages to match module namespace
It is good time to do so, because it is first development release.
Does that sound right?
Denis
>
> None o
>> I opened PRs to move the contents from that repo into ESB, jbpm, and
>> droolsjbpm, but the droolsjbpm stuff requires further changes as it
>> changes the way they build. With this change they will depend on JBT,
>> and therefore will need to retool they way they produce their update
>> site. They've also asked to upversion the feature/plugin to match their
>> release version (eg., 6.0.0).
>>
>> Ref: https://github.com/droolsjbpm/droolsjbpm-tools/pull/14
> Okey - if Drools pluginrefer to one of our sites is that stripped out when
composited/aggregated in JBTIS ?
>
> Otherwise when user point to this site they will have jboss tools updatesite show up
twice with possible incompatible versions, right ?
>
> /max
4327
days inactive
4328
days old
jbosstools-dev@lists.jboss.org
8 comments
6 participants
participants (6)
-
Brian Fitzpatrick -
Denis Golovin -
Len DiMaggio -
Max Andersen -
Max Rydahl Andersen -
Nick Boldt