Discussion:
WO Maven getting started
(too old to reply)
Ramsey Gurley
2015-09-11 21:19:41 UTC
Permalink
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here

https://wiki.wocommunity.org/display/WOL/Quick+Start

But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get

Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem

and

Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem

If I simply try to mvn clean package in the project directory, I get

[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]

Can anyone explain why this isn’t working?

Thanks,

Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This em
T Worman
2015-09-11 22:32:46 UTC
Permalink
I have nothing substantive to offer - other than thank you for reminding me why I won’t try this.

You’re brave.

Tim
UCLA GSE&IS
Post by Ramsey Gurley
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to ***@ml
Ramsey Gurley
2015-09-12 00:47:52 UTC
Permalink
The sad thing is, Maven itself seems fairly intuitive. I’ve got it running in eclipse, I’ve downloaded 15000 archetypes from the apache server. Everything seems to work very nicely. Trying to get a WOApp running is the problem.
Post by T Worman
I have nothing substantive to offer - other than thank you for reminding me why I won’t try this.
You’re brave.
Tim
UCLA GSE&IS
Post by Ramsey Gurley
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to uo
Faizel Dakri
2015-09-12 02:15:16 UTC
Permalink
I just tried generating a hello world app using the Quick Start guide and I had to make a couple of changes to the generated POM to get it work:

- In the plugins section, I changed the version of the wolifecycle plugin to 2.1 (I use 2.2.1 for my projects, but 2.1 it seems to work).
- Get rid of the “wonder.classifier" tags in the dependencies section. I don’t think those are used any more.

Try recompiling after that--I think that should get you going. I do have a repository manager sitting between my machine and the wocommunity repos, but since it is pulling the same dependencies, it should work the same for you.

FYI: if you downloaded the archetype-catalog.xml file at the top of the Quick Start page, you will get many older archetype versions in your catalog. You probably want to download the current catalog from the repo directly:

http://maven.wocommunity.org/service/local/repositories/releases/content/org/objectstyle/woproject/maven2/archetypes/2.1/archetypes-2.1-catalog.xml

Good luck.

F

Faizel Dakri
Post by Ramsey Gurley
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/listfez%40dakri.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to
Faizel Dakri
2015-09-12 02:33:07 UTC
Permalink
As to the why it was not working, I believe it was because of the “wonder.classifier” defined in the pom.xml, whose value was set to wo54. That classifier was used to identify different instances of the same dependency, one for WO 5.4 and another for WO 5.3. But I think that classifier is a holdover from earlier versions of Wonder (when WO 5.4 and 5.3 were being used simultaneously) and is no longer used; it seems the archetype that was used to generate the pom.xml is still including it, though.

That said, I can’t explain the missing ERPrototypes artifact in your error message. Perhaps it has something to do with the version of the wolifecycle plugin that was being referenced.

F
--
Faizel Dakri
Post by Ramsey Gurley
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/listfez%40dakri.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net
Fabian Peters
2015-09-12 07:36:49 UTC
Permalink
Hi Ramsey,

First, it seems you're using an old version specification for the wolifecycle plugin, the current being "[2.2.1,)".

The error messages only concern the m2e plugin, not the "real" maven build. The plugin has to be told to ignore the woapplication goal of the wolifecycle plugin. If you select the warning/error entry in the problems view, you should be offered quick-fix solutions that will add the XML boilerplate necessary to achieve this.

If you have a common parent pom, you should be able to add the following section to it and thus have it configured for all child pom files:

<build>
<pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse m2e settings
only. It has no influence on the Maven build itself. -->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>
org.objectstyle.woproject.maven2
</groupId>
<artifactId>
maven-wolifecycle-plugin
</artifactId>
<goals>
<goal>
define-woframework-resources
</goal>
<goal>woframework</goal>
<goal>
define-woapplication-resources
</goal>
<goal>woapplication</goal>
</goals>
<versionRange>[2.2.1,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore></ignore>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>

As for the failure to find ERExtensions, you should check that you have downloaded and installed the settings file referenced in the getting started guide. IMHO step 2 there should not be skipped.

cheers, Fabian
Post by Ramsey Gurley
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to
Henrique Prange
2015-09-13 23:26:17 UTC
Permalink
Ramsey,

The last change to WebObjects Maven plugins were back in 2010. Lots of things changed since then in Maven tooling world. I took the time during the weekend to make the Maven plugin and the Maven archetypes compatible with the current features. I still have to make a release and update the docs. In the meantime, could you try the new archetypes and the new version of the maven-wolifecycle-plugin?

You can add a Remote Catalog using the URL below (Eclipse -> Preferences -> Maven -> Archetypes) to get the new archetypes:

http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml

After that, you can create a new Maven Project using the Eclipse wizard. Select the WOCommunity catalog and include snapshot archetypes. Follow the wizard steps and the new project should be created with no errors. The new archetypes will configure the maven-wolifecycle-plugin version to 2.3-SNAPSHOT.

Let me know if you have any problems.

Cheers,

Henrique
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com
G Brown
2015-09-16 15:41:56 UTC
Permalink
@Ramsey,

I don't want to shock you but the documentation is out of date!

At one time one could create maven projects using eclipse, but that stopped working. The way I now initialize a maven project is using the command line. That always seems to work. Perhaps I can go over the documentation but it will be in 4 to 6 weeks.

@Henrique,

While you are in there working on the archetypes, I do have a suggestion.

If you look at the pom.xml for wonder it contains all kinds of good reusable information. It has the plug-ins, versions, etc. all needed to create the wonder project. But this same information is also needed to create any wonder/WebObjects project. So we see there is a highly reusable part mixed in with a very specific part in the wonder pom.xml. So why not split the pom.xml into a reusable generic WO parent pom.xml and the specific parts to build the wonder project?

I have been doing this and it seems to work well. I use a utility which is described here:

https://github.com/gitgb/splitpom.git

The downside is that the newly created/initialized project needs to have its pom.xml edited as outlined in the github project above. That utility can create the generic reusable parent pom.xml for I think any version of wonder. If the maven archetypes created the initial pom.xml that would work with this or a generic parent pom.xml then people would be using the correct version of plug-ins that would match the same version of plug-ins as used to create wonder.

I think it would be a good move to someday soon re-factor the wonder pom.xml into a highly reusable parent pom.xml and a more specific part to build wonder. This would mean maven users would get all your work on updating the generic parent pom.xml for free! Think of your wonderful karma!

From the auto generated generic pom.xml:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!--
This parent pom was auto generated by splitting the main pom into parent/child poms.
-->
<modelVersion>4.0.0</modelVersion>
<groupId>wonder</groupId>
<artifactId>generic-woparent</artifactId>
<version>5.8.2</version>
<packaging>pom</packaging>
<name>Wonder generic woparent</name>
<description>
Includes the generic woparent pom for all Wonder/WebObjects projects. Has repositories needed, dependency
management, etc. Override in your project's pom when necessary items like distributionManagement.
Sections from the wonder master pom are passed through to create the parent pom. Also, a
wonder.version parameter is created, its value based off the wonder master pom.
</description>
<url>http://wiki.objectstyle.org/confluence/display/WONDER/Home</url>
<properties>
<skip.apple.frameworks xmlns:p="http://maven.apache.org/POM/4.0.0">false</skip.apple.frameworks>
<!--make property skip.apple.frameworks false to include apple jars-->
<wonder.version>5.8.2</wonder.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<webobjects.version>5.4.3</webobjects.version>
</properties>
<build>
…..


These auto generated generic-woparent poms could be inserted into the maven.wocommunity.com repository for all past versions of wonder, which would make past wonder versions work with a new pom generated by a new maven wonder archetype. But who would use an old version of wonder?



G Brown
Post by Fabian Peters
Ramsey,
The last change to WebObjects Maven plugins were back in 2010. Lots of things changed since then in Maven tooling world. I took the time during the weekend to make the Maven plugin and the Maven archetypes compatible with the current features. I still have to make a release and update the docs. In the meantime, could you try the new archetypes and the new version of the maven-wolifecycle-plugin?
http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml
After that, you can create a new Maven Project using the Eclipse wizard. Select the WOCommunity catalog and include snapshot archetypes. Follow the wizard steps and the new project should be created with no errors. The new archetypes will configure the maven-wolifecycle-plugin version to 2.3-SNAPSHOT.
Let me know if you have any problems.
Cheers,
Henrique
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/gsbrown%40umich.edu
Ramsey Gurley
2015-09-17 18:38:47 UTC
Permalink
Hi Henrique,

Thanks for making these updates! It looked like the maven stuff needed some love, and I’m not quite a maven plugin development wizard just yet.

Some progress here. I added the remote archetypes, and created a new maven project with eclipse. I no longer get any red errors in the pom.xml. I tried to Run as WOApplication on Application.java and it crashed on launch. I had to enable the generate bundles to fix that. Now it launches, but I get this error in the console and a blank page where hello world should be:

Sep 17 11:24:16 helloworld[50191] DEBUG NSLog - <com.webobjects.appserver._private.WOComponentDefinition> No template found for component Main at "file:/Users/rgurley/Workspaces/smarthealth/helloworld/".

It seems like it should be looking in

/Users/rgurley/Workspaces/smarthealth/helloworld/build/helloworld.woa/Contents/Resources/Main.wo/

I also get quite a lot of these properties warnings in the console:

Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley

And so on for basically every framework.
Post by Fabian Peters
Ramsey,
The last change to WebObjects Maven plugins were back in 2010. Lots of things changed since then in Maven tooling world. I took the time during the weekend to make the Maven plugin and the Maven archetypes compatible with the current features. I still have to make a release and update the docs. In the meantime, could you try the new archetypes and the new version of the maven-wolifecycle-plugin?
http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml
After that, you can create a new Maven Project using the Eclipse wizard. Select the WOCommunity catalog and include snapshot archetypes. Follow the wizard steps and the new project should be created with no errors. The new archetypes will configure the maven-wolifecycle-plugin version to 2.3-SNAPSHOT.
Let me know if you have any problems.
Cheers,
Henrique
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com
G Brown
2015-09-17 21:27:20 UTC
Permalink
Post by Ramsey Gurley
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
WebObjects works with jar type frameworks; Wonder expects non-jar or file based frameworks, at least er.extensions.foundation.ERXFileUtilities expects them.
So properties contained in Wonder frameworks have to be set in your properties file, as ERXFileUtilities is used often to read the properties.

G Brown
***@umich.edu
Ramsey Gurley
2015-09-17 22:28:16 UTC
Permalink
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?

Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
Post by G Brown
Post by Ramsey Gurley
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
WebObjects works with jar type frameworks; Wonder expects non-jar or file based frameworks, at least er.extensions.foundation.ERXFileUtilities expects them.
So properties contained in Wonder frameworks have to be set in your properties file, as ERXFileUtilities is used often to read the properties.
G Brown
Ramsey Gurley
2015-09-17 23:33:22 UTC
Permalink
Strike the second part of that question. deployment would be war, and those are exploded out, so it presumably would work there.
Post by Ramsey Gurley
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
G Brown
2015-09-18 12:50:55 UTC
Permalink
If you

cd ?../Frameworks then

find . -name Properties -exec cat {} \; >>SuperProperties

you should have all the framework properties in the SuperProperties file, bypassing any Properties issues with jar vs file frameworks.

Also, you may want to use JarResourceRequestHandler to get resources out of jars. Google it. https://gist.github.com/hprange/1068523

You must register it in the main App:

if (isDirectConnectEnabled()) {

registerRequestHandler(new JarResourceRequestHandler(), "wr");

}

I think everybody except Wonder can work with and read properties in jars, so you don’t need to put them as command line arguments.



G Brown
Post by Ramsey Gurley
Strike the second part of that question. deployment would be war, and those are exploded out, so it presumably would work there.
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in
Fabian Peters
2015-09-18 18:12:54 UTC
Permalink
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
I've been ignoring those warnings for years now. Everything seems to work as one would expect…
Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
That's the one thing that I find a bit annoying. To get the debugger to find the source files: <https://wiki.wocommunity.org/display/documentation/Maven+Running+or+Debugging+as+WO+Application> From my experience, you only have to do this for dependencies, not the application itself.
Post by G Brown
Post by Ramsey Gurley
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
WebObjects works with jar type frameworks; Wonder expects non-jar or file based frameworks, at least er.extensions.foundation.ERXFileUtilities expects them.
So properties contained in Wonder frameworks have to be set in your properties file, as ERXFileUtilities is used often to read the properties.
G Brown
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.nar
Ramsey Gurley
2015-09-18 19:02:25 UTC
Permalink
Post by Fabian Peters
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
I've been ignoring those warnings for years now. Everything seems to work as one would expect…
Interesting. Perhaps these properties files only contain commented properties as examples? I know there is at least a one framework (ERPersistentSessionStorage) where the properties file is quite important.
Post by Fabian Peters
Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
That's the one thing that I find a bit annoying. To get the debugger to find the source files: <https://wiki.wocommunity.org/display/documentation/Maven+Running+or+Debugging+as+WO+Application> From my experience, you only have to do this for dependencies, not the application itself.
I was reviewing my old email and saw that you answered this question for me once already. Thanks for both times :D

It didn’t work right away, and I’ve just figured out why. My application pom was wonder.version 6.1.3, but my workspace version on ERExtensions was 6.2-SNAPSHOT. So I needed to update my application pom and add the folders as suggested.

Now that I’ve done that, it stopped at the breakpoint. So if I switch branches, I’ll need to update the wonder.version in all my application pom.xml files?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.
Paul Hoadley
2016-04-28 13:38:09 UTC
Permalink
Hello,

Just resurrecting a thread from seven months ago as I finally bite the Maven bullet and attempt to get my own HelloWorld off the ground…
Post by Ramsey Gurley
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
Post by G Brown
Post by Ramsey Gurley
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
WebObjects works with jar type frameworks; Wonder expects non-jar or file based frameworks, at least er.extensions.foundation.ERXFileUtilities expects them.
So properties contained in Wonder frameworks have to be set in your properties file, as ERXFileUtilities is used often to read the properties.
G Brown
Can I just clarify this issue with Properties by asking a few specific questions?

1. I take it that the usual Properties precedence works as designed for Properties in the application bundle—there are no surprises here, right? It will find Properties, and then Properties.dev in development mode, and Properties.foo for -Duser.name=foo?

2. What are people doing in the real world for framework-level Properties in both development and deployment? This would be a bit of a show-stopper for us—we use framework-level Properties fairly widely, for example to set default values that often don’t need to be overridden at the app level.

Is this a big deal, or is there a straightforward solution?
--
Paul Hoadley
http://logicsquad.net/
Hugi Thordarson
2016-04-28 14:40:58 UTC
Permalink
Just resurrecting a thread from seven months ago as I finally bite the Maven bullet and attempt to get my own HelloWorld off the ground…


Welcome! I finally bit the bullet last month and migrated most of my projects to Maven. Took some patience in the beginning but boy; am I glad I followed through.
So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
Post by G Brown
Post by Ramsey Gurley
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
WebObjects works with jar type frameworks; Wonder expects non-jar or file based frameworks, at least er.extensions.foundation.ERXFileUtilities expects them.
So properties contained in Wonder frameworks have to be set in your properties file, as ERXFileUtilities is used often to read the properties.
G Brown
Can I just clarify this issue with Properties by asking a few specific questions?
1. I take it that the usual Properties precedence works as designed for Properties in the application bundle—there are no surprises here, right? It will find Properties, and then Properties.dev in development mode, and Properties.foo for -Duser.name=foo?
Yes, this works exactly as before, as far as I can tell.
2. What are people doing in the real world for framework-level Properties in both development and deployment? This would be a bit of a show-stopper for us—we use framework-level Properties fairly widely, for example to set default values that often don’t need to be overridden at the app level.
Is this a big deal, or is there a straightforward solution?
Now… Framework Properties seem to work fine for me. I just verified that by creating a Properties file in one of my frameworks with a property, deploying a dependent app and checking the property’s value. Worked fine. Overrode the same property in the application’s Properties file—also works fine.

Not sure why it works for me. Perhaps someone can shed some light on it? I’m using Wonder v. 7.0.0-SNAPSHOT.

Cheers,
- hugi
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in
Paul Hoadley
2016-04-28 23:01:08 UTC
Permalink
Hi Hugi,
Post by Hugi Thordarson
Post by Paul Hoadley
Can I just clarify this issue with Properties by asking a few specific questions?
1. I take it that the usual Properties precedence works as designed for Properties in the application bundle—there are no surprises here, right? It will find Properties, and then Properties.dev in development mode, and Properties.foo for -Duser.name=foo?
Yes, this works exactly as before, as far as I can tell.
Post by Paul Hoadley
2. What are people doing in the real world for framework-level Properties in both development and deployment? This would be a bit of a show-stopper for us—we use framework-level Properties fairly widely, for example to set default values that often don’t need to be overridden at the app level.
Is this a big deal, or is there a straightforward solution?
Now… Framework Properties seem to work fine for me. I just verified that by creating a Properties file in one of my frameworks with a property, deploying a dependent app and checking the property’s value. Worked fine. Overrode the same property in the application’s Properties file—also works fine.
Not sure why it works for me. Perhaps someone can shed some light on it? I’m using Wonder v. 7.0.0-SNAPSHOT.
Thanks for the info Hugi. I haven’t got as far as deploying a test app yet, but that sounds promising.
--
Paul Hoadley
http://logicsquad.net/




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to uo
Paul Hoadley
2016-04-28 23:40:03 UTC
Permalink
Post by Hugi Thordarson
Now… Framework Properties seem to work fine for me. I just verified that by creating a Properties file in one of my frameworks with a property, deploying a dependent app and checking the property’s value. Worked fine. Overrode the same property in the application’s Properties file—also works fine.
Not sure why it works for me. Perhaps someone can shed some light on it? I’m using Wonder v. 7.0.0-SNAPSHOT.
Ah—I thought I was too, but at runtime it was showing 6.1.3. Changing wonder.version to 7.0.0-SNAPSHOT makes all those logged warnings go away. Looking good.
--
Paul Hoadley
http://logicsquad.net/




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to uo
Hugi Thordarson
2015-09-18 10:22:39 UTC
Permalink
Did you find out how to solve the problem of the application not looking for templates at the correct path?

Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!

Cheers,
- hugi
Post by Ramsey Gurley
Hi Henrique,
Thanks for making these updates! It looked like the maven stuff needed some love, and I’m not quite a maven plugin development wizard just yet.
Sep 17 11:24:16 helloworld[50191] DEBUG NSLog - <com.webobjects.appserver._private.WOComponentDefinition> No template found for component Main at "file:/Users/rgurley/Workspaces/smarthealth/helloworld/".
It seems like it should be looking in
/Users/rgurley/Workspaces/smarthealth/helloworld/build/helloworld.woa/Contents/Resources/Main.wo/
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.dev
Sep 17 11:24:16 helloworld[50191] WARN er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar: JavaFoundation - Properties.rgurley
And so on for basically every framework.
Post by Fabian Peters
Ramsey,
The last change to WebObjects Maven plugins were back in 2010. Lots of things changed since then in Maven tooling world. I took the time during the weekend to make the Maven plugin and the Maven archetypes compatible with the current features. I still have to make a release and update the docs. In the meantime, could you try the new archetypes and the new version of the maven-wolifecycle-plugin?
http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml <http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml>
After that, you can create a new Maven Project using the Eclipse wizard. Select the WOCommunity catalog and include snapshot archetypes. Follow the wizard steps and the new project should be created with no errors. The new archetypes will configure the maven-wolifecycle-plugin version to 2.3-SNAPSHOT.
Let me know if you have any problems.
Cheers,
Henrique
So I really desperately want to migrate my projects to Maven. I tried back in May when I had a chance, and failed. I’m trying again now. I can’t get a hello world to compile. I’m starting here
https://wiki.wocommunity.org/display/WOL/Quick+Start <https://wiki.wocommunity.org/display/WOL/Quick+Start>
But from step 5 on, nothing works. I installed the m2e plugin on mars, imported my hello world, and I get
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication (execution: default-woapplication, phase: generate-test-resources) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
and
Plugin execution not covered by lifecycle configuration: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources (execution: default-define-woapplication-resources, phase: validate) pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem
If I simply try to mvn clean package in the project directory, I get
[ERROR] Failed to execute goal on project testing: Could not resolve dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The following artifacts could not be resolved: wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in http://maven.wocommunity.org/content/groups/public-snapshots <http://maven.wocommunity.org/content/groups/public-snapshots> was cached in the local repository, resolution will not be reattempted until the update interval of wocommunity.snapshots has elapsed or updates are forced -> [Help 1]
Can anyone explain why this isn’t working?
Thanks,
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com <https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is
Ramsey Gurley
2015-09-18 16:42:27 UTC
Permalink
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Cheers,
- hugi
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent t
Fabian Peters
2015-09-18 18:08:10 UTC
Permalink
Hi Ramsey,
Post by Ramsey Gurley
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
I've never had a problem with the application not finding component templates. To add the "maven nature" to a project in eclipse, just right-click the project directory and choose "Configure > Convert to Maven Project".

Fabian
Post by Ramsey Gurley
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Cheers,
- hugi
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.n
Ramsey Gurley
2015-09-18 18:23:17 UTC
Permalink
In this case, I’m starting with a maven project by creating it with the erxapplication archetype in eclipse. This is the result I’m getting. I should try again from the command line to see if that makes a difference.

I tried doing exactly this with ERExtensions and ERPrototypes, and it works. I noticed it does not fix up the classpath when I do it and I have to manually remove all the Wonder libraries (ERJars and friends) and just leave the JRE and maven dependencies.
Post by Fabian Peters
Hi Ramsey,
Post by Ramsey Gurley
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
I've never had a problem with the application not finding component templates. To add the "maven nature" to a project in eclipse, just right-click the project directory and choose "Configure > Convert to Maven Project".
Fabian
Post by Ramsey Gurley
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Cheers,
- hugi
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to uoh8@
Hugi Thordarson
2015-09-18 19:40:36 UTC
Permalink
Post by Ramsey Gurley
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
OK. I’m going to try to work this out on this side as well.
Post by Ramsey Gurley
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
For me (apart for similar reasons as yours) it’s that as a java developer, my world depends (bad pun fully intended) on having managed and versioned dependencies. I actually write a lot of code that’s not only intended for consumption within a WO universe. I’ve moved my most used WO projects to Ivy for dependency management (as an addition to Ant) but that feels kind of hacky. Probably because it’s a hack.

The entire modern world is versioned and dependency managed and the old guys can’t just laugh maven off any more as “too complicated". This is the *the* part about WO that doesn’t feel right and makes me feel ashamed to introduce it to new developers.

For this project, I’m more than willing to put in time for creating documentation. Wish I could also contribute to the development part, but I’m pretty thin on knowledge for both Eclipse and Maven plugin development. But if there’s development workings that needs’a’done-ings, I’m pretty willing to learn, so do tell.

- hugi
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkiv
Ramsey Gurley
2015-09-18 22:05:12 UTC
Permalink
So the reason it doesn’t find the main component: It looks like I’m getting a NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.

NSStandardProjectBundle$Factory expects to find

"org.maven.ide.eclipse.maven2Nature".equals(nature)

in the .project natures but my .project has org.eclipse.m2e.core.maven2Nature instead. The last nature on the list is org.objectstyle.wolips.incrementalapplicationnature, which matches

nature.startsWith("org.objectstyle.wolips.”)

So I get a fluffy bunny instead. I modified my .project and added

<nature>org.sonar.ide.eclipse.core.sonarNature</nature> <nature>org.eclipse.m2e.core.maven2Nature</nature> <nature>org.maven.ide.eclipse.maven2Nature</nature>
<nature>org.eclipse.jdt.core.javanature</nature> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>

And now the main component will load. Is this an issue with the .project file in the archetype, or is this something that should instead be updated in the NSStandardProjectBundle$Factory class? It seems if it looked for nature.contains(“maven”) that would be sufficient.

Also, is there some reason there’s no source for ERWebObjects and ERFoundation in the wonder repo? This would have been a lot easier to debug with that.
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
OK. I’m going to try to work this out on this side as well.
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
For me (apart for similar reasons as yours) it’s that as a java developer, my world depends (bad pun fully intended) on having managed and versioned dependencies. I actually write a lot of code that’s not only intended for consumption within a WO universe. I’ve moved my most used WO projects to Ivy for dependency management (as an addition to Ant) but that feels kind of hacky. Probably because it’s a hack.
The entire modern world is versioned and dependency managed and the old guys can’t just laugh maven off any more as “too complicated". This is the *the* part about WO that doesn’t feel right and makes me feel ashamed to introduce it to new developers.
For this project, I’m more than willing to put in time for creating documentation. Wish I could also contribute to the development part, but I’m pretty thin on knowledge for both Eclipse and Maven plugin development. But if there’s development workings that needs’a’done-ings, I’m pretty willing to learn, so do tell.
- hugi
John Huss
2015-09-19 18:27:25 UTC
Permalink
So the reason it doesn’t find the main component: It looks like I’m
getting a NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.
NSStandardProjectBundle$Factory expects to find
"org.maven.ide.eclipse.maven2Nature".equals(nature)
in the .project natures but my .project has
org.eclipse.m2e.core.maven2Nature instead. The last nature on the list is
org.objectstyle.wolips.incrementalapplicationnature, which matches
nature.startsWith("org.objectstyle.wolips.”)
So I get a fluffy bunny instead. I modified my .project and added
<nature>org.sonar.ide.eclipse.core.sonarNature</nature> <nature>org.eclipse.m2e.core.maven2Nature</nature>
*<nature>org.maven.ide.eclipse.maven2Nature</nature>*
<nature>org.eclipse.jdt.core.javanature</nature> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>
And now the main component will load. Is this an issue with the .project
file in the archetype, or is this something that should instead be updated
in the NSStandardProjectBundle$Factory class? It seems if it looked for
nature.contains(“maven”) that would be sufficient.
Also, is there some reason there’s no source for ERWebObjects and
ERFoundation in the wonder repo? This would have been a lot easier to debug
with that.
These were closed source contributions from Apple. Pretty sketchy, but it
is what it is.
Did you find out how to solve the problem of the application not looking
for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace
and import it again as Maven projects. Right now they don’t have the little
M beside them and I suspect that’s part of the problem.
OK. I’m going to try to work this out on this side as well.
Thanks, btw, for starting the discussion and thanks to Henrique for the
work on the software. This is proving immensely useful and I swear, I’m
going to complete my migration to Maven this time!
Same here. If any maven fans are wondering what finally put a fire under
me, I want to use dependency-check-maven and sonarqube. I realize neither
of these things strictly require maven, but it seems they are both much
easier to use in conjunction with maven.
For me (apart for similar reasons as yours) it’s that as a java developer,
my world depends (bad pun fully intended) on having managed and versioned
dependencies. I actually write a lot of code that’s not only intended for
consumption within a WO universe. I’ve moved my most used WO projects to
Ivy for dependency management (as an addition to Ant) but that feels kind
of hacky. Probably because it’s a hack.
The entire modern world is versioned and dependency managed and the old
guys can’t just laugh maven off any more as “too complicated". This is the
*the* part about WO that doesn’t feel right and makes me feel ashamed to
introduce it to new developers.
For this project, I’m more than willing to put in time for creating
documentation. Wish I could also contribute to the development part, but
I’m pretty thin on knowledge for both Eclipse and Maven plugin
development. But if there’s development workings that needs’a’done-ings,
I’m pretty willing to learn, so do tell.
- hugi
Ramsey Gurley
2015-09-28 18:29:18 UTC
Permalink
Now that I’ve gotten a hello world to run, the next step would be to convert existing projects to use maven. It looks like I need to rearrange the project layout. Is there any sort of tool to convert a fluffy bunny to a maven project?

Also, unit testing? Is WOUnit the recommended way to go here?
Post by Ramsey Gurley
So the reason it doesn’t find the main component: It looks like I’m getting a NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.
NSStandardProjectBundle$Factory expects to find
"org.maven.ide.eclipse.maven2Nature".equals(nature)
in the .project natures but my .project has org.eclipse.m2e.core.maven2Nature instead. The last nature on the list is org.objectstyle.wolips.incrementalapplicationnature, which matches
nature.startsWith("org.objectstyle.wolips.”)
So I get a fluffy bunny instead. I modified my .project and added
<nature>org.sonar.ide.eclipse.core.sonarNature</nature> <nature>org.eclipse.m2e.core.maven2Nature</nature> <nature>org.maven.ide.eclipse.maven2Nature</nature>
<nature>org.eclipse.jdt.core.javanature</nature> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>
And now the main component will load. Is this an issue with the .project file in the archetype, or is this something that should instead be updated in the NSStandardProjectBundle$Factory class? It seems if it looked for nature.contains(“maven”) that would be sufficient.
Also, is there some reason there’s no source for ERWebObjects and ERFoundation in the wonder repo? This would have been a lot easier to debug with that.
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
OK. I’m going to try to work this out on this side as well.
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
For me (apart for similar reasons as yours) it’s that as a java developer, my world depends (bad pun fully intended) on having managed and versioned dependencies. I actually write a lot of code that’s not only intended for consumption within a WO universe. I’ve moved my most used WO projects to Ivy for dependency management (as an addition to Ant) but that feels kind of hacky. Probably because it’s a hack.
The entire modern world is versioned and dependency managed and the old guys can’t just laugh maven off any more as “too complicated". This is the *the* part about WO that doesn’t feel right and makes me feel ashamed to introduce it to new developers.
For this project, I’m more than willing to put in time for creating documentation. Wish I could also contribute to the development part, but I’m pretty thin on knowledge for both Eclipse and Maven plugin development. But if there’s development workings that needs’a’done-ings, I’m pretty willing to learn, so do tell.
- hugi
Ramsey Gurley
2015-09-28 22:06:45 UTC
Permalink
Post by Ramsey Gurley
Now that I’ve gotten a hello world to run, the next step would be to convert existing projects to use maven. It looks like I need to rearrange the project layout. Is there any sort of tool to convert a fluffy bunny to a maven project?
Ohhhh, nevermind :)

https://wiki.wocommunity.org/display/documentation/Maven+Kicking+the+tyres+without+changing+your+project+structure?src=search
Post by Ramsey Gurley
Also, unit testing? Is WOUnit the recommended way to go here?
Post by Ramsey Gurley
So the reason it doesn’t find the main component: It looks like I’m getting a NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.
NSStandardProjectBundle$Factory expects to find
"org.maven.ide.eclipse.maven2Nature".equals(nature)
in the .project natures but my .project has org.eclipse.m2e.core.maven2Nature instead. The last nature on the list is org.objectstyle.wolips.incrementalapplicationnature, which matches
nature.startsWith("org.objectstyle.wolips.”)
So I get a fluffy bunny instead. I modified my .project and added
<nature>org.sonar.ide.eclipse.core.sonarNature</nature> <nature>org.eclipse.m2e.core.maven2Nature</nature> <nature>org.maven.ide.eclipse.maven2Nature</nature>
<nature>org.eclipse.jdt.core.javanature</nature> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>
And now the main component will load. Is this an issue with the .project file in the archetype, or is this something that should instead be updated in the NSStandardProjectBundle$Factory class? It seems if it looked for nature.contains(“maven”) that would be sufficient.
Also, is there some reason there’s no source for ERWebObjects and ERFoundation in the wonder repo? This would have been a lot easier to debug with that.
Post by Hugi Thordarson
Did you find out how to solve the problem of the application not looking for templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and import it again as Maven projects. Right now they don’t have the little M beside them and I suspect that’s part of the problem.
OK. I’m going to try to work this out on this side as well.
Post by Hugi Thordarson
Thanks, btw, for starting the discussion and thanks to Henrique for the work on the software. This is proving immensely useful and I swear, I’m going to complete my migration to Maven this time!
Same here. If any maven fans are wondering what finally put a fire under me, I want to use dependency-check-maven and sonarqube. I realize neither of these things strictly require maven, but it seems they are both much easier to use in conjunction with maven.
For me (apart for similar reasons as yours) it’s that as a java developer, my world depends (bad pun fully intended) on having managed and versioned dependencies. I actually write a lot of code that’s not only intended for consumption within a WO universe. I’ve moved my most used WO projects to Ivy for dependency management (as an addition to Ant) but that feels kind of hacky. Probably because it’s a hack.
The entire modern world is versioned and dependency managed and the old guys can’t just laugh maven off any more as “too complicated". This is the *the* part about WO that doesn’t feel right and makes me feel ashamed to introduce it to new developers.
For this project, I’m more than willing to put in time for creating documentation. Wish I could also contribute to the development part, but I’m pretty thin on knowledge for both Eclipse and Maven plugin development. But if there’s development workings that needs’a’done-ings, I’m pretty willing to learn, so do tell.
- hugi
Continue reading on narkive:
Loading...