Summary: modern maven requires secure HTTPS

I haven’t figured out all my ant -> maven conversion issues but wanted to summarize one finding. Newer maven installations require HTTPS (with an “S” for “secure”) for your connections to things such as the wocommunity repos. It wasn’t always this way and following community tutorials you mig

Re: Maven build - no main bundle name

Hi Markus, I'm still getting a similar error when I do "mvn build" from terminal -> [ERROR] Unresolveable build extension: Plugin org.wocommunity:wolifecycle-maven-plugin:2.6-SNAPSHOT or one of its dependencies could not be resolved I'm referring to the 2.6-SNAPSHOT from the pom.xml file like

Re: Maven build - no main bundle name

as its a snapshot, its here https://maven.wocommunity.org/content/repositories/snapshots/org/wocommunity/wolifecycle-maven-plugin/2.6-SNAPSHOT/ 2.6 has some small but important changes (at least to me) Markus > Am 29.07.2024 um 18:47 schrieb Aaron Rosenzweig : > > Hi Markus, > > The latest

Re: Maven build - no main bundle name

Hi Markus, The latest I see is 2.5 for the lifecycle plugin here: https://mvnrepository.com/artifact/org.wocommunity/wolifecycle-maven-plugin Where is 2.6? > On Jul 29, 2024, at 12:45 PM, Aaron Rosenzweig wrote: >

Re: Maven build - no main bundle name

Thanks Markus, I was using this to refer to the plugin: org.wocommunity wolifecycle-maven-plugin 2.5 true true I’ll try 2.6-SNAPSHOT :-) > On Jul 29, 2024, at 12:17 PM, Markus Stoll, junidas GmbH > wrote: > > you should use

Re: Maven build - no main bundle name

you should use version 2.6-SNAPSHOT for wolifecycle-maven-plugin, which is the current one and do you refer to the wocommunity repository for obtaining the plugin? I strongly suggest to first fix the maven standalone build. Once this is building and running, do a new import as maven project int

Re: Maven build - no main bundle name

Inside the WO app’s folder from terminal I tried: mvn build It says: Unresolveable build extension: Plugin org.wocommunity:wolifecycle-maven-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.wocommunity:wolifecycle-maven-plugin:jar:2.5: Th

Re: Maven build - no main bundle name

Hi Markus thanks for the quick reply! Good question, I don’t know. I haven’t run from command line, hadn’t done it with Ant and also haven’t tried it with Maven. It’s an interesting idea to try if I can figure it out. Maybe it will show a difference that leads to discovery. > On Jul 29, 2024,

Re: Maven build - no main bundle name

Hi Aaron, I did the very thing just recently without any problems does the maven build run outside eclipse (standalone)? So does the problem occur only when started from eclipse? Regards Markus > Am 29.07.2024 um 17:49 schrieb Aaron Rosenzweig via Webobjects-dev > : > > Hi, > > I’m trying t

Maven build - no main bundle name

Hi, I’m trying to convert an ANT based webobjects application into a Maven build. At the moment It’s building in Eclipse without errors but when I try to launch within the Eclipse environment I get errors due to not finding the main bundle. Specifically the following call inside of ERXApplicat