- 浏览: 52513 次
- 性别:
- 来自: 沈阳
最新评论
-
imu2008:
嗯,此方法可用。好文。mark
rcp中新建工程没有图标解决方案 -
553563608:
今天也遇到这个问题了,,,,
这个方法可以解决。。。
rcp中新建工程没有图标解决方案 -
zhaozhongwei:
这个就不清楚了,我们也是两个文件啊。我很久没搞gmf了
关于gmf copy/paste 的解决方案 -
popjxc:
我下了你的代码,发现copy paste后,原来复制的是一个n ...
关于gmf copy/paste 的解决方案 -
赤道螞蟻:
你這不是用附件的方式傳的圖片嗎? 沒有什麽新招?
用java mail发送包含图片的html
java -jar
<eclipse-installation-path>\plugins\org.eclipse.equinox.launcher_<version><qualifier>.jar
-application org.eclipse.ant.core.antRunner -buildfile
<eclipse-workspace-path>\<project-name>\<build-xml-path>
example
java -jar C:\eclipse\plugins\org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.ant.core.antRunner -buildfile C:\workspace\com.example.helloworld\build.xml
Building
through features
Plug-ins are rarely required to be build in isolation. The nicer way of building them is through features. Of course, features are more useful from distribution and deployment point of view. A feature is build the same way as a plug-in. Include the required plug-ins in the feature.xml and generate the build.xml from build.properties file (right-click and choose PDE Tools). Now launch the feature build.
java
-jar
<eclipse-installation-path>\plugins\org.eclipse.equinox.launcher_<version><qualifier>.jar
-application org.eclipse.ant.core.antRunner -buildfile
<eclipse-workspace-path>\<feature-project-path
>\<build-xml-path>
example
java -jar C:\eclipse\plugins\org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.ant.core.antRunner -buildfile C:\workspace\com.example.helloworld.feature\build.xml
Note that
build will fail if the included plug-ins do not have the build.xml generated for
them. This is not a likely scenario and definitely not the way it is done. But
let it be for time being. Generate the build.xml for all the plug-ins for build
to succeed. Later on we will see how it can be done without it.
Passing
parameters to AntRunner from command line
The build generated by the above command will leave the feature jar inside the feature project and the plug-in jar inside the plug-in project folder. Of course they shouldn't scattered all around. They need to be collected to one place.
Open the
build.xml for the plug-in project and inside the 'init' target there is one
property called 'plugin.destination'. It is this location where the jar is
finally created by the 'build.update.jar' target.
<property name="plugin.destination" value="${basedir}"/>
Change the
value of this property to "${buildDirectory}". Make the similar change for the
'feature.destination' property in the build.xml for the feature project.
If the build
is triggered now, it will fail because it can not find the value for the
'buildDirectory'. The value can be provided through command line using -D
option.
java
-jar
<eclipse-installation-path>\plugins\org.eclipse.equinox.launcher_<version><qualifier>.jar
-application org.eclipse.ant.core.antRunner -buildfile
<eclipse-workspace-path>\<feature-project-path
>\<build-xml-path>
-DbuildDirectory=<build-storage-location>
example
java -jar C:\eclipse\plugins\org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.ant.core.antRunner -buildfile C:\workspace\com.example.helloworld.feature\build.xml -DbuildDirectory=c:\build\buildOutput
More parameters can be supplied using -D<variable-name>=<value> from the command line.
Ant properties file
Passing parameters from the command line is not very scalable or maintainable. A better way is to pass the parameters using a properties file.
Create a properties file, say, 'custom_build.properties' inside a folder, say, 'buildConfiguration'. The name 'custom_build.properties' have been chosen to distinguish it from 'build.properties'. Carefully note that though both are name=value kind properties file, it is common(rather better) practice to not mix them. Since 'build.properties' has a special meaning in context of PDE, it is recommended that a different name is used to avoid any confusion.
Store the property and its value in the properties file.
buildDirectory=c:/build/buildConfigurationNote the forward slashes instead of backslash. The backslashes will work too but needs to be escaped.
Now open the build.xml for the feature project and add the 'loadproperties' entry under the 'project' tag.
<project name="com.example.helloworld.feature" default="build.update.jar" basedir="."> <loadproperties srcfile="../../buildConfiguration/build.properties" /> ...This entry needs to be made only in feature project's build.xml and is not required for the plug-in projects' build.xml. They still can use the same variable name and will get the value from the properties file.
Note that the value for the 'srcfile' is a relative path and the ../../ (grand-parent directory) indicates that the properties file has been kept in one folder outside the folder (or workspace) containing the projects.
发表评论
-
How to Debug and Detect Deadlocks
2010-12-01 15:04 1006Deadlocks in 2 minutes ... -
Run FindBugs from your Eclipse RCP headless build
2010-12-01 14:53 977Running FindBugs from Eclipse R ... -
Markers and Annotations in Eclipse for Error Feedback(forward)
2010-12-01 14:39 1561Motto: Ninety per cent ... -
Testing declarative Eclipse expressions(forward)
2010-11-19 08:32 1036Our Eclipse-based product plugs ... -
Release engineer vs dependency management: Basing RCP Product and headless build
2010-11-02 23:32 837http://www.bonitasoft.org/blog/ ... -
Unit testing puzzle – How can I verify that System.exit() gets called?
2010-08-14 08:17 0Sounds strange – yes, very ... -
Invoking an Eclipse Wizard programmatically
2010-07-23 09:45 0Sometimes I find the need to ... -
A testing strategy for multiple inheritance in EMF generated code.
2010-07-23 09:12 0I recently became a comittter ... -
Can we build it? Yes we can!(FW)
2010-07-16 11:05 0Thomas Hallgren, Michal Ruzicka ... -
Generating p2 meta data from command line
2010-06-11 12:08 780Many times when working with ... -
Opening files in Eclipse from the command line(转发)
2010-06-11 12:08 1187I ran a query to see all the ... -
http://cvalcarcel.wordpress.com/
2010-04-09 03:00 0http://cvalcarcel.wordpress.com ... -
HOWTO: Build Plugin & Feature Projects, Then Run Their Unit Tests w/ Tycho ::GEF
2010-04-03 14:30 01. Check out entire source tree ... -
Tip: How to Debug SWT components in Modal Dialogs(转发)
2010-04-03 14:22 0SWT and JFace components, and e ... -
action
2010-03-24 17:22 0这两天在改一个bug,跟action有关的,以前一直也没好好弄 ... -
SWT: Drop an Outlook Email(转发)
2010-03-18 14:43 1795I wanted to drop an outlook ema ... -
终于成为eclipse的committer了
2010-03-16 16:33 3143虽然以前也是committer,但是是个非常小的工程还是卵化期 ... -
Animated GIF in TableViewer
2010-03-02 12:23 0I'm quite attached to TableVie ... -
extend jdt with ot
2010-02-28 11:56 0extend jdt with ot http://blog ... -
RCP Update: No more "jammern" with InstallJammer
2010-01-29 14:44 0Wow, I got a lot of feedback be ...
相关推荐
Docker 打包的 Headless Chrome 方案。.zip,无头镀铬渲染解决方案
Headless-Browser 是一款采用C 开发的基于WebKit 无界面浏览器。安装:git clone git://github.com/alexandernst/headless_browser.git headless_browser cd headless_browser git submodule init git ...
一个用于处理headless Chrome的Go包。 使用go和Chrome在页面上运行交互式JavaScript命令。
Unity headless builder v1.1 资源包
使用headless版Chrome将网页转换为图片
资源分类:Python库 所属语言:Python 资源全名:opencv_python_headless-4.5.4.60-cp39-cp39-win32.whl 资源来源:官方 安装方法:https://lanzao.blog.csdn.net/article/details/101784059
linux的chrome 63版本,zip包解压即可使用 ...1,特别适合使用chrome headless功能,在后台运行导出PDF和PNG的场景 2,在docker上使用chrome 3,任何linux版本均可,绿色zip压缩版本,解压后即可执行
资源来自pypi官网。 资源全名:opencv_python_headless-4.3.0.38-cp38-cp38-win32.whl
基于Headless Chrome开发分布式爬虫,Distributed crawler powered by Headless Chrome
python库,解压后可用。 资源全名:opencv_python_headless-4.3.0.38-cp38-cp38-win32.whl
Headless是一款无界面浏览器,支持快速Web验测试,采用.Net环境。 优点: 支持快速网络接受测试。 HTML 元素解析。 支持多种表单。 支持超链接。 手册,页面或动态规划模型。 支持位置和状态代码验证 可扩展。
使用 Headless Chrome 渲染 JavaScript 前端渲染的网页(如 AngularJS)以便搜索引擎爬取
python库。 资源全名:opencv_python_headless-4.5.4.58-cp37-cp37m-win32.whl
使用案例驱动的示例来使用Puppeteer和headless chrome
使用headless Chrome作为自动化截图工具(替代PhantomJS)
Chrome Headless 模式下的控制封装 Api.zip,node.js的chrome调试协议接口
离线安装包,亲测可用