3.0.2 POM broken?? Could you elaborate?
jcr-1.0.jar is not "missing". Licensing issues prevent it from being
made available via a public maven repository. If you follow the advice
of the maven error, it's easy to install in your local repository.
On the second issue, I'm not entirely sure what your question is. I
have filed a bug report indicating 'mvn package' from the magnolia
subproject really builds 3.0.2, not 3.0.3-SNAPSHOT which is what the
rest of the branch builds. If you'd like to hack the build, edit the
pom.xml of the magnolia subproject and update all the version 3.0.2 to
3.0.3-SNAPSHOT. That's what I'm doing until it's fixed.
--David
Michael Beaty wrote:
Ivar
The 3.0.2 POM appears to be broken, and only partially fixed in the
3.0.3 branch.
First of all, as noted in the bug reports, the jcr-1.0.jar is still
missing.
Second, and more seriously, the magnolia project is not built anymore.
In the 3.0.3 branch version, you can at least go into the magnolia
project and build it seperately (mvn clean install, then mvn
eclipse:eclipse) and get it into Eclipse.
Is there a resident Maven expert in the house?
-Michael Beaty
Senior Software Engineer
LeapFrog Enterprises
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: April 5, 2007 1:40 AM
To: [email protected]
Subject: [magnolia-user] Developing with Eclipse WTP
Dear Magnolians!
I've been using magnolia for quite a while now... and it is impressive
peace of software, but>
I have a question 4 u who managed to work it out in Eclipse WTP.
Basically, I have no problem building magnolia from svn, almost all the
releases (trunk, tag and branches) but somehow I have missed to set this
up and running within Eclipse.
I have followed all the steps from all kinds of sources (wiki,
sourceforge...) and still have no luck of getting it work as Dynamic Web
project (DWP). I have tried almost everything (except shooting my
head) to manage it. The only way to make it is to copy all the sources
under NEW dynamic web projects, setting same configs etc but this is not
I was planning to do.
When I checkout all the sources from SVN it builds nicely with mvn,
creating eclipse project files, but not for the 'magnolia' project dir
to be recognized as dynamic web project (DWP). Sometimes when it works
unfortunatelly it runs with magnolia***.jars in the classpath not
subproject sources, therefore no changes in subproject sources are
reflected on the running instance of tomcat. (all versions of WTP1.0
-1.5.3 and tomcat 5.5> were tested, win, mac and linux platform, sun jdk
1.5 & 1.6).
Somewhere I have read that mvn should be setup to be external tool for
building, but that failed for me too.
I simply don't know how to correctly set up magnolia to use all
subproject sources within eclipse so I could stay bound to magnolia SVN.
Maven mvn -Dwtpversion1.5 eclipse:eclipse fails to generate eclipse
project files for magnolia project (ex. magnolia-project) so it can be
run on the server. Furthermore, there are differences between different
releases of WTP 1.x - 1.5.
What are the exact steps of configuring this as I get frustrated day by
day. I know that this process should be straightforward but it is not.
I hope someone could help sorting this out.
Thank you and greetings from Iceland
Ivar
p.s. does anyone have eclipse .classpath, .project files and .settings
folder under magnolia DWP that actually works with mulitiple subprojects
as this is the actual missing puzzle in all this IMHO. :-)
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
