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 <[email protected]> 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 <[email protected]> > Sent: July 27, 2018 5:03 PM > To: dev <[email protected]> > 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 < > [email protected]> > 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 <[email protected]> > > Sent: July 27, 2018 4:04 PM > > To: dev <[email protected]> > > 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 > > <[email protected] > > > > > 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: [email protected] > > For additional commands, e-mail: > > [email protected] > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
