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 <[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 > > >
