Re: WOLips + Maven
Re: WOLips + Maven
- Subject: Re: WOLips + Maven
- From: Gintautas Sulskus <email@hidden>
- Date: Tue, 09 Oct 2012 19:53:11 +0100
Thanks for reply, G :)
My .project is identical to yours.
.classpath looks like this:
<classpath>
<classpathentry kind="src" output="bin" path="Sources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="bin"/>
</classpath>
Where MAVEN2_CLASSPATH_CONTAINER contains all references to the lib in the form of absolute path:
/Users/User/.m2/repository/...
Comparing both log files I see on a maven project:
1. Many entries of:
- Can't get path when run as jar: ERCoolComponents - Properties
- Can't get path when run as jar: ERCoolComponents - Properties.dev
- Can't get path when run as jar: ERCoolComponents - Properties.ginga
2. <com.webobjects.foundation.NSBundle> warning: There is already a unique instance for Bundle named 'JavaWebObjects' at the path + '/Users/User/.m2/repository/com/webobjects/JavaWebObjects/5.4.3/JavaWebObjects-5.4.3.jar'. Skipping the version located at '/System/Library/Frameworks/JavaWebObjects.framework'.
On Tue, Oct 9, 2012 at 6:30 PM, G Brown
<email@hidden> wrote:
Hi,
Eclipse has a .project file. If you just bring in a maven project into Eclispse, it is lacking some info about the project.
Specifically, your project build section should look something like:
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
</arguments>
</buildCommand>
<buildCommand>
<name>org.objectstyle.wolips.incrementalbuilder</name>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.m2e.core.maven2Builder</name>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.m2e.core.maven2Nature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.objectstyle.wolips.incrementalframeworknature</nature>
</natures>
I am guessing you are missing some org.objectstyle.wolips.incrementalbuilder stuff. I went through this.
Check/edit your .project file.
I would make a run config for it, the default run config should work after eclipse knows what kind of project you have.
On Oct 9, 2012, at 11:46 AM, Gintautas Sulskus wrote:
Hello everyone,
I've posted this message in wonder-disc group already, but Lachlan Deck suggested this group is more active.
Hopefully you don't mind for re-posting.
QUESTION_1.
I wanted to ask you, is it possible to have a working combination
of WOLips and Maven3 for development and deployment?
I have 2 projects. The only difference between them is the classpath:
1st (OLD), working project, has references to WOFramework/* WebObjects/Wonder framework and custom jar entries.
2nd (NEW), problematic project, has got only jar entries for everything.
What I want to achieve is:
1. dependency management in pom.xml
- OK (everything rests in Maven repos)
2. "Existing Maven project" import to Eclipse
- OK (imports and builds without errors)
3. building woapplication with maven
- OK (builds and runs)
4. development from Eclipse
- DOESN'T WORK
QUESTION_2.
Should I also include my WebObjects/Wonder projects in run conf? WOLips properties file points to their location though.
Not sure where to start looking for mistakes. Advices are very appreciated!
Thanks!
Best Regards,
Gintas
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
This email sent to email@hidden
--
Best Regards,
Gintautas Sulskus
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden