Yes, if anyone can achieve this it will be Robert, Apache Maven PMC Chair. :-) Would be a great way for Maven and NetBeans to work together. Thanks for the info on where he might be able to start Jan. Indeed, the “platform” cluster on our GitHub, would be the first set of modules and there specifically the “openide” modules.
Gj On Tue, 3 Sep 2019 at 08:10, Jan Lahoda <[email protected]> wrote: > Hi Robert, > > I'd recommend to start with platform/openide.util.lookup - the code for it > does not have any dependencies, the group of its test dependencies is > fairly small and self-contained, and the resulting jar is useful by itself. > It also shows what Lazslo mentioned - a semi-circular dependency in test > dependencies. The test dependencies for openide.util.lookup are: > platform/libs.junit4 and harness/nbjunit. platform/libs.junit4 is a plain > wrapped for junit4, that shouldn't be a problem. harness/nbjunit has module > dependencies: harness/o.n.insane, platform/junit4 and > platform/openide.util.lookup and test dependencies: platform/libs.junit4 > (which is unnecessary to mention), platform/openide.util.ui, > platform/openide.util and platform/openide.util.lookup. And I believe all > these modules only have dependencies from this list, so this should be > self-contained. > > Not sure what would be the next step once the openide.util.lookup would > work - possibly have a working platform (i.e. everything under the platform > directory, so that it would actually start), but the issue there is that > the NetBeans modulesystem needs a specific filesystem structure to start. > Here: > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin > > are tasks like: > > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/CreateClusterAppMojo.java > > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/CreateClusterMojo.java > > may be interesting there, although those are not meant to work on the base > platform cluster, I believe, so I'd expect some tweaking there. > > > A completely different approach might be to try to peel off some "leaf" > clusters of modules (those that noone else is depending on them) using the > existing tools above (i.e. depending on existing modules built by Ant, and > "exported" to Maven - there are tools for that already). This might mean > e.g. the apisupport of javafx clusters (directories in the repository). The > main complication there might be that in the main NetBeans code base, tests > directories may have dependencies on other test directories. So, e.g., > tests of apisupport/apisupport.project.ant depend on tests of > platform/openide.util.lookup (and other). So solving this might be tricky, > esp. if openide.util.lookup would not be converted to Maven yet. > > > I am eager to hear what you think/what are your experiences! > > Thanks, > Jan > > > On Mon, Sep 2, 2019 at 11:24 PM Robert Scholte <[email protected]> > wrote: > > > Hi, > > > > this month I'll be giving a training about Maven. The last part of the > > session I want to use to transform existing projects to Maven. > > Since Netbeans is still using Ant, it might be an interesting experiment > > to see if this project can ALSO be built with Maven. > > To increase the chance of success, I'd like to have an ordered list of > > the > > Netbeans "deliverables", starting with the least amount of internal > > dependencies. > > Can anybody provide me such a starting list? > > > > regards, > > Robert Scholte > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > >
