%HTTP_EQUIV_ON_VIEW%
build.xml. In maven, all the tasks are provided for you (and there are tons). Maven calls tasks 'goals'. They run using properties you specify in your project definition (project.xml). So all you have to do is define some properties and you can run tons of tasks. If you need a plugin to do a goal, it downloads and installs it automatically.
If you want to add more, you can define your own goals for your project in maven.xml. Any ant task can be called from a goal.
With maven, one project can extend another, inheriting any properties that are not overridden.
PluginName.props file are already required for project.xml. jEdit could parse project.xml or build.xml instead of having a separate properties file.
project.xml and replace a few properties.
jEdit could also provide a default plugin project definition, which plugin project definitions could extend, making plugin build files even simpler.
project.xml to install plugins and set properties to their liking.
| Web Form | |
|---|---|
| Topic Classification: | No Disclosure |
| Operating System: | |
| Os Version: | |
| Topic ApacheMaven . { Edit | Attach | Ref-By | Printable | Diffs | r1.2 | > | r1.1 | More } |
| Revision r1.2 - 23 Jan 2004 - 21:05 GMT - Brad Mace | %WEBCOPYRIGHT% |