You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Eddy D. Sanchez" <ed...@gmail.com> on 2007/03/22 04:50:40 UTC
The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version could be found
Hello, I'm new on list.
I'm trying to install jasperserver, with: mvn -e install
but I've got an error with xdoclet-plugin, someone can explainme
about this or how to correct it??
thanks.
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Jasper Server
[INFO] Jasper Server API
[INFO] Jasper Server API - Common
[INFO] Jasper Server API - Metadata Interfaces
[INFO] Jasper Server API - Engine
[INFO] Jasper Server API Implementations - Common
[INFO] Jasper Server API Implementations - All
[INFO] Jasper Server API Implementations - Metadata
[INFO] Jasper Server API Implementations - Engine
[INFO] JasperServer Jar for Webapp
[INFO] JasperServer Common Webapp
[INFO] JasperServer Web application
[INFO] JasperServer Web Services Webapp
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/pom.xml to /
var/root/.m2/repository/com/jaspersoft/jasperserver/server/0.9.2/
server-0.9.2.pom
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/pom.xml to /var/root/.m2/repository/com/jaspersoft/
jasperserver/jasperserver-api/0.9.2/jasperserver-api-0.9.2.pom
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API - Common
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/common/target/jasperserver-api-common-0.9.2.jar
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/common/target/jasperserver-api-common-0.9.2.jar to /
var/root/.m2/repository/com/jaspersoft/jasperserver/api/common/
jasperserver-api-common/0.9.2/jasperserver-api-common-0.9.2.jar
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API - Metadata Interfaces
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/metadata/target/jasperserver-api-metadata-0.9.2.jar
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/metadata/target/jasperserver-api-metadata-0.9.2.jar
to /var/root/.m2/repository/com/jaspersoft/jasperserver/api/metadata/
jasperserver-api-metadata/0.9.2/jasperserver-api-metadata-0.9.2.jar
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API - Engine
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/engine/target/jasperserver-api-engine-0.9.2.jar
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api/engine/target/jasperserver-api-engine-0.9.2.jar to /
var/root/.m2/repository/com/jaspersoft/jasperserver/api/engine/
jasperserver-api-engine/0.9.2/jasperserver-api-engine-0.9.2.jar
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API Implementations - Common
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api-impl/common/target/jasperserver-api-common-
impl-0.9.2.jar
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api-impl/common/target/jasperserver-api-common-
impl-0.9.2.jar to /var/root/.m2/repository/com/jaspersoft/
jasperserver/api/common/impl/jasperserver-api-common-impl/0.9.2/
jasperserver-api-common-impl-0.9.2.jar
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API Implementations - All
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /usr/src/jasperintel/jasperserver/trunk/
jasperserver-api-impl/pom.xml to /var/root/.m2/repository/com/
jaspersoft/jasperserver/jasperserver-api-impl/0.9.2/jasperserver-api-
impl-0.9.2.pom
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Jasper Server API Implementations - Metadata
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or
no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version
could be found
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin
(DefaultLifecycleExecutor.java:1286)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl
e(DefaultLifecycleExecutor.java:1221)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:987)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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:585)
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.version.PluginVersionNotFoundException: The
plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid
version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:228)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:90)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin
(DefaultPluginManager.java:161)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin
(DefaultLifecycleExecutor.java:1257)
... 17 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Wed Mar 21 23:35:29 BOT 2007
[INFO] Final Memory: 7M/13M
[INFO]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version could be found
Posted by Wayne Fay <wa...@gmail.com>.
On 3/21/07, Wendy Smoak <ws...@gmail.com> wrote:
> Looking around a bit, I found a page that explains how to build it.
> It looks like there's a considerable amount of setup involved:
>
Understatement of the year... That's rather amazing!
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version could be found
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/21/07, Eddy D. Sanchez <ed...@gmail.com> wrote:
> Thanks for your answer Wendy, I'm trying to install on Mac OSX 10.4.9
> and there is no binary installers for this OS.
>
> I read these install guide and following its instructions, I download
> the source code with
> svn co https://svn.sourceforge.net/svnroot/jasperintel jasperintel
That seems to be old... for some reason they have version jasperserver
0.9.2 sitting on the trunk. The latest version appears to be 1.2.0,
for which there is a platform independent binary distribution
available here:
http://sourceforge.net/project/showfiles.php?group_id=162962&package_id=195243
I don't know anything about this project, but I'd try the binary (even
without an installer) before I would try to build it myself.
Try asking on their support forums if you need more help:
http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=listcat&catid=1
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version could be found
Posted by "Eddy D. Sanchez" <ed...@gmail.com>.
Thanks for your answer Wendy, I'm trying to install on Mac OSX 10.4.9
and there is no binary installers for this OS.
I read these install guide and following its instructions, I download
the source code with
svn co https://svn.sourceforge.net/svnroot/jasperintel jasperintel
but it doesn't work, I have these error, and I can't fix it.
Thank you for all.
On Mar 22, 2007, at 12:36 AM, Wendy Smoak wrote:
> On 3/21/07, Eddy D. Sanchez <ed...@gmail.com> wrote:
>
>> I'm trying to install jasperserver, with: mvn -e install
>> but I've got an error with xdoclet-plugin, someone can explainme
>> about this or how to correct it??
>
> Just to clarify, are you trying to build this project from source for
> some reason, or do you just want to install it and use it?
>
> The best source of information for building it from source would be
> the development team for that project. Ask on their development list
> or forum, and someone familiar with the project should be able to
> help.
>
> Looking around a bit, I found a page that explains how to build it.
> It looks like there's a considerable amount of setup involved:
>
> http://jasperforge.org/sf/wiki/do/viewPage/
> projects.jasperintelligence/wiki/V0.9.2SourceCodeBuildGuide
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The plugin 'xdoclet:maven2-xdoclet2-plugin' does not exist or no valid version could be found
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/21/07, Eddy D. Sanchez <ed...@gmail.com> wrote:
> I'm trying to install jasperserver, with: mvn -e install
> but I've got an error with xdoclet-plugin, someone can explainme
> about this or how to correct it??
Just to clarify, are you trying to build this project from source for
some reason, or do you just want to install it and use it?
The best source of information for building it from source would be
the development team for that project. Ask on their development list
or forum, and someone familiar with the project should be able to
help.
Looking around a bit, I found a page that explains how to build it.
It looks like there's a considerable amount of setup involved:
http://jasperforge.org/sf/wiki/do/viewPage/projects.jasperintelligence/wiki/V0.9.2SourceCodeBuildGuide
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Emmanuel Venisse <em...@venisse.net>.
Jason van Zyl a écrit :
>
> On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
>
>> I think we'll need to modify more report plugins with the same patch
>>
>
> No, I should just put the HtmlTools back and deprecate it.
>
> I didn't know people were pulling out core utilities, but not
> surprising. I'll restore the original location.
ok, cool. I think it's a better solution.
Emmanuel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Jason van Zyl <ja...@maven.org>.
On 24 Mar 07, at 1:03 PM 24 Mar 07, Henning P. Schmiedehausen wrote:
> Jason van Zyl <ja...@maven.org> writes:
>
> But then plugins needing to build ids need a dependency on the xhtml
> module. Is that better? And link/anchor generation is needed for
> e.g. pdf, too.
Then it should be put into the appropriate sink with a method to have
that work.
>
> Providing this functionality would IMHO be the job of the core of a
> system, not one of the components.
Writing anchors for a specific type of output is the concern of the
module producing the output.
Jason.
>
> Best regards
> Henning
>
>
>> On 22 Mar 07, at 7:28 PM 22 Mar 07, Henning P. Schmiedehausen wrote:
>
>>> Jason van Zyl <ja...@maven.org> writes:
>>>
>>>> On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
>>>
>>>>> I think we'll need to modify more report plugins with the same
>>>>> patch
>>>>>
>>>
>>>> No, I should just put the HtmlTools back and deprecate it.
>>>
>>>> I didn't know people were pulling out core utilities, but not
>>>> surprising. I'll restore the original location.
>>>
>>> And how are plugins supposed to generate the same link
>>> information as
>>> the Doxia core? That is the reason why that patch went in there
>>> in the
>>> first place.
>>>
>>> There was a change in the way Doxia created attributes on the pages
>>> and Plugins which reference these attributes (e.g. html anchors)
>>> suddently broke.
>>>
>>> At least in my understanding, you provide a class that offers this
>>> functionality in a central place and let both pieces (Doxia and the
>>> plugins) reference it so that the next change will not break this
>>> again.
>>>
>>> Just deprecating the class and saying "do no longer use it" is IMHO
>>> not the right way to go.
>>>
>
>> It needs to go into the module where it belongs. It should not be
>> used from its current location as it doesn't belong there.
>
>> it belongs in the xhtml module.
>
>>> Best regards
>>> Henning
>>>
>>>
>>>
>>>
>>>
>>>> Jason.
>>>
>>>>> Emmanuel
>>>>>
>>>>> Emmanuel Venisse a écrit :
>>>>>> Fixed.
>>>>>> Wendy Smoak a écrit :
>>>>>>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>>>>>>
>>>>>>>> All is fixed, but I can't deploy doxia because files are in
>>>>>>>> read
>>>>>>>> mode for group.
>>>>>>>> Jason, can you fix it?
>>>>>>>
>>>>>>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>>>>>>> problem in the Changes plugin:
>>>>>>>
>>>>>>> ERROR] BUILD FAILURE
>>>>>>> [INFO]
>>>>>>> ----------------------------------------------------------------
>>>>>>> --
>>>>>>> --
>>>>>>> ----
>>>>>>> [INFO] Compilation failure
>>>>>>>
>>>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>>>> maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>>>>>> package org.apache.maven.doxia.module does not exist
>>>>>>>
>>>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>>>> maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>>>>>> cannot find symbol
>>>>>>> symbol : variable HtmlTools
>>>>>>> location: class
>>>>>>> org.apache.maven.plugin.changes.ChangesReportGenerator
>>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> --
>>>>>> --
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> --
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>
>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --
>>> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE,
>>> Linux, |gls
>>> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache
>>> person |eau
>>> Open Source Consulting, Development, Design | Velocity - Turbine
>>> guy |rwc
>>>
>>> |m k
>>> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
>>> 7350 |a s
>>> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
>>> Schmiedehausen |n
>>>
>>> "Save the cheerleader. Save the world."
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE,
> Linux, |gls
> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache
> person |eau
> Open Source Consulting, Development, Design | Velocity - Turbine
> guy |rwc
>
> |m k
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
> 7350 |a s
> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
> Schmiedehausen |n
>
> "Save the cheerleader. Save the world."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Jason van Zyl <ja...@maven.org> writes:
But then plugins needing to build ids need a dependency on the xhtml
module. Is that better? And link/anchor generation is needed for
e.g. pdf, too.
Providing this functionality would IMHO be the job of the core of a
system, not one of the components.
Best regards
Henning
>On 22 Mar 07, at 7:28 PM 22 Mar 07, Henning P. Schmiedehausen wrote:
>> Jason van Zyl <ja...@maven.org> writes:
>>
>>> On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
>>
>>>> I think we'll need to modify more report plugins with the same patch
>>>>
>>
>>> No, I should just put the HtmlTools back and deprecate it.
>>
>>> I didn't know people were pulling out core utilities, but not
>>> surprising. I'll restore the original location.
>>
>> And how are plugins supposed to generate the same link information as
>> the Doxia core? That is the reason why that patch went in there in the
>> first place.
>>
>> There was a change in the way Doxia created attributes on the pages
>> and Plugins which reference these attributes (e.g. html anchors)
>> suddently broke.
>>
>> At least in my understanding, you provide a class that offers this
>> functionality in a central place and let both pieces (Doxia and the
>> plugins) reference it so that the next change will not break this
>> again.
>>
>> Just deprecating the class and saying "do no longer use it" is IMHO
>> not the right way to go.
>>
>It needs to go into the module where it belongs. It should not be
>used from its current location as it doesn't belong there.
>it belongs in the xhtml module.
>> Best regards
>> Henning
>>
>>
>>
>>
>>
>>> Jason.
>>
>>>> Emmanuel
>>>>
>>>> Emmanuel Venisse a �crit :
>>>>> Fixed.
>>>>> Wendy Smoak a �crit :
>>>>>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>>>>>
>>>>>>> All is fixed, but I can't deploy doxia because files are in read
>>>>>>> mode for group.
>>>>>>> Jason, can you fix it?
>>>>>>
>>>>>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>>>>>> problem in the Changes plugin:
>>>>>>
>>>>>> ERROR] BUILD FAILURE
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------
>>>>>> --
>>>>>> ----
>>>>>> [INFO] Compilation failure
>>>>>>
>>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>>> maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>>>>> package org.apache.maven.doxia.module does not exist
>>>>>>
>>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>>> maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>>>>> cannot find symbol
>>>>>> symbol : variable HtmlTools
>>>>>> location: class
>>>>>> org.apache.maven.plugin.changes.ChangesReportGenerator
>>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> --
>> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE,
>> Linux, |gls
>> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache
>> person |eau
>> Open Source Consulting, Development, Design | Velocity - Turbine
>> guy |rwc
>>
>> |m k
>> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
>> 7350 |a s
>> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
>> Schmiedehausen |n
>>
>> "Save the cheerleader. Save the world."
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Jason van Zyl <ja...@maven.org>.
On 22 Mar 07, at 7:28 PM 22 Mar 07, Henning P. Schmiedehausen wrote:
> Jason van Zyl <ja...@maven.org> writes:
>
>> On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
>
>>> I think we'll need to modify more report plugins with the same patch
>>>
>
>> No, I should just put the HtmlTools back and deprecate it.
>
>> I didn't know people were pulling out core utilities, but not
>> surprising. I'll restore the original location.
>
> And how are plugins supposed to generate the same link information as
> the Doxia core? That is the reason why that patch went in there in the
> first place.
>
> There was a change in the way Doxia created attributes on the pages
> and Plugins which reference these attributes (e.g. html anchors)
> suddently broke.
>
> At least in my understanding, you provide a class that offers this
> functionality in a central place and let both pieces (Doxia and the
> plugins) reference it so that the next change will not break this
> again.
>
> Just deprecating the class and saying "do no longer use it" is IMHO
> not the right way to go.
>
It needs to go into the module where it belongs. It should not be
used from its current location as it doesn't belong there.
it belongs in the xhtml module.
> Best regards
> Henning
>
>
>
>
>
>> Jason.
>
>>> Emmanuel
>>>
>>> Emmanuel Venisse a écrit :
>>>> Fixed.
>>>> Wendy Smoak a écrit :
>>>>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>>>>
>>>>>> All is fixed, but I can't deploy doxia because files are in read
>>>>>> mode for group.
>>>>>> Jason, can you fix it?
>>>>>
>>>>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>>>>> problem in the Changes plugin:
>>>>>
>>>>> ERROR] BUILD FAILURE
>>>>> [INFO]
>>>>> ------------------------------------------------------------------
>>>>> --
>>>>> ----
>>>>> [INFO] Compilation failure
>>>>>
>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>> maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>>>> package org.apache.maven.doxia.module does not exist
>>>>>
>>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>>> maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>>>> cannot find symbol
>>>>> symbol : variable HtmlTools
>>>>> location: class
>>>>> org.apache.maven.plugin.changes.ChangesReportGenerator
>>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE,
> Linux, |gls
> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache
> person |eau
> Open Source Consulting, Development, Design | Velocity - Turbine
> guy |rwc
>
> |m k
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
> 7350 |a s
> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
> Schmiedehausen |n
>
> "Save the cheerleader. Save the world."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Jason van Zyl <ja...@maven.org> writes:
>On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
>> I think we'll need to modify more report plugins with the same patch
>>
>No, I should just put the HtmlTools back and deprecate it.
>I didn't know people were pulling out core utilities, but not
>surprising. I'll restore the original location.
And how are plugins supposed to generate the same link information as
the Doxia core? That is the reason why that patch went in there in the
first place.
There was a change in the way Doxia created attributes on the pages
and Plugins which reference these attributes (e.g. html anchors)
suddently broke.
At least in my understanding, you provide a class that offers this
functionality in a central place and let both pieces (Doxia and the
plugins) reference it so that the next change will not break this
again.
Just deprecating the class and saying "do no longer use it" is IMHO
not the right way to go.
Best regards
Henning
>Jason.
>> Emmanuel
>>
>> Emmanuel Venisse a �crit :
>>> Fixed.
>>> Wendy Smoak a �crit :
>>>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>>>
>>>>> All is fixed, but I can't deploy doxia because files are in read
>>>>> mode for group.
>>>>> Jason, can you fix it?
>>>>
>>>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>>>> problem in the Changes plugin:
>>>>
>>>> ERROR] BUILD FAILURE
>>>> [INFO]
>>>> --------------------------------------------------------------------
>>>> ----
>>>> [INFO] Compilation failure
>>>>
>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>> maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>>> package org.apache.maven.doxia.module does not exist
>>>>
>>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>>> maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>>> cannot find symbol
>>>> symbol : variable HtmlTools
>>>> location: class
>>>> org.apache.maven.plugin.changes.ChangesReportGenerator
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Jason van Zyl <ja...@maven.org>.
On 22 Mar 07, at 11:56 AM 22 Mar 07, Emmanuel Venisse wrote:
> I think we'll need to modify more report plugins with the same patch
>
No, I should just put the HtmlTools back and deprecate it.
I didn't know people were pulling out core utilities, but not
surprising. I'll restore the original location.
Jason.
> Emmanuel
>
> Emmanuel Venisse a écrit :
>> Fixed.
>> Wendy Smoak a écrit :
>>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>>
>>>> All is fixed, but I can't deploy doxia because files are in read
>>>> mode for group.
>>>> Jason, can you fix it?
>>>
>>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>>> problem in the Changes plugin:
>>>
>>> ERROR] BUILD FAILURE
>>> [INFO]
>>> --------------------------------------------------------------------
>>> ----
>>> [INFO] Compilation failure
>>>
>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>> maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>> package org.apache.maven.doxia.module does not exist
>>>
>>> /home/continuum/working-directory/8/src/main/java/org/apache/
>>> maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>> cannot find symbol
>>> symbol : variable HtmlTools
>>> location: class
>>> org.apache.maven.plugin.changes.ChangesReportGenerator
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Emmanuel Venisse <em...@venisse.net>.
I think we'll need to modify more report plugins with the same patch
Emmanuel
Emmanuel Venisse a écrit :
> Fixed.
>
> Wendy Smoak a écrit :
>> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>>
>>> All is fixed, but I can't deploy doxia because files are in read mode
>>> for group.
>>> Jason, can you fix it?
>>
>> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
>> problem in the Changes plugin:
>>
>> ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Compilation failure
>>
>> /home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>>
>> package org.apache.maven.doxia.module does not exist
>>
>> /home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>>
>> cannot find symbol
>> symbol : variable HtmlTools
>> location: class org.apache.maven.plugin.changes.ChangesReportGenerator
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Emmanuel Venisse <em...@venisse.net>.
Fixed.
Wendy Smoak a écrit :
> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>
>> All is fixed, but I can't deploy doxia because files are in read mode
>> for group.
>> Jason, can you fix it?
>
> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
> problem in the Changes plugin:
>
> ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> /home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[22,37]
>
> package org.apache.maven.doxia.module does not exist
>
> /home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[188,60]
>
> cannot find symbol
> symbol : variable HtmlTools
> location: class org.apache.maven.plugin.changes.ChangesReportGenerator
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Andrew Williams <an...@handyande.co.uk>.
+1 very useful for sane defaults to be around, and I think maven is
the right context to have them set.
Andy
On 22 Mar 2007, at 14:54, Jason van Zyl wrote:
>
> On 22 Mar 07, at 10:41 AM 22 Mar 07, Daniel Kulp wrote:
>
>> On Thursday 22 March 2007 10:28, Jason van Zyl wrote:
>>> Sure, once I'm done with some 2.0.6 stuff I finish off Doxia
>>> stuff. I
>>> might look at the Wagon permissions because it's becoming
>>> infinitely
>>> irritating. I have several settings.xml files for testing various
>>> things and, of course, the one I used didn't have the perm entries.
>>> Geronimo keeps running into this over and over as well.
>>
>> Yea!!!
>>
>> Seriously, we ended up putting a cron job on our internal
>> repository that
>> every 15 minutes goes through and resets all the permissions to
>> something sane. I got too fed up with developers not setting things
>> correctly. I kind of decided it was easier to let them just do the
>> wrong thing and have a process that automatically fixes it.
>>
>
> I am thinking that we leave Wagon policy agnostic and I'll just
> push the change into Maven so that it pops in some sane defaults.
> These are the policies that we want for Maven deployment. Not
> everyone using Wagon may want this set by default but I think it's
> a sensible default for Maven deployments.
>
> Jason.
>
>> --
>> J. Daniel Kulp
>> Principal Engineer
>> IONA
>> P: 781-902-8727 C: 508-380-7194
>> daniel.kulp@iona.com
>> http://www.dankulp.com/blog
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Jason van Zyl <ja...@maven.org>.
On 22 Mar 07, at 10:41 AM 22 Mar 07, Daniel Kulp wrote:
> On Thursday 22 March 2007 10:28, Jason van Zyl wrote:
>> Sure, once I'm done with some 2.0.6 stuff I finish off Doxia stuff. I
>> might look at the Wagon permissions because it's becoming
>> infinitely
>> irritating. I have several settings.xml files for testing various
>> things and, of course, the one I used didn't have the perm entries.
>> Geronimo keeps running into this over and over as well.
>
> Yea!!!
>
> Seriously, we ended up putting a cron job on our internal
> repository that
> every 15 minutes goes through and resets all the permissions to
> something sane. I got too fed up with developers not setting things
> correctly. I kind of decided it was easier to let them just do the
> wrong thing and have a process that automatically fixes it.
>
I am thinking that we leave Wagon policy agnostic and I'll just push
the change into Maven so that it pops in some sane defaults. These
are the policies that we want for Maven deployment. Not everyone
using Wagon may want this set by default but I think it's a sensible
default for Maven deployments.
Jason.
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday 22 March 2007 10:28, Jason van Zyl wrote:
> Sure, once I'm done with some 2.0.6 stuff I finish off Doxia stuff. I
> might look at the Wagon permissions because it's becoming infinitely
> irritating. I have several settings.xml files for testing various
> things and, of course, the one I used didn't have the perm entries.
> Geronimo keeps running into this over and over as well.
Yea!!!
Seriously, we ended up putting a cron job on our internal repository that
every 15 minutes goes through and resets all the permissions to
something sane. I got too fed up with developers not setting things
correctly. I kind of decided it was easier to let them just do the
wrong thing and have a process that automatically fixes it.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Jason van Zyl <ja...@maven.org>.
On 22 Mar 07, at 8:44 AM 22 Mar 07, Wendy Smoak wrote:
> On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
>
>> All is fixed, but I can't deploy doxia because files are in read
>> mode for group.
>> Jason, can you fix it?
>
Sure, once I'm done with some 2.0.6 stuff I finish off Doxia stuff. I
might look at the Wagon permissions because it's becoming infinitely
irritating. I have several settings.xml files for testing various
things and, of course, the one I used didn't have the perm entries.
Geronimo keeps running into this over and over as well.
I haven't done any report testing, but I'll find the nice coupling
cases and binary incompatibilities. The internal utility code
shouldn't be used outside Doxia, but looks like I'l have to deprecate
that class. It's unfortunate it's coupled to doxia's core.
> Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
> problem in the Changes plugin:
>
> ERROR] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Compilation failure
>
> /home/continuum/working-directory/8/src/main/java/org/apache/maven/
> plugin/changes/ChangesReportGenerator.java:[22,37]
> package org.apache.maven.doxia.module does not exist
>
> /home/continuum/working-directory/8/src/main/java/org/apache/maven/
> plugin/changes/ChangesReportGenerator.java:[188,60]
> cannot find symbol
> symbol : variable HtmlTools
> location: class org.apache.maven.plugin.changes.ChangesReportGenerator
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/22/07, Emmanuel Venisse <em...@venisse.net> wrote:
> All is fixed, but I can't deploy doxia because files are in read mode for group.
> Jason, can you fix it?
Thanks. Your Doxia change fixed 'mvn site' but now I'm seeing a
problem in the Changes plugin:
ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[22,37]
package org.apache.maven.doxia.module does not exist
/home/continuum/working-directory/8/src/main/java/org/apache/maven/plugin/changes/ChangesReportGenerator.java:[188,60]
cannot find symbol
symbol : variable HtmlTools
location: class org.apache.maven.plugin.changes.ChangesReportGenerator
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Emmanuel Venisse <em...@venisse.net>.
All is fixed, but I can't deploy doxia because files are in read mode for group.
Jason, can you fix it?
Emmanuel
Wendy Smoak a écrit :
> On 3/21/07, Wendy Smoak <ws...@gmail.com> wrote:
>
>> Reported on the user list, and I just got a failure notice with the
>> same error from my Continuum instance when it tried 'mvn clean site'
>> on the site module.
>>
>> The site plugin won't build, at least not with the deployed Doxia
>> snapshots:
>
> Also being discussed on http://jira.codehaus.org/browse/MSITE-218
>
> After building Doxia, the maven-site-plugin will now compile, but I
> get a test error:
>
> -------------------------------------------------------------------------------
>
> Test set: org.apache.maven.plugins.site.SiteMojoTest
> -------------------------------------------------------------------------------
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.11 sec
> <<< FAI
> LURE!
> testGetInterpolatedSiteDescriptorContent(org.apache.maven.plugins.site.SiteMojoT
>
> est) Time elapsed: 0.046 sec <<< ERROR!
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.PlexusContainer.initialize()V
> at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:119)
> at
> org.apache.maven.plugin.testing.AbstractMojoTestCase.setUp(AbstractMojoTestCase.java:62)
>
> at junit.framework.TestCase.runBare(TestCase.java:125)
> 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:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
>
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
>
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
>
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j
> ava:747)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/21/07, Wendy Smoak <ws...@gmail.com> wrote:
> Reported on the user list, and I just got a failure notice with the
> same error from my Continuum instance when it tried 'mvn clean site'
> on the site module.
>
> The site plugin won't build, at least not with the deployed Doxia snapshots:
Also being discussed on http://jira.codehaus.org/browse/MSITE-218
After building Doxia, the maven-site-plugin will now compile, but I
get a test error:
-------------------------------------------------------------------------------
Test set: org.apache.maven.plugins.site.SiteMojoTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.11 sec <<< FAI
LURE!
testGetInterpolatedSiteDescriptorContent(org.apache.maven.plugins.site.SiteMojoT
est) Time elapsed: 0.046 sec <<< ERROR!
java.lang.NoSuchMethodError: org.codehaus.plexus.PlexusContainer.initialize()V
at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:119)
at org.apache.maven.plugin.testing.AbstractMojoTestCase.setUp(AbstractMojoTestCase.java:62)
at junit.framework.TestCase.runBare(TestCase.java:125)
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:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j
ava:747)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Fwd: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Wendy Smoak <ws...@gmail.com>.
Reported on the user list, and I just got a failure notice with the
same error from my Continuum instance when it tried 'mvn clean site'
on the site module.
The site plugin won't build, at least not with the deployed Doxia snapshots:
--
Wendy
---------- Forwarded message ----------
From: Daniel Murley <dm...@xbiosystems.com>
Date: Mar 21, 2007 9:06 PM
Subject: Whats wrong with Maven at the moment - maven-site-plugin fails!
To: Maven Users List <us...@maven.apache.org>
Hi all,
We've been running maven quite successfully for a while now, however as of
two days ago, the site plugin has started failing.
I'm currently getting the following exception:
Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site': Unable to
find the mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site'
in the plugin 'org.apache.maven.plugins:maven-site-plugin'
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
Has something changed in the last few days?
Cheers,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/21/07, Daniel Murley <dm...@xbiosystems.com> wrote:
> We've been running maven quite successfully for a while now, however as of
> two days ago, the site plugin has started failing.
>
> I'm currently getting the following exception:
>
> Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site': Unable to
> find the mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site'
> in the plugin 'org.apache.maven.plugins:maven-site-plugin'
> org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
>
> Has something changed in the last few days?
There have definitely been changes in Doxia recently, and in fact I
just saw the same failure. Questions about snapshots/unreleased code
are more appropriate on the dev list, so let's move over there.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Whats wrong with Maven at the moment - maven-site-plugin fails!
Posted by Daniel Murley <dm...@xbiosystems.com>.
Hi all,
We've been running maven quite successfully for a while now, however as of
two days ago, the site plugin has started failing.
I'm currently getting the following exception:
Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site': Unable to
find the mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:site'
in the plugin 'org.apache.maven.plugins:maven-site-plugin'
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
Has something changed in the last few days?
Cheers,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org