Ok - I understand your point :)
Just a general advice, if something goes wrong, I'd try to eliminate potential sources of problems, to simply better spot the actual problem. So now, well, it seems Magnolia doesn't really want to work from the Eclipse browser. Is that an issue? Yes. Is it an important/ urgent issue? I wouldn't think so... but if it's important for you.. well, you know the deal ;) As to get the *project* inside eclipse/rad, did you try to generate the eclipse project from maven? That's how we work internally, both with Eclipse and IntelliJ: type mvn idea:idea or mvn eclipse:eclipse from command line, as appropriate. That *should* get you started with a pretty decent/usable ide project. Getting it to *execute* from there is a different story though. And that leads me back to your first thread. Since dms as been moved from the main trunk to modules/ community, it might indeed be causing problems. So if you wanna help in getting this running from Eclipse, I'd advise ignoring dms for a while and get the main Magnolia project running first. Get familiar with maven, you'll probably need to activate a profile or the other. (to get dms back in your project for instance) Please report any issue/progress, we'll happily improve things (the pom, for instance, can probably be improved to help others get started faster with their ide of choice), but in case of issues, try to "slice the meat" to spot the actual problem first ;)

Cheers .. and good luck ;)

g


On 25 Jan 2007, at 20:16, EricCho wrote:

Hi Gregory,

I've been playing with Magnolia intermittently since 3.0 rc1. Originally, I deployed it to a Tomcat server and had some success with the tutorials
and even creating a sample site.
This was in fact a "discovery" project, funded by my employer to determine
if we should be utilizing Magnolia in future projects.
We, as a company, are pro-open source and believe that Magnolia has a lot
to offer and we would in fact utilize this product in future
implementations. We haven't been able to do so yet, but now that I have some free time, I wanted to delve back into the Magnolia realm and perhaps
even be able to contribute code/bug fixes.

My IDE of choice is IBM's Rational Application Developer (v7.0) which is based on the Eclipse 3.2 project. So naturally, I've been trying to get the code base from SVN running off of RAD without any success as you've seen on my earlier post. In the meantime, I've also downloaded the latest war builds (3.0.1) to play with and I know it's probably just as easy to deploy it directly to Tomcat, but my natural instinct is to get it running
through RAD.

So, to answer your question..... I'd like to get the application running from the codebase on RAD/Eclipse so that I can familiarize myself with the
code and possibly help you guys with a bug or two.
And I ran the war build on RAD just because...... I usually do almost
everything through RAD  *shrug*     : )

Regards,
Eric




"Grégory Joseph" <[email protected]>
Sent by: <[email protected]>
25/01/2007 11:41 AM
Please respond to
<[email protected]>


To
<[email protected]>
cc

Subject
Re: [magnolia-user] Samples dialog popup problems?






Eric,

With this thread and your previous one, I'm getting curious: why do
you seem to be trying to run and use Magnolia from/within Eclipse at
all cost, before you're even able to do so in a regular environment?
(i.e executed from a standalone appserver and used from a standalone
webbrowser)

Just curious... :)

g


On Jan 25, 2007, at 19:36 , EricCho wrote:

Well it turns out that this only happens on the Eclipse browser.  I
don't
know why I didn't do it before but I just tried it on an IE browser
and it
works fine.
The jira site is a bit slow for me this morning so I haven't been
able to
do a search for it, but I'll try again later.  If the issue isn't in
there, I'll make sure to create one.


Thanks,
Eric




"David Smith" <[email protected]>
Sent by: <[email protected]>
25/01/2007 09:54 AM
Please respond to
<[email protected]>


To
<[email protected]>
cc

Subject
Re: [magnolia-user] Samples dialog popup problems?






Check the logs for problems.  They should be in the logs directory of
the magnolia app.

--David

EricCho wrote:

I've recently downloaded the 3.0.1 war build and deployed it to
tomcat
5.5.
I wanted to mess around with the samples to famliarize myself with
the
application again.

I've noticed that when I try to edit content and/or create new
content,
the dialogs that popup aren't complete.

For example, on the features page, under the "A very breif history of Magnolia" content, I click on "new". The popup shows up but the only
content is the "OK" and "Cancel" button.  It doesn't show the rest
of the

items like it had back when I originally used 3.0 RC2.

I've looked in Jira and it doesn't seem to be a known issue, so I'm
assuming I missed a step.  Has anyone encountered this as well?

thanks,
Eric


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------




----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to