Hi,

I skipped the tests and I removed all the dependencies from all other modules. 
I stopped getting the exceptions related to test-jar. But now I am getting the 
following error:
What can I do now!?

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] XDoclet plugin failed: Failed to set property restrictedpath to 
file://C:\Users\kaaljabr\.m2\repository: null

The filename, directory name, or volume label syntax is incorrect
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: XDoclet plugin failed: 
Failed to set property restrictedpath to 
file://C:\Users\kaaljabr\.m2\repository: null
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: XDoclet plugin 
failed: Failed to set property restrictedpath to 
file://C:\Users\kaaljabr\.m2\repository: null
        at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:260)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        ... 17 more
Caused by: org.picocontainer.PicoInitializationException: Failed to set 
property restrictedpath to file://C:\Users\kaaljabr\.m2\repository: null
        at 
org.picocontainer.defaults.BeanPropertyComponentAdapter.getComponentInstance(BeanPropertyComponentAdapter.java:79)
        at 
org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)
        at 
org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfTypeWithContainerAdaptersLast(DefaultPicoContainer.java:377)
        at 
org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:347)
        at 
org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(LifecycleContainerBuilder.java:52)
        at 
org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(LifecycleContainerBuilder.java:45)
        at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:251)
        ... 19 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.picocontainer.defaults.BeanPropertyComponentAdapter.getComponentInstance(BeanPropertyComponentAdapter.java:77)
        ... 25 more
Caused by: java.io.IOException: The filename, directory name, or volume label 
syntax is incorrect
        at java.io.WinNTFileSystem.canonicalize0(Native Method)
        at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
        at java.io.File.getCanonicalPath(File.java:559)
        at 
org.generama.defaults.QDoxPlugin.setRestrictedpath(QDoxPlugin.java:43)
        ... 30 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 42 seconds
[INFO] Finished at: Wed Dec 01 18:27:21 GST 2010
[INFO] Final Memory: 147M/762M
[INFO] ------------------------------------------------------------------------



-----Original Message-----
From: Kareem AlJabr
Sent: Wednesday, December 01, 2010 6:06 PM
To: Magnolia User-List
Subject: RE: [magnolia-user] Magnolia setup

Hi,

I have skipped checkstyle check and tests when running the build thru Maven and 
I ended up with the below error:
=========================================================================================
[INFO] Failed to resolve artifact.

Missing:
----------
1) info.magnolia:magnolia-core:test-jar:tests:4.5.1-SNAPSHOT

  Try downloading the file manually from:
      http://sourceforge.net/projects/magnolia/files/

  Then, install it using the command:
      mvn install:install-file -DgroupId=info.magnolia 
-DartifactId=magnolia-core -Dversion=4.5.1-SNAPSHOT -Dclassifier=tests 
-Dpackaging=test-jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=info.magnolia -DartifactId=magnolia-core 
-Dversion=4.5.1-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) info.magnolia:magnolia-gui:jar:4.5.1-SNAPSHOT
        2) info.magnolia:magnolia-core:test-jar:tests:4.5.1-SNAPSHOT

----------
1 required artifact is missing.
==========================================================================================
I guess magnolia-core:test-jar is required because it was not built due to 
skipping the test.  But if I don’t exclude the test I get into this error 
please guys help me in this matter, 
==========================================================================================
2010-12-01 18:05:08,427 WARN  info.magnolia.module.InstallContextImpl           
: > boo !
2010-12-01 18:05:08,427 ERROR info.magnolia.module.InstallContextImpl           
: > hoolala
java.lang.Exception: booh-ooh!
        at 
info.magnolia.module.ui.ModuleManagerWebUITest.doTestTemplate(ModuleManagerWebUITest.java:162)
        at 
info.magnolia.module.ui.ModuleManagerWebUITest.testRestartNeededTemplate(ModuleManagerWebUITest.java:144)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at junit.framework.TestCase.runTest(TestCase.java:164)
        at junit.framework.TestCase.runBare(TestCase.java:130)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:120)
        at junit.framework.TestSuite.runTest(TestSuite.java:230)
        at junit.framework.TestSuite.run(TestSuite.java:225)
        at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
        at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
        at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
        at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)

==========================================================================================



-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Zdenek Skodik
Sent: Wednesday, December 01, 2010 12:12 PM
To: Magnolia User-List
Subject: RE: [magnolia-user] Magnolia setup


Hi Kareem,

mvn clean install -Dcheckstyle.skip=true

-zdenek



On Wed, 2010-12-01 at 10:52 +0400, Kareem AlJabr wrote:
>
>
> Hi,
>
> Thanks for the reply.
>
>
>
> How to disable checkstyle check when running the command mvn clean install, 
> that’s the way I actually run the mvn build for magnolia.
>
>
>
> Thanks,
>
> Kareem Jabr
>
>
>
>
>
>
>
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Jan Haderka
> Sent: Monday, November 29, 2010 6:40 PM
> To: Magnolia User-List
> Subject: Re: [magnolia-user] Magnolia setup
>
>
>
>
> Hi Kareem,
>
> if checkstyle is the only problem you should be able to disable it. It is 
> relevant only to the developers of MAgnolia who should try to fix all the 
> checkstyle issues to improve generated javadoc, but not to you if you just 
> want to build magnolia yourself.
>
>
>
>
>
> 4.4 branch is in making so it is possible that there are some problems, but 
> the 4.3 should be fine.
>
>
>
>
>
> Also to run Magnolia in the Eclipse you should not need to checkout the 
> sources. You can just define your own webapp (<packaging>war</packaging>) 
> project in maven and make it dependent on magnolia-bundle-webapp (or 
> enterprise-webapp or empty-webapp).
>
>
>
>
>
> HTH,
>
>
> Jan
>
>
>
>
>
>
>
> On Nov 29, 2010, at 3:26 PM, Kareem AlJabr wrote:
>
>
>
>
> Hi,
>
>
>
>
>
> I tried following  
> (http://wiki.magnolia-cms.com/display/DEV/Eclipse#Eclipse-SetuptheServer%28Tomcat%29)
>  to complete the setup Magnolia on Eclipse-Helios. I followed all the steps. 
> When I build the project in eclipse I provide clean install as goals, the 
> build works fine then fails in magnolia-core in the test suite doSimpleTest I 
> guess was the name of the class. When I  skipped the test, but then build 
> fails saying 160 checkstyle errors. I was trying on Magnolia community 
> edition 4.4 then I tried 4.3 but with the same errors.
>
>
>
>
>
> Could anyone please let me know where can I find a good documentation 
> explaining exactly how this can be done. BTW I tried doing it outside the 
> eclipse I checked out the files using tortoise, I also ended up with some 
> other issues.
>
>
>
>
>
> Thanks
>
>
>
>
>
>
> ______________________________________________________________________
> Disclaimer:
> This email and any attachments may contain confidential and/or privileged 
> information. If you are not the intended recipient (or have received this 
> e-mail in error) please notify the sender immediately by email and destroy 
> this email. Any unauthorized copying, dissemination, disclosure or 
> distribution of the material in this email is strictly forbidden.
> Unless expressly stated to the contrary, the sender of this email is not 
> authorized by MBC to make any representations, negotiations or enter into any 
> agreement on behalf of MBC. This e-mail message and any attached files have 
> been scanned for the presence of computer viruses. However, it is the 
> responsibility of the recipient to ensure that it is virus free; we accept no 
> responsibility for any loss or damage arising in any way from its use.
>
>
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
>
>
> -
>
>
> Best regards,
>
>
>
>
>
> Jan Haderka, PhD.
>
>
> Magnolia International Ltd.
>
>
> http://www.magnolia-cms.com
>
>
>
>
>
> http://twitter.com/magnolia_cms
>
>
> http://facebook.com/Magnolia
>
>
> --------------------------------------
>
>
> Magnolia®  - Simple Open-Source Content Management
>
>
>
>
>
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
>
> ______________________________________________________________________
>
> Disclaimer:
> This email and any attachments may contain confidential and/or privileged 
> information. If you are not the intended recipient (or have received this 
> e-mail in error) please notify the sender immediately by email and destroy 
> this email. Any unauthorized copying, dissemination, disclosure or 
> distribution of the material in this email is strictly forbidden.
> Unless expressly stated to the contrary, the sender of this email is not 
> authorized by MBC to make any representations, negotiations or enter into any 
> agreement on behalf of MBC. This e-mail message and any attached files have 
> been scanned for the presence of computer viruses. However, it is the 
> responsibility of the recipient to ensure that it is virus free; we accept no 
> responsibility for any loss or damage arising in any way from its use.
>
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------


________________________________________Disclaimer:
This email and any attachments may contain confidential and/or privileged 
information. If you are not the intended recipient (or have received this 
e-mail in error) please notify the sender immediately by email and destroy this 
email. Any unauthorized copying, dissemination, disclosure or distribution of 
the material in this email is strictly forbidden.
Unless expressly stated to the contrary, the sender of this email is not 
authorized by MBC to make any representations, negotiations or enter into any 
agreement on behalf of MBC. This e-mail message and any attached files have 
been scanned for the presence of computer viruses. However, it is the 
responsibility of the recipient to ensure that it is virus free; we accept no 
responsibility for any loss or damage arising in any way from its 
use.________________________________________



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to