| RE: [corona-dev] org.apache.axis2 jar files retrieving in workbench |
|
Glenn: I
thought of such approach, that clean done on org.apache.axis2 project, removes all
the jar files from the lib folder and than it downloads all required jar files.
But it’s not done this way. Currently clean operation
does not remove jar files from the lib folder, so the download operation is
performed once. You have to be aware, that each time if you modify org.apache.axis2
plugin, and it will require compilation, the script will be called and it will check
whether all necessary jar files are available, if not than the script will get them
from the internet. If all required jars are available than nothing will happen.
Piotr From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of So every time I do a clean all and then
build it is going to download the Axis2 jar files? I thought we were just
going to have a script that ran once to download the plugins.zip file from
Joel’s Apache People folder and unzipped and copied the jar files into
the correct projects. I thought I would just run the script the first
time I was setting up a workspace. Glenn Everitt From: Hi,
The script in org.apache.axis2 project, for automatic jar files
retrieving is checked into repository. The script is automatically called when
project requires a build. I’ve found out few problems concerning the script: 1. When the
script is called just after importing the plugin into repository, you have to
update the .classpath file by
calling right click on
project->PDE Tools->Update Classpath... (I guess we can fix
it by checking in the .class file into repository). 2. If the .classpath is updated,
and you’ll build the clean project (without the jar files in it). Than,
after the build, Manifest.mf file in Export-Package: section will
report errors. To fix it you’ll have to rebuild the project again. Maybe
someone have an idea how to solve that problem… For now the script
is configured that it downloads jars without a proxy. If the download process
fails (and it will fail for all of us), add proxy properties to global eclipse ant properties, Window->Preferences->Ant->Runtime, "properties" tab. Add there proxyhost, proxyport, proxyuser, proxypassword. (you can also define a global ant properties file and specify it
over there). Cheers, Piotr The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it. The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it. |