What version of maven are you running? So, If I call: mvn archetype:generate -DarchetypeGroupId=org.apache.training -DarchetypeArtifactId=content-archetype -DarchetypeVersion=1.3.0 (which now works as I released the artifacts)
I see that I’m using archetype in version 3.3.0 So, if I run: mvn --version I see that I’m using Maven 3.9.9 Chris Von: Craig Russell <[email protected]> Datum: Donnerstag, 3. Oktober 2024 um 15:57 An: [email protected] <[email protected]> Betreff: Re: Now what after cloning Hi Chris, The biggest technical issue seems to be that somehow the ancient plugin is being called by the mvn setup. I don't have anything configured in my mvn setup but the plugin is: org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-4 This looks like it has been around since 2006. What component needs this plugin? > On Oct 3, 2024, at 01:24, Christofer Dutz <[email protected]> wrote: > > Yeah I guess a dedicated f2f training session works be perfect.... Hmmmmm... > Should I apply for one of the lightning talks? (I know it's not about > presenting slides... But nobody mentioned you couldn't create slides :-)) I think there is no presentation computer at the light talks... Craig > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > ________________________________ > From: Craig Russell <[email protected]> > Sent: Wednesday, October 2, 2024 10:00:36 PM > To: [email protected] <[email protected]> > Subject: Re: Now what after cloning > > I'm still a bit lost. > > The reason I started thinking that I'd put my first presentation in a totally > separate place is that I thought it would be easier if I could see the entire > presentation from source to binary result. I could select which parts of > existing presentations to use and copy or link to them. > > Is this a good approach? > > I looked at the Apache/Training/Presentations linked below and I could not > really understand the structure. > > A pointer to the "if you're new to this stuff read this" will help. The > README.md and HOWTO.md didn't give me enough of a high level perspective. > > I guess I'll have to jump on a f2f in Denver to sort this. > > Craig > > >> On Sep 30, 2024, at 07:24, Christofer Dutz <[email protected]> wrote: >> >> Hi Craig, >> >> So this is an example of a collection of presentation directory: >> https://github.com/apache/incubator-training/tree/develop/content/Apache/Training >> Usually they have no “src” directory and if you have a look at the pom.xml >> inside, they have a “packaging =pom”. >> >> A presentation directory would be something like this: >> https://github.com/apache/incubator-training/tree/develop/content/Apache/Training/Presentations >> It has the “src” directory and the pom.xml says: “packaging=war” >> >> Hope that helps. >> >> Chris >> >> Von: Craig Russell <[email protected]> >> Datum: Montag, 30. September 2024 um 14:53 >> An: [email protected] <[email protected]> >> Betreff: Re: Now what after cloning >> Hi Christofer, >> >>> Simply go to a directory where you want to add the new presentation. >>> If you want o add it to apache training, go to the directory where you want >>> to create it, but make sure it’s not a presentation directory, but a >>> collection of presentation module, as the archetype plugin will add the new >>> presentation to the overall build and that only works in non-presentation >>> directories. >> >> Can you give an example of a "presentation directory" and a "collection of >> presentation modules"? I'm still orienting to the layout of the project and >> don't quite understand the terminology yet. >> >> I created a brand new local directory. The results are below. >> >> And my local copy of incubator-training has no branches except develop. The >> other branches are in GitHub but I don't know how to get them here. I used >> GitHub Desktop to clone the repo but it did not automatically clone the >> branches. >> >> >> Thanks, >> Craig >> >> >> If you want o add it to apache training, go to the directory where you want >> to create it, but make sure it’s not a presentation directory, but a >> collection of presentation module, as the archetype plugin will add the new >> presentation to the overall build and that only works in non-presentation >> directories. >> [MacBook-Pro-10:~/apache/2024-coc-experiment] clr% mvn archetype:generate >> -DarchetypeGroupId=org.apache.training >> -DarchetypeArtifactId=content-archetype -DarchetypeVersion=1.3.0-SNAPSHOT -X >> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) >> Maven home: /Users/clr/apache-maven-3.8.6 >> Java version: 11.0.18, vendor: Oracle Corporation, runtime: >> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "12.7.6", arch: "x86_64", family: "mac" >> [DEBUG] Created new class realm maven.api >> [DEBUG] Importing foreign packages into class realm maven.api >> [DEBUG] Imported: javax.annotation.* < plexus.core >> [DEBUG] Imported: javax.annotation.security.* < plexus.core >> [DEBUG] Imported: javax.inject.* < plexus.core >> [DEBUG] Imported: org.apache.maven.* < plexus.core >> [DEBUG] Imported: org.apache.maven.artifact < plexus.core >> [DEBUG] Imported: org.apache.maven.classrealm < plexus.core >> [DEBUG] Imported: org.apache.maven.cli < plexus.core >> [DEBUG] Imported: org.apache.maven.configuration < plexus.core >> [DEBUG] Imported: org.apache.maven.exception < plexus.core >> [DEBUG] Imported: org.apache.maven.execution < plexus.core >> [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core >> [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core >> [DEBUG] Imported: org.apache.maven.model < plexus.core >> [DEBUG] Imported: org.apache.maven.monitor < plexus.core >> [DEBUG] Imported: org.apache.maven.plugin < plexus.core >> [DEBUG] Imported: org.apache.maven.profiles < plexus.core >> [DEBUG] Imported: org.apache.maven.project < plexus.core >> [DEBUG] Imported: org.apache.maven.reporting < plexus.core >> [DEBUG] Imported: org.apache.maven.repository < plexus.core >> [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core >> [DEBUG] Imported: org.apache.maven.settings < plexus.core >> [DEBUG] Imported: org.apache.maven.toolchain < plexus.core >> [DEBUG] Imported: org.apache.maven.usability < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core >> [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core >> [DEBUG] Imported: org.codehaus.classworlds < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.* < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.component < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.container < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.context < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < >> plexus.core >> [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException >> < plexus.core >> [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < >> plexus.core >> [DEBUG] Imported: org.eclipse.aether.* < plexus.core >> [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core >> [DEBUG] Imported: org.eclipse.aether.collection < plexus.core >> [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core >> [DEBUG] Imported: org.eclipse.aether.graph < plexus.core >> [DEBUG] Imported: org.eclipse.aether.impl < plexus.core >> [DEBUG] Imported: org.eclipse.aether.installation < plexus.core >> [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core >> [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core >> [DEBUG] Imported: org.eclipse.aether.repository < plexus.core >> [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core >> [DEBUG] Imported: org.eclipse.aether.spi < plexus.core >> [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core >> [DEBUG] Imported: org.eclipse.aether.version < plexus.core >> [DEBUG] Imported: org.fusesource.jansi.* < plexus.core >> [DEBUG] Imported: org.slf4j.* < plexus.core >> [DEBUG] Imported: org.slf4j.event.* < plexus.core >> [DEBUG] Imported: org.slf4j.helpers.* < plexus.core >> [DEBUG] Imported: org.slf4j.spi.* < plexus.core >> [DEBUG] Populating class realm maven.api >> [INFO] Error stacktraces are turned on. >> [DEBUG] Message scheme: color >> [DEBUG] Message styles: debug info warning error success failure strong mojo >> project >> [DEBUG] Reading global settings from >> /Users/clr/apache-maven-3.8.6/conf/settings.xml >> [DEBUG] Reading user settings from /Users/clr/.m2/settings.xml >> [DEBUG] Reading global toolchains from >> /Users/clr/apache-maven-3.8.6/conf/toolchains.xml >> [DEBUG] Reading user toolchains from /Users/clr/.m2/toolchains.xml >> [DEBUG] Using local repository at /Users/clr/.m2/repository >> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for >> /Users/clr/.m2/repository >> [INFO] Scanning for projects... >> [DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1: >> (none) >> [DEBUG] Looking up lifecycle mappings for packaging pom from >> ClassRealm[plexus.core, parent: null] >> [DEBUG] Resolving plugin prefix archetype from [org.apache.maven.plugins, >> org.codehaus.mojo] >> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for >> apache.snapshots (http://repository.apache.org/snapshots). >> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for >> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). >> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for >> codehaus.org (http://snapshots.repository.codehaus.org). >> [DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml >> in local (/Users/clr/.m2/repository) >> [DEBUG] Skipped remote request for >> org.apache.maven.plugins/maven-metadata.xml, locally cached metadata >> up-to-date >> [DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in >> local (/Users/clr/.m2/repository) >> [DEBUG] Skipped remote request for org.codehaus.mojo/maven-metadata.xml, >> locally cached metadata up-to-date >> [DEBUG] Resolved plugin prefix archetype to >> org.apache.maven.plugins:maven-archetype-plugin from repository central >> [DEBUG] Could not find metadata >> org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml in local >> (/Users/clr/.m2/repository) >> [DEBUG] Skipped remote request for >> org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml, locally >> cached metadata up-to-date >> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for >> apache.snapshots (http://svn.apache.org/maven-snapshot-repository). >> [DEBUG] Resolved plugin version for >> org.apache.maven.plugins:maven-archetype-plugin to 1.0-alpha-4 from >> repository central (https://repo.maven.apache.org/maven2, default, releases) >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 0.264 s >> [INFO] Finished at: 2024-09-30T05:44:01-07:00 >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Could not find goal 'generate' in plugin >> org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-4 among available >> goals create-from-project, create -> [Help 1] >> org.apache.maven.plugin.MojoNotFoundException: Could not find goal >> 'generate' in plugin >> org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-4 among available >> goals create-from-project, create >> at >> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor >> (DefaultMavenPluginManager.java:292) >> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor >> (DefaultBuildPluginManager.java:244) >> at >> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor >> (MojoDescriptorCreator.java:239) >> at >> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments >> (DefaultLifecycleTaskSegmentCalculator.java:104) >> at >> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments >> (DefaultLifecycleTaskSegmentCalculator.java:83) >> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute >> (LifecycleStarter.java:89) >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294) >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) >> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960) >> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293) >> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196) >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke >> (NativeMethodAccessorImpl.java:62) >> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke >> (DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke (Method.java:566) >> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced >> (Launcher.java:282) >> at org.codehaus.plexus.classworlds.launcher.Launcher.launch >> (Launcher.java:225) >> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode >> (Launcher.java:406) >> at org.codehaus.plexus.classworlds.launcher.Launcher.main >> (Launcher.java:347) >> [ERROR] >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, please >> read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoNotFoundException >> [MacBook-Pro-10:~/apache/2024-coc-experiment] clr% >> >> >>> On Sep 30, 2024, at 03:35, Christofer Dutz <[email protected]> >>> wrote: >>> >>> Simply go to a directory where you want to add the new presentation. >>> If you want o add it to apache training, go to the directory where you want >>> to create it, but make sure it’s not a presentation directory, but a >>> collection of presentation module, as the archetype plugin will add the new >>> presentation to the overall build and that only works in non-presentation >>> directories. >>> >>> If you want to create a completely detached presentation, just go to the >>> directory you want to create it in. >>> >>> Then run: >>> >>> mvn archetype:generate -DarchetypeGroupId=org.apache.training >>> -DarchetypeArtifactId=content-archetype -DarchetypeVersion=1.3.0-SNAPSHOT >>> >>> As soon as the release is out, that will become: >>> >>> mvn archetype:generate -DarchetypeGroupId=org.apache.training >>> -DarchetypeArtifactId=content-archetype -DarchetypeVersion=1.3.0 >>> >>> Hope that helps. >>> >>> Chris >>> >>> >>> Von: Craig Russell <[email protected]> >>> Datum: Montag, 30. September 2024 um 04:13 >>> An: [email protected] <[email protected]> >>> Betreff: Now what after cloning >>> I've successfully used GitHub Desktop to clone the incubator-training repo >>> and built using mvn clean install. >>> >>> So, where do I create a new presentation? >>> Where and how can I present an existing presentation? I see lots of >>> material but not sure where to go from here... >>> >>> I only have one branch locally: develop. Are there other branches I should >>> be looking at? How do I get them? >>> >>> Thanks, >>> Craig >>> >>> Craig L Russell >>> [email protected] >> >> Craig L Russell >> [email protected] > > Craig L Russell > [email protected] > Craig L Russell [email protected]
