I think it'd be great to see how each proposal would solve the following
issues at a minimum:
(1) Our recommended approach of one module per project in the standard
deployment structure
(2) The Maven standard structure
(3) The J2EE recommend structure in your email
I think seeing these comparisons would help us flush out any unforseen
details or problems with each approach.
Naci -- can you propose a scenario from some of the intiial requirements
that were put together from Eteration et al?
-------------------------------------------------------------------------
Kind Regards,
Michael D. Elder
Rational Studio / J2EE Tools
Development
IBM RTP Lab
Ext: (919) 543-8356
T/L: 441-8356
[EMAIL PROTECTED]
Thursday, September 08, 2005 1:29 PM
To: "General discussion of project-wide or architectural issues." <[email protected]>
cc:
From: Chuck Bridgham/Raleigh/[EMAIL PROTECTED]
Subject: Re: [wtp-dev] For review: Alternate flexible workspace proposals
To: "General discussion of project-wide or architectural issues." <[email protected]>
cc:
From: Chuck Bridgham/Raleigh/[EMAIL PROTECTED]
Subject: Re: [wtp-dev] For review: Alternate flexible workspace proposals
Absolutely,
I can add additional scenarios, do you have suggestions?
I can think of a couple:
1) Sharing/composing content from multiple projects.
2) Module projects consumed by multiple EAR modules.
Yes I can give more details, I really wanted to just present the idea at a conceptual level first before overwhelming everyone with too many details, but can produce them as needed.
Any area in particular?
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: [EMAIL PROTECTED]
Phone: 919-254-1848 (T/L: 444)
| Michael
Elder/Cambridge/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/09/2010 11:50 AM
|
|
Hi Chuck,
Will there be other scenarios described with details of how each proposal might solve them? Can we have more details on each option as well?
-------------------------------------------------------------------------
Kind Regards,
Michael D. Elder
Rational Studio / Services Tools Development
IBM RTP Lab
Ext: (919) 543-8356
T/L: 441-8356
[EMAIL PROTECTED]
| Chuck
Bridgham/Raleigh/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/07/2005 03:04 PM
|
|
Hi everyone,
Please review the document posted below, here is the first section:
Recently we have had two very productive meetings with the eclipse platform team, in understanding some of
the proposals for V3.2 that give WTP more options in regards to flexible workspaces/projects. During these
meetings 4 proposals were discussed that tackle different aspects of "flexible workspaces" Much of the existing
flexible project internal api is an implementation that satisfies many of the requirements declared last year.
Many of these scenarios should be solved at the platform level, and our current WTP api has a few serious
restrictions that forces us to re-evaluate our direction.
http://www.eclipse.org/webtools/jst/components/j2ee/proposals/WTPFlexibleProjectProposals.html
Please respond with your feedback soon.
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: [EMAIL PROTECTED]
Phone: 919-254-1848 (T/L: 444)
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
