I don’t see any reason why
productization support could not be handled incrementally with some facilities
added in 1.0.1, some in 1.5, etc.
From BEA’s standpoint some action on
this is necessary in 1.0.1 timeframe, since that’s the release that we
will be shipping on and the current behavior is pretty bad for us. If we don’t
want to start implementing productization hooks in 1.0.1, it would also be
acceptable for WTP wizards to not attempt to switch the perspective. I suspect
that’s a less desirable solution, since that will make the J2EE
perspective less discoverable for base WTP users.
- Konstantin
From: wtp-dev-bounces@xxxxxxxxxxx
[mailto:wtp-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chuck Bridgham
Sent: Friday, January 20, 2006
10:16 AM
To: General
discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Invitation
for comment -
The question of Eclipse productization is broader and
really needs to be coordinated across WTP.
I
know of several areas where default settings should be configurable including
validation, wizard properties, facet selection etc....
Your
example of a configurable "final perspective" is a good one, and one
we had in mind as well.
Once
we collect all of these configurable properties, we could publish this list,
and adopters will have an opportunity to customize for their product.
My
timeframe for this is R1.5
Thanks
- Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle
Park, NC
Email: cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)
|
"Konstantin
Komissarchik" <kosta@xxxxxxx>
Sent
by: wtp-dev-bounces@xxxxxxxxxxx
01/20/2006 11:47 AM
|
Please
respond to
"General discussion of project-wide or
architectural issues."
|
|
|
To
|
"General
discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
[wtp-dev] Invitation for comment
|
|
I’d like to invite anyone who is interested to comment on:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=122667
WTP
project wizards should not change perspective or allow the perspective to be
configurable
Problem:
BEA is
building a product using WTP (vs. just building some plugins that work with
WTP). Our product definition people created a custom perspective that they feel
is best suited for people using our product. That is the perspective
that’s active when our product is launched. The problem comes up when
creating WTP projects. The WTP project creation wizards prompt the user to
switch to the default J2EE perspective after the project is created. We feel
that this behavior creates confusion for our users because it leads them away
from the perspective that we created.
Proposed
Solution:
Eclipse
productization api (see IProduct) allows an arbitrary bag of properties to be
attached to the product definition. Only one product definition is active at a
time. If we create a new “wtp.perspective” property, whose default
value is the J2EE perspective, we could override that property in our product
definition. The WTP project creation wizards would check the value of the
property when prompting the user to switch the perspective.
Impact:
Low.
The behavior would not change in any way unless the property is overridden.
Timeframe:
1.0.1
If you
want to comment on this issue, please post your comments directly into the
bugzilla.
Thanks,
Konstantin
BEA
Systems_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
