You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Kenneth Fogel <kf...@dawsoncollege.qc.ca> on 2018/07/27 19:55:49 UTC
Error updating version in pom.xml
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:
<version>1.5</version> in any place in a pom.xml.
Type a period in front of the existing period and I get a list of other version numbers.
When I select the new version it is inserted into the existing version instead of replacing it.
<version>1.1.75.5</version>
It did work properly in 8.2.
Ken Fogel
Re: Error updating version in pom.xml
Posted by Hanasaki Jiji <ha...@gmail.com>.
You could use ranges (available maven and Gradle) and teach maven
coordinate concepta and semcer.org While I realize this may not address
using the IDE the way you want, it may help address the software
engineering issue raised.
On Fri, Jul 27, 2018, 16:51 Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> What I like about 8.2 was that I could explore all the possible versions
> and either stay with the one I have or switch to a newer or older one.
> Deleting what's there first 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.
>
> Ken
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: July 27, 2018 4:04 PM
> To: dev <de...@netbeans.incubator.apache.org>
> Subject: Re: Error updating version in pom.xml
>
> 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 <kfogel@dawsoncollege.qc.ca
> >
> 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:
> > <version>1.5</version> in any place in a pom.xml.
> > Type a period in front of the existing period and I get a list of
> > other version numbers.
> > When I select the new version it is inserted into the existing version
> > instead of replacing it.
> > <version>1.1.75.5</version>
> > It did work properly in 8.2.
> >
> > Ken Fogel
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Maybe you can tell students to first select the whole number and then call
up code completion. Then code completion will replace that whole selected
number with whatever is selected from the code completion box.
Gj
On Fri, Jul 27, 2018 at 11:03 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
>
> 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 going to be fixed in
> time for 9.0 at this stage. Not sure how it's going to be worked out to fix
> this, since again no one has touched the Maven code AFAIK. Possibly that
> functionality is provided by some plugin that isn't part of Java SE, i.e.,
> note again that Apache NetBeans (incubating) 9.0 is focused on 9.0 only. If
> you add the 8.2 update center (as explained here https://blogs.apache.org/
> netbeans/entry/what-s-happened-to-my) you might find that when you
> install the Java EE related plugins, that functionality you're missing will
> be added.
>
> Gj
>
>
> On Fri, Jul 27, 2018 at 10:50 PM, Kenneth Fogel <
> kfogel@dawsoncollege.qc.ca> wrote:
>
>> What I like about 8.2 was that I could explore all the possible versions
>> and either stay with the one I have or switch to a newer or older one.
>> Deleting what's there first 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.
>>
>> Ken
>>
>> -----Original Message-----
>> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
>> Sent: July 27, 2018 4:04 PM
>> To: dev <de...@netbeans.incubator.apache.org>
>> Subject: Re: Error updating version in pom.xml
>>
>> 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 <
>> kfogel@dawsoncollege.qc.ca>
>> 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:
>> > <version>1.5</version> in any place in a pom.xml.
>> > Type a period in front of the existing period and I get a list of
>> > other version numbers.
>> > When I select the new version it is inserted into the existing version
>> > instead of replacing it.
>> > <version>1.1.75.5</version>
>> > It did work properly in 8.2.
>> >
>> > Ken Fogel
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>
Re: Error updating version in pom.xml
Posted by Brett Ryan <br...@gmail.com>.
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 <ge...@googlemail.com.INVALID> 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
>
>
>
>> On Sat, Jul 28, 2018 at 7:12 AM, Brett Ryan <br...@gmail.com> wrote:
>>
>> 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 supported in maven 3 any more.
>>
>> [1]: https://www.mojohaus.org/versions-maven-plugin/
>>
>>> On 28 Jul 2018, at 13:15, Tim Boudreau <ni...@gmail.com> wrote:
>>>
>>> I'm frequently annoyed by this too. Has a bug been filed?
>>>
>>> -Tim
>>> --
>>> http://timboudreau.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Error updating version in pom.xml
Posted by Kenneth Fogel <kf...@dawsoncollege.qc.ca>.
I was notified today that this bug has been located and squished. I assume the fix will appear in 9.01 or 9.1 although the notice stated that the fix is in the master now. Kudos to Matthias Bläsing for resolving this.
Ken
-----Original Message-----
From: Brett Ryan <br...@gmail.com>
Sent: July 31, 2018 6:53 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 it filters from that prefix.
I guess this is why I thought it wasn’t avail in 8.2 as I always do if after the >
> On 28 Jul 2018, at 19:11, Geertjan Wielenga <ge...@googlemail.com.INVALID> 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
>
>
>
>> On Sat, Jul 28, 2018 at 7:12 AM, Brett Ryan <br...@gmail.com> wrote:
>>
>> 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 supported in maven 3 any more.
>>
>> [1]: https://www.mojohaus.org/versions-maven-plugin/
>>
>>> On 28 Jul 2018, at 13:15, Tim Boudreau <ni...@gmail.com> wrote:
>>>
>>> I'm frequently annoyed by this too. Has a bug been filed?
>>>
>>> -Tim
>>> --
>>> http://timboudreau.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Brett Ryan <br...@gmail.com>.
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 always do if after the >
> On 28 Jul 2018, at 19:11, Geertjan Wielenga <ge...@googlemail.com.INVALID> 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
>
>
>
>> On Sat, Jul 28, 2018 at 7:12 AM, Brett Ryan <br...@gmail.com> wrote:
>>
>> 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 supported in maven 3 any more.
>>
>> [1]: https://www.mojohaus.org/versions-maven-plugin/
>>
>>> On 28 Jul 2018, at 13:15, Tim Boudreau <ni...@gmail.com> wrote:
>>>
>>> I'm frequently annoyed by this too. Has a bug been filed?
>>>
>>> -Tim
>>> --
>>> http://timboudreau.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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 <br...@gmail.com> wrote:
> 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 supported in maven 3 any more.
>
> [1]: https://www.mojohaus.org/versions-maven-plugin/
>
> > On 28 Jul 2018, at 13:15, Tim Boudreau <ni...@gmail.com> wrote:
> >
> > I'm frequently annoyed by this too. Has a bug been filed?
> >
> > -Tim
> > --
> > http://timboudreau.com
>
Re: Error updating version in pom.xml
Posted by Brett Ryan <br...@gmail.com>.
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 supported in maven 3 any more.
[1]: https://www.mojohaus.org/versions-maven-plugin/
> On 28 Jul 2018, at 13:15, Tim Boudreau <ni...@gmail.com> wrote:
>
> I'm frequently annoyed by this too. Has a bug been filed?
>
> -Tim
> --
> http://timboudreau.com
Re: Error updating version in pom.xml
Posted by Tim Boudreau <ni...@gmail.com>.
I'm frequently annoyed by this too. Has a bug been filed?
-Tim
--
http://timboudreau.com
Re: Error updating version in pom.xml
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
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 invalid XML structure was created
when code completion was invoked inside the version tag. That was fixed
by the changeset.
Whether or not the whole version is replaced is a different matter.
The logic in the XML completion provider needs to be checked, as the
behavior is also present in the groupId completion.
It is this:
- if the selected value matches the current content, it replaces the
current text
- if the selected value is different, the suffix of the selected value
is inserted at the cursor position
I think the problem is in:
org.netbeans.modules.maven.grammar.spi.AbstractSchemaBasedGrammar.MyTextElement
does not override
org.netbeans.modules.xml.spi.dom.AbstractNode.getLength()
and this results in missing/wrong delete information.
This is a very quick analysis without going to deep.
Maybe this already helps with fixing.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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.wielenga@googlemail.com> wrote:
> 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 <
> mblaesing@doppel-helix.eu> wrote:
>
>> 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/browse/NETBEANS-250?jql=proje
>> ct%20%3D%20NETBEANS%20AND%20status%20in%20(Open%2C%20%
>> 22In%20Progress%22%2C%20Reopened%2C%20Resolved%2C%20Closed)%
>> 20AND%20text%20~%20%22maven%20pom%20dependency%22%20ORDER%
>> 20BY%20updated%20DESC
>>
>> was traced into the XML modules:
>>
>> https://github.com/apache/incubator-netbeans/pull/357/files
>>
>> I'll look into this, but I'm currently occupied and focused on other
>> projects, so it won't happen right now.
>>
>> Greetings
>>
>> Matthias
>>
>> > > >
>> > > > On Fri, Jul 27, 2018 at 9:55 PM, Kenneth Fogel <
>> kfogel@dawsoncollege.qc.ca> 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:
>> > > > > <version>1.5</version> in any place in a pom.xml.
>> > > > > Type a period in front of the existing period and I get a list of
>> > > > > other version numbers.
>> > > > > When I select the new version it is inserted into the existing
>> > > > > version instead of replacing it.
>> > > > > <version>1.1.75.5</version>
>> > > > > It did work properly in 8.2.
>> > > > >
>> > > > > Ken Fogel
>> > > > >
>> > > > >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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 <
mblaesing@doppel-helix.eu> wrote:
> 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/browse/NETBEANS-250?jql=
> project%20%3D%20NETBEANS%20AND%20status%20in%20(Open%
> 2C%20%22In%20Progress%22%2C%20Reopened%2C%20Resolved%2C%
> 20Closed)%20AND%20text%20~%20%22maven%20pom%20dependency%22%
> 20ORDER%20BY%20updated%20DESC
>
> was traced into the XML modules:
>
> https://github.com/apache/incubator-netbeans/pull/357/files
>
> I'll look into this, but I'm currently occupied and focused on other
> projects, so it won't happen right now.
>
> Greetings
>
> Matthias
>
> > > >
> > > > On Fri, Jul 27, 2018 at 9:55 PM, Kenneth Fogel <
> kfogel@dawsoncollege.qc.ca> 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:
> > > > > <version>1.5</version> in any place in a pom.xml.
> > > > > Type a period in front of the existing period and I get a list of
> > > > > other version numbers.
> > > > > When I select the new version it is inserted into the existing
> > > > > version instead of replacing it.
> > > > > <version>1.1.75.5</version>
> > > > > It did work properly in 8.2.
> > > > >
> > > > > Ken Fogel
> > > > >
> > > > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Error updating version in pom.xml
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
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/browse/NETBEANS-250?jql=project%20%3D%20NETBEANS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Resolved%2C%20Closed)%20AND%20text%20~%20%22maven%20pom%20dependency%22%20ORDER%20BY%20updated%20DESC
was traced into the XML modules:
https://github.com/apache/incubator-netbeans/pull/357/files
I'll look into this, but I'm currently occupied and focused on other projects, so it won't happen right now.
Greetings
Matthias
> > >
> > > On Fri, Jul 27, 2018 at 9:55 PM, Kenneth Fogel <kf...@dawsoncollege.qc.ca> 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:
> > > > <version>1.5</version> in any place in a pom.xml.
> > > > Type a period in front of the existing period and I get a list of
> > > > other version numbers.
> > > > When I select the new version it is inserted into the existing
> > > > version instead of replacing it.
> > > > <version>1.1.75.5</version>
> > > > It did work properly in 8.2.
> > > >
> > > > Ken Fogel
> > > >
> > > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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.
Gj
On Fri, Jul 27, 2018 at 11:29 PM, Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> I absolutely do not consider this an issue that should hold up the
> release. However, 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 <ge...@googlemail.com.INVALID>
> Sent: July 27, 2018 5:03 PM
> To: dev <de...@netbeans.incubator.apache.org>
> 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 going to be fixed in
> time for 9.0 at this stage. Not sure how it's going to be worked out to fix
> this, since again no one has touched the Maven code AFAIK. Possibly that
> functionality is provided by some plugin that isn't part of Java SE, i.e.,
> note again that Apache NetBeans (incubating) 9.0 is focused on 9.0 only. If
> you add the 8.2 update center (as explained here
> https://blogs.apache.org/netbeans/entry/what-s-happened-to-my) you might
> find that when you install the Java EE related plugins, that functionality
> you're missing will be added.
>
> Gj
>
>
> On Fri, Jul 27, 2018 at 10:50 PM, Kenneth Fogel <
> kfogel@dawsoncollege.qc.ca>
> wrote:
>
> > What I like about 8.2 was that I could explore all the possible
> > versions and either stay with the one I have or switch to a newer or
> older one.
> > Deleting what's there first 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.
> >
> > Ken
> >
> > -----Original Message-----
> > From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> > Sent: July 27, 2018 4:04 PM
> > To: dev <de...@netbeans.incubator.apache.org>
> > Subject: Re: Error updating version in pom.xml
> >
> > 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
> > <kfogel@dawsoncollege.qc.ca
> > >
> > 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:
> > > <version>1.5</version> in any place in a pom.xml.
> > > Type a period in front of the existing period and I get a list of
> > > other version numbers.
> > > When I select the new version it is inserted into the existing
> > > version instead of replacing it.
> > > <version>1.1.75.5</version>
> > > It did work properly in 8.2.
> > >
> > > Ken Fogel
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
RE: Error updating version in pom.xml
Posted by Kenneth Fogel <kf...@dawsoncollege.qc.ca>.
I absolutely do not consider this an issue that should hold up the release. However, 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 <ge...@googlemail.com.INVALID>
Sent: July 27, 2018 5:03 PM
To: dev <de...@netbeans.incubator.apache.org>
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 going to be fixed in time for 9.0 at this stage. Not sure how it's going to be worked out to fix this, since again no one has touched the Maven code AFAIK. Possibly that functionality is provided by some plugin that isn't part of Java SE, i.e., note again that Apache NetBeans (incubating) 9.0 is focused on 9.0 only. If you add the 8.2 update center (as explained here
https://blogs.apache.org/netbeans/entry/what-s-happened-to-my) you might find that when you install the Java EE related plugins, that functionality you're missing will be added.
Gj
On Fri, Jul 27, 2018 at 10:50 PM, Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> What I like about 8.2 was that I could explore all the possible
> versions and either stay with the one I have or switch to a newer or older one.
> Deleting what's there first 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.
>
> Ken
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: July 27, 2018 4:04 PM
> To: dev <de...@netbeans.incubator.apache.org>
> Subject: Re: Error updating version in pom.xml
>
> 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
> <kfogel@dawsoncollege.qc.ca
> >
> 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:
> > <version>1.5</version> in any place in a pom.xml.
> > Type a period in front of the existing period and I get a list of
> > other version numbers.
> > When I select the new version it is inserted into the existing
> > version instead of replacing it.
> > <version>1.1.75.5</version>
> > It did work properly in 8.2.
> >
> > Ken Fogel
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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 going to be fixed in
time for 9.0 at this stage. Not sure how it's going to be worked out to fix
this, since again no one has touched the Maven code AFAIK. Possibly that
functionality is provided by some plugin that isn't part of Java SE, i.e.,
note again that Apache NetBeans (incubating) 9.0 is focused on 9.0 only. If
you add the 8.2 update center (as explained here
https://blogs.apache.org/netbeans/entry/what-s-happened-to-my) you might
find that when you install the Java EE related plugins, that functionality
you're missing will be added.
Gj
On Fri, Jul 27, 2018 at 10:50 PM, Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> What I like about 8.2 was that I could explore all the possible versions
> and either stay with the one I have or switch to a newer or older one.
> Deleting what's there first 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.
>
> Ken
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: July 27, 2018 4:04 PM
> To: dev <de...@netbeans.incubator.apache.org>
> Subject: Re: Error updating version in pom.xml
>
> 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 <kfogel@dawsoncollege.qc.ca
> >
> 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:
> > <version>1.5</version> in any place in a pom.xml.
> > Type a period in front of the existing period and I get a list of
> > other version numbers.
> > When I select the new version it is inserted into the existing version
> > instead of replacing it.
> > <version>1.1.75.5</version>
> > It did work properly in 8.2.
> >
> > Ken Fogel
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
RE: Error updating version in pom.xml
Posted by Kenneth Fogel <kf...@dawsoncollege.qc.ca>.
What I like about 8.2 was that I could explore all the possible versions and either stay with the one I have or switch to a newer or older one. Deleting what's there first 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.
Ken
-----Original Message-----
From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
Sent: July 27, 2018 4:04 PM
To: dev <de...@netbeans.incubator.apache.org>
Subject: Re: Error updating version in pom.xml
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 <kf...@dawsoncollege.qc.ca>
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:
> <version>1.5</version> in any place in a pom.xml.
> Type a period in front of the existing period and I get a list of
> other version numbers.
> When I select the new version it is inserted into the existing version
> instead of replacing it.
> <version>1.1.75.5</version>
> It did work properly in 8.2.
>
> Ken Fogel
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Error updating version in pom.xml
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
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 <kf...@dawsoncollege.qc.ca>
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:
> <version>1.5</version> in any place in a pom.xml.
> Type a period in front of the existing period and I get a list of other
> version numbers.
> When I select the new version it is inserted into the existing version
> instead of replacing it.
> <version>1.1.75.5</version>
> It did work properly in 8.2.
>
> Ken Fogel
>
>
>
Re: Error updating version in pom.xml
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Freitag, den 27.07.2018, 19:55 +0000 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:
> <version>1.5</version> in any place in a pom.xml.
> Type a period in front of the existing period and I get a list of
> other version numbers.
> When I select the new version it is inserted into the existing
> version instead of replacing it.
> <version>1.1.75.5</version>
> It did work properly in 8.2.
the problem is reproducible and happens as described. I think this was
introduced, when xml.text was moved to a newer API.
The suggested fix:
https://github.com/apache/incubator-netbeans/pull/642
I would appreciate a test run.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists