| Make plugins for legacy Java code [message #23762] |
Wed, 24 September 2008 19:01  |
Eclipse User |
|
|
|
Hi there,
I have a big repository with one big source directory containing a big
Java package structure and all Java source files.
I need to create several Eclipse plug-ins that bundle some parts of that
source tree, WITHOUT moving files around to new locations. I may only
ADD certain config files, like manifests, plugin.xml and stuff, or
create completely new directories for eclipse projects. But I can NOT
move or copy some of the source files into new source directories within
the new Eclipse projects.
What can I do? Can I convince Eclipse somehow to adapt to our directory
structure instead of we have to adapt to Eclipse? I'm not allowed to
break the current structure as the code is also used in other contexts
than Eclipse.
Is there any way?
Cheers,
Hauke
|
|
|
|
| Re: Make plugins for legacy Java code [message #24231 is a reply to message #23846] |
Thu, 25 September 2008 16:03  |
| Eclipse User |
|
|
|
You can make plugin projects the have all the metadata as if the project
actually contained the source. Then use custom callbacks to
automatically copy .java files from the main structure at build time.
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_custom_callbacks.htm
-Andrew
ekke wrote:
> Hauke Fuhrmann schrieb:
>> Hi there,
>>
>> I have a big repository with one big source directory containing a big
>> Java package structure and all Java source files.
>>
>> I need to create several Eclipse plug-ins that bundle some parts of that
>> source tree, WITHOUT moving files around to new locations. I may only
>> ADD certain config files, like manifests, plugin.xml and stuff, or
>> create completely new directories for eclipse projects. But I can NOT
>> move or copy some of the source files into new source directories within
>> the new Eclipse projects.
>>
>> What can I do? Can I convince Eclipse somehow to adapt to our directory
>> structure instead of we have to adapt to Eclipse? I'm not allowed to
>> break the current structure as the code is also used in other contexts
>> than Eclipse.
>>
>> Is there any way?
>>
>> Cheers,
>> Hauke
> in this case I would use ant taks to automate copying of files to
> plug-in projects. your origin files and structure will remain intact
>
> ekke
|
|
|
| Re: Make plugins for legacy Java code [message #581333 is a reply to message #23762] |
Thu, 25 September 2008 03:22 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Hauke Fuhrmann schrieb:
> Hi there,
>
> I have a big repository with one big source directory containing a big
> Java package structure and all Java source files.
>
> I need to create several Eclipse plug-ins that bundle some parts of that
> source tree, WITHOUT moving files around to new locations. I may only
> ADD certain config files, like manifests, plugin.xml and stuff, or
> create completely new directories for eclipse projects. But I can NOT
> move or copy some of the source files into new source directories within
> the new Eclipse projects.
>
> What can I do? Can I convince Eclipse somehow to adapt to our directory
> structure instead of we have to adapt to Eclipse? I'm not allowed to
> break the current structure as the code is also used in other contexts
> than Eclipse.
>
> Is there any way?
>
> Cheers,
> Hauke
in this case I would use ant taks to automate copying of files to
plug-in projects. your origin files and structure will remain intact
ekke
|
|
|
| Re: Make plugins for legacy Java code [message #581611 is a reply to message #23846] |
Thu, 25 September 2008 16:03 |
| Eclipse User |
|
|
|
You can make plugin projects the have all the metadata as if the project
actually contained the source. Then use custom callbacks to
automatically copy .java files from the main structure at build time.
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/tasks/pde_custom_callbacks.htm
-Andrew
ekke wrote:
> Hauke Fuhrmann schrieb:
>> Hi there,
>>
>> I have a big repository with one big source directory containing a big
>> Java package structure and all Java source files.
>>
>> I need to create several Eclipse plug-ins that bundle some parts of that
>> source tree, WITHOUT moving files around to new locations. I may only
>> ADD certain config files, like manifests, plugin.xml and stuff, or
>> create completely new directories for eclipse projects. But I can NOT
>> move or copy some of the source files into new source directories within
>> the new Eclipse projects.
>>
>> What can I do? Can I convince Eclipse somehow to adapt to our directory
>> structure instead of we have to adapt to Eclipse? I'm not allowed to
>> break the current structure as the code is also used in other contexts
>> than Eclipse.
>>
>> Is there any way?
>>
>> Cheers,
>> Hauke
> in this case I would use ant taks to automate copying of files to
> plug-in projects. your origin files and structure will remain intact
>
> ekke
|
|
|
Powered by
FUDForum. Page generated in 0.05598 seconds
Home