Hi, Am Mittwoch, den 18.09.2019, 16:59 +0200 schrieb Andreas Sewe: > > (I'm not sure it's not a bug.) > > External libs are detected during manifest parse of module. If > > validationAPI is no more referenced it will not be populated. > > Some others like implementations of nbjavac disappears already in > > the RELEASE90. > > ah, so there is some magic happening that I wasn't aware of. > > > Maybe you can use hardcoded 110 for your usage. > > Yes, I could do that, but depending on an unmaintained(?) library always > makes me slightly nervous. > > Is there any chance that ValidationAPI makes it into NetBeans proper? > It's referenced in "Apache NetBeans Platform for Beginners", so I always > thought it to be a part of NetBeans. Or are licensing issues standing in > the way?
the library is still used in Netbeans 11.1: https://search.maven.org/artifact/org.netbeans.modules/org-netbeans-modules-swing-validation/RELEASE111/jar However, the dependency for the external jar is: <dependency> <groupId>org.netbeans.external</groupId> <artifactId>ValidationAPI</artifactId> <version>RELEASE90</version> </dependency> I'm not deep enough in the process, that creates the maven artifacts, but it might help to find a leed. Greetings Matthias --------------------------------------------------------------------- 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
