Hi, I'm working on https://github.com/gradle/gradle/blob/master/design-docs/publication-model.md#customising-maven-descriptor-xml
Some questions: 1. Multiple artifacts The spec says that: > When this MavenPublication instance is used for publishing, the following > defaults are used: > … > • All artifacts from public configurations are published. This strategy works for Ivy (kinda), but is problematic for Maven. There's a key difference between Maven and Ivy publication; Ivy can publish an arbitrary set of artifacts, Maven can publish one non-classified artifact and zero or more additional, classified, artifacts. If we use this “All artifacts from public configurations are published” strategy, all artifacts except one would need to have a classifier. Is this what we want at this stage? 2. Only runtime dependencies? Spec: > When this MavenPublication instance is used for publishing, the following > defaults are used: > … > • No dependencies are included in the pom. > • When the java plugin is applied, the following dependencies are included in > the pom.xml: > • All dependencies specified in configurations.runtime are added with > runtime scope. Why only runtime scope? 3. Identifiers Spec: > When this MavenPublication instance is used for publishing, the following > defaults are used: > • groupId == project.group > • artifactId == project.name (_not_ archivesBaseName) > • version == project.version > • packaging == null This means that the settings on the artifact object itself will have no effect at all. Is this what we want ? (I'd say yes, but just checking) 4. MavenPom type We already have a MavenPom class. We can't really use this for the new publication stuff. Is the plan to introduce a new one in parallel and then eventually remove what we have now? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
