Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (athena.apache.org: domain of PWardrip@tandbergtv.com
 designates 66.0.13.30 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Ivy 2.0.0 beta2: MakePom Patch (Enhancement)
Date: Thu, 13 Mar 2008 12:19:09 -0400
Message-ID: 
 <5090F837D397EC47818B18D3B0461821010A7D77@ATL-EXCH1.US.TANDBERGTV.COM>
In-Reply-To: <635a05060803130553i3d9b7e73y2ec7ea8b8ade32b2@mail.gmail.com>
Thread-Topic: Ivy 2.0.0 beta2: MakePom Patch (Enhancement)
Thread-Index: AciFCUKcF2ap/aLnSOmZy3Wfk4auNAAHFpsg
References: 
 <5090F837D397EC47818B18D3B0461821010A7D06@ATL-EXCH1.US.TANDBERGTV.COM>
 <635a05060803130553i3d9b7e73y2ec7ea8b8ade32b2@mail.gmail.com>
From: "Wardrip, Paul" <PWardrip@tandbergtv.com>
To: "Ant Developers List" <dev@ant.apache.org>

https://issues.apache.org/jira/browse/IVY-770=20

--pw

-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]=20
Sent: Thursday, March 13, 2008 8:53 AM
To: Ant Developers List
Subject: Re: Ivy 2.0.0 beta2: MakePom Patch (Enhancement)

This sounds interesting. Could you open an issue and attach your patch
to it?

Xavier

On Wed, Mar 12, 2008 at 11:08 PM, Wardrip, Paul
<PWardrip@tandbergtv.com> wrote:
>
>
>
> I am working on a new build process for my company using Ivy and an=20
> Archiva
> (Maven2 based) repository. I use the Ibiblio resolver to read and SFTP

> to publish. SFTP is not ideal, but I read that webdav support was=20
> currently broken in Ivy 2.0. I need to deploy projects in a Maven2=20
> format for the repository and other users. I made some changes to the=20
> MakePom task to handle projects with multiple artifacts. I thought=20
> they may be useful so I wanted to pass them along.
>
> Maven2 won't create more than one uniquely named artifact for a=20
> project, unless you set the packaging to "pom". Then you have a=20
> separate pom for each of the artifacts, referencing the project pom=20
> with a parent tag. They would get deployed like this:
>
> /myorg/mymodule/1.0/mymodule-1.0.pom
> /myorg/artifact-core/1.0/artifact-core-1.0.pom
> /myorg/artifact-core/1.0/artifact-core-1.0.jar
> /myorg/artifact-util/1.0/artifact-util-1.0.pom
> /myorg/artifact-util/1.0/artifact-util-1.0.jar
>
> I changed the MakePom task to build separate poms when it detects=20
> uniquely named artifacts. I have 2 patterns for my SFTP resolver. The=20
> default pattern is used when there are no declared artifacts or when=20
> the artifact name matches the module name. I have the task setting a=20
> property "ivy.pom.descriptor.size" with the number of poms that were=20
> generated. I use this property to decide which pattern to use:
>
> Default Pattern:
> /[organization]/[module]/[revision]/[module]-[revision].[ext]
> Multi Artifact:
> /[organization]/[artifact]/[revision]/[artifact]-[revision].[ext]
>
> This works very well for my build process and repository, the only=20
> thing that would be better is a resolver for Maven2 that does all of=20
> this automatically. A good Maven2 resolver should build and publish=20
> the poms automatically, without calling MakePom or declaring them as=20
> artifacts. Use the Ibiblio functionality for reads, webdav for writes=20
> and handle multiple artifact projects with a different pattern.
>
> ------------
> Paul Wardrip
> Software Engineer, OpenStream
> TANDBERG Television | Part of the Ericsson Group 4500 River Green=20
> Parkway | Duluth | GA 30096
> Mobile: 770-312-2852 | AIM: paulwardrip
> Email: pwardrip@tandbergtv.com | www.tandbergtv.com
>
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org  For=20
> additional commands, e-mail: dev-help@ant.apache.org
>


--
Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/
http://ant.apache.org/ivy/ http://www.xoocode.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
commands, e-mail: dev-help@ant.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org