I've seen a few posts about a single project producing multiple artifacts and
even regarding uloading those artifacts to a repository. And I have read
http://gradle.org/0.9.2/docs/userguide/userguide_single.html#sub:multiple_artifacts_per_project
and related sections.
But I have not found information about handling these multiple artifacts:
a) with customized poms
b) through the install task of the Maven plugin
Essentially I have 6 artifacts produced by this one project, the two "main"
artifacts plus source and javadocs jars for each:
task testingJar(type: Jar, dependsOn: compileTestJava) {
from sourceSets.test.classes
includes += "org/hibernate/testing/*"
baseName = 'hibernate-testing'
}
As I mentioned I use a customized pom already (from the root project):
def pomConfig = {
url 'http://hibernate.org'
...
}
configure(install.repositories.mavenInstaller) {
pom.project pomConfig
}
uploadArchives {
repositories.mavenDeployer {
name = 'jbossDeployer'
configuration = configurations.deployerJars
pom.project pomConfig
repository(url: ...)
snapshotRepository(url: ...)
}
}
From this point I am really just lost. The new artifact needs an overridden
artifactId in the pom (it cannot use the project name). In terms of uploading
and installing, I have seen both the filter approach and split configuration
naming. But it seems like each require an awful lot of duplication in setting
up.
Can anyone help show me the light?
P.S. Personally, it seems to me that these details should be handled much more
transparently by the maven plugin. For example, in my opinion if an artifact
is uploaded to a repository by the maven deployer it ought to automatcally be
handled by the install task : http://jira.codehaus.org/browse/GRADLE-1383
---
Steve Ebersole <[email protected]>
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
