aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Provision libraries in 'lib' automaticallyAlexander Kriegisch2021-05-051-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upon special request by Andy Clement, I included 'lib' as a child module in the parent POM again, making several modules which refer to downloaded library files dependent the 'lib' module. I am not sure I caught all of them, but I hope so. Now after cloning the project and configuring the token for reading from GitHub Packages (sorry!), you can just run a Maven build for the main project and no longer need to fail the first build, read the Maven Enforcer message and run 'cd lib && mvn compile' as a first step. This convenience comes at the price of a more complex POM and two new profiles: - Profile 'provision-libs' is auto-activated by the absence of a marker file, kicking off the library provisioning process and creating same marker file at the end, if successful. Therefore, during subsequent builds libraries will not be re-provisioned, because the marker file exists and Maven skips all download and (un)zip steps, which saves build time and bandwidth. Otherwise offline builds would not work either. - Profile 'clean-libs' needs to be activated manually, because by default 'mvn clean' will not erase provisioned libraries. In most cases, even after a clean a developer does not want to re-provision all libraries if they have not changed (e.g. new JDT Core build). But if you do wish too erase the libraries and the marker file, just call 'cd lib && mvn -P clean-libs clean'. Please note: The Maven Enforcer build step, which additionally checks for existence of other files, still exists and was moved from the parent POM to 'libs'. No matter if provisioning was just done or skipped because the main marker file exists, a quick heuristic check for that list of files is done during each build, failing the build with a comprehensive message if an inconsistency was found. The error message says which files are missing and tells the user: "There is an inconsistency in module subdirectory 'lib'. Please run 'mvn --projects lib -P clean-libs clean compile'. This should take care of cleaning and freshly downloading all necessary libraries to that directory, where some tests expect them to be." This should cover the topic. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Remove redundant 'name' and 'packaging' tags from POMsAlexander Kriegisch2021-04-151-2/+0
| | | | | | | If 'name' is identical to 'artifactId' and 'packaging' has the default value 'jar', we can just remove those tags from the POM. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Fix image formatting glitch in docs/devGuideDB/ajbrowser.xmlAlexander Kriegisch2021-04-101-18/+22
| | | | | | | | | An image which should be in its own paragraph was shown inline with the text, somewhere to the right in the middle of a text paragraph. I noticed while visually checking if docs generation still works as expected after the last few commits, so I quickly fixed it. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Delete all remaining docbook contents, download them insteadAlexander Kriegisch2021-04-101-7/+1
| | | | | | | | Actually, only fop:fop:0.20.5 and batik:batik-1.5-fop:0.20-5 are really used in addition to lib/saxon/saxon.jar (saxon:saxon:6.5.3). So the rest does not need to be replaced and can just be wiped. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Remove indentation from <programlisting> blocks in docsAlexander Kriegisch2021-04-1028-4590/+4472
| | | | | | | | | | | | | | | Many dozens (hundreds?) of documentation code blocks were indented to match the surrounding XML or just arbitrarily. The thing is: Inside <programlisting> tags, similar to <pre> tags, line feeds and leading whitespace are being preserved, which looked very awkward in the HTML documentation. While a few files were mostly correct in this respect, which shows that it was meant to be like that, many others were not. This was tedious, stupid work to fix, but it had to be done. Please note that the documentation was in no way updated content-wise. This is also overdue, but not my focus here. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Add comments about wrong classpath entries to docs/build.xmlAlexander Kriegisch2021-04-101-9/+9
| | | | | | | | Of 6 classpath entries for Ant taskdef "fop", only 2 are actually correct. That might mean that the others are not necessary, because docs generation works correctly anyway. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Fix faulty path in docs/progGuideDB/progguide.html.xslAlexander Kriegisch2021-04-101-9/+9
| | | | Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Clean up remaining references to system-scoped dependenciesAlexander Kriegisch2021-04-101-80/+0
| | | | | | | | Now there is no system-scoped dependency left anymore in the Maven build, i.e. the corresponding warnings are gone and we can focus on the actual build log. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Remove JRockit LTW support, particularly JRockitAgentAlexander Kriegisch2021-04-101-68/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | In two places, the documentation now contains this text: "Since AspectJ 1.9.7, the obsolete Oracle/BEA JRockit agent is no longer part of AspectJ. JRockit JDK never supported Java versions higher than 1.6. Several JRockit JVM features are now part of HotSpot and tools like Mission Control available for OpenJDK and Oracle JDK." The decision to drop JRockit support was made during a discussion between Alexander Kriegisch and Andy Clement: Andy Clement wrote on 26 Mar 2021: > Yes I think so. > > > Alexander Kriegisch wrote on 26 Mar 2021: > >> https://en.wikipedia.org/wiki/JRockit >> >> Can we get rid of that? AspectJ requires Java 8, JRockit never >> supported more than Java 6. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Bump maven-antrun-plugin from 1.6 to 3.0.0Alexander Kriegisch2021-03-291-1/+1
| | | | | | | | This is not strictly necessary, but probably does not hurt either. While upgrading, '<tasks>' tags have been renamed to the new standard '<target>'. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Add developer info + sample config about how to work with a RAM diskAlexander Kriegisch2021-03-253-0/+69
| | | | | | | | | | | | | | | | | | There are two files: - docs/developer/ram-disk/maven.config - docs/developer/ram-disk/settings-ramdisk.xml The latter contains info about how to set up a development environment inside a RAM disk. Both files are to be copied to the project's '.mvn' folder in the root directory and adjusted according to the description. Just in case, .gitignore ignores the files if they exist in '.mvn', so they are not being staged and committed accidentally. An additional screenshot shows how to configure the Windows Recycle Bin to immediately delete files in order too save space on the RAM disk. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Upgrade to ASM 9.1, delete obsolete ASM binariesAlexander Kriegisch2021-03-161-1/+1
| | | | | | | | | | | Keep only ASM 2.0 binary because it is still used in UnweavableTest which uses an old ASM API, e.g. with a ClassWriter constructor which no longer exists. Also add JarJar 1.3 library because it is needed by an Ant task in lib/asm/build.xml. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Move documentation generation into Maven profile 'create-docs'Alexander Kriegisch2021-03-141-128/+167
| | | | | | | | | The profile is active by default, but can be deactivated via '-P !create-docs' on the Maven command line. This helps to speed up 'mvn install', maybe in combination with skipping tests, if we just want to create a new set of AspectJ binaries. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
* Update the URL of BCELEmmanuel Bourg2021-01-071-1/+1
|
* Fix apostrophe in the licenseJerry James2020-09-151-1/+1
|
* Fix misplaced or incorrect javadoc tagsJerry James2020-09-142-2/+2
|
* Give docbook IDs unique namesJerry James2020-09-094-6/+6
|
* Revert to 1.9.7.BUILD-SNAPSHOTAndy Clement2020-08-211-1/+1
|
* 1.9.7 milestone 1 publishedAndy Clement2020-08-211-1/+1
|
* Remove project.parent.relative path as ../pom.xml is already the defaultLars Grefer2020-08-151-1/+0
| | | | Signed-off-by: Lars Grefer <eclipse@larsgrefer.de>
* Rev to 1.9.7.BUILD-SNAPSHOTAndy Clement2020-07-221-1/+1
|
* Fixed a misplaced <para> element in the Docbook documentation for ajcEmmanuel Bourg2020-07-221-1/+1
|
* AspectJ 1.9.6 final bitsV1_9_6Andy Clement2020-07-222-2/+2
|
* polishAndy Clement2020-04-201-5/+4
|
* Include JDTCore for Java14Andy Clement2020-04-202-0/+75
|
* Move to 1.9.6.BUILD-SNAPSHOT versionAndy Clement2019-11-281-1/+1
|
* 1.9.5 release versions in pomsV1_9_5Andy Clement2019-11-281-1/+1
|
* polishAndy Clement2019-11-281-2/+2
|
* 1.9.5 readmeAndy Clement2019-11-282-1/+76
|
* 552724: fix typoAndy Clement2019-11-251-1/+1
|
* polishAndy Clement2019-07-021-1/+1
|
* Update to 1.9.5.BUILD-SNAPSHOT in pomsAndy Clement2019-06-031-1/+1
|
* polish 1.9.4V1_9_4Andy Clement2019-05-101-0/+1
|
* 1.9.4 POMSAndy Clement2019-05-101-1/+1
|
* Final bits of AspectJ 1.9.4Andy Clement2019-05-102-0/+47
|
* pushed versions to 1.9.4.BUILD-SNAPSHOTAndy Clement2019-04-171-1/+1
|
* Updated with Java12 supportAndy Clement2019-04-031-0/+66
|
* 1.9.3 inclusionAndy Clement2019-04-011-0/+1
|
* 1.9.3.RC1 final bitsV1_9_3RC1Andy Clement2019-03-071-0/+30
|
* tidyup - last bits of maven stuffAndy Clement2019-02-081-0/+12
|
* tidyupAndy Clement2019-02-081-0/+137
|
* tidyupAndy Clement2019-02-082-7/+5
|
* tidyup retired modules and add aspectjtools submoduleAndy Clement2019-02-081-17/+0
|
* wip 1.9.2 readmeAndy Clement2018-10-152-0/+36
|
* typo reported by Emmanuel BourgAndy Clement2018-10-151-1/+1
|
* Working towards 1.9.1V1_9_1Andy Clement2018-04-202-0/+53
|
* tweak titleV1_9_0Andy Clement2018-04-021-1/+1
|
* Fixed release date to 2-Apr for 1.9.0Andy Clement2018-04-021-1/+1
|
* Updated readme for 1.9.0 releaseAndy Clement2018-04-021-28/+34
|
* docs for new code generation and factory methodsAndy Clement2018-03-121-0/+32
|