ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: IDEA project setup, or "Is there a standard way to deal with source and library artifacts?"
Date Wed, 21 Feb 2007 19:33:05 GMT
On 2/21/07, Blšták Peter <peter.blstak@softec.sk> wrote:
>
>
> IvyDE is able to retrieve sources jar for (classes) jar and associate them
> together automatically.
> Sources and classes have to have the same artifact name and diferent types
> (default jar, source and javadoc ... yes, javadoc is also suppose to work).
>
> Currently there is a problem with using associated sources during debug
> (at least on Eclipse 3.2). Would be nice to if someone could fix it.
>
> Does anybody (Xavier) know why associated sources are available in
> development mode and not in debug mode (in Eclipse 3.2)  ? I did not try
> older versions of Eclipse ...


No, I don't know, I don't see why there is such a difference. And I still
lack of time to investigate on this issue... sorry

Xavier

Peter
>
> ________________________________
>
> From: Gilles Scokart [mailto:gscokart@gmail.com]
> Sent: st 21. 2. 2007 10:26
> To: ivy-user@incubator.apache.org
> Subject: RE: IDEA project setup, or "Is there a standard way to deal with
> source and library artifacts?"
>
>
>
> I did that by adding the src and the javadoc artefacts into the list of
> artefacts in the ivy.xml, and I put some dedicated values in the type
> attribute ('src' and 'javadoc') in order to be able to retrieve them
> separately (for example, when I setup a path, I don't need them).
>
> Hope it help,
>
> Gilles
>
> > -----Original Message-----
> > From: Davide Baroncelli [mailto:baroncelli@yahoo.com]
> > Sent: mercredi 21 février 2007 10:14
> > To: ivy-user@incubator.apache.org
> > Subject: IDEA project setup, or "Is there a standard way to deal with
> > source and library artifacts?"
> >
> > Hello,
> > as part of our build process (which is "ivy-ized" in that every
> subproject
> > declares its dependencies and its publications through ivy) we would
> like
> > to provide some sort of standard way of not only retrieving the
> > dependencies when building, but some sort of support for retrieving not
> > only the binary dependencies but also their source and javadoc packages.
> I
> > wondered what is the best way to deal with this in ivy: it seems there
> is
> > no explicit way to declare source and javadoc artifacts, is it there?
> >
> > Thanks,
> > Davide Baroncelli.
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message