Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325877 - Implementation Defaults to User Library , preventing Finish from first page
Summary: Implementation Defaults to User Library , preventing Finish from first page
Status: RESOLVED WONTFIX
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: General (show other bugs)
Version: 2.3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-21 12:48 EDT by Zina Mostafia CLA
Modified: 2011-05-11 16:40 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zina Mostafia CLA 2010-09-21 12:48:56 EDT
Build Identifier: 3.6

When creating a project with a JPA facet, the 'JPA Facet' panel appears at the end. There is a red error mark because there are no configured JPA libraries for it to use. If the default for this page were to 'Disable Library Configuration' then there wouldn't be a red error, and Finish could be pressed much earlier on in the wizard (taking the subsequent defaults). 

Reproducible: Always
Comment 1 Zina Mostafia CLA 2010-11-01 11:26:29 EDT
Any update on this defect ?
Comment 2 Neil Hauge CLA 2010-11-01 14:55:01 EDT
I think this would be a desirable thing to do if we were able to determine that the selected Target Runtime already contained the necessary libraries.  I think that is the issue in this case, that we would not be able to accurately make this determination in all cases.  That said, we will investigate and determine if this can be done in at least some cases.
Comment 3 Neil Hauge CLA 2011-05-11 16:40:10 EDT
Upon further review we have determined that the current behavior is preferred.  Our thought is that the user should have to see this warning message at least once.  After initial selection the disabled library config will become the default selection and the user would be able to click Finish from the first page of the wizard on subsequent wizard runs.

Another option to avoid this scenario would be to provide your own disabled library provider (named whatever you would prefer) and set this as the highest priority library provider.  This way an adopter who always wanted to default to a particular library provider could do so.

Please reopen if you have any questions or would like to pursue a different solution.