| Re: Migration from JBuilder (Export dependencies) [message #205411] |
Wed, 05 December 2007 21:49  |
Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
Paul wrote:
> Hey guys,
>
> I'm trying to move JEE projects out of JBuilder(2005) and into Eclipse.
>
> One function that JBuilder does and I can't seem to figure out how to do
> in Eclipse is this:
> In JBuilder, we have a number of common frameworks as Required Libraries
> that are versioned and reside outside of the project. Whenever we build
> the project, it extracts the classes out of the library and includes
> them in the application (the setting is under Properties for the EJB
> under Dependencies and we simply select "Include All")
>
> In Eclipse, I assumed we could do the same thing by checking the box for
> the library under "Order and Export", but checking that box does nothing.
>
> Is there any way to mimic our setup in JBuilder? I don't want to have
> to add this to the project in Eclipse, it's an external library and I
> want to keep it that way until we export our EAR.
>
> Thanks guys! Using Eclipse 3.2 (soon to upgrade to 3.3)
>
I believe you will need to setup a Project Dependency on your Build
Path. I'm copying the eclipse.webtools newsgroup on this as well, as I
know this has been answered there.
You might also want to take a look at the WTP FAQ and the Tomcat FAQ
(has some stuff not necessarily related to Tomcat).
http://wiki.eclipse.org/WTP_FAQ
http://wiki.eclipse.org/WTP_Tomcat_FAQ
Dave
|
|
|
| Re: Migration from JBuilder (Export dependencies) [message #205419 is a reply to message #205411] |
Thu, 06 December 2007 17:01  |
 Rob Frost
Messages: 64
Registered: July 2009 |
Member |
|
|
Hi Paul/Dave,
Based on the description, it sounds like you want the contents of these
libraries (referenced on the project classpath in Eclipse) to be included in
the published/exported structure of the module. WTP does allow you to mark
library and container classpath entries for inclusion in the
published/exported structure of an EAR/WAR via the J2EE Module Dependencies
page (will be placed in the root of the EAR or WEB-INF/lib dir of the WAR).
See http://wiki.eclipse.org/ClasspathEntriesPublishExportSupport for details
on the current support and planned 3.0 enhancements.
Hope this helps,
Rob
"David Carver" <dcarver@starstandard.org> wrote in message
news:47571CF2.7070803@starstandard.org...
> Paul wrote:
>> Hey guys,
>>
>> I'm trying to move JEE projects out of JBuilder(2005) and into Eclipse.
>>
>> One function that JBuilder does and I can't seem to figure out how to do
>> in Eclipse is this:
>> In JBuilder, we have a number of common frameworks as Required Libraries
>> that are versioned and reside outside of the project. Whenever we build
>> the project, it extracts the classes out of the library and includes them
>> in the application (the setting is under Properties for the EJB under
>> Dependencies and we simply select "Include All")
>>
>> In Eclipse, I assumed we could do the same thing by checking the box for
>> the library under "Order and Export", but checking that box does nothing.
>>
>> Is there any way to mimic our setup in JBuilder? I don't want to have to
>> add this to the project in Eclipse, it's an external library and I want
>> to keep it that way until we export our EAR.
>>
>> Thanks guys! Using Eclipse 3.2 (soon to upgrade to 3.3)
>>
>
> I believe you will need to setup a Project Dependency on your Build Path.
> I'm copying the eclipse.webtools newsgroup on this as well, as I know this
> has been answered there.
>
> You might also want to take a look at the WTP FAQ and the Tomcat FAQ (has
> some stuff not necessarily related to Tomcat).
>
> http://wiki.eclipse.org/WTP_FAQ
> http://wiki.eclipse.org/WTP_Tomcat_FAQ
>
> Dave
|
|
|
| Re: Migration from JBuilder (Export dependencies) [message #205435 is a reply to message #205419] |
Thu, 06 December 2007 18:54 |
| Eclipse User |
|
|
|
Originally posted by: paul.richardson.thebeerstore.ca
Thank you both, that is indeed what I was wanting.
The only interesting thing JBuilder does is it actually extracts the
needed files out of the library and compiles it directly into the source.
I would imagine this would not be considered "Best-Practices" since its
essentially mixing code and will move to exporting the entire Library when
its needed instead.
|
|
|
| Re: Migration from JBuilder (Export dependencies) [message #205459 is a reply to message #205435] |
Thu, 06 December 2007 22:19 |
| Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
Paul wrote:
> Thank you both, that is indeed what I was wanting.
>
> The only interesting thing JBuilder does is it actually extracts the
> needed files out of the library and compiles it directly into the
> source. I would imagine this would not be considered "Best-Practices"
> since its essentially mixing code and will move to exporting the entire
> Library when its needed instead.
>
You can get something similiar with Importing a WAR or EAR file, but
typically that is a messy situation.
|
|
|
Powered by
FUDForum. Page generated in 0.03303 seconds
] 
Search
Help
Register
Login
Home
