Hey Branden,

I have no time to look at it just now, the libraries used for the MailFactoryTest have changed.
For now, you can just remove the tests by deleting the following folder:
magnolia-module-mail/src/test

Regards,

Niko,

On Sep 7, 2006, at 8:52 AM, Branden Root wrote:

Niko,


        Running mvn install in the root folder produces this:

Running info.magnolia.cms.mail.MgnlMailFactoryTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.635 sec <<< FAILURE!

Results :
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0

[INFO] ---------------------------------------------------------------------- --
[ERROR] BUILD FAILURE
[INFO] ---------------------------------------------------------------------- --
[INFO] There are test failures.
[INFO] ---------------------------------------------------------------------- --
[INFO] For more information, run Maven with the -e switch
[INFO] ---------------------------------------------------------------------- --
[INFO] Total time: 18 seconds
[INFO] Finished at: Wed Sep 06 16:51:46 PDT 2006
[INFO] Final Memory: 10M/19M
[INFO] ---------------------------------------------------------------------- --


Thanks,

Branden Root
Senior Developer | 206.575.3740
Portent Interactive
An Internet Marketing Agency
http://www.portentinteractive.com




On Sep 6, 2006, at 4:42 PM, Nicolas Modrzyk wrote:

Hey Branden,

To build magnolia, you just type "mvn install" at the root folder, and the resulting war file will be in ${HOME}/magnolia/target/ magnolia-3.0-RC3-SNAPSHOT.war To migrate version, I would recommend, exporting your website from RC2 to XML , building&bootstrapping RC3, and then import the previously exported XML to the new instance. Safest way.

Let us know if you have any problem.

Regards,

Niko

On Sep 7, 2006, at 4:59 AM, Branden Root wrote:

Hello,

We're currently having a problem with magnolia 3.0 RC2, where whenever we enter a URL in the FCK editor, either through source or through the link tool (and even for image tags as well), fck/ magnolia rewrites the source for that URL to include the current content handle. An example: If we enter <a href="http://www.cnn.com";>Cnn.com</a>, magnolia/ fck changes this to: <a href="/page1/page2http:// www.cnn.com">Cnn.com</a>.

Needless to say its a showstopper. I know someone replied earlier on this list and said that the problem was fixed in RC3. If this is true, how do we fix it on our RC2 instance? We tried checking out the latest SVN, grabbing the files in mgnl-resources/ fckeditor, jarring them up and overwriting the existing jar, but this didn't solve anything. Note - checking out the latest svn, then typing mvn war doesn't work to build the latest magnolia.


Any help is greatly appreciated!

Branden Root
Senior Developer | 206.575.3740
Portent Interactive
An Internet Marketing Agency
http://www.portentinteractive.com





----------------------------------------------------------------
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