You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Xavier Hanin <xa...@gmail.com> on 2007/05/14 10:24:23 UTC
Use of deprecated elements in ivysettings.xml
I would like to discuss the update of the ivysettings we use for building
Ivy.
As Jan reported (and fixed with a patch, thanks Jan!), we are still using
the old tag names in our settings, resulting in deprecration warning while
we build Ivy from ant. Updating the settings seems pretty obvious, but there
is an issue for people developing Ivy using eclipse and IvyDE 1.2.0, which
internally uses Ivy 1.4.1 for its dependency resolution. Note that this is
the default configuration for people using eclipse, since the .classpath is
in svn declares the ivyde container.
So I see several options:
1) keep things like that for the moment
2) update the settings, and
2.1) use another settings file (maybe referring to the first, since Ivy
doesn't do much verification on settings files) for IvyDE
2.2) update the .classpath to use the latest IvyDE version which works with
latest Ivy version (not released yet, with no update site)
2.3) update the .classpath to use lib/* files resolved by a previous ant
call
I'm in favor of the 2.2 option, mainly because I already have a latest IvyDE
version installed in my eclipse install :-)
Opinions?
Xavier
On 5/14/07, Jan Matèrne (JIRA) <ji...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/IVY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Jan Matèrne updated IVY-505:
> ----------------------------
>
> Attachment: ivysettings.xml.patch
>
> Patch for renaming the deprecated elements.
>
> > Use of deprecated elements in ivysettings.xml
> > ---------------------------------------------
> >
> > Key: IVY-505
> > URL: https://issues.apache.org/jira/browse/IVY-505
> > Project: Ivy
> > Issue Type: Improvement
> > Components: Core
> > Reporter: Jan Matèrne
> > Priority: Trivial
> > Attachments: ivysettings.xml.patch
> >
> >
> > init-ivy:
> > [ivy:configure] :: loading settings :: file =
> C:\ant\svn-repository\ivy\core\ivysettings.xml
> > [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use
> 'ivysettings' instead (file:/C:/ant/svn-repository/ivy/core/ivysettings.xml)
> > [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings' instead
> (file:/C:/ant/svn-repository/ivy/core/ivysettings.xml)
> > change the elements to their new names
> > see: https://issues.apache.org/jira/browse/IVY-438
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
Re: Use of deprecated elements in ivysettings.xml
Posted by Xavier Hanin <xa...@gmail.com>.
Maarten, any opinion about this?
On 5/14/07, Gilles Scokart <gs...@gmail.com> wrote:
>
> +0 to any of the solution. As I don't use ivyDE (yet), I'm already in the
> case 2.3
>
> Gilles
>
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: lundi 14 mai 2007 12:24
> > To: ivy-dev@incubator.apache.org
> > Subject: Use of deprecated elements in ivysettings.xml
> >
> > I would like to discuss the update of the ivysettings we use for
> building
> > Ivy.
> >
> > As Jan reported (and fixed with a patch, thanks Jan!), we are still
> using
> > the old tag names in our settings, resulting in deprecration warning
> while
> > we build Ivy from ant. Updating the settings seems pretty obvious, but
> > there
> > is an issue for people developing Ivy using eclipse and IvyDE 1.2.0,
> which
> > internally uses Ivy 1.4.1 for its dependency resolution. Note that this
> is
> > the default configuration for people using eclipse, since the .classpath
> > is
> > in svn declares the ivyde container.
> >
> > So I see several options:
> > 1) keep things like that for the moment
> > 2) update the settings, and
> > 2.1) use another settings file (maybe referring to the first, since Ivy
> > doesn't do much verification on settings files) for IvyDE
> > 2.2) update the .classpath to use the latest IvyDE version which works
> > with
> > latest Ivy version (not released yet, with no update site)
> > 2.3) update the .classpath to use lib/* files resolved by a previous ant
> > call
> >
> > I'm in favor of the 2.2 option, mainly because I already have a latest
> > IvyDE
> > version installed in my eclipse install :-)
> > Opinions?
> >
> > Xavier
> >
> > On 5/14/07, Jan Matèrne (JIRA) <ji...@apache.org> wrote:
> > >
> > >
> > > [
> > > https://issues.apache.org/jira/browse/IVY-
> > 505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> > >
> > > Jan Matèrne updated IVY-505:
> > > ----------------------------
> > >
> > > Attachment: ivysettings.xml.patch
> > >
> > > Patch for renaming the deprecated elements.
> > >
> > > > Use of deprecated elements in ivysettings.xml
> > > > ---------------------------------------------
> > > >
> > > > Key: IVY-505
> > > > URL: https://issues.apache.org/jira/browse/IVY-505
> > > > Project: Ivy
> > > > Issue Type: Improvement
> > > > Components: Core
> > > > Reporter: Jan Matèrne
> > > > Priority: Trivial
> > > > Attachments: ivysettings.xml.patch
> > > >
> > > >
> > > > init-ivy:
> > > > [ivy:configure] :: loading settings :: file =
> > > C:\ant\svn-repository\ivy\core\ivysettings.xml
> > > > [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use
> > > 'ivysettings' instead (file:/C:/ant/svn-
> > repository/ivy/core/ivysettings.xml)
> > > > [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings'
> > instead
> > > (file:/C:/ant/svn-repository/ivy/core/ivysettings.xml)
> > > > change the elements to their new names
> > > > see: https://issues.apache.org/jira/browse/IVY-438
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > Manage your dependencies with Ivy!
> > http://incubator.apache.org/ivy/
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
RE: Use of deprecated elements in ivysettings.xml
Posted by Gilles Scokart <gs...@gmail.com>.
+0 to any of the solution. As I don't use ivyDE (yet), I'm already in the
case 2.3
Gilles
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: lundi 14 mai 2007 12:24
> To: ivy-dev@incubator.apache.org
> Subject: Use of deprecated elements in ivysettings.xml
>
> I would like to discuss the update of the ivysettings we use for building
> Ivy.
>
> As Jan reported (and fixed with a patch, thanks Jan!), we are still using
> the old tag names in our settings, resulting in deprecration warning while
> we build Ivy from ant. Updating the settings seems pretty obvious, but
> there
> is an issue for people developing Ivy using eclipse and IvyDE 1.2.0, which
> internally uses Ivy 1.4.1 for its dependency resolution. Note that this is
> the default configuration for people using eclipse, since the .classpath
> is
> in svn declares the ivyde container.
>
> So I see several options:
> 1) keep things like that for the moment
> 2) update the settings, and
> 2.1) use another settings file (maybe referring to the first, since Ivy
> doesn't do much verification on settings files) for IvyDE
> 2.2) update the .classpath to use the latest IvyDE version which works
> with
> latest Ivy version (not released yet, with no update site)
> 2.3) update the .classpath to use lib/* files resolved by a previous ant
> call
>
> I'm in favor of the 2.2 option, mainly because I already have a latest
> IvyDE
> version installed in my eclipse install :-)
> Opinions?
>
> Xavier
>
> On 5/14/07, Jan Matèrne (JIRA) <ji...@apache.org> wrote:
> >
> >
> > [
> > https://issues.apache.org/jira/browse/IVY-
> 505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Jan Matèrne updated IVY-505:
> > ----------------------------
> >
> > Attachment: ivysettings.xml.patch
> >
> > Patch for renaming the deprecated elements.
> >
> > > Use of deprecated elements in ivysettings.xml
> > > ---------------------------------------------
> > >
> > > Key: IVY-505
> > > URL: https://issues.apache.org/jira/browse/IVY-505
> > > Project: Ivy
> > > Issue Type: Improvement
> > > Components: Core
> > > Reporter: Jan Matèrne
> > > Priority: Trivial
> > > Attachments: ivysettings.xml.patch
> > >
> > >
> > > init-ivy:
> > > [ivy:configure] :: loading settings :: file =
> > C:\ant\svn-repository\ivy\core\ivysettings.xml
> > > [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use
> > 'ivysettings' instead (file:/C:/ant/svn-
> repository/ivy/core/ivysettings.xml)
> > > [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings'
> instead
> > (file:/C:/ant/svn-repository/ivy/core/ivysettings.xml)
> > > change the elements to their new names
> > > see: https://issues.apache.org/jira/browse/IVY-438
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant
> Manage your dependencies with Ivy!
> http://incubator.apache.org/ivy/