PM
To: dev@netbeans.incubator.apache.org
Subject: Re: Error updating version in pom.xml
Gj, just found that in 8.2 if you have the cursor immediately after the >, it
doesn’t replace the version string and does the 9.0 behaviour.
Also, if you have the cursor in the middle of a version string
Gj, just found that in 8.2 if you have the cursor immediately after the >, it
doesn’t replace the version string and does the 9.0 behaviour.
Also, if you have the cursor in the middle of a version string it filters from
that prefix.
I guess this is why I thought it wasn’t avail in 8.2 as I alwa
Hi,
Am Freitag, den 27.07.2018, 19:55 + schrieb Kenneth Fogel:
> I have just added this to jira but I'm curious if anyone else noticed
> this in 9.0 vc3.
>
> When editing the pom.xml file:
> 1.5 in any place in a pom.xml.
> Type a period in front of the existing period and I get a list of
> o
Oh wow, that’s kinda neat. It works for version strings also. I.e. ctrl*space
inside ${here}
> On 28 Jul 2018, at 19:11, Geertjan Wielenga
> wrote:
>
> https://www.youtube.com/watch?v=wGuvhDJ0f80
>
> Above you see how it works in 8.2 and how it works in 9.0 vc3.
>
> Hope it helps,
>
> Gj
>
https://www.youtube.com/watch?v=wGuvhDJ0f80
Above you see how it works in 8.2 and how it works in 9.0 vc3.
Hope it helps,
Gj
On Sat, Jul 28, 2018 at 7:12 AM, Brett Ryan wrote:
> I’m still using 8.2 in production, and I’ve never seen it replace the
> version. However, i use the following rec
I’m still using 8.2 in production, and I’ve never seen it replace the version.
However, i use the following recommended strategy in maven projects.
1. Use variables for storing versions used in dependencies
2. Use the versions [1] plugin to identify new releases
3. Never use ranges, it’s not s
I'm frequently annoyed by this too. Has a bug been filed?
-Tim
--
http://timboudreau.com
Am Freitag, den 27.07.2018, 23:41 +0200 schrieb Geertjan Wielenga:
> Or maybe, thanks to the changes in that PR, the current issue
> reported by
Please don't jump to conclusions. The issues are not identical and the
changeset is not the cause of the new bug.
Before the referenced changeset an inv
Or maybe, thanks to the changes in that PR, the current issue reported by
Ken occurs.
Gj
On Fri, Jul 27, 2018 at 11:39 PM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> That's exactly the same problem that Ken describes, thanks a lot for
> identifying this.
>
> Gj
>
> On Fri, Ju
That's exactly the same problem that Ken describes, thanks a lot for
identifying this.
Gj
On Fri, Jul 27, 2018 at 11:36 PM, Matthias Bläsing <
mblaes...@doppel-helix.eu> wrote:
> Hi Gj,
>
> Am Freitag, den 27.07.2018, 23:30 +0200 schrieb Geertjan Wielenga:
> > Absolutely, I'm not disagreeing wit
Hi Gj,
Am Freitag, den 27.07.2018, 23:30 +0200 schrieb Geertjan Wielenga:
> Absolutely, I'm not disagreeing with you at all, in fact it's 24.00 here
> and I am trying to identify where the problem is coming from.
a similar problem (corruption of XML structure)
https://issues.apache.org/jira/brow
ion numbers into the field only to have it fail during the project
> compile. I suspect this is an unintended side effect from some other
> change.
>
> Ken
>
> -Original Message-
> From: Geertjan Wielenga
> Sent: July 27, 2018 4:04 PM
> To: dev
> Subject: Re:
ver, it is in my opinion a bug that needs to be addressed. A
> feature of NetBeans has been diminished and needs to be addressed at least
> for 9.01.
>
> Ken
>
> -Original Message-
> From: Geertjan Wielenga
> Sent: July 27, 2018 5:03 PM
> To: dev
> Subject:
27, 2018 5:03 PM
To: dev
Subject: Re: Error updating version in pom.xml
Well, no one has touched the Maven modules AFAIK. I can reproduce it though.
I'm sure you're aware that we've now voted on the release and we're pretty
close to releasing it, so it's certainly not
t shouldn’t be necessary. From a teaching
>> perspective, what will happen is that students will be inserting new
>> version numbers into the field only to have it fail during the project
>> compile. I suspect this is an unintended side effect from some other
>> change.
>>
have it fail during the project
> compile. I suspect this is an unintended side effect from some other
> change.
>
> Ken
>
> -Original Message-
> From: Geertjan Wielenga
> Sent: July 27, 2018 4:04 PM
> To: dev
> Subject: Re: Error updating version in pom.xml
rsion numbers into the
field only to have it fail during the project compile. I suspect this is an
unintended side effect from some other change.
Ken
-Original Message-
From: Geertjan Wielenga
Sent: July 27, 2018 4:04 PM
To: dev
Subject: Re: Error updating version in pom.xml
Maybe delet
Maybe delete the number that you don't want and then call up code
completion?
Gj
On Fri, Jul 27, 2018 at 9:55 PM, Kenneth Fogel
wrote:
> I have just added this to jira but I'm curious if anyone else noticed this
> in 9.0 vc3.
>
> When editing the pom.xml file:
> 1.5 in any place in a pom.xml.
>
18 matches
Mail list logo
