| generating build.xml from build.properties [message #316681] |
Thu, 14 June 2007 14:17  |
Eclipse User |
|
|
|
Hello,
I am trying to automate the creation of build.xml files, using the example
code provided in the Eclipse Help.
I've created an ant script containing the eclipse.buildScript Ant task, and
I can run it using:
java -cp startup.jar org.eclipse.core.launcher.Main -application
org.eclipse.ant.core.antRunner -buildfile
c:\eclipseRepository\BuildProject\build.xml
The script runs and reports BUILD SUCCESSFUL, but there is no build.xml in
c:\eclipseRepository
What do I need to do to get this to work?
<project name="MyBuilder">
<target name="makeMyBuild">
<eclipse.buildScript elements="plugin@org.foo.myplugin"
buildDirectory="c:\eclipseRepository\org.foo.myplugin"/>
</target>
</project>
|
|
|
| Re: generating build.xml from build.properties [message #316692 is a reply to message #316681] |
Fri, 15 June 2007 06:14  |
| Eclipse User |
|
|
|
sigpete@ca.ibm.com wrote:
> Hello,
>
> I am trying to automate the creation of build.xml files, using the example
> code provided in the Eclipse Help.
>
> I've created an ant script containing the eclipse.buildScript Ant task, and
> I can run it using:
> java -cp startup.jar org.eclipse.core.launcher.Main -application
> org.eclipse.ant.core.antRunner -buildfile
> c:\eclipseRepository\BuildProject\build.xml
> The script runs and reports BUILD SUCCESSFUL, but there is no build.xml in
> c:\eclipseRepository
>
> What do I need to do to get this to work?
>
> <project name="MyBuilder">
>
> <target name="makeMyBuild">
> <eclipse.buildScript elements="plugin@org.foo.myplugin"
> buildDirectory="c:\eclipseRepository\org.foo.myplugin"/>
> </target>
>
> </project>
I guess it is because the buildDirectory should contain a plugins
subdirectory where your plugin resides. So, you probably should copy
your plugin to C:\eclipseRepository\plugins\org.foo.myplugin and set
buildDirectory to C:\eclipseRepository.
What is the context of your automation? Would it make sense to set up a
complete headless build? You could use map files with the copy method so
that you don't have to start the headless build with checking out the
sources from a repository. The advantage: the headless build (the fetch
phase) would create the buildDirectory with the correct structure for
you (which includes to map project names to plug-in ids).
If you have not yet set up a headless build so far, you could have a
look at http://www.pluginbuilder.org.
cheers
Markus
|
|
|
Powered by
FUDForum. Page generated in 0.07628 seconds
Home