Ivy JIRA issues - how do I subscribe?

[Jaikiran Pai]

Is there a specific mailing list to where the Ivy JIRA issue 
notifications go to? I would like to subscribe to these issues and I 
can't find a way in JIRA project to send me notifications only for Ivy 
project JIRAs.



-Jaikiran

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

Re: AW: Ivy - any future or is it also going to be retired?

[Maarten Coene]

Thanks Jaikiran! :-)
I'll try to review it ...
kind regards,Maarten

  Van: Jaikiran Pai 
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 7 december 18:17 2016
 Onderwerp: Re: AW: Ivy - any future or is it also going to be retired?
   
Thank you. Given that there does seem to be willingness to do something 
to move things forward with the project, I have now submitted a PR for 
one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an 
attempt to fix it.

Over the weekend, I'll see if I can come up with a list of JIRAs which 
might be worth to be included in the proposed release (whenever next it 
happens). Of course, someone who has more knowledge about the project 
can do this and I'll happily step aside from that task.

-Jaikiran

On Wednesday 07 December 2016 08:41 PM, Jan Matèrne (jhm) wrote:
>> One thing that I think is probably is a priority (based on what I have
>> been trying to attempt while helping out with Ivy patches) is that we
>> have a central system which builds this project and runs the testsuite
>> regularly against a *nix and Windows system. Is this already available
>> in the project/Ant ecosystem somewhere? Something like a Jenkins? If
>> not, is there any other option we have to make sure we really release
>> something that is reproducible?
> Apache hosts a Jenkins instance with several slaves we could use.
> We already have some Ivy jobs:
>
> https://builds.apache.org/view/All/job/Ivy/
> Build Ivy on Ubuntu
> JDK 1.6, Ubuntu
> git: Recursively update submodules
> runs: @hourly
> run: Ant (latest)
> Target: clean jar sources
> archive: build/artifact/**
>
>
> https://builds.apache.org/view/All/job/Ivy-check/
> Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
> JDK 1.6, Ubuntu
> git: clean before checkout
> run: seems to be just run manually
> run-1: Ant (latest): findbugs checkstyle-internal
> run-2: Ant (latest): rat
> check for TODOs
>
> https://builds.apache.org/view/All/job/Ivy-tests/
> seems to be a "test-job" of mine ...
> git: clean before checkout, Recursively update submodules
> matrix: (atm only JDK1.5)
>
> https://builds.apache.org/view/All/job/Ivy-tests-matrix/
> run tests
> triggerd by stable "Ivy" job
> git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
> clean test-report
>
>
>
> Jan
>
>
>
> -
> 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



   

Re: VOTE Retire IvyDE

[Gintautas Grigelionis]

I decided to take a quick look at the build process and it's not broken per
se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32. I would like to
make the process to adapt to the build platform. Any suggestions for a
reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or
maybe even 4.5.2).
​
Gintas

Re: AW: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

Thank you. Given that there does seem to be willingness to do something 
to move things forward with the project, I have now submitted a PR for 
one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an 
attempt to fix it.


Over the weekend, I'll see if I can come up with a list of JIRAs which 
might be worth to be included in the proposed release (whenever next it 
happens). Of course, someone who has more knowledge about the project 
can do this and I'll happily step aside from that task.


-Jaikiran

On Wednesday 07 December 2016 08:41 PM, Jan Matèrne (jhm) wrote:

One thing that I think is probably is a priority (based on what I have
been trying to attempt while helping out with Ivy patches) is that we
have a central system which builds this project and runs the testsuite
regularly against a *nix and Windows system. Is this already available
in the project/Ant ecosystem somewhere? Something like a Jenkins? If
not, is there any other option we have to make sure we really release
something that is reproducible?

Apache hosts a Jenkins instance with several slaves we could use.
We already have some Ivy jobs:

https://builds.apache.org/view/All/job/Ivy/
Build Ivy on Ubuntu
JDK 1.6, Ubuntu
git: Recursively update submodules
runs: @hourly
run: Ant (latest)
Target: clean jar sources
archive: build/artifact/**


https://builds.apache.org/view/All/job/Ivy-check/
Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
JDK 1.6, Ubuntu
git: clean before checkout
run: seems to be just run manually
run-1: Ant (latest): findbugs checkstyle-internal
run-2: Ant (latest): rat
check for TODOs

https://builds.apache.org/view/All/job/Ivy-tests/
seems to be a "test-job" of mine ...
git: clean before checkout, Recursively update submodules
matrix: (atm only JDK1.5)

https://builds.apache.org/view/All/job/Ivy-tests-matrix/
run tests
triggerd by stable "Ivy" job
git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
clean test-report



Jan



-
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

[GitHub] ant-ivy pull request #10: Fix for IVY-1531

[jaikiran]

GitHub user jaikiran opened a pull request:

https://github.com/apache/ant-ivy/pull/10

Fix for IVY-1531

The commit here contains a potential fix for the issue reported in 
https://issues.apache.org/jira/browse/IVY-1531.

Maven pom.xml allows dependency exclusion to include groupid=* and 
artifactid=* in the exclusion, which technically translates to transitive = 
false in Ivy world. The commit here handles that explicitly so that it doesn't 
lead to a ivy.xml (generated off pom.xml) to have something like:

   

which effectively excludes the dependency which has this exclusion (as 
noted in that JIRA).

The change in this commit now generates the ivy.xml as follows for such 
exclusions in pom.xml:

   

(notice the transitive=false in there)

This commit also includes a test which verifies this change.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaikiran/ant-ivy ivy-1531

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #10


commit d3b8e1906c7f33b089824a4e6f71cc98d38dc369
Author: Jaikiran Pai 
Date:   2016-12-07T16:43:38Z

IVY-1531 Fix translation of * for groupid and artifactid, in pom.xml 
exclusion, for implying transitive=false in ivy

modified:   
src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java
new file:   test/java/org/apache/ivy/core/makepom/MakePomTest.java
modified:   
test/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParserTest.java
modified:   
test/java/org/apache/ivy/plugins/parser/m2/test-exclusion.pom




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

AW: Ivy - any future or is it also going to be retired?

[jhm]

> One thing that I think is probably is a priority (based on what I have
> been trying to attempt while helping out with Ivy patches) is that we
> have a central system which builds this project and runs the testsuite
> regularly against a *nix and Windows system. Is this already available
> in the project/Ant ecosystem somewhere? Something like a Jenkins? If
> not, is there any other option we have to make sure we really release
> something that is reproducible?

Apache hosts a Jenkins instance with several slaves we could use.
We already have some Ivy jobs:

https://builds.apache.org/view/All/job/Ivy/
Build Ivy on Ubuntu
JDK 1.6, Ubuntu
git: Recursively update submodules
runs: @hourly
run: Ant (latest) 
Target: clean jar sources
archive: build/artifact/**


https://builds.apache.org/view/All/job/Ivy-check/
Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
JDK 1.6, Ubuntu
git: clean before checkout
run: seems to be just run manually
run-1: Ant (latest): findbugs checkstyle-internal
run-2: Ant (latest): rat
check for TODOs

https://builds.apache.org/view/All/job/Ivy-tests/
seems to be a "test-job" of mine ...
git: clean before checkout, Recursively update submodules
matrix: (atm only JDK1.5)

https://builds.apache.org/view/All/job/Ivy-tests-matrix/
run tests
triggerd by stable "Ivy" job
git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
clean test-report



Jan



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

Re: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

+1. Nicolas' mail has some precise things that need to be done. I am 
willing to help out wherever possible on those steps. I think the first 
thing to release probably should be a 2.4.1-Beta-1 just to iron out any 
process and other issues in itself and explicitly tag it as a beta so as 
to maintain the right expectations.


One thing that I think is probably is a priority (based on what I have 
been trying to attempt while helping out with Ivy patches) is that we 
have a central system which builds this project and runs the testsuite 
regularly against a *nix and Windows system. Is this already available 
in the project/Ant ecosystem somewhere? Something like a Jenkins? If 
not, is there any other option we have to make sure we really release  
something that is reproducible?


-Jaikiran

On Wednesday 07 December 2016 05:36 PM, Oulds, Jonathan wrote:

Nicolas raises some great ideas,

I would suggest that we get those into Jira and try to cut a release from the 
current code (just to test the release process).  If that works let's try to 
address one or two simple to fix issues (just to give the release some value) 
and push out 2.4.1.

If there is enough interest we can start implementing some bigger features and 
plan for a 2.5 release next year.



Jonathan Oulds
Snr. Software Engineer
McAfee

-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: Wednesday, December 7, 2016 10:56 AM
To: dev@ant.apache.org
Subject: Re: Ivy - any future or is it also going to be retired?

On 2016-12-06, Nicolas Lalevée wrote:


These are just ideas poping up my mind to show that if people are
enough motivated, they can make things happen. And obviously, if
things work well, credentials will be granted.

Yes, of course.


I think this is the same for IvyDE, but it requires much more effort
because the build is broken since we migrated to git, and so the
release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can 
certainly (partially) revert it. Nobody says we need to use the same scm for 
all subprojects of Ant.

Stefan

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

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-
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

Re: VOTE Retire IvyDE

[Nicolas Lalevée]

> Le 7 déc. 2016 à 12:34, Gintautas Grigelionis  a 
> écrit :
> 
> I would prefer an agreement on status. IvyDE is dependent on Ivy and
> ideally their release cycles should be synced.
> Since there seem to be some changes brewing in Ivy, IvyDE could be used as
> a test case.

Actually there is no need for synchronization between both project, unless 
there is a new feature in Ivy required for IvyDE. In the Eclipse updatesite 
there are two separate « Eclipse features », and one is dedicated to the 
version of Ivy you want to install.

Nicolas


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

RE: Ivy - any future or is it also going to be retired?

[Oulds, Jonathan]

Nicolas raises some great ideas,

I would suggest that we get those into Jira and try to cut a release from the 
current code (just to test the release process).  If that works let's try to 
address one or two simple to fix issues (just to give the release some value) 
and push out 2.4.1.

If there is enough interest we can start implementing some bigger features and 
plan for a 2.5 release next year.



Jonathan Oulds
Snr. Software Engineer
McAfee

-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org] 
Sent: Wednesday, December 7, 2016 10:56 AM
To: dev@ant.apache.org
Subject: Re: Ivy - any future or is it also going to be retired?

On 2016-12-06, Nicolas Lalevée wrote:

> These are just ideas poping up my mind to show that if people are 
> enough motivated, they can make things happen. And obviously, if 
> things work well, credentials will be granted.

Yes, of course.

> I think this is the same for IvyDE, but it requires much more effort 
> because the build is broken since we migrated to git, and so the 
> release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can 
certainly (partially) revert it. Nobody says we need to use the same scm for 
all subprojects of Ant.

Stefan

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

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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

Re: VOTE Retire IvyDE

[Gintautas Grigelionis]

I would prefer an agreement on status. IvyDE is dependent on Ivy and
ideally their release cycles should be synced.
Since there seem to be some changes brewing in Ivy, IvyDE could be used as
a test case.

Gintas

2016-12-07 11:37 GMT+01:00 Stefan Bodewig :

> On 2016-12-07, Gintautas Grigelionis wrote:
>
> > Somebody mentioned that IvyDE build process is broken and I would like to
> > look into that if it could help to prevent retirement.
>
> That would be wonderful, regardless of whether it prevents retirement.
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Ivy - any future or is it also going to be retired?

[Stefan Bodewig]

On 2016-12-06, Nicolas Lalevée wrote:

> These are just ideas poping up my mind to show that if people are
> enough motivated, they can make things happen. And obviously, if
> things work well, credentials will be granted.

Yes, of course.

> I think this is the same for IvyDE, but it requires much more effort
> because the build is broken since we migrated to git, and so the
> release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can
certainly (partially) revert it. Nobody says we need to use the same scm
for all subprojects of Ant.

Stefan

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

Re: VOTE Retire IvyDE

[Stefan Bodewig]

On 2016-12-07, Gintautas Grigelionis wrote:

> Somebody mentioned that IvyDE build process is broken and I would like to
> look into that if it could help to prevent retirement.

That would be wonderful, regardless of whether it prevents retirement.

Stefan

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

Re: VOTE Retire IvyDE

[Gintautas Grigelionis]

Somebody mentioned that IvyDE build process is broken and I would like to
look into that if it could help to prevent retirement.

Gintas

2016-12-07 10:00 GMT+01:00 Dominique Devienne :

> +1
>
> On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
> jeanlouis.boud...@gmail.com> wrote:
>
> > +1
> >
> > Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée"  a
> > écrit :
> >
> > > +1
> > >
> > > Nicolas
> > >
> > > > Le 6 déc. 2016 à 17:22, Stefan Bodewig  a écrit
> :
> > > >
> > > > On 2016-12-05, Jan Matèrne (jhm) wrote:
> > > >
> > > >> I start a vote for retiring IvyDE.
> > > >
> > > > +0
> > > >
> > > > The discussion in the "Ivy" thread makes me think we'd probably want
> to
> > > > update it with new Ivy releases, even if nothing else changes in
> > > > between.
> > > >
> > > > Stefan
> > > >
> > > > 
> -
> > > > 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
> > >
> > >
> >
>

Re: VOTE Retire IvyDE

[Dominique Devienne]

+1

On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
jeanlouis.boud...@gmail.com> wrote:

> +1
>
> Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée"  a
> écrit :
>
> > +1
> >
> > Nicolas
> >
> > > Le 6 déc. 2016 à 17:22, Stefan Bodewig  a écrit :
> > >
> > > On 2016-12-05, Jan Matèrne (jhm) wrote:
> > >
> > >> I start a vote for retiring IvyDE.
> > >
> > > +0
> > >
> > > The discussion in the "Ivy" thread makes me think we'd probably want to
> > > update it with new Ivy releases, even if nothing else changes in
> > > between.
> > >
> > > Stefan
> > >
> > > -
> > > 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
> >
> >
>

Re: VOTE Retire EasyAnt subproject

[Dominique Devienne]

+1

On Wed, Dec 7, 2016 at 8:14 AM, Jean-Louis Boudart <
jeanlouis.boud...@gmail.com> wrote:

> +1
>
> 2016-12-07 1:05 GMT+01:00 Conor MacNeill :
>
> > +1
> >
> > Conor
> >
> >
> > On 5 December 2016 at 18:04, Jan Matèrne (jhm) 
> wrote:
> > > I start a vote for retiring EasyAnt and all its components:
> > >
> > > - core
> > >
> > > - buildtypes
> > >
> > > - plugins
> > >
> > > - skeletons
> > >
> > > - tasks
> > >
> > > - easyant4e
> > >
> > >
> > >
> > > We never had a real release after the incubator.
> > >
> > > The last 'real' activity in vcs was in 09/2015 for EA-Core and 07/2013
> > for
> > > EA4E.
> > >
> > >
> > >
> > > It seems that we havent the community, committers and PMC to hold this
> > > subproject.
> > >
> > >
> > >
> > > The general procedure is described in http://ant.apache.org/
> > processes.html.
> > >
> > >
> > >
> > >
> > >
> > > I start with my +1.
> > >
> > >
> > >
> > >
> > >
> > > Jan
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > For additional commands, e-mail: dev-h...@ant.apache.org
> >
> >
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://ant.apache.org/easyant/
>