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.
On Sep 18, 2015, at 12:40 PM, Hugi Thordarson <[email protected]> wrote:
>>> 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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
