Home » Eclipse Projects » Plugin Development Environment (PDE) » Problem Exporting Product with Eclipse 3.4
| Problem Exporting Product with Eclipse 3.4 [message #21287] |
Fri, 12 September 2008 11:34  |
Eclipse User |
|
|
|
I was told to post here after posting to a mailing list. Here is the
original message:
http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
Since he mentioned the build.properties file, I guess I'll post that here:
bin.includes = plugin.xml,\
META-INF/,\
log4j.properties,\
xmlBlaster.properties,\
com/,\
external/,\
logging.properties,\
.
src.includes = log4j.properties,\
.classpath,\
.project,\
META-INF/,\
RUGUD.product,\
Sample/,\
build.properties,\
buildgui.xml,\
com/,\
external/,\
nativeCode/,\
plugin.xml,\
logging.properties,\
xmlBlaster.properties
# source.. = /
I commented out the last line, and the project export worked much faster,
but the resulting generated project still isn't able to run. What is the
value of source.. supposed to be?
Thanks in advance.
Joe
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #21719 is a reply to message #21287] |
Fri, 12 September 2008 13:42  |
| Eclipse User |
|
|
|
The source.. property specifies where the .java files that need to be
compiled into the root (".") of your bundle are. The value should be a
relative path to the source folders in your project. Something like:
source.. = src/
The resulting .class files from the compilation are automatically
included in the resulting bundle.
The "/" is an absolute path to the root of the drive, by having that you
are basically telling ant to compile all the *.java files it can find on
your C: drive.
If you have no source to compile, you can omit the property.
-Andrew
Joe wrote:
> I was told to post here after posting to a mailing list. Here is the
> original message:
> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>
> Since he mentioned the build.properties file, I guess I'll post that here:
>
> bin.includes = plugin.xml,\
> META-INF/,\
> log4j.properties,\
> xmlBlaster.properties,\
> com/,\
> external/,\
> logging.properties,\
> .
> src.includes = log4j.properties,\
> .classpath,\
> .project,\
> META-INF/,\
> RUGUD.product,\
> Sample/,\
> build.properties,\
> buildgui.xml,\
> com/,\
> external/,\
> nativeCode/,\
> plugin.xml,\
> logging.properties,\
> xmlBlaster.properties
> # source.. = /
>
>
> I commented out the last line, and the project export worked much
> faster, but the resulting generated project still isn't able to run.
> What is the value of source.. supposed to be?
>
> Thanks in advance.
> Joe
>
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #21761 is a reply to message #21719] |
Fri, 12 September 2008 14:07 |
| Eclipse User |
|
|
|
When I try to run the generated RUGUD.exe, I get the following message:
"The RUGUD executable launcher was unable to locate its companion shared
library."
I'm trying to run it from the directory that's there after running the
export. It appears as though all the plugins are there as they should be.
Any ideas on what the problem could be?
Thanks
Joe
Andrew Niefer wrote:
> The source.. property specifies where the .java files that need to be
> compiled into the root (".") of your bundle are. The value should be a
> relative path to the source folders in your project. Something like:
> source.. = src/
> The resulting .class files from the compilation are automatically
> included in the resulting bundle.
> The "/" is an absolute path to the root of the drive, by having that you
> are basically telling ant to compile all the *.java files it can find on
> your C: drive.
> If you have no source to compile, you can omit the property.
> -Andrew
> Joe wrote:
>> I was told to post here after posting to a mailing list. Here is the
>> original message:
>> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>>
>> Since he mentioned the build.properties file, I guess I'll post that here:
>>
>> bin.includes = plugin.xml,
>> META-INF/,
>> log4j.properties,
>> xmlBlaster.properties,
>> com/,
>> external/,
>> logging.properties,
>> .
>> src.includes = log4j.properties,
>> .classpath,
>> .project,
>> META-INF/,
>> RUGUD.product,
>> Sample/,
>> build.properties,
>> buildgui.xml,
>> com/,
>> external/,
>> nativeCode/,
>> plugin.xml,
>> logging.properties,
>> xmlBlaster.properties
>> # source.. = /
>>
>>
>> I commented out the last line, and the project export worked much
>> faster, but the resulting generated project still isn't able to run.
>> What is the value of source.. supposed to be?
>>
>> Thanks in advance.
>> Joe
>>
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #22029 is a reply to message #21761] |
Mon, 15 September 2008 10:56 |
| Eclipse User |
|
|
|
The executable is split into two pieces, the eclipse.exe and an
associated shared library (something like eclipse_1200.dll). Most of
the code actually lives in the library so that it can be updated.
The library normally lives in a platform specific fragment name
"org.eclipse.equinox.launcher.<ws>.<os>.<arch>" that should be in folder
form in the plugins directory.
Getting that error message means either:
1) You are missing that fragment entirely
2) The fragment is there but it is a jar instead of a folder.
The product build should have automatically included these fragments
assuming the delta pack is part of the build. You get the fragments
through the org.eclipse.equinox.executable feature which should have
been included.
-Andrew
Joe wrote:
> When I try to run the generated RUGUD.exe, I get the following message:
> "The RUGUD executable launcher was unable to locate its companion shared
> library."
>
> I'm trying to run it from the directory that's there after running the
> export. It appears as though all the plugins are there as they should be.
>
> Any ideas on what the problem could be?
>
> Thanks
> Joe
>
> Andrew Niefer wrote:
>
>> The source.. property specifies where the .java files that need to be
>> compiled into the root (".") of your bundle are. The value should be
>> a relative path to the source folders in your project. Something like:
>> source.. = src/
>
>> The resulting .class files from the compilation are automatically
>> included in the resulting bundle.
>
>> The "/" is an absolute path to the root of the drive, by having that
>> you are basically telling ant to compile all the *.java files it can
>> find on your C: drive.
>
>> If you have no source to compile, you can omit the property.
>
>> -Andrew
>
>> Joe wrote:
>>> I was told to post here after posting to a mailing list. Here is the
>>> original message:
>>> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>>>
>>> Since he mentioned the build.properties file, I guess I'll post that
>>> here:
>>>
>>> bin.includes = plugin.xml,
>>> META-INF/,
>>> log4j.properties,
>>> xmlBlaster.properties,
>>> com/,
>>> external/,
>>> logging.properties,
>>> .
>>> src.includes = log4j.properties,
>>> .classpath,
>>> .project,
>>> META-INF/,
>>> RUGUD.product,
>>> Sample/,
>>> build.properties,
>>> buildgui.xml,
>>> com/,
>>> external/,
>>> nativeCode/,
>>> plugin.xml,
>>> logging.properties,
>>> xmlBlaster.properties
>>> # source.. = /
>>>
>>>
>>> I commented out the last line, and the project export worked much
>>> faster, but the resulting generated project still isn't able to run.
>>> What is the value of source.. supposed to be?
>>>
>>> Thanks in advance.
>>> Joe
>>>
>
>
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #580211 is a reply to message #21287] |
Fri, 12 September 2008 13:42 |
| Eclipse User |
|
|
|
The source.. property specifies where the .java files that need to be
compiled into the root (".") of your bundle are. The value should be a
relative path to the source folders in your project. Something like:
source.. = src/
The resulting .class files from the compilation are automatically
included in the resulting bundle.
The "/" is an absolute path to the root of the drive, by having that you
are basically telling ant to compile all the *.java files it can find on
your C: drive.
If you have no source to compile, you can omit the property.
-Andrew
Joe wrote:
> I was told to post here after posting to a mailing list. Here is the
> original message:
> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>
> Since he mentioned the build.properties file, I guess I'll post that here:
>
> bin.includes = plugin.xml,\
> META-INF/,\
> log4j.properties,\
> xmlBlaster.properties,\
> com/,\
> external/,\
> logging.properties,\
> .
> src.includes = log4j.properties,\
> .classpath,\
> .project,\
> META-INF/,\
> RUGUD.product,\
> Sample/,\
> build.properties,\
> buildgui.xml,\
> com/,\
> external/,\
> nativeCode/,\
> plugin.xml,\
> logging.properties,\
> xmlBlaster.properties
> # source.. = /
>
>
> I commented out the last line, and the project export worked much
> faster, but the resulting generated project still isn't able to run.
> What is the value of source.. supposed to be?
>
> Thanks in advance.
> Joe
>
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #580230 is a reply to message #21719] |
Fri, 12 September 2008 14:07 |
| Eclipse User |
|
|
|
When I try to run the generated RUGUD.exe, I get the following message:
"The RUGUD executable launcher was unable to locate its companion shared
library."
I'm trying to run it from the directory that's there after running the
export. It appears as though all the plugins are there as they should be.
Any ideas on what the problem could be?
Thanks
Joe
Andrew Niefer wrote:
> The source.. property specifies where the .java files that need to be
> compiled into the root (".") of your bundle are. The value should be a
> relative path to the source folders in your project. Something like:
> source.. = src/
> The resulting .class files from the compilation are automatically
> included in the resulting bundle.
> The "/" is an absolute path to the root of the drive, by having that you
> are basically telling ant to compile all the *.java files it can find on
> your C: drive.
> If you have no source to compile, you can omit the property.
> -Andrew
> Joe wrote:
>> I was told to post here after posting to a mailing list. Here is the
>> original message:
>> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>>
>> Since he mentioned the build.properties file, I guess I'll post that here:
>>
>> bin.includes = plugin.xml,
>> META-INF/,
>> log4j.properties,
>> xmlBlaster.properties,
>> com/,
>> external/,
>> logging.properties,
>> .
>> src.includes = log4j.properties,
>> .classpath,
>> .project,
>> META-INF/,
>> RUGUD.product,
>> Sample/,
>> build.properties,
>> buildgui.xml,
>> com/,
>> external/,
>> nativeCode/,
>> plugin.xml,
>> logging.properties,
>> xmlBlaster.properties
>> # source.. = /
>>
>>
>> I commented out the last line, and the project export worked much
>> faster, but the resulting generated project still isn't able to run.
>> What is the value of source.. supposed to be?
>>
>> Thanks in advance.
>> Joe
>>
|
|
|
| Re: Problem Exporting Product with Eclipse 3.4 [message #580373 is a reply to message #21761] |
Mon, 15 September 2008 10:56 |
| Eclipse User |
|
|
|
The executable is split into two pieces, the eclipse.exe and an
associated shared library (something like eclipse_1200.dll). Most of
the code actually lives in the library so that it can be updated.
The library normally lives in a platform specific fragment name
"org.eclipse.equinox.launcher.<ws>.<os>.<arch>" that should be in folder
form in the plugins directory.
Getting that error message means either:
1) You are missing that fragment entirely
2) The fragment is there but it is a jar instead of a folder.
The product build should have automatically included these fragments
assuming the delta pack is part of the build. You get the fragments
through the org.eclipse.equinox.executable feature which should have
been included.
-Andrew
Joe wrote:
> When I try to run the generated RUGUD.exe, I get the following message:
> "The RUGUD executable launcher was unable to locate its companion shared
> library."
>
> I'm trying to run it from the directory that's there after running the
> export. It appears as though all the plugins are there as they should be.
>
> Any ideas on what the problem could be?
>
> Thanks
> Joe
>
> Andrew Niefer wrote:
>
>> The source.. property specifies where the .java files that need to be
>> compiled into the root (".") of your bundle are. The value should be
>> a relative path to the source folders in your project. Something like:
>> source.. = src/
>
>> The resulting .class files from the compilation are automatically
>> included in the resulting bundle.
>
>> The "/" is an absolute path to the root of the drive, by having that
>> you are basically telling ant to compile all the *.java files it can
>> find on your C: drive.
>
>> If you have no source to compile, you can omit the property.
>
>> -Andrew
>
>> Joe wrote:
>>> I was told to post here after posting to a mailing list. Here is the
>>> original message:
>>> http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01150.html
>>>
>>> Since he mentioned the build.properties file, I guess I'll post that
>>> here:
>>>
>>> bin.includes = plugin.xml,
>>> META-INF/,
>>> log4j.properties,
>>> xmlBlaster.properties,
>>> com/,
>>> external/,
>>> logging.properties,
>>> .
>>> src.includes = log4j.properties,
>>> .classpath,
>>> .project,
>>> META-INF/,
>>> RUGUD.product,
>>> Sample/,
>>> build.properties,
>>> buildgui.xml,
>>> com/,
>>> external/,
>>> nativeCode/,
>>> plugin.xml,
>>> logging.properties,
>>> xmlBlaster.properties
>>> # source.. = /
>>>
>>>
>>> I commented out the last line, and the project export worked much
>>> faster, but the resulting generated project still isn't able to run.
>>> What is the value of source.. supposed to be?
>>>
>>> Thanks in advance.
>>> Joe
>>>
>
>
|
|
|
Goto Forum:
Current Time: Thu Jul 24 14:07:30 EDT 2025
Powered by FUDForum. Page generated in 0.04086 seconds |
Home