You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Jaikiran Pai <ja...@gmail.com> on 2018/06/25 05:52:47 UTC
[VOTE] Release 2.3.0-rc1 of Apache IvyDE
I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
project. This addresses the blocker issue that Nicolas identified, the
last time a vote was initiated for this version.
The newly updated tag is here
https://git-wip-us.apache.org/repos/asf?p=ant-ivyde.git;a=tag;h=refs/tags/2.3.0-rc1
with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
You can download the distribution from this URL:
https://dist.apache.org/repos/dist/dev/ant/ivyde/2.3.0-rc1/ at rev 27709
The Eclipse p2 repository is here:
https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivyde-2.3.0.rc1-201806251008-RELEASE/
at rev 27707
The 2.3.0-rc1 release of IvyDE consists of the following changes:
* FIX: xml bomb in workspace causes hang in Ivy code during Search or
Synchronize operations (https://issues.apache.org/jira/browse/IVYDE-354)
* FIX: Deadlock in classpath container
(https://issues.apache.org/jira/browse/IVYDE-361)
* FIX: Typo in IvyResolveJob
(https://issues.apache.org/jira/browse/IVYDE-362)
* FIX: User-selected configurations not checked in the viewer
(https://issues.apache.org/jira/browse/IVYDE-378)
* FIX: Fix ClassCastException
(https://issues.apache.org/jira/browse/IVYDE-386)
* FIX: Fix the issue where the IvyDE preferences couldn't be saved
(https://issues.apache.org/jira/browse/IVYDE-388)
* NEW: Support for OSGi 'Bundle-Classpath' directive
* NEW: Basic support for the workspace resolver to find OSGi bundles
managed by Ivy in the workspace
* NEW: Support for storing credentials securely
Do you vote for the release of these binaries?
-Jaikiran
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Stefan Bodewig <bo...@apache.org>.
On 2018-06-25, Jaikiran Pai wrote:
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
> project. This addresses the blocker issue that Nicolas identified, the
> last time a vote was initiated for this version.
As usual I've only checked the source archive matches the tag, all sigs
and hashes are good and the legal stuff is fine.
+1
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
[CANCELLED]Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
This vote is now officially cancelledfor the reasons noted below.
-Jaikiran
On 28/06/18 12:11 PM, Jaikiran Pai wrote:
>
> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>> Since there is a work around (hitting refresh after resolve) and it
>> is an RC, we could ship it like that and fix it later. But due to the
>> automatic update via the update site, I bet most users will update
>> even if it is an RC. So I am not sure what I should vote. So I vote
>> -0 for me for now.
> I was reserving my vote just for this reason. I don't use Eclipse so I
> wanted to see if someone more familiar with it has an opinion about
> this bug. You are right that it's going to end up affecting everyone
> once we release this. Given that the purpose of this release is revive
> this project a bit and not break setups where things are working fine
> and the fact that this will end up being an annoying kind of
> workaround (having to hit refresh after resolve), I don't see rushing
> this release without fixing this issue serves any purpose.
>
> So I'll vote a -1 on this now. I know we have gone through 3 voting
> rounds for this release, so thank you everyone for being patient and
> testing out the binaries. I'll file this issue in JIRA and hopefully
> spend some time in Eclipse this weekend to try and sort this out.
>
> -Jaikiran
>
>
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by rc...@e1b.org.
I think canceling was the right decision. Maybe something new in the
code is cutting short whatever is happening at the end of the
Ivy->Refresh? Hopefully someone will figure out the eclipse problem
soon. I've have no experience programming eclipse plugins, or I would
look at this myself.
Ross
From: "Jaikiran Pai" <ja...@gmail.com>
To: ivy-user@ant.apache.org, "Ant Developers List"
<de...@ant.apache.org>,
Date: 06/28/2018 02:41 AM
Subject: Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
> Since there is a work around (hitting refresh after resolve) and it is
> an RC, we could ship it like that and fix it later. But due to the
> automatic update via the update site, I bet most users will update
> even if it is an RC. So I am not sure what I should vote. So I vote -0
> for me for now.
I was reserving my vote just for this reason. I don't use Eclipse so I
wanted to see if someone more familiar with it has an opinion about this
bug. You are right that it's going to end up affecting everyone once we
release this. Given that the purpose of this release is revive this
project a bit and not break setups where things are working fine and the
fact that this will end up being an annoying kind of workaround (having
to hit refresh after resolve), I don't see rushing this release without
fixing this issue serves any purpose.
So I'll vote a -1 on this now. I know we have gone through 3 voting
rounds for this release, so thank you everyone for being patient and
testing out the binaries. I'll file this issue in JIRA and hopefully
spend some time in Eclipse this weekend to try and sort this out.
-Jaikiran
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 04W46FSTR) is spam:
Spam:
https://milton-web.wnyric.org/canit/b.php?c=s&i=04W46FSTR&m=4337cae36d64&t=20180628
Not spam:
https://milton-web.wnyric.org/canit/b.php?c=n&i=04W46FSTR&m=4337cae36d64&t=20180628
Forget vote:
https://milton-web.wnyric.org/canit/b.php?c=f&i=04W46FSTR&m=4337cae36d64&t=20180628
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.
[CANCELLED]Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
This vote is now officially cancelledfor the reasons noted below.
-Jaikiran
On 28/06/18 12:11 PM, Jaikiran Pai wrote:
>
> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>> Since there is a work around (hitting refresh after resolve) and it
>> is an RC, we could ship it like that and fix it later. But due to the
>> automatic update via the update site, I bet most users will update
>> even if it is an RC. So I am not sure what I should vote. So I vote
>> -0 for me for now.
> I was reserving my vote just for this reason. I don't use Eclipse so I
> wanted to see if someone more familiar with it has an opinion about
> this bug. You are right that it's going to end up affecting everyone
> once we release this. Given that the purpose of this release is revive
> this project a bit and not break setups where things are working fine
> and the fact that this will end up being an annoying kind of
> workaround (having to hit refresh after resolve), I don't see rushing
> this release without fixing this issue serves any purpose.
>
> So I'll vote a -1 on this now. I know we have gone through 3 voting
> rounds for this release, so thank you everyone for being patient and
> testing out the binaries. I'll file this issue in JIRA and hopefully
> spend some time in Eclipse this weekend to try and sort this out.
>
> -Jaikiran
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: Testing IvyDE
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
Due the update the permission for cancelling a job is gone.
https://jenkins.io/changelog-stable/
Notable changes since 2.107.3:
* It is no longer possible to rename jobs from their configuration page. Jobs now have a link in the side panel titled "Rename" that links to a page specifically dedicated to renaming jobs.
* The Job/Build permission no longer implies the Job/Cancel permission. The latter needs to be granted explicitly to users who previously got it via this relationship.
...
I'll check how we get that permission back (global grant by admin, posting a list via mail, jira...)
Jan
> -----Ursprüngliche Nachricht-----
> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
> Gesendet: Sonntag, 1. Juli 2018 21:30
> An: 'Ant Developers List'
> Betreff: AW: Testing IvyDE
>
> > It looks like Ant nightly is stuck (possibly due to plugin update in
> > Jenkins) and it's blocking all other builds.
> >
> > Gintas
>
> I can't do it myself so I'll ask for killing the job.
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Testing IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
On Sun, 1 Jul 2018 at 21:30, Jan Matèrne (jhm) <ap...@materne.de> wrote:
> > It looks like Ant nightly is stuck (possibly due to plugin update in
> > Jenkins) and it's blocking all other builds.
> >
> > Gintas
>
> I can't do it myself so I'll ask for killing the job.
>
> Jan
>
Ant nightly aborted, now IvyDE is stuck near artifact archiving...
Besides, IvyDE build could not find WTP 3.4.2, and the archive page at
http://archive.eclipse.org/webtools/downloads/
seems to be broken. Strangely, the patch drop
http://download.eclipse.org/webtools/patches/drops/R3.4.2/P-3.4.2-20130826221819/
is available...
Gintas
AW: Testing IvyDE
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> It looks like Ant nightly is stuck (possibly due to plugin update in
> Jenkins) and it's blocking all other builds.
>
> Gintas
I can't do it myself so I'll ask for killing the job.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Testing IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
It looks like Ant nightly is stuck (possibly due to plugin update in
Jenkins) and it's blocking all other builds.
Gintas
Re: Testing IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
On Sun, 1 Jul 2018 at 15:05, Nicolas Lalevée <ni...@hibnet.org>
wrote:
> I have found the issue and pushed a fix.
>
> I am then worried that the master is not well tested nor used after the
> big cleanups. Two big bugs were raised during the release process.
>
> So I suggest we do a little testing now of the master.
>
> To help with that, there is a folder in the IvyDE project which contains
> projects ready to be imported into Eclipse, they are samples of many
> different configurations which should be supported:
> https://github.com/apache/ant-ivyde/tree/master/test <
> https://github.com/apache/ant-ivyde/tree/master/test>
> And the last build can be installed from an update site built there:
> https://builds.apache.org/view/A/view/Ant/job/IvyDE-updatesite/ <
> https://builds.apache.org/view/A/view/Ant/job/IvyDE-updatesite/>
>
> Nicolas
>
The nightly build is still pending...
Gintas
Re: Testing IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
So the crash of Eclipse occurs also with Java 8. But I have managed to make it crash with other kind of Eclipse console, so this is probably not related to IvyDE.
While testing I have found a little bug, some context menu doing nothing, most probably not a regression. Still, I have fixed it in master.
And I have fixed some test projects.
It would be great if somebody could do some testing on Windows, since I tested on MacOS.
Then for me it is all good.
Nicolas
PS: since now I am mainly using Intellij, it was a bit of pain to get back into Eclipse. But this was a joy to use IvyDE, which is way better integrated than IvyIDEA :)
> Le 15 juil. 2018 à 21:06, Nicolas Lalevée <ni...@hibnet.org> a écrit :
>
> I have fixed the build, now relying on more recent dependencies. The updatesite built by Jenkins is now up to date.
>
> I have started to do some test, but there are some crashes, the jvm of Eclipse is crashing on clearing the Ivy console for instance. I bet this is more due to the fact that I am running with Java 10. I’ll try to run it with a lower Java version and redo the tests.
>
> Nicolas
>
>> Le 4 juil. 2018 à 14:01, Jaikiran Pai <ja...@gmail.com> a écrit :
>>
>>
>> On 01/07/18 6:35 PM, Nicolas Lalevée wrote:
>>> Le 28 juin 2018 à 08:41, Jaikiran Pai <ja...@gmail.com> a écrit :
>>>>
>>>> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>>>>> Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC. So I am not sure what I should vote. So I vote -0 for me for now.
>>>> I was reserving my vote just for this reason. I don't use Eclipse so I wanted to see if someone more familiar with it has an opinion about this bug. You are right that it's going to end up affecting everyone once we release this. Given that the purpose of this release is revive this project a bit and not break setups where things are working fine and the fact that this will end up being an annoying kind of workaround (having to hit refresh after resolve), I don't see rushing this release without fixing this issue serves any purpose.
>>>>
>>>> So I'll vote a -1 on this now. I know we have gone through 3 voting rounds for this release, so thank you everyone for being patient and testing out the binaries. I'll file this issue in JIRA and hopefully spend some time in Eclipse this weekend to try and sort this out.
>>> I have found the issue and pushed a fix.
>> Thank you.
>>>
>>> I am then worried that the master is not well tested nor used after the big cleanups.
>> Yes, I agree.
>>
>>>
>>> So I suggest we do a little testing now of the master.
>>>
>>> To help with that, there is a folder in the IvyDE project which contains projects ready to be imported into Eclipse, they are samples of many different configurations which should be supported
>> I'll test some of these out during the week.
>>
>> -Jaikiran
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Testing IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I have fixed the build, now relying on more recent dependencies. The updatesite built by Jenkins is now up to date.
I have started to do some test, but there are some crashes, the jvm of Eclipse is crashing on clearing the Ivy console for instance. I bet this is more due to the fact that I am running with Java 10. I’ll try to run it with a lower Java version and redo the tests.
Nicolas
> Le 4 juil. 2018 à 14:01, Jaikiran Pai <ja...@gmail.com> a écrit :
>
>
> On 01/07/18 6:35 PM, Nicolas Lalevée wrote:
>> Le 28 juin 2018 à 08:41, Jaikiran Pai <ja...@gmail.com> a écrit :
>>>
>>> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>>>> Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC. So I am not sure what I should vote. So I vote -0 for me for now.
>>> I was reserving my vote just for this reason. I don't use Eclipse so I wanted to see if someone more familiar with it has an opinion about this bug. You are right that it's going to end up affecting everyone once we release this. Given that the purpose of this release is revive this project a bit and not break setups where things are working fine and the fact that this will end up being an annoying kind of workaround (having to hit refresh after resolve), I don't see rushing this release without fixing this issue serves any purpose.
>>>
>>> So I'll vote a -1 on this now. I know we have gone through 3 voting rounds for this release, so thank you everyone for being patient and testing out the binaries. I'll file this issue in JIRA and hopefully spend some time in Eclipse this weekend to try and sort this out.
>> I have found the issue and pushed a fix.
> Thank you.
>>
>> I am then worried that the master is not well tested nor used after the big cleanups.
> Yes, I agree.
>
>>
>> So I suggest we do a little testing now of the master.
>>
>> To help with that, there is a folder in the IvyDE project which contains projects ready to be imported into Eclipse, they are samples of many different configurations which should be supported
> I'll test some of these out during the week.
>
> -Jaikiran
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Testing IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
On 01/07/18 6:35 PM, Nicolas Lalevée wrote:
> Le 28 juin 2018 à 08:41, Jaikiran Pai <ja...@gmail.com> a écrit :
>>
>> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>>> Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC. So I am not sure what I should vote. So I vote -0 for me for now.
>> I was reserving my vote just for this reason. I don't use Eclipse so I wanted to see if someone more familiar with it has an opinion about this bug. You are right that it's going to end up affecting everyone once we release this. Given that the purpose of this release is revive this project a bit and not break setups where things are working fine and the fact that this will end up being an annoying kind of workaround (having to hit refresh after resolve), I don't see rushing this release without fixing this issue serves any purpose.
>>
>> So I'll vote a -1 on this now. I know we have gone through 3 voting rounds for this release, so thank you everyone for being patient and testing out the binaries. I'll file this issue in JIRA and hopefully spend some time in Eclipse this weekend to try and sort this out.
> I have found the issue and pushed a fix.
Thank you.
>
> I am then worried that the master is not well tested nor used after the big cleanups.
Yes, I agree.
>
> So I suggest we do a little testing now of the master.
>
> To help with that, there is a folder in the IvyDE project which contains projects ready to be imported into Eclipse, they are samples of many different configurations which should be supported
I'll test some of these out during the week.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Testing IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 28 juin 2018 à 08:41, Jaikiran Pai <ja...@gmail.com> a écrit :
>
>
> On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
>> Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC. So I am not sure what I should vote. So I vote -0 for me for now.
> I was reserving my vote just for this reason. I don't use Eclipse so I wanted to see if someone more familiar with it has an opinion about this bug. You are right that it's going to end up affecting everyone once we release this. Given that the purpose of this release is revive this project a bit and not break setups where things are working fine and the fact that this will end up being an annoying kind of workaround (having to hit refresh after resolve), I don't see rushing this release without fixing this issue serves any purpose.
>
> So I'll vote a -1 on this now. I know we have gone through 3 voting rounds for this release, so thank you everyone for being patient and testing out the binaries. I'll file this issue in JIRA and hopefully spend some time in Eclipse this weekend to try and sort this out.
I have found the issue and pushed a fix.
I am then worried that the master is not well tested nor used after the big cleanups. Two big bugs were raised during the release process.
So I suggest we do a little testing now of the master.
To help with that, there is a folder in the IvyDE project which contains projects ready to be imported into Eclipse, they are samples of many different configurations which should be supported:
https://github.com/apache/ant-ivyde/tree/master/test <https://github.com/apache/ant-ivyde/tree/master/test>
And the last build can be installed from an update site built there:
https://builds.apache.org/view/A/view/Ant/job/IvyDE-updatesite/ <https://builds.apache.org/view/A/view/Ant/job/IvyDE-updatesite/>
Nicolas
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
> Since there is a work around (hitting refresh after resolve) and it is
> an RC, we could ship it like that and fix it later. But due to the
> automatic update via the update site, I bet most users will update
> even if it is an RC. So I am not sure what I should vote. So I vote -0
> for me for now.
I was reserving my vote just for this reason. I don't use Eclipse so I
wanted to see if someone more familiar with it has an opinion about this
bug. You are right that it's going to end up affecting everyone once we
release this. Given that the purpose of this release is revive this
project a bit and not break setups where things are working fine and the
fact that this will end up being an annoying kind of workaround (having
to hit refresh after resolve), I don't see rushing this release without
fixing this issue serves any purpose.
So I'll vote a -1 on this now. I know we have gone through 3 voting
rounds for this release, so thank you everyone for being patient and
testing out the binaries. I'll file this issue in JIRA and hopefully
spend some time in Eclipse this weekend to try and sort this out.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
Who's Ross? :-S
For me, "reload" is resulting in an empty container, and the contents are
updated by subsequent "refresh".
Codewise, "reload" does
container.reloadSettings()
which is the same as
state.setIvySettingsLastModified(-1);
launchResolve(false, null);
(and the last line is the same as "resolve") vs
container.launchResolve(true, null);
I don't think that code was modified a lot; AFAICS, there are two changes
made in code of IvyClasspathContainerImpl:
first, generics in Comparator in setClassPath() entries; then, path was
made final.
Before that, there's a javadoc fix and a fix for IVYDE-361.
If there's something suspicious, then it's path being final.
Gintas
On Wed, 27 Jun 2018 at 18:43, Nicolas Lalevée <ni...@hibnet.org>
wrote:
> Everything looks good apart from the bug Ross reported which I have been
> able to reproduce. And it seems pretty consistent, not very random. And I
> see no error in Eclipse’s log.
>
> I have been able to reproduce it with the Eclipse version:
> Version: Neon.3 Release (4.6.3)
> Build id: 20170314-1500
>
> I am also using java 10, which is a bit tricky to make it run smoothly due
> to the modules thing. Maybe it is related.
>
> And the project I tried to build in Eclipse is the Ivy project, which is
> about just an ivy.xml and a version.properties.
>
> I know that the IvyDE code which is triggering the update of the classpath
> is tricky, it is quite sensible, partly due to the non trivial Eclipse
> APIs. Maybe with the last « cleanup » the resolve process has been messed
> up, and somehow it still work in the refresh case.
>
> Since there is a work around (hitting refresh after resolve) and it is an
> RC, we could ship it like that and fix it later. But due to the automatic
> update via the update site, I bet most users will update even if it is an
> RC.
> So I am not sure what I should vote.
>
> So I vote -0 for me for now.
>
> Nicolas
>
> > Le 25 juin 2018 à 07:52, Jaikiran Pai <ja...@gmail.com> a
> écrit :
> >
> > I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
> project. This addresses the blocker issue that Nicolas identified, the last
> time a vote was initiated for this version.
> >
> > The newly updated tag is here
> https://git-wip-us.apache.org/repos/asf?p=ant-ivyde.git;a=tag;h=refs/tags/2.3.0-rc1
> with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
> >
> > You can download the distribution from this URL:
> https://dist.apache.org/repos/dist/dev/ant/ivyde/2.3.0-rc1/ at rev 27709
> >
> > The Eclipse p2 repository is here:
> https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivyde-2.3.0.rc1-201806251008-RELEASE/
> at rev 27707
> >
> > The 2.3.0-rc1 release of IvyDE consists of the following changes:
> >
> > * FIX: xml bomb in workspace causes hang in Ivy code during Search or
> Synchronize operations (https://issues.apache.org/jira/browse/IVYDE-354)
> > * FIX: Deadlock in classpath container (
> https://issues.apache.org/jira/browse/IVYDE-361)
> > * FIX: Typo in IvyResolveJob (
> https://issues.apache.org/jira/browse/IVYDE-362)
> > * FIX: User-selected configurations not checked in the viewer (
> https://issues.apache.org/jira/browse/IVYDE-378)
> > * FIX: Fix ClassCastException (
> https://issues.apache.org/jira/browse/IVYDE-386)
> > * FIX: Fix the issue where the IvyDE preferences couldn't be saved (
> https://issues.apache.org/jira/browse/IVYDE-388)
> >
> > * NEW: Support for OSGi 'Bundle-Classpath' directive
> > * NEW: Basic support for the workspace resolver to find OSGi bundles
> managed by Ivy in the workspace
> > * NEW: Support for storing credentials securely
> >
> >
> > Do you vote for the release of these binaries?
> >
> > -Jaikiran
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
>
>
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
> Since there is a work around (hitting refresh after resolve) and it is
> an RC, we could ship it like that and fix it later. But due to the
> automatic update via the update site, I bet most users will update
> even if it is an RC. So I am not sure what I should vote. So I vote -0
> for me for now.
I was reserving my vote just for this reason. I don't use Eclipse so I
wanted to see if someone more familiar with it has an opinion about this
bug. You are right that it's going to end up affecting everyone once we
release this. Given that the purpose of this release is revive this
project a bit and not break setups where things are working fine and the
fact that this will end up being an annoying kind of workaround (having
to hit refresh after resolve), I don't see rushing this release without
fixing this issue serves any purpose.
So I'll vote a -1 on this now. I know we have gone through 3 voting
rounds for this release, so thank you everyone for being patient and
testing out the binaries. I'll file this issue in JIRA and hopefully
spend some time in Eclipse this weekend to try and sort this out.
-Jaikiran
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Everything looks good apart from the bug Ross reported which I have been able to reproduce. And it seems pretty consistent, not very random. And I see no error in Eclipse’s log.
I have been able to reproduce it with the Eclipse version:
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I am also using java 10, which is a bit tricky to make it run smoothly due to the modules thing. Maybe it is related.
And the project I tried to build in Eclipse is the Ivy project, which is about just an ivy.xml and a version.properties.
I know that the IvyDE code which is triggering the update of the classpath is tricky, it is quite sensible, partly due to the non trivial Eclipse APIs. Maybe with the last « cleanup » the resolve process has been messed up, and somehow it still work in the refresh case.
Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC.
So I am not sure what I should vote.
So I vote -0 for me for now.
Nicolas
> Le 25 juin 2018 à 07:52, Jaikiran Pai <ja...@gmail.com> a écrit :
>
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE project. This addresses the blocker issue that Nicolas identified, the last time a vote was initiated for this version.
>
> The newly updated tag is here https://git-wip-us.apache.org/repos/asf?p=ant-ivyde.git;a=tag;h=refs/tags/2.3.0-rc1 with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
>
> You can download the distribution from this URL: https://dist.apache.org/repos/dist/dev/ant/ivyde/2.3.0-rc1/ at rev 27709
>
> The Eclipse p2 repository is here: https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivyde-2.3.0.rc1-201806251008-RELEASE/ at rev 27707
>
> The 2.3.0-rc1 release of IvyDE consists of the following changes:
>
> * FIX: xml bomb in workspace causes hang in Ivy code during Search or Synchronize operations (https://issues.apache.org/jira/browse/IVYDE-354)
> * FIX: Deadlock in classpath container (https://issues.apache.org/jira/browse/IVYDE-361)
> * FIX: Typo in IvyResolveJob (https://issues.apache.org/jira/browse/IVYDE-362)
> * FIX: User-selected configurations not checked in the viewer (https://issues.apache.org/jira/browse/IVYDE-378)
> * FIX: Fix ClassCastException (https://issues.apache.org/jira/browse/IVYDE-386)
> * FIX: Fix the issue where the IvyDE preferences couldn't be saved (https://issues.apache.org/jira/browse/IVYDE-388)
>
> * NEW: Support for OSGi 'Bundle-Classpath' directive
> * NEW: Basic support for the workspace resolver to find OSGi bundles managed by Ivy in the workspace
> * NEW: Support for storing credentials securely
>
>
> Do you vote for the release of these binaries?
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
+1
Gintas
P.S. Disappearing Ivy container seems to be default Eclipse behaviour in
Oxygen where the filtering of
empty library containers is on in Package Explorer. The filter was first
introduced in Neon
[1]
https://www.eclipse.org/eclipse/news/4.6/M7/#hide-empty-library-containers-project-explorer
On Mon, 25 Jun 2018 at 07:53, Jaikiran Pai <ja...@gmail.com> wrote:
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
> project. This addresses the blocker issue that Nicolas identified, the
> last time a vote was initiated for this version.
>
> The newly updated tag is here
>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivyde.git;a=tag;h=refs/tags/2.3.0-rc1
> with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
>
> You can download the distribution from this URL:
> https://dist.apache.org/repos/dist/dev/ant/ivyde/2.3.0-rc1/ at rev 27709
>
> The Eclipse p2 repository is here:
>
> https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivyde-2.3.0.rc1-201806251008-RELEASE/
> at rev 27707
>
> The 2.3.0-rc1 release of IvyDE consists of the following changes:
>
> * FIX: xml bomb in workspace causes hang in Ivy code during Search or
> Synchronize operations (https://issues.apache.org/jira/browse/IVYDE-354)
> * FIX: Deadlock in classpath container
> (https://issues.apache.org/jira/browse/IVYDE-361)
> * FIX: Typo in IvyResolveJob
> (https://issues.apache.org/jira/browse/IVYDE-362)
> * FIX: User-selected configurations not checked in the viewer
> (https://issues.apache.org/jira/browse/IVYDE-378)
> * FIX: Fix ClassCastException
> (https://issues.apache.org/jira/browse/IVYDE-386)
> * FIX: Fix the issue where the IvyDE preferences couldn't be saved
> (https://issues.apache.org/jira/browse/IVYDE-388)
>
> * NEW: Support for OSGi 'Bundle-Classpath' directive
> * NEW: Basic support for the workspace resolver to find OSGi bundles
> managed by Ivy in the workspace
> * NEW: Support for storing credentials securely
>
>
> Do you vote for the release of these binaries?
>
> -Jaikiran
>
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by rc...@e1b.org.
Yes, Eclipse it is actually losing the added libraries -- hence the
compile errors.
Here is my eclipse.ini (I am using the "enterprise" distribution). I
guess, I'll try to see if I can recreated
it with a fresh eclipse download.
-vm
C:/Program Files/Java/jdk10/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.epp.package.common
--launcher.defaultAction
openFile
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-XX:MaxPermSize=384m
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=@user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Xms1024m
-Xmx1024m
--add-modules=ALL-SYSTEM
Ross
From: "Jaikiran Pai" <ja...@gmail.com>
To: ivy-user@ant.apache.org,
Date: 06/25/2018 08:38 PM
Subject: Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Hi Ross,
Thank you for testing this. Comment inline.
On 25/06/18 11:03 PM, rcohen@e1b.org wrote:
> I think there is a problem.
>
> Working in Eclipse 4.7, whenever I do an Ivy->"resolve", the project
loses
> all its Ivy-provided libraries, and then, of course, all sorts of
compile
> errors appear. But if I then do an Ivy->Refresh, suddenly all my
> IvyDE-provided lib Icons return, and all the compile errors go away.
This was mentioned as an issue in one of the vote mails. At that time
though it was noted as the icons disappear so it didn't look like a
major issue. If the IDE is losing Ivy provided libraries too, then it
does sound a bit more important one. However, I haven't yet been able to
reproduce this. I'll wait for a few others to try this binary in this
voting mail to see if this is reproducible consistently and how serious
this is.
-Jaikiran
> There
> are no IvDE log errors at start up or at when I resolve. My eclipse is
> up-to-date, and I don't run any exotic plugins. I tried cleaning the
> caches but this did not help. I tried re-adding Ivy support to project,
> but this had no effect. The only thing that might be considered exotic
> about the project/resolve is that it contains 5 Ivy modules -- which
> caused no problems for 2.2.
>
> Obviously, not having the resolve work properly is a kind of a problem
--
> though I suppose there is the work-around of always doing a refresh
after
> the resolve. I didn't have any problems with 2.2, so I'll stick with
> that for now, and I'll understand if people with some longstanding issue
> really want this fix. So put me down for +0.
>
>
>
> Ross
>
> I
>
>
>
> From: "Jaikiran Pai" <ja...@gmail.com>
> To: "Ant Developers List" <de...@ant.apache.org>,
> Cc: ivy-user@ant.apache.org
> Date: 06/25/2018 01:53 AM
> Subject: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
>
>
>
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
> project. This addresses the blocker issue that Nicolas identified, the
> last time a vote was initiated for this version.
>
> The newly updated tag is here
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXQtd2lwLXVzLmFwYWNoZS5vcmcvcmVwb3MvYXNmP3A9YW50LWl2eWRlLmdpdDthPXRhZztoPXJlZnMvdGFncy8yLjMuMC1yYzE%3D&_s=ZXJpZTE%3D&_c=e4b1e885
>
> with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
>
> You can download the distribution from this URL:
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlLzIuMy4wLXJjMS8%3D&_s=ZXJpZTE%3D&_c=606a32cc
> at rev 27709
>
> The Eclipse p2 repository is here:
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlL3VwZGF0ZXNpdGUvaXZ5ZGUtMi4zLjAucmMxLTIwMTgwNjI1MTAwOC1SRUxFQVNFLw%3D%3D&_s=ZXJpZTE%3D&_c=fe30bb4d
>
> at rev 27707
>
> The 2.3.0-rc1 release of IvyDE consists of the following changes:
>
> * FIX: xml bomb in workspace causes hang in Ivy code during Search or
> Synchronize operations (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNTQ%3D&_s=ZXJpZTE%3D&_c=0dec03b4
> )
> * FIX: Deadlock in classpath container
> (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjE%3D&_s=ZXJpZTE%3D&_c=aac009a8
> )
> * FIX: Typo in IvyResolveJob
> (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjI%3D&_s=ZXJpZTE%3D&_c=26af1123
> )
> * FIX: User-selected configurations not checked in the viewer
> (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNzg%3D&_s=ZXJpZTE%3D&_c=ee43d332
> )
> * FIX: Fix ClassCastException
> (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODY%3D&_s=ZXJpZTE%3D&_c=f71b43e1
> )
> * FIX: Fix the issue where the IvyDE preferences couldn't be saved
> (
>
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODg%3D&_s=ZXJpZTE%3D&_c=ec36b742
> )
>
> * NEW: Support for OSGi 'Bundle-Classpath' directive
> * NEW: Basic support for the workspace resolver to find OSGi bundles
> managed by Ivy in the workspace
> * NEW: Support for storing credentials securely
>
>
> Do you vote for the release of these binaries?
>
> -Jaikiran
>
>
>
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 03W3cCpWe) is spam:
Spam:
https://milton-web.wnyric.org/canit/b.php?c=s&i=03W3cCpWe&m=56198526f363&t=20180625
Not spam:
https://milton-web.wnyric.org/canit/b.php?c=n&i=03W3cCpWe&m=56198526f363&t=20180625
Forget vote:
https://milton-web.wnyric.org/canit/b.php?c=f&i=03W3cCpWe&m=56198526f363&t=20180625
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Jaikiran Pai <ja...@gmail.com>.
Hi Ross,
Thank you for testing this. Comment inline.
On 25/06/18 11:03 PM, rcohen@e1b.org wrote:
> I think there is a problem.
>
> Working in Eclipse 4.7, whenever I do an Ivy->"resolve", the project loses
> all its Ivy-provided libraries, and then, of course, all sorts of compile
> errors appear. But if I then do an Ivy->Refresh, suddenly all my
> IvyDE-provided lib Icons return, and all the compile errors go away.
This was mentioned as an issue in one of the vote mails. At that time
though it was noted as the icons disappear so it didn't look like a
major issue. If the IDE is losing Ivy provided libraries too, then it
does sound a bit more important one. However, I haven't yet been able to
reproduce this. I'll wait for a few others to try this binary in this
voting mail to see if this is reproducible consistently and how serious
this is.
-Jaikiran
> There
> are no IvDE log errors at start up or at when I resolve. My eclipse is
> up-to-date, and I don't run any exotic plugins. I tried cleaning the
> caches but this did not help. I tried re-adding Ivy support to project,
> but this had no effect. The only thing that might be considered exotic
> about the project/resolve is that it contains 5 Ivy modules -- which
> caused no problems for 2.2.
>
> Obviously, not having the resolve work properly is a kind of a problem --
> though I suppose there is the work-around of always doing a refresh after
> the resolve. I didn't have any problems with 2.2, so I'll stick with
> that for now, and I'll understand if people with some longstanding issue
> really want this fix. So put me down for +0.
>
>
>
> Ross
>
> I
>
>
>
> From: "Jaikiran Pai" <ja...@gmail.com>
> To: "Ant Developers List" <de...@ant.apache.org>,
> Cc: ivy-user@ant.apache.org
> Date: 06/25/2018 01:53 AM
> Subject: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
>
>
>
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
> project. This addresses the blocker issue that Nicolas identified, the
> last time a vote was initiated for this version.
>
> The newly updated tag is here
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXQtd2lwLXVzLmFwYWNoZS5vcmcvcmVwb3MvYXNmP3A9YW50LWl2eWRlLmdpdDthPXRhZztoPXJlZnMvdGFncy8yLjMuMC1yYzE%3D&_s=ZXJpZTE%3D&_c=e4b1e885
>
> with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
>
> You can download the distribution from this URL:
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlLzIuMy4wLXJjMS8%3D&_s=ZXJpZTE%3D&_c=606a32cc
> at rev 27709
>
> The Eclipse p2 repository is here:
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlL3VwZGF0ZXNpdGUvaXZ5ZGUtMi4zLjAucmMxLTIwMTgwNjI1MTAwOC1SRUxFQVNFLw%3D%3D&_s=ZXJpZTE%3D&_c=fe30bb4d
>
> at rev 27707
>
> The 2.3.0-rc1 release of IvyDE consists of the following changes:
>
> * FIX: xml bomb in workspace causes hang in Ivy code during Search or
> Synchronize operations (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNTQ%3D&_s=ZXJpZTE%3D&_c=0dec03b4
> )
> * FIX: Deadlock in classpath container
> (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjE%3D&_s=ZXJpZTE%3D&_c=aac009a8
> )
> * FIX: Typo in IvyResolveJob
> (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjI%3D&_s=ZXJpZTE%3D&_c=26af1123
> )
> * FIX: User-selected configurations not checked in the viewer
> (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNzg%3D&_s=ZXJpZTE%3D&_c=ee43d332
> )
> * FIX: Fix ClassCastException
> (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODY%3D&_s=ZXJpZTE%3D&_c=f71b43e1
> )
> * FIX: Fix the issue where the IvyDE preferences couldn't be saved
> (
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODg%3D&_s=ZXJpZTE%3D&_c=ec36b742
> )
>
> * NEW: Support for OSGi 'Bundle-Classpath' directive
> * NEW: Basic support for the workspace resolver to find OSGi bundles
> managed by Ivy in the workspace
> * NEW: Support for storing credentials securely
>
>
> Do you vote for the release of these binaries?
>
> -Jaikiran
>
>
>
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by rc...@e1b.org.
I think there is a problem.
Working in Eclipse 4.7, whenever I do an Ivy->"resolve", the project loses
all its Ivy-provided libraries, and then, of course, all sorts of compile
errors appear. But if I then do an Ivy->Refresh, suddenly all my
IvyDE-provided lib Icons return, and all the compile errors go away. There
are no IvDE log errors at start up or at when I resolve. My eclipse is
up-to-date, and I don't run any exotic plugins. I tried cleaning the
caches but this did not help. I tried re-adding Ivy support to project,
but this had no effect. The only thing that might be considered exotic
about the project/resolve is that it contains 5 Ivy modules -- which
caused no problems for 2.2.
Obviously, not having the resolve work properly is a kind of a problem --
though I suppose there is the work-around of always doing a refresh after
the resolve. I didn't have any problems with 2.2, so I'll stick with
that for now, and I'll understand if people with some longstanding issue
really want this fix. So put me down for +0.
Ross
I
From: "Jaikiran Pai" <ja...@gmail.com>
To: "Ant Developers List" <de...@ant.apache.org>,
Cc: ivy-user@ant.apache.org
Date: 06/25/2018 01:53 AM
Subject: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE
project. This addresses the blocker issue that Nicolas identified, the
last time a vote was initiated for this version.
The newly updated tag is here
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXQtd2lwLXVzLmFwYWNoZS5vcmcvcmVwb3MvYXNmP3A9YW50LWl2eWRlLmdpdDthPXRhZztoPXJlZnMvdGFncy8yLjMuMC1yYzE%3D&_s=ZXJpZTE%3D&_c=e4b1e885
with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
You can download the distribution from this URL:
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlLzIuMy4wLXJjMS8%3D&_s=ZXJpZTE%3D&_c=606a32cc
at rev 27709
The Eclipse p2 repository is here:
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9kaXN0LmFwYWNoZS5vcmcvcmVwb3MvZGlzdC9kZXYvYW50L2l2eWRlL3VwZGF0ZXNpdGUvaXZ5ZGUtMi4zLjAucmMxLTIwMTgwNjI1MTAwOC1SRUxFQVNFLw%3D%3D&_s=ZXJpZTE%3D&_c=fe30bb4d
at rev 27707
The 2.3.0-rc1 release of IvyDE consists of the following changes:
* FIX: xml bomb in workspace causes hang in Ivy code during Search or
Synchronize operations (
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNTQ%3D&_s=ZXJpZTE%3D&_c=0dec03b4
)
* FIX: Deadlock in classpath container
(
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjE%3D&_s=ZXJpZTE%3D&_c=aac009a8
)
* FIX: Typo in IvyResolveJob
(
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNjI%3D&_s=ZXJpZTE%3D&_c=26af1123
)
* FIX: User-selected configurations not checked in the viewer
(
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zNzg%3D&_s=ZXJpZTE%3D&_c=ee43d332
)
* FIX: Fix ClassCastException
(
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODY%3D&_s=ZXJpZTE%3D&_c=f71b43e1
)
* FIX: Fix the issue where the IvyDE preferences couldn't be saved
(
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9pc3N1ZXMuYXBhY2hlLm9yZy9qaXJhL2Jyb3dzZS9JVllERS0zODg%3D&_s=ZXJpZTE%3D&_c=ec36b742
)
* NEW: Support for OSGi 'Bundle-Classpath' directive
* NEW: Basic support for the workspace resolver to find OSGi bundles
managed by Ivy in the workspace
* NEW: Support for storing credentials securely
Do you vote for the release of these binaries?
-Jaikiran
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 05W2RR1c8) is spam:
Spam:
https://milton-web.wnyric.org/canit/b.php?c=s&i=05W2RR1c8&m=2d0f1a6be422&t=20180625
Not spam:
https://milton-web.wnyric.org/canit/b.php?c=n&i=05W2RR1c8&m=2d0f1a6be422&t=20180625
Forget vote:
https://milton-web.wnyric.org/canit/b.php?c=f&i=05W2RR1c8&m=2d0f1a6be422&t=20180625
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.
Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Everything looks good apart from the bug Ross reported which I have been able to reproduce. And it seems pretty consistent, not very random. And I see no error in Eclipse’s log.
I have been able to reproduce it with the Eclipse version:
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I am also using java 10, which is a bit tricky to make it run smoothly due to the modules thing. Maybe it is related.
And the project I tried to build in Eclipse is the Ivy project, which is about just an ivy.xml and a version.properties.
I know that the IvyDE code which is triggering the update of the classpath is tricky, it is quite sensible, partly due to the non trivial Eclipse APIs. Maybe with the last « cleanup » the resolve process has been messed up, and somehow it still work in the refresh case.
Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic update via the update site, I bet most users will update even if it is an RC.
So I am not sure what I should vote.
So I vote -0 for me for now.
Nicolas
> Le 25 juin 2018 à 07:52, Jaikiran Pai <ja...@gmail.com> a écrit :
>
> I'm initiating a newer vote mail for 2.3.0-rc1 release of Apache IvyDE project. This addresses the blocker issue that Nicolas identified, the last time a vote was initiated for this version.
>
> The newly updated tag is here https://git-wip-us.apache.org/repos/asf?p=ant-ivyde.git;a=tag;h=refs/tags/2.3.0-rc1 with sha1 3581a61ec159ede16005f36e58e5e258d32090fa
>
> You can download the distribution from this URL: https://dist.apache.org/repos/dist/dev/ant/ivyde/2.3.0-rc1/ at rev 27709
>
> The Eclipse p2 repository is here: https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivyde-2.3.0.rc1-201806251008-RELEASE/ at rev 27707
>
> The 2.3.0-rc1 release of IvyDE consists of the following changes:
>
> * FIX: xml bomb in workspace causes hang in Ivy code during Search or Synchronize operations (https://issues.apache.org/jira/browse/IVYDE-354)
> * FIX: Deadlock in classpath container (https://issues.apache.org/jira/browse/IVYDE-361)
> * FIX: Typo in IvyResolveJob (https://issues.apache.org/jira/browse/IVYDE-362)
> * FIX: User-selected configurations not checked in the viewer (https://issues.apache.org/jira/browse/IVYDE-378)
> * FIX: Fix ClassCastException (https://issues.apache.org/jira/browse/IVYDE-386)
> * FIX: Fix the issue where the IvyDE preferences couldn't be saved (https://issues.apache.org/jira/browse/IVYDE-388)
>
> * NEW: Support for OSGi 'Bundle-Classpath' directive
> * NEW: Basic support for the workspace resolver to find OSGi bundles managed by Ivy in the workspace
> * NEW: Support for storing credentials securely
>
>
> Do you vote for the release of these binaries?
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>