Temoving the file:// from the restrictedpath didn't change the result--it still failed. However after inspecting the plugin properties the restrictedpath isn't required so I removed it and was able to build everything. I have no idea if there are side effects from doing this but for now at least it's building. Thanks for everyone's help. If some side effects do pop up, I'll reply to this posting--or if anyone has any other ideas about this. I hate to modify the POM file of the project to get it to compile in case I ever need to do updates...
2009/7/10 Grégory Joseph <[email protected]>: > > I see... > Well if you edit the pom.xml file and replace > <restrictedpath>file://${settings.localRepository}</restrictedpath> > by <restrictedpath>${settings.localRepository}</restrictedpath> > .. the build will work.. but the 2nd taglib (magnolia-taglib-utilities) will > be generated with both the magnolia-taglib-cms and magnolia-taglib-utilities > classes... not exactly sure why. > > On Jul 10, 2009, at 3:41 PM, Ryan Underwood wrote: > >> >> Touche Grégory, I did get an exception when I turned on debugging. >> And I do get a similar error as the other person: >> >> The following mojo encountered an error while executing: >> Group-Id: org.codehaus.xdoclet >> Artifact-Id: maven2-xdoclet2-plugin >> Version: 2.0.7 >> Mojo: xdoclet >> brought in via: POM >> >> While building project: >> Group-Id: info.magnolia >> Artifact-Id: magnolia-taglib-cms >> Version: 4.1 >> From file: >> C:\apps\eclipse\workspace\magnolia-4.1\magnolia-taglib-cms\pom.xml >> Reason: XDoclet plugin failed: Failed to set property restrictedpath >> to file://C:/repository: null >> >> org.picocontainer.PicoInitializationException: Failed to set property >> restrictedpath to file://C:/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) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) >> at >> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) >> at >> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) >> at >> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) >> at >> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) >> at >> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) >> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:31) >> 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) >> ... 28 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) >> ... 33 more >> >> >> >> Error stacktrace: >> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error >> in the plugin manager executing goal >> 'org.codehaus.xdoclet:maven2-xdoclet2-plugin:2.0.7:xdoclet': Mojo >> execution failed. >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) >> at >> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) >> at >> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) >> at >> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) >> at >> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) >> at >> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) >> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:31) >> Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo >> execution failed. >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) >> ... 20 more >> Caused by: org.apache.maven.plugin.MojoExecutionException: XDoclet >> plugin failed: Failed to set property restrictedpath to >> file://C:/repository: null >> at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:260) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) >> ... 21 more >> Caused by: org.picocontainer.PicoInitializationException: Failed to >> set property restrictedpath to file://C:/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) >> ... 22 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) >> ... 28 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) >> ... 33 more >> >> >> Building it from the command line (mvn) produces the same error. I've >> deleted 'org' from my repository, that didn't change anything; I >> deleted my repository and recreated it, that did the same thing. I'm >> fairly new to Maven so it's likely that I've configured something >> wrong or there's an issue with the XDoclet plugin. I am using a >> barebones settings.xml with only the additional repository mentioned >> before. The XDoclet plugin I have configured in eclipse is 1.2.1 I >> think, but that shouldn't matter for this considering it fails with a >> command line build outside of eclipse. >> >> 2009/7/10 Grégory Joseph <[email protected]>: >>> >>> Sorry Ryan, I hadn't seen this specific message. >>> Where's the output coming from here ? Could you try simply building from >>> a >>> regular command shell ? It might even be helpful to do so with the -X >>> flag >>> to get more debug output. >>> >>> (just try to build from the magnolia-taglib-cms folder) >>> >>> Cheers, >>> >>> -g >>> >>> On Jul 9, 2009, at 7:19 PM, Ryan Underwood wrote: >>> >>>> >>>> I added that repository to my maven. I am still getting an error. I >>>> also tried moving my repository from 'Documents and Settings' to avoid >>>> the " " in the file path. Here is what I'm still getting...any ideas? >>>> Thanks >>>> >>>> [INFO] [enforcer:enforce] >>>> [INFO] [2-xdoclet2:xdoclet] >>>> [INFO] >>>> [INFO] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] magnolia-project ...................................... SUCCESS >>>> [1:52.625s] >>>> [INFO] magnolia-core ......................................... SUCCESS >>>> [6:38.094s] >>>> [INFO] magnolia-jaas ......................................... SUCCESS >>>> [2.937s] >>>> [INFO] magnolia-gui .......................................... SUCCESS >>>> [6.547s] >>>> [INFO] magnolia-module-exchange-simple ....................... SUCCESS >>>> [14.594s] >>>> [INFO] magnolia-module-templating ............................ SUCCESS >>>> [11.281s] >>>> [INFO] magnolia-module-admininterface ........................ SUCCESS >>>> [15.172s] >>>> [INFO] magnolia-module-mail .................................. SUCCESS >>>> [23.110s] >>>> [INFO] magnolia-module-workflow .............................. SUCCESS >>>> [1:35.500s] >>>> [INFO] magnolia-module-cache ................................. SUCCESS >>>> [32.109s] >>>> [INFO] CMS Tag Library ....................................... FAILED >>>> [4:41.484s] >>>> [INFO] CMS Utility Tag Library ............................... NOT BUILT >>>> [INFO] magnolia-module-fckeditor ............................. NOT BUILT >>>> [INFO] magnolia-module-samples ............................... NOT BUILT >>>> [INFO] magnolia-empty-webapp ................................. NOT BUILT >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] >>>> >>>> The following mojo encountered an error while executing: >>>> Group-Id: org.codehaus.xdoclet >>>> Artifact-Id: maven2-xdoclet2-plugin >>>> Version: 2.0.7 >>>> Mojo: xdoclet >>>> brought in via: POM >>>> >>>> While building project: >>>> Group-Id: info.magnolia >>>> Artifact-Id: magnolia-taglib-cms >>>> Version: 4.1 >>>> From file: >>>> C:\apps\eclipse\workspace\magnolia-4.1\magnolia-taglib-cms\pom.xml >>>> Reason: XDoclet plugin failed: Failed to set property restrictedpath >>>> to file://C:/repository: null >>>> >>>> >>>> >>>> On Thu, Jul 9, 2009 at 10:15 AM, Jan >>>> Haderka<[email protected]> wrote: >>>>> >>>>> You can find maven2-xdoclet2-plugin 2.0.7 in our repo >>>>> >>>>> >>>>> http://repo.magnolia-cms.com/m2/org/codehaus/xdoclet/maven2-xdoclet2-plugin/2.0.7-20090592-magnolia/ >>>>> >>>>> Jan >>>>> >>>>> On Thu, 2009-07-09 at 09:55 -0400, Ryan Underwood wrote: >>>>>> >>>>>> I can't seem to find a release of maven2-xdoclet2-plugin version >>>>>> 2.0.7. I downloaded 2.0.5 and added it to my maven repository but >>>>>> like I said, the 2.0.7 doesn't seem to be found anywhere... >>>>>> And I did delete and redownload things. I'm using the Community >>>>>> Edition tag of 4.1 (26146) >>>>>> Thanks >>>>>> >>>>>> On Thu, Jul 9, 2009 at 9:11 AM, Jan >>>>>> Haderka<[email protected]> wrote: >>>>>>> >>>>>>> I believe the original author "solved" the issue by deleting checked >>>>>>> out >>>>>>> content and checking out everything again. You might want to give it >>>>>>> a >>>>>>> try, tho I have no explanation as to what could be missing or >>>>>>> corrupted >>>>>>> when checking out things for the first time. I was unable to >>>>>>> reproduce >>>>>>> the problem myself. >>>>>>> >>>>>>> HTH, >>>>>>> Jan >>>>>>> >>>>>>> On Thu, 2009-07-09 at 05:47 -0700, Ryan Underwood wrote: >>>>>>>> >>>>>>>> I'm having the same problem...anyone that was having this problem >>>>>>>> make >>>>>>>> this >>>>>>>> work? >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> >>>>>>> Jan Haderka >>>>>>> Magnolia International Ltd. >>>>>>> >>>>>>> Meet us at the Magnolia Conference >>>>>>> http:/www.magnolia-cms.com/conference >>>>>>> >>>>>>> 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]> >>>>>>> ---------------------------------------------------------------- >>>>>>> >>>>>>> >>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> 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 >>>>> Magnolia International Ltd. >>>>> >>>>> Meet us at the Magnolia Conference >>>>> http:/www.magnolia-cms.com/conference >>>>> >>>>> 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]> >>>>> ---------------------------------------------------------------- >>>>> >>>>> >>>> >>>> ---------------------------------------------------------------- >>>> 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]> >>> ---------------------------------------------------------------- >>> >>> >> >> ---------------------------------------------------------------- >> 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]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
