On Sun, 1 Jul 2018 at 21:30, Jan Matèrne (jhm) 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 stu
> 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-unsubscr.
It looks like Ant nightly is stuck (possibly due to plugin update in
Jenkins) and it's blocking all other builds.
Gintas
On Sun, 1 Jul 2018 at 15:05, Nicolas Lalevée
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
Le 28 juin 2018 à 08:41, Jaikiran Pai 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
At my first read of the code I wondered if paths ending with slash are properly
handled in every case. After more careful reading, it is seems ok. Maybe some
unit tests about it would be nice, just to be sure.
Then, about tackling the bug, I am on the same page as you both. It looks good
to me.
On 2018-06-28, Stefan Bodewig wrote:
> On 2018-06-28, Jaikiran Pai wrote:
>> Which then makes me wonder - in the context of this specific
>> untar/expand/unzip issue, should we probably be using a different
>> custom very specific logic (which relies on canonical files and
>> getParent()) instead
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
