| Exporting and importing source bundle [message #603575] |
Tue, 24 November 2009 11:06  |
Eclipse User |
|
|
|
Hi,
I want to be able to export a bundle and its source code so that another developer can simply import the bundle, view the source and edit it. Is this possible? I am having trouble figuring out exactly which options to check on the build.xml and the export wizard. n the export wizard, I check the 'export source' option. I have tried generating source bundles and including the source in the exported plugin. I have also tried packaging the plugins as individual jars.
The problem is that when I import the bundle (using the eclipse import->plugins and fragment wizard) bundles that have been exported as individual jars, the source code seems to be in a zip file. When I don't use the export as individual jar option, the source is there, but its just a normal folder called src. That is the classpath isn't set up so that I can just start modifying the source.
I'd just like to export the bundle with its source code out of one workspace and then be able to import the bundle into another workspace and be able to start modifying the bundle just like I could in the first one.
Thanks,
Kyle
|
|
|
| Re: Exporting and importing source bundle [message #603637 is a reply to message #603575] |
Fri, 27 November 2009 04:40  |
| Eclipse User |
|
|
|
Kyle Neumeier wrote:
> Hi,
> I want to be able to export a bundle and its source code so that another
> developer can simply import the bundle, view the source and edit it. Is
> this possible? I am having trouble figuring out exactly which options to
> check on the build.xml and the export wizard. n the export wizard, I
> check the 'export source' option. I have tried generating source bundles
> and including the source in the exported plugin. I have also tried
> packaging the plugins as individual jars.
> The problem is that when I import the bundle (using the eclipse
> import->plugins and fragment wizard) bundles that have been exported as
> individual jars, the source code seems to be in a zip file. When I don't
> use the export as individual jar option, the source is there, but its
> just a normal folder called src. That is the classpath isn't set up so
> that I can just start modifying the source.
>
> I'd just like to export the bundle with its source code out of one
> workspace and then be able to import the bundle into another workspace
> and be able to start modifying the bundle just like I could in the first
> one.
> Thanks,
> Kyle
If copying a set of bundles to a different workspace is all you wish to achieve then simplest way
would be to Export them as (General ->) Archive File.
It can be imported using (General ->) Existing Projects into Workspace option.
Since compiling the bundles successfully depends on Target Platform, you will have to replicate it
too. If your target is not located in a file, you can do so by opening the Target Platform
Preference page choose the "Share" button.
--
Ankur..
Eclipse PDE UI Committer | IBM India Software Lab, Bangalore
+91-99456-94011 | @ankur_sharma | http://blog.ankursharma.org
|
|
|
Powered by
FUDForum. Page generated in 0.04247 seconds
Home