diff options
| author | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-05-12 12:03:33 +0700 |
|---|---|---|
| committer | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-05-16 07:05:28 +0700 |
| commit | de12ea9f2c59f4654c36e291e1f8160948d533eb (patch) | |
| tree | 2aa3edd5b9894472509342c40d191b24e11564a5 /aspectjmatcher/pom.xml | |
| parent | 49ae298d31859132fd61f187d53b91f5ec2c1d4b (diff) | |
| download | aspectj-de12ea9f2c59f4654c36e291e1f8160948d533eb.tar.gz aspectj-de12ea9f2c59f4654c36e291e1f8160948d533eb.zip | |
Add information required by Maven Central to public artifact POMs
This is another step away from manual deployment towards Maven-triggered
deployment for both releases and snapshots. The 5 main POMs (matcher,
runtime, weaver, tools, installer) now contain information required by
Sonatype for Maven Central deployments according to:
https://central.sonatype.org/publish/requirements/
TODO:
- Add corresponding 'distributionManagement' section and necessary
release plugins for Sonatype OSS repositories to parent POM.
- Enable Maven to also use Install plugin in order to automatically
set release versions, commit to Git and tag releases, then upgrade
to a new snapshot afterwards.
- Make sure that Flatten Maven plugin does not strip off the required
tags we just added to the POMs. It looks as if the chosen
flattenMode=oss already retains the exact tags we need, only
slightly reformatting (hence "uglifying") the POM. But an ugly POM
does not block Maven Central deployments, as long as it is complete.
So it looks as if this to-do item is already done.
Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'aspectjmatcher/pom.xml')
| -rw-r--r-- | aspectjmatcher/pom.xml | 37 |
1 files changed, 35 insertions, 2 deletions
diff --git a/aspectjmatcher/pom.xml b/aspectjmatcher/pom.xml index 0cba8cae9..e0cd44e8a 100644 --- a/aspectjmatcher/pom.xml +++ b/aspectjmatcher/pom.xml @@ -1,6 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<project xmlns="http://maven.apache.org/POM/4.0.0" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> @@ -11,7 +10,41 @@ </parent> <artifactId>aspectjmatcher</artifactId> + <name>AspectJ Matcher</name> + <description> + The AspectJ matcher can be used for matching pointcuts independently of any AspectJ compilation or weaving steps. + Most notably, this can be used by frameworks such as Spring AOP which utilise the @AspectJ pointcut syntax but + implement aspect weaving in a way independent of AspectJ, e.g. using dynamic proxies. + </description> + <url>https://www.eclipse.org/aspectj/</url> + + <licenses> + <license> + <name>Eclipse Public License - v 1.0</name> + <url>http://www.eclipse.org/legal/epl-v10.html</url> + <distribution>repo</distribution> + </license> + </licenses> + + <developers> + <developer> + <id>aclement</id> + <name>Andy Clement</name> + <email>aclement@vmware.com</email> + </developer> + <developer> + <id>kriegaex</id> + <name>Alexander Kriegisch</name> + <email>kriegaex@aspectj.dev</email> + </developer> + </developers> + + <scm> + <url>https://github.com/eclipse/org.aspectj</url> + <connection>scm:git:https://github.com/eclipse/org.aspectj.git</connection> + <developerConnection>scm:git:ssh://git@github.com:eclipse/org.aspectj.git</developerConnection> + </scm> <properties> <!-- By default, do not deploy artifacts - but deploy this public one --> |