Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] Regression in Java EE / EJB component

The same fix also takes care of 209264, which has a lot worse of an affect on the user. Given the simplicity of the fix and the fact that two issues will be resolved, I went ahead and released. I think it makes sense to respin to pickup this change for this week's I-build. No re-testing should be required.
 
I am looking at 209268 now. That problem doesn't look as severe as the first two. The add to ear option on project creation is not working for any project type. There are no errors displayed or logged. There is a simple workaround (use j2ee module dependencies to make the link later). This issue should't to preclude declaration of this i-build, but should be fixed for final m3 build.
 
- Konstantin
 


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Angel Vera
Sent: Thursday, November 08, 2007 2:35 PM
To: General discussion of project-wide or architectural issues.
Cc: General discussion of project-wide or architectural issues.; wtp-dev-bounces@xxxxxxxxxxx
Subject: RE: [wtp-dev] Regression in Java EE / EJB component


hmm.. I took a look at the scenario and although the "Context Root"  field is empty if you click Finish the field get populated correctly.

In my opinion, the fact that field gets populated if you click Finish makes the defect not a major one. It would be major if it leads to user to some state where he can't deploy the application or his application doesn't work and it is difficult to find it how the application is broken. But in this case, if the user doesn't notice the empty field, everything will still work. Because of this I do not think it is a candidate for a re-spin.

Best Regards,
-- --
Mr. Angel Vera
  Server Tools Developer for WTP and Rational
  Lotus Notes: Angel Vera/Toronto/IBM@IBMCA
  Tel: 905-413-5919 - E-Mail: arvera@xxxxxxxxxx
-----
Those who think that something is impossible,
should not interfere with those who are willing to do it. - Angel Vera



"Konstantin Komissarchik" <kosta@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

11/08/2007 04:42 PM

Please respond to
"General discussion of project-wide or architectural issues."        <wtp-dev@xxxxxxxxxxx>

To
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject
RE: [wtp-dev] Regression in Java EE / EJB component





I have a fix for 209262 in hand. Petty simple. Should I release it for a re-spin? Thoughts?
 
- Konstantin
 


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Raev, Kaloyan
Sent:
Thursday, November 08, 2007 1:12 PM
To:
General discussion of project-wide or architectural issues.
Subject:
[wtp-dev] Regression in Java EE / EJB component

Hello,

I mark the Java EE smoke test as successful, but there are three issues that are regression from the last I-build:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209262
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209264
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209268

It would be nice if they are fixed during the M3 shutdown period.

Greetings,
Kaloyan Raev

Senior Developer

NW C JS TOOLS JEE (BG)

SAP Labs Bulgaria

T +359/2/9157-416

mailto:kaloyan.raev@xxxxxxx
www.sap.com


Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev


Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Back to the top