Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: 2 Questions for ivyIDE
Date: Tue, 20 Mar 2012 13:51:59 -0400
Message-ID: <A859ED91E5B64A49A34C4340328BB43D73B07D@dsource.local>
In-Reply-To: <4F68BA66.9010701@writingshow.com>
Thread-Topic: 2 Questions for ivyIDE
Thread-Index: Ac0GvKq7mWudB3E+TGmtro0nxYDw3wABUcfg
References: <A859ED91E5B64A49A34C4340328BB43D73B078@dsource.local>
	<4F68BA66.9010701@writingshow.com>
From: "David Sills" <DSills@datasourceinc.com>
To: <ivy-user@ant.apache.org>

What an interesting problem. I still haven't been able to publish source
files correctly. You indicated that the file name must be

someproject-src.jar

Does "someproject" include the version number? I'm trying every
combination I can think of to get the source file (which of course I
have easily assembled) published, and nothing at all is working, with
version number or without.

Thanks for your help!

David Sills


-----Original Message-----
From: Alan Chaney [mailto:alan@writingshow.com]=20
Sent: Tuesday, March 20, 2012 1:12 PM
To: ivy-user@ant.apache.org
Subject: Re: 2 Questions for ivyIDE

Hi,

I can't comment on the first part of your answer, but I have commented
in line on the sources issue.

On 3/20/2012 9:56 AM, David Sills wrote:
> All:
>
> I love working with Eclipse and ivyIDE with 2 exceptions, and I wonder

> if I am just missing something.
>
> My environment consists of a company-wide repository, where I place=20
> the results of building my projects, and of course a local repository,

> which sometimes though not always has folders for some of the same
projects.
> As an example, let's assume that my project, say, "xxx-encryption"
> depends on "xxx-common". All is well and Ivy does well with it.
>
> However, I add some functionality to "xxx-common", up the build=20
> number, and rebuild. Great. Using Eclipse, I resolve "xxx-encryption"=20
> and it gets the correct updated value for the version number. In order

> to update the "xxx-encryption" Ivy files, I build "xxx-encryption"=20
> even though there have not been any changes to the project itself,=20
> only its dependencies. The company-wide repository's version of=20
> ivy.xml is correctly updated with the appropriate dependency on the=20
> new version of "xxx-common". However, the local repository's version
of ivy.xml is not!
> This means that when I have a third project, say "xxx-web", that=20
> depends on "xxx-encryption" and try to resolve that project, the old=20
> (now
> incorrect) version of "xxx-common" is taken, since the local=20
> repository's version is read first if it exists.
>
> What am I missing? I find myself constantly manually updating the=20
> files in the local repository in order to get the transitive=20
> dependencies right.
>
> Also, can someone explain to me why my Ivy container in ivyIDE doesn't

> allow me to put source code locations on the JARs? That would be=20
> hugely helpful in debugging, especially in a situation where I have=
 a=20
> lot of smaller projects that depend on each other and I assemble them=20
> as needed for a specific requirement. Or do I have to create source=20
> JAR files for each project using Ivy to make that happen? And will it=20
> happen if I do make source JAR files?
I don't quite understand what you mean by "source code locations on the
JARs". Its possible to publish  Ivy artifacts for sources and javadocs
(or anything else for that matter.) You need to add them to the
publications section of your Ivy module.

Also, see this thread:

http://old.nabble.com/Ivyde%2C-ivy-roundup-and-%27source%27-td33388096.h
tml

With the current released version you need to have the source and
javadocs artifacts named with a pattern like:

someproject-src.jar

or
someproject-src.zip


However, there are a lot of ivy files out there which define the sources
as source.jar or source.zip. The next release of ivyde will, hopefully,
rectify this by adding in some additional metadata.

In the mean time, if you have a corporate repository, you can simply
arrange a folder structure that complies with existing mechanism and
update your third party ivy files correspondingly. I've done this for
one client using XSLT and an ant script.

HTH

ALan


> Many thanks for anyone who can answer either or both of these
questions.
>
> David Sills
>