Ok, thanks.

Jan

> -----Ursprüngliche Nachricht-----
> Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org]
> Gesendet: Mittwoch, 17. Mai 2017 15:37
> An: dev@ant.apache.org
> Betreff: Re: [jira] [Resolved] (IVY-1520) Have makepom task take
> description from ivy-module > info > description element
> 
> FYI, the things fixed in the master in git are marked in jira « master
> » as « fix version », so that we can just rename it when the release is
> done, wether we do a 2.5.0 or 2.4.x.
> Here we’ll indeed do a 2.5.0, but since others jira are already marked
> as on « master », I changed this one.
> 
> Nicolas
> 
> > Le 17 mai 2017 à 14:36, Jan Matèrne (JIRA) <j...@apache.org> a écrit
> :
> >
> >
> >     [
> > https://issues.apache.org/jira/browse/IVY-
> 1520?page=com.atlassian.jira
> > .plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Jan Matèrne resolved IVY-1520.
> > ------------------------------
> >       Resolution: Fixed
> >    Fix Version/s: 2.5.0-RC1
> >
> >> Have makepom task take description from ivy-module > info >
> >> description element
> >> --------------------------------------------------------------------
> -
> >> ----------
> >>
> >>                Key: IVY-1520
> >>                URL: https://issues.apache.org/jira/browse/IVY-1520
> >>            Project: Ivy
> >>         Issue Type: Improvement
> >>         Components: Ant
> >>   Affects Versions: 2.4.0
> >>           Reporter: Eric Milles
> >>           Priority: Minor
> >>            Fix For: 2.5.0-RC1
> >>
> >>
> >> I've been exploring the Ant ivy:makepom task in more detail and
> found that I can transfer the module, organisation and homepage from
> the original Ivy file but not the description.  The docs for makepom
> say that I can set property ivy.pom.description or use a description
> element.  But using either of these does not present me with a
> straightforward means of transferring the description from the resolved
> Ivy file.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.15#6346)
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> commands, e-mail: dev-h...@ant.apache.org



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

Reply via email to