Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Fix the build and fix the version qualifier
Now IvyDE needs more than just the SDK to build
Update IvyDE version and make the build support an empty qualifier in the version
Make the archives contain a nested directory as suggested by Stefan
Make the license included in the binaries packaging
Scripting the source packaging
- avoid duplicate template files - document how to package the sources
- move CHANGES.txt next to the other text files - fix the checksum and sign scripts
Change the way the binary and source distribution is build: - add license and notice - add the generated doc into the binary distribution - since the packaging changed, update the documentation about installing the plugin manually
Fix the build in the release mode : the version was not computed correctly
IVYDE-48: - add simple target to generate checkstyle report
Add the timestamp to the release version so it will be correctly ordered. But then also add an additional qualifier to make the difference between the different kind of build
No more need to build an updatesite here
- make IvyDE on hudson use the last release of Ivy - make hudson always trying to update the Ivy installed in the Eclipse install, but now keep the downloaded files
The name of the site.xml file changed: make it still included in the source package
Add a target to generate an updatesite for a fresh trunk build
xml formatting
Add some targets dedicated to the preparation of the environment of Hudson
IVYDE-150: Add the IvyDE documentation to the Eclipse help - add a xooki template used for the eclipse doc - add the declaration of the doc in the plugin - add an ant target to generate the doc formatted for the eclipse plugin - add an ant target to generate the eclipse toc from the xooki one
Add some usefull target to install the home made IvyDE build into an Eclipse installation
Make the install-ivy target also work on windows
Little cleanup of the build: - by default do not log very very verbosely - always build update jars - make the default mirror url configurable - give better exemples in the install-ivy inline help
IVYDE-122: - use a more uniform work directory path handling - really add the check of the installed Ivy
IVYDE-122: - add a task to list the installed Ivy - add a check if Ivy exists in the Eclipse install before starting to build
IVYDE-122: add tasks to install an ivy jar into an Eclipse install
- remove the now useless ivy feature which is now managed when updating the updatesite - make the installation of the ivy bundle more configurable
Simplify the build as there is no more updatesite to handle here, and no more ivy feature to handle neither
Also sign the digest.zip
Package also the binaries of the ivy bundle and feature (it should probably be added later directly into Ivy's build system).
Fix the spell mistake in the source packaging
Add the new files to the source distribution
Add a description to the task to make it public
Add an ant task to verify the md5 and sha check sums
Add the task that repackage the ivy bundle
Add some description to the public target
* Packaging of Ivy as a feature because it seems that eclipse don't like optimizing the update site for only one feature. * Add some "feature.properties" files in order to make the digest being build
Fix the generation of the md5 and sha files
Follow Apache guidelines
- The source are actaully more a zip than a jar, later we would probably support better jar sources - add the site.xml to the sources
Simplify the build system: it will only produce files to be pushed into the "replicated" Apache dist directory. The real update site will only hold the site.xml, published on www.apache.org, maintained manually.
Improve the build: - remove tabs and use of spaces - add a dist directory - add task to manage an updatesite
outputUpdateJars is not suitable for manual install
Improve the build system: - add source packaging - when doing official release, do not append the timestamp - in the feature zip, do not prefix with an eclipse folder - remove the obsolete build.xml - add a local.build.properties to avoid specifying everytime baseLocation
Make the build put the eclipse logs into the console for easier debugging of the build
Make sure that the debug info are embedded into the .class files
Fix the build path which where not working under Windows
IVYDE-88 : Add new target to build.xml to build the plugin with Ant - as discussed on the mailing list, IvyDE is 2.0 now - introduce a root build.xml that build everything ready to be deployed in an eclipse install
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |