|
| Re: WTP project import/export and version control? [message #199679 is a reply to message #199631] |
Thu, 13 September 2007 13:20   |
Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Steve,
first of all, you can export/import WTP specific projects as EAR or WAR file
(depending on the type of project).
You should not need workspace\.metadata, normally all relevant settings are
stored in the files starting with a dot in your project, or in the subdirectory
".settings".
What errors do you see ?
Best regards
Wolfgang
Steve Jones wrote:
> Hi,
>
> If I take a collection error free and working WTP projects and import
> them into a clean workspace I get errors all over the place.
>
> If I save and recover the projects using svn or cvs the error count is
> even worse.
>
> The only thing that seems to work for me so far is to zip the entire
> workspace.
>
> The metadata stored in <workspace>\.metadata is clearly critical to the
> successful building of WTP projects.
>
> It must be possible to import/export and version control WTP projects
> can someone tell me what the secret is.
>
> Thanks, Steve.
|
|
|
| Re: WTP project import/export and version control? [message #199816 is a reply to message #199679] |
Mon, 17 September 2007 09:17 |
 Steve Jones
Messages: 95
Registered: July 2009 |
Member |
|
|
Hi Wolfgang,
I'm new to web services and WTP. I'm working through the WTP book as an
introduction to both.
Chapter 8 of the book develops an EAR/EJB/EJBClient/Model example as
four projects using JBoss as the target.
Having got the example working (page 366) if I import the the four
projects using "Import->Existing Projects into Workspace" into a clean
workspace I get 113 errors.
Many of these errors are classpath related but others are more obscure:
CHKJ2804E: ...
javax.jms cannot be resolved ...
javax.ejb cannot be resolved to a type ...
Target runtime JBoss v4.2 is not defined.
I emailed Arthur Ryman, one of the books authors, about why complete
reference solutions for the books examples were not available. His reply
was:
"The complete projects aren't available for download since they have
too much metadata in them".
This reply together the load of errors that I've experienced made me
wonder if I was wasting my time trying to archive the projects using svn.
The problem for me is that all these project have been kicked off using
the WTP project wizards. You're never quite sure what properties the
wizards have set on your behalf.
If your saying that the WTP project metadata is minimalistic then I'll
put some effort into working out what needs to be done to manually
recover the projects to an error free state. It will be a good learning
exercise if nothing else.
Cheers, Steve.
Wolfgang Knauf wrote:
> Hi Steve,
>
> first of all, you can export/import WTP specific projects as EAR or WAR
> file (depending on the type of project).
>
> You should not need workspace\.metadata, normally all relevant settings
> are stored in the files starting with a dot in your project, or in the
> subdirectory ".settings".
>
> What errors do you see ?
>
> Best regards
>
> Wolfgang
>
> Steve Jones wrote:
>> Hi,
>>
>> If I take a collection error free and working WTP projects and import
>> them into a clean workspace I get errors all over the place.
>>
>> If I save and recover the projects using svn or cvs the error count is
>> even worse.
>>
>> The only thing that seems to work for me so far is to zip the entire
>> workspace.
>>
>> The metadata stored in <workspace>\.metadata is clearly critical to
>> the successful building of WTP projects.
>>
>> It must be possible to import/export and version control WTP projects
>> can someone tell me what the secret is.
>>
>> Thanks, Steve.
|
|
|
| Re: WTP project import/export and version control? [message #199867 is a reply to message #199816] |
Mon, 17 September 2007 13:47 |
| Eclipse User |
|
|
|
Originally posted by: kosta.bea.com
Steve,
WTP stores as much of metadata as possible at project-level in order to
enable project portability and sharing among team members.
Unfortunately, some of the metadata contains machine-specific
information and thus cannot be stored in the project. The most common
example of this is the definition of the server runtime that you are
using. The name of the runtime is stored in the project metadata. The
definition (which includes one or more absolute paths) is stored in the
workspace metadata.
One of the errors that you see is "Target runtime JBoss v4.2 is not
defined". You can define the runtime in your new workspace by going to
Workspace Preferences -> Server -> Installed Runtimes. I suspect that
once you define the runtime a lot of the other errors will resolve as
well. They look to be due to your projects missing types that are
contributed by the server runtime. If there are any remaining errors,
post the details and we can help you sort them out.
Hope this helps,
- Konstantin
|
|
|
Powered by
FUDForum. Page generated in 0.02050 seconds
] 
Search
Help
Register
Login
Home
