You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Jörn Kottmann <ko...@gmail.com> on 2008/04/04 11:44:22 UTC
Cas Editor build script
Hello,
finally there is a basic build script which can compile the Cas Editor.
1. Create a build_local.properties file inside CasEditor/build-files,
there
is a sample which can simply copied and modified.
The sample contains also comments which describe how it works.
2. Launch the CasEditor/build-files/build.xml file
The build scripts copies the
org.apache.uima.runtime_2.2.2.incubating.jar from the uimaj-ep-runtime
project.
So make sure that this was build prior.
Michael, can you please test if it works on your setup ?
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>>>
>> Just one other thing...
>>
>> I think the release notes are also missing.
>> The release notes for release 2.2.2CE can be generated using Jira.
>
> How do you generate release notes from Jira ?
>
> Do you download a issue list as .doc or .xls and then
> create html and txt from it ?
>
> Jörn
Not sure if the link works for you
https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310570
When browsing the UIMA project you will find three links in the left upper corner
- Create a new issue in project UIMA
- Administer Project
- Release Notes
Use the Release Notes link to generate the release notes. You just have to select the release
version (2.2.2CE) and choose the format.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
>>
> Just one other thing...
>
> I think the release notes are also missing.
> The release notes for release 2.2.2CE can be generated using Jira.
How do you generate release notes from Jira ?
Do you download a issue list as .doc or .xls and then
create html and txt from it ?
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler wrote:
> Jörn Kottmann wrote:
>>> Does the example from the ANT documentation not work?
>>> http://ant.apache.org/manual/CoreTypes/fileset.html
>>>
>>> <fileset dir="${server.src}" casesensitive="yes">
>>> <include name="**/*.java"/>
>>> <exclude name="**/*Test*"/>
>>> <exclude name="**/target/**"/> <- should exclude the target dir I think
>>> </fileset>
>> Yeah I tried this already, but thought it does not work. Through
>> a mistake I did not notice that it does.
>>
>>>> I also hat trouble to call the build_documentation.xml from the
>>>> build.xml ant file.
>>>> I did a import of this file and then called it with ant call, but the
>>>> path
>>>> are broken since they are all relative. This means
>>>> that build_documentation.xml cannot import files from
>>>> the SandboxDocs project.
>>>>
>>> When calling ANT file you can also provide a base directory...
>>>
>>> <ant antfile="build_documentation.xml" dir=".." inheritall="true"/>
>>>
>>> Did you try this?
>> Now I tried the import, that did not work. With antfile it works properly.
>>
>> Thanks,
>> Jörn
> I tried your build and it seems to work (at least I don't get any build errors :-))
>
> But I have two more comments:
>
> - The source Package cannot be compiled since the UIMA core plugins cannot be copied (not available
> in the source package). I'm currently not sure how to solve this issue. The current source package
> cannot be reproduced since the dependencies can change. Does anyone has another idea than copying
> the used jars to the CasEditor project?
>
> - The binary package for the CasEditor still contains many sources at
> 2.2.2-win32.win32.x86.zip\CasEditor\plugins\org.apache.uima.caseditor_2.2.2.incubating\
>
Just one other thing...
I think the release notes are also missing.
The release notes for release 2.2.2CE can be generated using Jira.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On May 26, 2008, at 5:42 PM, Michael Baessler wrote:
> Jörn Kottmann wrote:
>>> For all jars we ship, we have to set the correct manifest. So
>>> maybe it
>>> will be easier to package the
>>> CasEditor plugin as jar and add to this jar the correct manifest -
>>> seems to be easier right :-)
>>> But this is just my point of view. Maybe there is no issue with such
>>> jars inside eclipse plugins.
>>
>> I do not know how to get the manifest into the jar, I think we can
>> look
>> into later and just release it
>> now as it is.
>>
>> Does everyone agrees with this ?
>>
>> Jörn
>
> Do you changed the packaging of the CasEditor plugin?
No
> If you just have one plugin jar, we can update
> the jar using some jar update tasks.
Ok, thats good, lets do this.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Great, thanks.
I just added LICENSE, NOTICE and DISCLAIMER files to the jar and to the plugin and updated
the ReleaseNotes. So I think we are fine building the next release candidate. Will you take care of
that?
But before that, what is the status of UIMA-536? (https://issues.apache.org/jira/browse/UIMA-536)
Can this issue be closed?
-- Michael
Jörn Kottmann wrote:
> Ok, now the caseditor.jar contains a manifest file.
> Any other things which must be done before we
> create the next release candidate ?
>
> Jörn
>
> On May 26, 2008, at 5:42 PM, Michael Baessler wrote:
>
>> Jörn Kottmann wrote:
>>>> For all jars we ship, we have to set the correct manifest. So maybe it
>>>> will be easier to package the
>>>> CasEditor plugin as jar and add to this jar the correct manifest -
>>>> seems to be easier right :-)
>>>> But this is just my point of view. Maybe there is no issue with such
>>>> jars inside eclipse plugins.
>>>
>>> I do not know how to get the manifest into the jar, I think we can look
>>> into later and just release it
>>> now as it is.
>>>
>>> Does everyone agrees with this ?
>>>
>>> Jörn
>>
>> Do you changed the packaging of the CasEditor plugin? If you just have
>> one plugin jar, we can update
>> the jar using some jar update tasks.
>>
>> -- Michael
>
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
Ok, now the caseditor.jar contains a manifest file.
Any other things which must be done before we
create the next release candidate ?
Jörn
On May 26, 2008, at 5:42 PM, Michael Baessler wrote:
> Jörn Kottmann wrote:
>>> For all jars we ship, we have to set the correct manifest. So
>>> maybe it
>>> will be easier to package the
>>> CasEditor plugin as jar and add to this jar the correct manifest -
>>> seems to be easier right :-)
>>> But this is just my point of view. Maybe there is no issue with such
>>> jars inside eclipse plugins.
>>
>> I do not know how to get the manifest into the jar, I think we can
>> look
>> into later and just release it
>> now as it is.
>>
>> Does everyone agrees with this ?
>>
>> Jörn
>
> Do you changed the packaging of the CasEditor plugin? If you just
> have one plugin jar, we can update
> the jar using some jar update tasks.
>
> -- Michael
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> For all jars we ship, we have to set the correct manifest. So maybe it
>> will be easier to package the
>> CasEditor plugin as jar and add to this jar the correct manifest -
>> seems to be easier right :-)
>> But this is just my point of view. Maybe there is no issue with such
>> jars inside eclipse plugins.
>
> I do not know how to get the manifest into the jar, I think we can look
> into later and just release it
> now as it is.
>
> Does everyone agrees with this ?
>
> Jörn
Do you changed the packaging of the CasEditor plugin? If you just have one plugin jar, we can update
the jar using some jar update tasks.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> For all jars we ship, we have to set the correct manifest. So maybe
> it will be easier to package the
> CasEditor plugin as jar and add to this jar the correct manifest -
> seems to be easier right :-)
> But this is just my point of view. Maybe there is no issue with such
> jars inside eclipse plugins.
I do not know how to get the manifest into the jar, I think we can
look into later and just release it
now as it is.
Does everyone agrees with this ?
Jörn
Re: Cas Editor build script
Posted by Marshall Schor <ms...@schor.com>.
Re: where to get Jars for builds -
How about getting them from the local Maven Repo, using the maven
version info?
This implies that the builder has run some process which insures the
local repo has
the right tagged build of the particular version of the plugin, and
works even if the
version hasn't yet been uploaded (released) to the official maven repo
but instead
was built locally from a release candidate.
For the Eclipse Update Site, I use this ant macro:
<macrodef name="makePluginJar">
<attribute name="project-name"/>
<attribute name="org-name"/>
<sequential>
<copy
tofile="target/eclipse-update-site/plugins/@{org-name}_${project.full.eclipse.version}.jar"
file="${envVar.HOMEPATH}/.m2/repository/org/apache/uima/@{project-name}/${project.full.eclipse.version}/@{project-name}-${project.full.eclipse.version}.jar"/>
</sequential>
</macrodef>
The line of interest is the one starting with "file=".
-Marshall
Jörn Kottmann wrote:
>>> You changed the build.xml file to copy the org.apache.uima.runtime from
>>> ${eclipseLocation}/plugins instead from the uimaj-ep-runtime project.
>>> This change does not help, because the build already
>>> looks at ${eclipseLocation}/plugins which are necessary for the build.
>>> The build will work without copying it. Here is the story behind it.
>>> The question a while ago was how we can handle the dependence
>>> on the runtime plugin. My first solution to this was that we just
>>> copy it
>>> over from the uimaj-ep-runtime project. But this does not worked for
>>> tagging the release and building the Cas Editor from the source
>>> package.
>>> Then I extended the build script to not necessarily copy the runtime
>>> plugin from the uimaj-ep-runtime project, but if it exists. The build
>>> then works only
>>> if the runtime is only located at ${eclipseLocation}/plugins. If
>>> both ways
>>> of getting the runtime plugin fail the build is halted and an error
>>> message is printed to the console.
>>>
>>> Do you think now we should only get the runtime plugin
>>> from ${eclipseLocation}/plugins ?
>> I think so. Getting it from uimaj-ep-runtime project can't work for
>> extracting the
>> CasEditor for a tagged release. If the copying from
>> ${eclipseLocation}/plugins
>> isn't necessary we can remove this step. Agreed?
>
> Ok, I committed it already.
>
>> For all jars we ship, we have to set the correct manifest. So maybe
>> it will be easier to package the
>> CasEditor plugin as jar and add to this jar the correct manifest -
>> seems to be easier right :-)
>> But this is just my point of view. Maybe there is no issue with such
>> jars inside eclipse plugins.
>
> I already planned to ship the plugin as jar file instead of the
> folder. There are other good
> reasons to do this. I encountered problems with unzipping the Cas
> Editor zip file in the
> windows desktop folder because of too long paths.
> This resulted in a strange error message of the unzip tool.
>
> I just have to find out how to tell the build to package it as a jar
> plugin.
>
> Jörn
>
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
>> You changed the build.xml file to copy the org.apache.uima.runtime
>> from
>> ${eclipseLocation}/plugins instead from the uimaj-ep-runtime project.
>> This change does not help, because the build already
>> looks at ${eclipseLocation}/plugins which are necessary for the
>> build.
>> The build will work without copying it. Here is the story behind it.
>> The question a while ago was how we can handle the dependence
>> on the runtime plugin. My first solution to this was that we just
>> copy it
>> over from the uimaj-ep-runtime project. But this does not worked for
>> tagging the release and building the Cas Editor from the source
>> package.
>> Then I extended the build script to not necessarily copy the runtime
>> plugin from the uimaj-ep-runtime project, but if it exists. The build
>> then works only
>> if the runtime is only located at ${eclipseLocation}/plugins. If
>> both ways
>> of getting the runtime plugin fail the build is halted and an error
>> message is printed to the console.
>>
>> Do you think now we should only get the runtime plugin
>> from ${eclipseLocation}/plugins ?
> I think so. Getting it from uimaj-ep-runtime project can't work for
> extracting the
> CasEditor for a tagged release. If the copying from $
> {eclipseLocation}/plugins
> isn't necessary we can remove this step. Agreed?
Ok, I committed it already.
> For all jars we ship, we have to set the correct manifest. So maybe
> it will be easier to package the
> CasEditor plugin as jar and add to this jar the correct manifest -
> seems to be easier right :-)
> But this is just my point of view. Maybe there is no issue with such
> jars inside eclipse plugins.
I already planned to ship the plugin as jar file instead of the
folder. There are other good
reasons to do this. I encountered problems with unzipping the Cas
Editor zip file in the
windows desktop folder because of too long paths.
This resulted in a strange error message of the unzip tool.
I just have to find out how to tell the build to package it as a jar
plugin.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@apache.org>.
Jörn Kottmann wrote:
>> I committed some changes for the CasEditor build, please review and
>> check if still all works fine.
>
> Ok, cool, I just reviewed it.
>
> Every time the caseditor.product file is changed with the product editor
> the
> Apache License Header ist gone. I already added it again.
:-) thanks!
>
> You changed the build.xml file to copy the org.apache.uima.runtime from
> ${eclipseLocation}/plugins instead from the uimaj-ep-runtime project.
> This change does not help, because the build already
> looks at ${eclipseLocation}/plugins which are necessary for the build.
> The build will work without copying it. Here is the story behind it.
> The question a while ago was how we can handle the dependence
> on the runtime plugin. My first solution to this was that we just copy it
> over from the uimaj-ep-runtime project. But this does not worked for
> tagging the release and building the Cas Editor from the source package.
> Then I extended the build script to not necessarily copy the runtime
> plugin from the uimaj-ep-runtime project, but if it exists. The build
> then works only
> if the runtime is only located at ${eclipseLocation}/plugins. If both ways
> of getting the runtime plugin fail the build is halted and an error
> message is printed to the console.
>
> Do you think now we should only get the runtime plugin
> from ${eclipseLocation}/plugins ?
I think so. Getting it from uimaj-ep-runtime project can't work for extracting the
CasEditor for a tagged release. If the copying from ${eclipseLocation}/plugins
isn't necessary we can remove this step. Agreed?
>
> All other changes you made are good.
>
>> I recognized that the caseditor.jar does not have the correct files in
>> META-INF directory and the
>> Manifest.mf of the jar is also pretty empty. But I was not able to
>> figure out how the build works
>> that create this jar. Seems that all is done inside the AntRunner
>> call. Is it possible to manipulate
>> that? Can you please explain how this works?
>
> Yes, the AntRunner call starts the eclipse product build script. The build
> process is configured in the build-files/build.properties file. This
> build script is provided by
> eclipse and it is like a black box. We feed it with everything it needs and
> then the build properly build Cas Editor comes out. If the build fails
> it is sometimes hard
> to diagnose the problem.
>
> Why is the manifest.mf in the jar important ?
> The caseditor.jar which comes out is only a part of the caseditor
> plugin, the plugin in
> uses a different manfifest.mf in the META-INF folder.
> Do you think it is better to package the caseditor plugin as jar, as it
> was done
> for the runtime plugin ?
For all jars we ship, we have to set the correct manifest. So maybe it will be easier to package the
CasEditor plugin as jar and add to this jar the correct manifest - seems to be easier right :-)
But this is just my point of view. Maybe there is no issue with such jars inside eclipse plugins.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> I committed some changes for the CasEditor build, please review and
> check if still all works fine.
Ok, cool, I just reviewed it.
Every time the caseditor.product file is changed with the product
editor the
Apache License Header ist gone. I already added it again.
You changed the build.xml file to copy the org.apache.uima.runtime from
${eclipseLocation}/plugins instead from the uimaj-ep-runtime project.
This change does not help, because the build already
looks at ${eclipseLocation}/plugins which are necessary for the build.
The build will work without copying it. Here is the story behind it.
The question a while ago was how we can handle the dependence
on the runtime plugin. My first solution to this was that we just copy
it
over from the uimaj-ep-runtime project. But this does not worked for
tagging the release and building the Cas Editor from the source
package.
Then I extended the build script to not necessarily copy the runtime
plugin from the uimaj-ep-runtime project, but if it exists. The build
then works only
if the runtime is only located at ${eclipseLocation}/plugins. If both
ways
of getting the runtime plugin fail the build is halted and an error
message is printed to the console.
Do you think now we should only get the runtime plugin
from ${eclipseLocation}/plugins ?
All other changes you made are good.
> I recognized that the caseditor.jar does not have the correct files
> in META-INF directory and the
> Manifest.mf of the jar is also pretty empty. But I was not able to
> figure out how the build works
> that create this jar. Seems that all is done inside the AntRunner
> call. Is it possible to manipulate
> that? Can you please explain how this works?
Yes, the AntRunner call starts the eclipse product build script. The
build
process is configured in the build-files/build.properties file. This
build script is provided by
eclipse and it is like a black box. We feed it with everything it
needs and
then the build properly build Cas Editor comes out. If the build fails
it is sometimes hard
to diagnose the problem.
Why is the manifest.mf in the jar important ?
The caseditor.jar which comes out is only a part of the caseditor
plugin, the plugin in
uses a different manfifest.mf in the META-INF folder.
Do you think it is better to package the caseditor plugin as jar, as
it was done
for the runtime plugin ?
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@apache.org>.
I committed some changes for the CasEditor build, please review and check if still all works fine.
I recognized that the caseditor.jar does not have the correct files in META-INF directory and the
Manifest.mf of the jar is also pretty empty. But I was not able to figure out how the build works
that create this jar. Seems that all is done inside the AntRunner call. Is it possible to manipulate
that? Can you please explain how this works?
-- Michael
Michael Baessler wrote:
> Looks good.
>
> Currently the created packages of the build process are called:
>
> 2.2.2-linux.gtk.x86.zip
> 2.2.2-win32.win32.x86.zip
> 2.2.2-src.zip
>
> I think we should change these names. Suggestions ?
>
> 1) CasEditor-linux.gtk.x86-2.2.2-incubating.zip
> CasEditor-win32.win32.x86-2.2.2-incubating.zip
> CasEditor-src-2.2.2-incubating.zip
>
> 2) uimaj-CasEditor-linux.gtk.x86-2.2.2-incubating.zip
> uimaj-CasEditor-win32.win32.x86-2.2.2-incubating.zip
> uimaj-CasEditor-src-2.2.2-incubating.zip
>
>
> The build naming control of your ant build contains:
>
> # Type of build. Used in naming the build output. Typically this value is
> # one of I, N, M, S, ...
> buildType=I
>
> Can you please explain the abbreviations?
>
> -- Michael
>
> Jörn Kottmann wrote:
>> On May 6, 2008, at 10:48 AM, Michael Baessler wrote:
>>
>>> Some recommendations from my side:
>>>
>>> - add some Apache license header to the release notes (the Incubator
>>> ask us to do this for the next
>>> release)
>> I added a license section to both release notes files.
>>
>>> - rename the release from 2.2.2CE to just 2.2.2 in the release notes
>> ok
>>
>>> - the "Cas Editor.ini" file and "configuration/config.ini" file does
>>> not have a license header, are
>>> these generated files?
>> They are both generated, so I think they do not need a license header.
>>
>>> - the first image in the HTML documentation is very small, is this
>>> related to the PDF?
>> I am not sure what is the problem here, if its scaled bigger than it
>> does not fit on a page in
>> the PDF.
>>
>>> - The NOTICE file has "Copyright 2006, 2007 The Apache Software
>>> Foundation" but I think it should be
>>> "Copyright 2006, 2008 The Apache Software Foundation"
>> done
>>
>>> - when packaging the source jar, I prefer to add a root folder to the
>>> zip that contains the content.
>> yeah, I prefer this too, its changed
>>
>>> -- Michael
>
Re: Cas Editor build script
Posted by Michael Baessler <mb...@apache.org>.
Looks good.
Currently the created packages of the build process are called:
2.2.2-linux.gtk.x86.zip
2.2.2-win32.win32.x86.zip
2.2.2-src.zip
I think we should change these names. Suggestions ?
1) CasEditor-linux.gtk.x86-2.2.2-incubating.zip
CasEditor-win32.win32.x86-2.2.2-incubating.zip
CasEditor-src-2.2.2-incubating.zip
2) uimaj-CasEditor-linux.gtk.x86-2.2.2-incubating.zip
uimaj-CasEditor-win32.win32.x86-2.2.2-incubating.zip
uimaj-CasEditor-src-2.2.2-incubating.zip
The build naming control of your ant build contains:
# Type of build. Used in naming the build output. Typically this value is
# one of I, N, M, S, ...
buildType=I
Can you please explain the abbreviations?
-- Michael
Jörn Kottmann wrote:
> On May 6, 2008, at 10:48 AM, Michael Baessler wrote:
>
>> Some recommendations from my side:
>>
>> - add some Apache license header to the release notes (the Incubator
>> ask us to do this for the next
>> release)
>
> I added a license section to both release notes files.
>
>> - rename the release from 2.2.2CE to just 2.2.2 in the release notes
>
> ok
>
>> - the "Cas Editor.ini" file and "configuration/config.ini" file does
>> not have a license header, are
>> these generated files?
>
> They are both generated, so I think they do not need a license header.
>
>> - the first image in the HTML documentation is very small, is this
>> related to the PDF?
>
> I am not sure what is the problem here, if its scaled bigger than it
> does not fit on a page in
> the PDF.
>
>> - The NOTICE file has "Copyright 2006, 2007 The Apache Software
>> Foundation" but I think it should be
>> "Copyright 2006, 2008 The Apache Software Foundation"
>
> done
>
>> - when packaging the source jar, I prefer to add a root folder to the
>> zip that contains the content.
>
> yeah, I prefer this too, its changed
>
>> -- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On May 6, 2008, at 10:48 AM, Michael Baessler wrote:
> Some recommendations from my side:
>
> - add some Apache license header to the release notes (the Incubator
> ask us to do this for the next
> release)
I added a license section to both release notes files.
> - rename the release from 2.2.2CE to just 2.2.2 in the release notes
ok
> - the "Cas Editor.ini" file and "configuration/config.ini" file does
> not have a license header, are
> these generated files?
They are both generated, so I think they do not need a license header.
> - the first image in the HTML documentation is very small, is this
> related to the PDF?
I am not sure what is the problem here, if its scaled bigger than it
does not fit on a page in
the PDF.
> - The NOTICE file has "Copyright 2006, 2007 The Apache Software
> Foundation" but I think it should be
> "Copyright 2006, 2008 The Apache Software Foundation"
done
> - when packaging the source jar, I prefer to add a root folder to
> the zip that contains the content.
yeah, I prefer this too, its changed
> -- Michael
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Now the build works fine for me :-) I also successfully verified the build when using the generated
source package.
Some recommendations from my side:
- add some Apache license header to the release notes (the Incubator ask us to do this for the next
release)
- rename the release from 2.2.2CE to just 2.2.2 in the release notes
- the "Cas Editor.ini" file and "configuration/config.ini" file does not have a license header, are
these generated files?
- the first image in the HTML documentation is very small, is this related to the PDF?
- The NOTICE file has "Copyright 2006, 2007 The Apache Software Foundation" but I think it should be
"Copyright 2006, 2008 The Apache Software Foundation"
- when packaging the source jar, I prefer to add a root folder to the zip that contains the content.
-- Michael
Jörn Kottmann wrote:
> Hello,
>
> sorry it took me a while to get to this, but I think I have finally
> solved the issue.
>
> On my machine is also a build.properties file which is necessary for the
> build.
> I did not noticed that is was not checked-in because it is ignored by svn.
> Now it should build without problems.
>
> Sorry,
> Jörn
>
> On Apr 23, 2008, at 12:06 PM, Thilo Goetz wrote:
>
>> Michael Baessler wrote:
>>> Jörn Kottmann wrote:
>>>> On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
>> [...]
>>>>> Sorry I'm still not able to build the CasEditor release.
>>>>> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2
>>>>> and the
>>>>> UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor
>>>>> plugin jar is not created.
>>>>> I also still see the source code in the binary package.
>>>>> Not sure what is wrong on my machine. Maybe someone else can try to
>>>>> build and check if it works.
>>
>> I tried this, too, and get the same results as Michael. Also windows.
>>
>>>> I tested this with mac os and ubuntu linux. I guess you use windows. I
>>>> will test it too
>>>> on windows tonight or tomorrow night. Maybe there lies the problem.
>>> Yes, I did my tests on windows.
>>> -- Michael
>
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
Hello,
sorry it took me a while to get to this, but I think I have finally
solved the issue.
On my machine is also a build.properties file which is necessary for
the build.
I did not noticed that is was not checked-in because it is ignored by
svn.
Now it should build without problems.
Sorry,
Jörn
On Apr 23, 2008, at 12:06 PM, Thilo Goetz wrote:
> Michael Baessler wrote:
>> Jörn Kottmann wrote:
>>> On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
> [...]
>>>> Sorry I'm still not able to build the CasEditor release.
>>>> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package
>>>> 3.3.2
>>>> and the
>>>> UIMA plulgins version 2.2.2. I got no build errors, but the
>>>> CasEditor
>>>> plugin jar is not created.
>>>> I also still see the source code in the binary package.
>>>> Not sure what is wrong on my machine. Maybe someone else can try to
>>>> build and check if it works.
>
> I tried this, too, and get the same results as Michael. Also windows.
>
>>> I tested this with mac os and ubuntu linux. I guess you use
>>> windows. I
>>> will test it too
>>> on windows tonight or tomorrow night. Maybe there lies the problem.
>> Yes, I did my tests on windows.
>> -- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On Apr 23, 2008, at 12:06 PM, Thilo Goetz wrote:
> Michael Baessler wrote:
>> Jörn Kottmann wrote:
>>> On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
> [...]
>>>> Sorry I'm still not able to build the CasEditor release.
>>>> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package
>>>> 3.3.2
>>>> and the
>>>> UIMA plulgins version 2.2.2. I got no build errors, but the
>>>> CasEditor
>>>> plugin jar is not created.
>>>> I also still see the source code in the binary package.
>>>> Not sure what is wrong on my machine. Maybe someone else can try to
>>>> build and check if it works.
>
> I tried this, too, and get the same results as Michael. Also windows.
Yes, it does not compile an my windows too. I have no clue what
is the problem.
I will spend some time on the weekend to figure it out.
Jörn
Re: Cas Editor build script
Posted by Thilo Goetz <tw...@gmx.de>.
Michael Baessler wrote:
> Jörn Kottmann wrote:
>> On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
[...]
>>> Sorry I'm still not able to build the CasEditor release.
>>> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2
>>> and the
>>> UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor
>>> plugin jar is not created.
>>> I also still see the source code in the binary package.
>>> Not sure what is wrong on my machine. Maybe someone else can try to
>>> build and check if it works.
I tried this, too, and get the same results as Michael. Also windows.
>> I tested this with mac os and ubuntu linux. I guess you use windows. I
>> will test it too
>> on windows tonight or tomorrow night. Maybe there lies the problem.
>
> Yes, I did my tests on windows.
>
> -- Michael
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>
> On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
>
>> Jörn Kottmann wrote:
>>>
>>> On Apr 8, 2008, at 10:00 AM, Michael Baessler wrote:
>>>
>>>> Jörn Kottmann wrote:
>>>>>> - The source Package cannot be compiled since the UIMA core plugins
>>>>>> cannot be copied (not available
>>>>>> in the source package). I'm currently not sure how to solve this
>>>>>> issue. The current source package
>>>>>> cannot be reproduced since the dependencies can change. Does anyone
>>>>>> has another idea than copying
>>>>>> the used jars to the CasEditor project?
>>>>>
>>>>> How does it works in the other sandbox components ? They need the doc
>>>>> packages
>>>>> to be build, are they included in the source build ?
>>>> Yes, they are included and specially tagged.
>>>
>>> Ok, then I have todo this too.
>>>
>>>>>
>>>>> It would be possible to get the runtime plugin in either from the core
>>>>> plugin project or
>>>>> make it mandatory plugin for the eclipse installation which is used to
>>>>> build
>>>>> the cas editor.
>>>>>
>>>>> The build script could check if the user did provide the correct
>>>>> version
>>>>> of the
>>>>> runtime plugin.
>>>>>
>>>>> To make the build reproducible we also have to enforce that the
>>>>> user is
>>>>> using
>>>>> the same eclipse version as we used for the release build.
>>>>> Should we checkin this too ?
>>>>
>>>> Maybe this is a good workaround.
>>>
>>> Ok, I will do it this way for now.
>>>
>>>>> Please give me more details.
>>>>>
>>>>> Maybe thats a sign that the build on your machine is still failing,
>>>>> could you start
>>>>> the cas editor ?
>>>>
>>>> I can't start the CasEditor, still some ClassNotFound exceptions.
>>>> Seems that the
>>>> CasEditor build doesn't work properly for me.
>>>>
>>>> I uploaded the ant build output to my home directory.
>>>
>>> I think there is still a problem with your eclipse installation.
>>> Can you please download eclipse 3.3.2, then install the EMF stuff
>>> and the delta package. This should work fine. I am sorry for this one.
>>>
>> Sorry I'm still not able to build the CasEditor release.
>> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2
>> and the
>> UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor
>> plugin jar is not created.
>> I also still see the source code in the binary package.
>> Not sure what is wrong on my machine. Maybe someone else can try to
>> build and check if it works.
>
> I tested this with mac os and ubuntu linux. I guess you use windows. I
> will test it too
> on windows tonight or tomorrow night. Maybe there lies the problem.
Yes, I did my tests on windows.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote:
> Jörn Kottmann wrote:
>>
>> On Apr 8, 2008, at 10:00 AM, Michael Baessler wrote:
>>
>>> Jörn Kottmann wrote:
>>>>> - The source Package cannot be compiled since the UIMA core
>>>>> plugins
>>>>> cannot be copied (not available
>>>>> in the source package). I'm currently not sure how to solve this
>>>>> issue. The current source package
>>>>> cannot be reproduced since the dependencies can change. Does
>>>>> anyone
>>>>> has another idea than copying
>>>>> the used jars to the CasEditor project?
>>>>
>>>> How does it works in the other sandbox components ? They need the
>>>> doc
>>>> packages
>>>> to be build, are they included in the source build ?
>>> Yes, they are included and specially tagged.
>>
>> Ok, then I have todo this too.
>>
>>>>
>>>> It would be possible to get the runtime plugin in either from the
>>>> core
>>>> plugin project or
>>>> make it mandatory plugin for the eclipse installation which is
>>>> used to
>>>> build
>>>> the cas editor.
>>>>
>>>> The build script could check if the user did provide the correct
>>>> version
>>>> of the
>>>> runtime plugin.
>>>>
>>>> To make the build reproducible we also have to enforce that the
>>>> user is
>>>> using
>>>> the same eclipse version as we used for the release build.
>>>> Should we checkin this too ?
>>>
>>> Maybe this is a good workaround.
>>
>> Ok, I will do it this way for now.
>>
>>>> Please give me more details.
>>>>
>>>> Maybe thats a sign that the build on your machine is still failing,
>>>> could you start
>>>> the cas editor ?
>>>
>>> I can't start the CasEditor, still some ClassNotFound exceptions.
>>> Seems that the
>>> CasEditor build doesn't work properly for me.
>>>
>>> I uploaded the ant build output to my home directory.
>>
>> I think there is still a problem with your eclipse installation.
>> Can you please download eclipse 3.3.2, then install the EMF stuff
>> and the delta package. This should work fine. I am sorry for this
>> one.
>>
> Sorry I'm still not able to build the CasEditor release.
> I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2
> and the
> UIMA plulgins version 2.2.2. I got no build errors, but the
> CasEditor plugin jar is not created.
> I also still see the source code in the binary package.
> Not sure what is wrong on my machine. Maybe someone else can try to
> build and check if it works.
I tested this with mac os and ubuntu linux. I guess you use windows. I
will test it too
on windows tonight or tomorrow night. Maybe there lies the problem.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>
> On Apr 8, 2008, at 10:00 AM, Michael Baessler wrote:
>
>> Jörn Kottmann wrote:
>>>> - The source Package cannot be compiled since the UIMA core plugins
>>>> cannot be copied (not available
>>>> in the source package). I'm currently not sure how to solve this
>>>> issue. The current source package
>>>> cannot be reproduced since the dependencies can change. Does anyone
>>>> has another idea than copying
>>>> the used jars to the CasEditor project?
>>>
>>> How does it works in the other sandbox components ? They need the doc
>>> packages
>>> to be build, are they included in the source build ?
>> Yes, they are included and specially tagged.
>
> Ok, then I have todo this too.
>
>>>
>>> It would be possible to get the runtime plugin in either from the core
>>> plugin project or
>>> make it mandatory plugin for the eclipse installation which is used to
>>> build
>>> the cas editor.
>>>
>>> The build script could check if the user did provide the correct version
>>> of the
>>> runtime plugin.
>>>
>>> To make the build reproducible we also have to enforce that the user is
>>> using
>>> the same eclipse version as we used for the release build.
>>> Should we checkin this too ?
>>
>> Maybe this is a good workaround.
>
> Ok, I will do it this way for now.
>
>>> Please give me more details.
>>>
>>> Maybe thats a sign that the build on your machine is still failing,
>>> could you start
>>> the cas editor ?
>>
>> I can't start the CasEditor, still some ClassNotFound exceptions.
>> Seems that the
>> CasEditor build doesn't work properly for me.
>>
>> I uploaded the ant build output to my home directory.
>
> I think there is still a problem with your eclipse installation.
> Can you please download eclipse 3.3.2, then install the EMF stuff
> and the delta package. This should work fine. I am sorry for this one.
>
Sorry I'm still not able to build the CasEditor release.
I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2 and the
UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor plugin jar is not created.
I also still see the source code in the binary package.
Not sure what is wrong on my machine. Maybe someone else can try to build and check if it works.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On Apr 8, 2008, at 10:00 AM, Michael Baessler wrote:
> Jörn Kottmann wrote:
>>> - The source Package cannot be compiled since the UIMA core plugins
>>> cannot be copied (not available
>>> in the source package). I'm currently not sure how to solve this
>>> issue. The current source package
>>> cannot be reproduced since the dependencies can change. Does anyone
>>> has another idea than copying
>>> the used jars to the CasEditor project?
>>
>> How does it works in the other sandbox components ? They need the doc
>> packages
>> to be build, are they included in the source build ?
> Yes, they are included and specially tagged.
Ok, then I have todo this too.
>>
>> It would be possible to get the runtime plugin in either from the
>> core
>> plugin project or
>> make it mandatory plugin for the eclipse installation which is used
>> to
>> build
>> the cas editor.
>>
>> The build script could check if the user did provide the correct
>> version
>> of the
>> runtime plugin.
>>
>> To make the build reproducible we also have to enforce that the
>> user is
>> using
>> the same eclipse version as we used for the release build.
>> Should we checkin this too ?
>
> Maybe this is a good workaround.
Ok, I will do it this way for now.
>> Please give me more details.
>>
>> Maybe thats a sign that the build on your machine is still failing,
>> could you start
>> the cas editor ?
>
> I can't start the CasEditor, still some ClassNotFound exceptions.
> Seems that the
> CasEditor build doesn't work properly for me.
>
> I uploaded the ant build output to my home directory.
I think there is still a problem with your eclipse installation.
Can you please download eclipse 3.3.2, then install the EMF stuff
and the delta package. This should work fine. I am sorry for this one.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> - The source Package cannot be compiled since the UIMA core plugins
>> cannot be copied (not available
>> in the source package). I'm currently not sure how to solve this
>> issue. The current source package
>> cannot be reproduced since the dependencies can change. Does anyone
>> has another idea than copying
>> the used jars to the CasEditor project?
>
> How does it works in the other sandbox components ? They need the doc
> packages
> to be build, are they included in the source build ?
Yes, they are included and specially tagged.
>
> It would be possible to get the runtime plugin in either from the core
> plugin project or
> make it mandatory plugin for the eclipse installation which is used to
> build
> the cas editor.
>
> The build script could check if the user did provide the correct version
> of the
> runtime plugin.
>
> To make the build reproducible we also have to enforce that the user is
> using
> the same eclipse version as we used for the release build.
> Should we checkin this too ?
Maybe this is a good workaround.
>
>
>> - The binary package for the CasEditor still contains many sources at
>> 2.2.2-win32.win32.x86.zip\CasEditor\plugins\org.apache.uima.caseditor_2.2.2.incubating\
>>
>
> I do not see source files inside the release build.
> Do you have the src folder there ?
Yes I still have the src folder with all its content.
> Please give me more details.
>
> Maybe thats a sign that the build on your machine is still failing,
> could you start
> the cas editor ?
I can't start the CasEditor, still some ClassNotFound exceptions. Seems that the
CasEditor build doesn't work properly for me.
I uploaded the ant build output to my home directory.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> - The source Package cannot be compiled since the UIMA core plugins
> cannot be copied (not available
> in the source package). I'm currently not sure how to solve this
> issue. The current source package
> cannot be reproduced since the dependencies can change. Does anyone
> has another idea than copying
> the used jars to the CasEditor project?
How does it works in the other sandbox components ? They need the doc
packages
to be build, are they included in the source build ?
It would be possible to get the runtime plugin in either from the core
plugin project or
make it mandatory plugin for the eclipse installation which is used to
build
the cas editor.
The build script could check if the user did provide the correct
version of the
runtime plugin.
To make the build reproducible we also have to enforce that the user
is using
the same eclipse version as we used for the release build.
Should we checkin this too ?
> - The binary package for the CasEditor still contains many sources at
> 2.2.2-win32.win32.x86.zip\CasEditor\plugins
> \org.apache.uima.caseditor_2.2.2.incubating\
I do not see source files inside the release build.
Do you have the src folder there ?
Please give me more details.
Maybe thats a sign that the build on your machine is still failing,
could you start
the cas editor ?
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> Does the example from the ANT documentation not work?
>> http://ant.apache.org/manual/CoreTypes/fileset.html
>>
>> <fileset dir="${server.src}" casesensitive="yes">
>> <include name="**/*.java"/>
>> <exclude name="**/*Test*"/>
>> <exclude name="**/target/**"/> <- should exclude the target dir I think
>> </fileset>
>
> Yeah I tried this already, but thought it does not work. Through
> a mistake I did not notice that it does.
>
>>>
>>> I also hat trouble to call the build_documentation.xml from the
>>> build.xml ant file.
>>> I did a import of this file and then called it with ant call, but the
>>> path
>>> are broken since they are all relative. This means
>>> that build_documentation.xml cannot import files from
>>> the SandboxDocs project.
>>>
>> When calling ANT file you can also provide a base directory...
>>
>> <ant antfile="build_documentation.xml" dir=".." inheritall="true"/>
>>
>> Did you try this?
>
> Now I tried the import, that did not work. With antfile it works properly.
>
> Thanks,
> Jörn
I tried your build and it seems to work (at least I don't get any build errors :-))
But I have two more comments:
- The source Package cannot be compiled since the UIMA core plugins cannot be copied (not available
in the source package). I'm currently not sure how to solve this issue. The current source package
cannot be reproduced since the dependencies can change. Does anyone has another idea than copying
the used jars to the CasEditor project?
- The binary package for the CasEditor still contains many sources at
2.2.2-win32.win32.x86.zip\CasEditor\plugins\org.apache.uima.caseditor_2.2.2.incubating\
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> Does the example from the ANT documentation not work?
> http://ant.apache.org/manual/CoreTypes/fileset.html
>
> <fileset dir="${server.src}" casesensitive="yes">
> <include name="**/*.java"/>
> <exclude name="**/*Test*"/>
> <exclude name="**/target/**"/> <- should exclude the target dir I
> think
> </fileset>
Yeah I tried this already, but thought it does not work. Through
a mistake I did not notice that it does.
>>
>> I also hat trouble to call the build_documentation.xml from the
>> build.xml ant file.
>> I did a import of this file and then called it with ant call, but
>> the path
>> are broken since they are all relative. This means
>> that build_documentation.xml cannot import files from
>> the SandboxDocs project.
>>
> When calling ANT file you can also provide a base directory...
>
> <ant antfile="build_documentation.xml" dir=".." inheritall="true"/>
>
> Did you try this?
Now I tried the import, that did not work. With antfile it works
properly.
Thanks,
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
> Now the License, Notice, Disclaimer and Keys files are included
> in all archives. I also added a source archive.
>
> Does someone know how to exclude a dir in a fileset ?
> I would like to exclude the target dir when copying the project folder
> for packaging.
Does the example from the ANT documentation not work?
http://ant.apache.org/manual/CoreTypes/fileset.html
<fileset dir="${server.src}" casesensitive="yes">
<include name="**/*.java"/>
<exclude name="**/*Test*"/>
<exclude name="**/target/**"/> <- should exclude the target dir I think
</fileset>
>
> I also hat trouble to call the build_documentation.xml from the
> build.xml ant file.
> I did a import of this file and then called it with ant call, but the path
> are broken since they are all relative. This means
> that build_documentation.xml cannot import files from
> the SandboxDocs project.
>
When calling ANT file you can also provide a base directory...
<ant antfile="build_documentation.xml" dir=".." inheritall="true"/>
Did you try this?
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
Now the License, Notice, Disclaimer and Keys files are included
in all archives. I also added a source archive.
Does someone know how to exclude a dir in a fileset ?
I would like to exclude the target dir when copying the project folder
for packaging.
I also hat trouble to call the build_documentation.xml from the
build.xml ant file.
I did a import of this file and then called it with ant call, but the
path
are broken since they are all relative. This means
that build_documentation.xml cannot import files from
the SandboxDocs project.
I am not sure whats causing your problems with the build script, maybe
it
has todo with this message:
" Some inter-plug-in dependencies have not been satisfied."
I do the build with eclipse 3.3.2, with EMF and delta package installed.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> Now, after installing the delta package and after fixing some
>> duplicate jar files that I have in my
>> environment I was able to build the package.
>>
>> But the created package is not ready to ship, since the NOTICE and
>> LICENSE files are missing.
>
> I can work on this tomorrow, documentation is also not build.
>
> Must the KEYS and DISCLAIMER files also be included ?
KEYS file is optional, DISCLAIMER have to be in.
>
>> For example the log contains enties like:
>> org.eclipse.core.runtime.CoreException[1]:
>> java.lang.ClassNotFoundException:
>> org.apache.uima.caseditor.Application
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:434)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.
>>
>
>
> I tested it for mac os and on a coworkers windows machine, both worked.
> Please check if the MANIFEST.MF has the head revision.
>
> Did you saw the compiler warnings on the console during building ?
>
> Is there the caseditor.jar file inside the org.apache.caseditor plugin ?
>
The jar file is missing...
The ant build output is available at people.a.o/home/mbaessler/public_html/CasEditorBuildOutput.txt
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> Now, after installing the delta package and after fixing some
> duplicate jar files that I have in my
> environment I was able to build the package.
>
> But the created package is not ready to ship, since the NOTICE and
> LICENSE files are missing.
I can work on this tomorrow, documentation is also not build.
Must the KEYS and DISCLAIMER files also be included ?
> For example the log contains enties like:
> org.eclipse.core.runtime.CoreException[1]:
> java.lang.ClassNotFoundException:
> org.apache.uima.caseditor.Application
> at
> org
> .eclipse
> .osgi
> .framework
> .internal.core.BundleLoader.findClassInternal(BundleLoader.java:434)
> at
> org
> .eclipse
> .osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.
I tested it for mac os and on a coworkers windows machine, both worked.
Please check if the MANIFEST.MF has the head revision.
Did you saw the compiler warnings on the console during building ?
Is there the caseditor.jar file inside the org.apache.caseditor plugin ?
If it still fails it would be interesting for me to see all build
output which is generated
by the ant script.
> The build script also copies some UIMA runtime plugin from the
> workspace. I'm not sure how we tag
> that, so that we can build it from a release tag. Maybe it would be
> easier to copy the jar of the
> used version to the CasEditor. What to other think about, how to do
> this?
>
>
> What about the CasEditor Source package. Can we also create it with
> the ant build?
I think this is easy, since its only a zip which contains all source
files.
I will work on this tomorrow too.
Would be nice if we can wait till sunday with the next sandbox tag.
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> What it the delta package?
>
> The dalta package contains plugins for other platforms as you eclipse is
> build for. So with
> the delta package you can build the CasEditor on windows for linux or
> macos.
>
> They are necessary for the build with this script.
>
> I changed the build.xml to accept a path instead of a file location, which
> I think caused the problem in your case.
>
> Can you please update you build.xml file and try again ?
>
> Sorry,
> Jörn
>
>
Now, after installing the delta package and after fixing some duplicate jar files that I have in my
environment I was able to build the package.
But the created package is not ready to ship, since the NOTICE and LICENSE files are missing. I was
also not able to run the CasEditor from the created package.
For example the log contains enties like:
org.eclipse.core.runtime.CoreException[1]: java.lang.ClassNotFoundException:
org.apache.uima.caseditor.Application
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:434)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.
The build script also copies some UIMA runtime plugin from the workspace. I'm not sure how we tag
that, so that we can build it from a release tag. Maybe it would be easier to copy the jar of the
used version to the CasEditor. What to other think about, how to do this?
What about the CasEditor Source package. Can we also create it with the ant build?
Seems there is some work to do before we can ship it.
-- Michael
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>
> On Apr 4, 2008, at 3:28 PM, Michael Baessler wrote:
>
>> Jörn Kottmann wrote:
>>>> What it the delta package?
>>>
>>> The dalta package contains plugins for other platforms as you eclipse is
>>> build for. So with
>>> the delta package you can build the CasEditor on windows for linux or
>>> macos.
>>>
>>> They are necessary for the build with this script.
>>
>> Where do I get the delta package, or what is the name. I can't find it
>> in the default update site
>> for eclipse.
>
> As fair as I know it cannot be installed via the update site, you have
> to manually download it.
> I always download and install it manually.
>
> Here is the link for eclipse 3.3.1.1:
>
> http://download.eclipse.org/eclipse/downloads/drops/R-3.3.1.1-200710231652/index.php
>
>
> Just search for "delta".
OK got it...
I think this should be documented with a README. What are the dependencies and how to get it.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
On Apr 4, 2008, at 3:28 PM, Michael Baessler wrote:
> Jörn Kottmann wrote:
>>> What it the delta package?
>>
>> The dalta package contains plugins for other platforms as you
>> eclipse is
>> build for. So with
>> the delta package you can build the CasEditor on windows for linux or
>> macos.
>>
>> They are necessary for the build with this script.
>
> Where do I get the delta package, or what is the name. I can't find
> it in the default update site
> for eclipse.
As fair as I know it cannot be installed via the update site, you have
to manually download it.
I always download and install it manually.
Here is the link for eclipse 3.3.1.1:
http://download.eclipse.org/eclipse/downloads/drops/R-3.3.1.1-200710231652/index.php
Just search for "delta".
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>> What it the delta package?
>
> The dalta package contains plugins for other platforms as you eclipse is
> build for. So with
> the delta package you can build the CasEditor on windows for linux or
> macos.
>
> They are necessary for the build with this script.
Where do I get the delta package, or what is the name. I can't find it in the default update site
for eclipse.
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
> What it the delta package?
The dalta package contains plugins for other platforms as you eclipse
is build for. So with
the delta package you can build the CasEditor on windows for linux or
macos.
They are necessary for the build with this script.
I changed the build.xml to accept a path instead of a file location,
which
I think caused the problem in your case.
Can you please update you build.xml file and try again ?
Sorry,
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
>>> Hello,
>>>
>>> finally there is a basic build script which can compile the Cas Editor.
>>>
>>> 1. Create a build_local.properties file inside CasEditor/build-files,
>>> there
>>> is a sample which can simply copied and modified.
>>> The sample contains also comments which describe how it works.
>>>
>>> 2. Launch the CasEditor/build-files/build.xml file
>>>
>>> The build scripts copies the
>>> org.apache.uima.runtime_2.2.2.incubating.jar from the uimaj-ep-runtime
>>> project.
>>> So make sure that this was build prior.
>>>
>>> Michael, can you please test if it works on your setup ?
>>>
>>> Jörn
>> I tried the build, but it seems there are some errors with the eclipse
>> classpath
>>
>> Buildfile: D:\code\eclipse330\apache\CasEditor\build-files\build.xml
>> prepareBuildDirectory:
>> [mkdir] Created dir: c:\uima\plugins
>> [mkdir] Created dir: c:\uima\features
>> [copy] Copying 1 file to c:\uima\plugins
>> [copy] Copying 613 files to c:\uima\plugins\org.apache.uima.caseditor
>> [copy] Copied 109 empty directories to 3 empty directories under
>> c:\uima\plugins\org.apache.uima.caseditor
>> build:
>> [java] The java class is not found: org.eclipse.core.launcher.Main
>>
>> BUILD FAILED
>> D:\code\eclipse330\apache\CasEditor\build-files\build.xml:70: Java
>> returned: 1
>>
>> The equinox classpath is:
>>
>> C:\Programme\eclipse330\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar;C:\Programme\eclipse330\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
>>
>
> I am note sure why it does not find the class
> org.eclipse.core.launcher.Main.
> It should be contained in both jar files, so it should pick the one in
> the jar file first specified on the classpath.
>
> Do you have an idea ?
>
> Why do you have two equinox.launcher jar files ? Did you used eclipse
> update ?
Right, some time ago I used eclipse update..
>
> Do you have the delta package installed ?
What it the delta package?
-- Michael
Re: Cas Editor build script
Posted by Jörn Kottmann <ko...@gmail.com>.
>> Hello,
>>
>> finally there is a basic build script which can compile the Cas
>> Editor.
>>
>> 1. Create a build_local.properties file inside CasEditor/build-
>> files, there
>> is a sample which can simply copied and modified.
>> The sample contains also comments which describe how it works.
>>
>> 2. Launch the CasEditor/build-files/build.xml file
>>
>> The build scripts copies the
>> org.apache.uima.runtime_2.2.2.incubating.jar from the uimaj-ep-
>> runtime
>> project.
>> So make sure that this was build prior.
>>
>> Michael, can you please test if it works on your setup ?
>>
>> Jörn
> I tried the build, but it seems there are some errors with the
> eclipse classpath
>
> Buildfile: D:\code\eclipse330\apache\CasEditor\build-files\build.xml
> prepareBuildDirectory:
> [mkdir] Created dir: c:\uima\plugins
> [mkdir] Created dir: c:\uima\features
> [copy] Copying 1 file to c:\uima\plugins
> [copy] Copying 613 files to c:\uima\plugins
> \org.apache.uima.caseditor
> [copy] Copied 109 empty directories to 3 empty directories under
> c:\uima\plugins\org.apache.uima.caseditor
> build:
> [java] The java class is not found:
> org.eclipse.core.launcher.Main
>
> BUILD FAILED
> D:\code\eclipse330\apache\CasEditor\build-files\build.xml:70: Java
> returned: 1
>
> The equinox classpath is:
>
> C:\Programme\eclipse330\eclipse\plugins
> \org.eclipse.equinox.launcher_1.0.0.v20070606.jar;C:\Programme
> \eclipse330\eclipse\plugins
> \org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
I am note sure why it does not find the class
org.eclipse.core.launcher.Main.
It should be contained in both jar files, so it should pick the one in
the jar file first specified on the classpath.
Do you have an idea ?
Why do you have two equinox.launcher jar files ? Did you used eclipse
update ?
Do you have the delta package installed ?
Jörn
Re: Cas Editor build script
Posted by Michael Baessler <mb...@michael-baessler.de>.
Jörn Kottmann wrote:
> Hello,
>
> finally there is a basic build script which can compile the Cas Editor.
>
> 1. Create a build_local.properties file inside CasEditor/build-files, there
> is a sample which can simply copied and modified.
> The sample contains also comments which describe how it works.
>
> 2. Launch the CasEditor/build-files/build.xml file
>
> The build scripts copies the
> org.apache.uima.runtime_2.2.2.incubating.jar from the uimaj-ep-runtime
> project.
> So make sure that this was build prior.
>
> Michael, can you please test if it works on your setup ?
>
> Jörn
I tried the build, but it seems there are some errors with the eclipse classpath
Buildfile: D:\code\eclipse330\apache\CasEditor\build-files\build.xml
prepareBuildDirectory:
[mkdir] Created dir: c:\uima\plugins
[mkdir] Created dir: c:\uima\features
[copy] Copying 1 file to c:\uima\plugins
[copy] Copying 613 files to c:\uima\plugins\org.apache.uima.caseditor
[copy] Copied 109 empty directories to 3 empty directories under
c:\uima\plugins\org.apache.uima.caseditor
build:
[java] The java class is not found: org.eclipse.core.launcher.Main
BUILD FAILED
D:\code\eclipse330\apache\CasEditor\build-files\build.xml:70: Java returned: 1
The equinox classpath is:
C:\Programme\eclipse330\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar;C:\Programme\eclipse330\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
-- Michael