che.org/blue/organizations/jenkins/maven-box%2Fmaven-si
> > te-plugin/detail/master/94/pipeline>
> > Le dimanche 24 mai 2020, 12:01:46 CEST Karl Heinz Marbaise a écrit :
> >> Hi to all,
> >>
> >> I've stumbled upon the following problem during the s
On Mon, May 25, 2020 at 2:49 AM Hervé BOUTEMY wrote:
>
> removing Maven 2 code is a good simplification
> but FYI it won't remove dependency on plexus-classworld: it's the core of all
> plugins classloading mechanism to have independant plugins
>
Yes, but there's an explicit dependency on classor
CEST Karl Heinz Marbaise a écrit :
Hi to all,
I've stumbled upon the following problem during the site generation
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.
g in an earlier version of plexus-utils since maven-site-plugin
> > declares that dependency directly, but that's what seems to be
> > happening.
> >
> > On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise
wrote:
> > > Hi to all,
> > >
> > &g
Heinz Marbaise a écrit :
> Hi to all,
>
> I've stumbled upon the following problem during the site generation
>
> mojo-parent (issue-105)$ mvn site site:stage
> ..
> [INFO]
> [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
Heinz Marbaise wrote:
> >
> > Hi to all,
> >
> > I've stumbled upon the following problem during the site generation
> >
> > mojo-parent (issue-105)$ mvn site site:stage
> > ..
> > [INFO]
> > [INFO] --- maven-site-plugin:3.9.0:site (default-si
gt; I've stumbled upon the following problem during the site generation
>
> mojo-parent (issue-105)$ mvn site site:stage
> ..
> [INFO]
> [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:ma
Hi to all,
I've stumbled upon the following problem during the site generation
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:
See the other email about the same topic from me
Enrico
Il dom 30 dic 2018, 02:31 Chris Graham ha scritto:
> Hi everyone,
>
> I was doing some work on maven-release and I ran 'mvn clean install site'
> on it (as I usually do), and the build fails with a velocity parsing error.
>
> The fix was s
Hi everyone,
I was doing some work on maven-release and I ran 'mvn clean install site'
on it (as I usually do), and the build fails with a velocity parsing error.
The fix was simple: upgrade fluido-skins from 1.3.1 to 1.7 in site.xml.
Looking at the jenkins build jobs, it looks like the site com
Hi Hervé,
On 5/1/16 5:03 PM, Hervé BOUTEMY wrote:
Hi,
fixed in http://svn.apache.org/r1741867
I'll upgrade back to 30-SNAPSHOT
Sure.Thanks for fixing it...
Kind regards
Karl Heinz
Regards,
Hervé
Le dimanche 1 mai 2016 11:59:02 Karl Heinz Marbaise a écrit :
Hi,
unfortunately there
Hi,
fixed in http://svn.apache.org/r1741867
I'll upgrade back to 30-SNAPSHOT
Regards,
Hervé
Le dimanche 1 mai 2016 11:59:02 Karl Heinz Marbaise a écrit :
> Hi,
>
> unfortunately there was a commit to upgrade the maven site parent
> https://svn.apache.org/repos/asf/maven/site/trunk which cause
Hi,
unfortunately there was a commit to upgrade the maven site parent
https://svn.apache.org/repos/asf/maven/site/trunk which caused the site
https://ci.apache.org/builders/maven-site-staging/ compile to fail.
At the moment i have undone those changes to get a working site publishing.
Kind re
Hi,
currently i'm bit confused, cause i can't get the whole site of the
maven-fluido-skin (release) correctly generated..
I just done the usual release staging...gone into target/checkout
mvn site
mvn scm-publish:publish-scm
but now i realized that some of the links to the tests pages do no
Filled in DOXIA-448, thanks for your help!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 9:26 AM, Lukas Theussl wrote:
>
> Doxia's JIRA is still at codehaus:
>
> http://jira.co
Doxia's JIRA is still at codehaus:
http://jira.codehaus.org/browse/DOXIA
Cheers,
-Lukas
On 10/14/2011 09:19 AM, Simone Tripodi wrote:
Thanks for confirming Lukas!
I just need to know if the Issue has to be filled in the Apache's or
Codehaus' JIRA...
TIA!
Simo
http://people.apache.org/~simon
Thanks for confirming Lukas!
I just need to know if the Issue has to be filled in the Apache's or
Codehaus' JIRA...
TIA!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 9:14 AM, L
It's a bug.
-Lukas
On 10/13/2011 10:03 PM, Simone Tripodi wrote:
Hi all guys!
while generating the Apache DirectMemory site[1] using the xdoc
format, I noticed that for every element, if `class`
attribute is specified, it is replicated to the nested element.
For example, for
A
Hi all guys!
while generating the Apache DirectMemory site[1] using the xdoc
format, I noticed that for every element, if `class`
attribute is specified, it is replicated to the nested element.
For example, for
Apache DirectMemory is a multi layered cache implementation
featuring off-
first...Hm
Ok. Thanks.
-
Kind regards
Karl Heinz Marbaise
http://www.soebes.de
http://www.skmwiki.de
http://supose.org/wiki/supose
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Site-Generation-Failure-Possible-Maven-JavaDoc-tp3370562p3370758.html
Sent
mvn.log
Method.java:597)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.j
e/pws-config/src/main/java/com/oneandone/devel/modules/pws/config/ConfigurationProperties.java:9:
package org.apache.log4j does not exist
[ERROR] import org.apache.log4j.Logger;
[ERROR] ^
[ERROR]
/home/ubuntu/ws-git/pustefix-workspace/pws-config/src/main/java/com/oneandone/devel/modules/pws/config/ACon
Yes, what is the problem?
Please continue this discussion on the user list if necessary, since this has
nothing to do with Maven development.
regards,
Hervé
Le vendredi 26 mars 2010, Karl Heinz Marbaise a écrit :
> Hi,
>
> first thanks for your answer...
>
> currently i have the following si
Hi,
first thanks for your answer...
currently i have the following situation:
http://site.supose.org/maven-licenses-verifier-plugin/
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Maven-License-Verifiert-Plugin---Site-Generation-tp28041703p28046550
Hi,
did you try "mvn site-deploy"?
regards,
Hervé
Le vendredi 26 mars 2010, Karl Heinz Marbaise a écrit :
> Hi,
>
> i have crated a maven plugin and structured some dependencies like the
> following:
>
> root
> +--- licenses-model
> +--- licenses-verifier
> +--- licenses-verifier-plugin
stions are appreciated...
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Maven-License-Verifiert-Plugin---Site-Generation-tp28041703p28041703.html
Sent from the Maven Developers mailing list archive at
that did the trick. Thanks
On Tue, Feb 16, 2010 at 11:39 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Stephane Nicoll wrote:
>
> Embedded error: Error rendering Maven report: Failed during checkstyle
>> configuration
>> FileLength is not allowed as a child in Checker
>>
>
> The EA
Stephane Nicoll wrote:
Embedded error: Error rendering Maven report: Failed during checkstyle
configuration
FileLength is not allowed as a child in Checker
The EAR Plugin is still inheriting from the rather old maven-plugins:14
parent, IIRC we fixed this in later parents, so try updating to v
Hi guys,
While staging the doc for the ear plugin 2.4.1 I got this
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Failed during checkstyle
configuration
FileLeng
This is a user group question - but look below.
On 5/31/07, Brent Kersanske <[EMAIL PROTECTED]> wrote:
I've been struggling with some of maven's custom site generation tools
for a few days now.
It seems there is very little helpful information out there, and the few
bits of
I've been struggling with some of maven's custom site generation tools
for a few days now.
It seems there is very little helpful information out there, and the few
bits of good information that do exist are difficult to find.
I've gotten to the point where I have a working ve
Hi all,
I've sent this mail to the users list but did not receive any reply.
Therefore I'm asking here:
I've had this problem for several weeks now. Anyone has an idea if this
can be worked around or if it's just a bug in the site plugin.
Use case: flat multi module project layout (due to ec
ite-plugin
navigation.xml
The site goal then finishes without any errors.
> Allow files to be excluded from site generation
> ---
>
> Key: MSITE-98
> URL: http://jira.codehaus.org/browse/MSITE-98
>
[ http://jira.codehaus.org/browse/MSITE-98?page=all ]
Dennis Lundberg updated MSITE-98:
-
Attachment: MSITE-98.patch
> Allow files to be excluded from site generation
> ---
>
> K
Allow files to be excluded from site generation
---
Key: MSITE-98
URL: http://jira.codehaus.org/browse/MSITE-98
Project: Maven 2.x Site Plugin
Type: New Feature
Reporter: Dennis Lundberg
--
This message is
people. If you don't want the build to fail, just don't set
fail.on.violation=true. Otherwise there is the workaround above.
> maven.checkstyle.fail.on.violation make the site generation fail
>
>
> Key
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-28?page=all ]
Lukas Theussl updated MPCHECKSTYLE-28:
--
Fix Version: 3.0.1
> maven.checkstyle.fail.on.violation make the site generation f
[ http://jira.codehaus.org/browse/MPJXR-30?page=all ]
Lukas Theussl closed MPJXR-30:
--
Resolution: Won't Fix
> Add an option to site generation to use clover xref files rather
the site generation
> phase
> ---
>
> Key: MNG-1931
> URL: http://jira.codehaus.org/browse/MNG-1931
> Project: Maven 2
> Type: Bug
> Components: POM, Design &
be a candidate for docu. somewhere (maybe in maven-model)
specifying the distinction between and
and what should go where (as part of best-practice).
> PluginManagement config is not used by plugins enabled in the site generation
>
)
Project: Maven 2.x Project Help Plugin (was: Maven 2)
> add a report mojo to create a an effective pom and effective settings report
> (to be used in site gene
: Maven)
Key: MSITE-26 (was: MNG-911)
Project: Maven 2.x Site Plugin (was: Maven 2)
> Error during site generation with '.'-files in src/site/
>
>
> Key: MSITE-26
> URL: http:/
)
Project: Maven 2.x Site Plugin (was: Maven 2)
> PluginManagement config is not used by plugins enabled in the site generation
> phase
> ---
>
> Key: MSITE-11
> URL: http:/
)
Key: MSITE-2 (was: MNG-912)
Project: Maven 2.x Site Plugin (was: Maven 2)
> Overzealous "duplicate files" checking during site generation
> -
>
> Key: MSITE-2
> URL: http:/
cated, but build plugins have a more honerous requirement -
specifically they will often fail the build when the reporting plugin won't
during site generation. For this reason, build configuration is not passed to
the reports.
> PluginManagement config is not used by plugins enabled in t
would land up in a situation where certain configurations have to
be repeated in as well as .
The solution would serve the purpose but won't be as elegent :)
> PluginManagement config is not used by plugins enabled in the site generation
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53690 ]
Brett Porter commented on MNG-1857:
---
this is a design issue... do we need a reportingManagement element?
> PluginManagement config is not used by plugins enabled in the s
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53689 ]
Brett Porter commented on MNG-1857:
---
not really related to mng-1855
> PluginManagement config is not used by plugins enabled in the site generation
>
well.
> PluginManagement config is not used by plugins enabled in the site generation
> phase
> ---
>
> Key: MNG-1857
> URL: http://jira.codehaus.org/browse/MNG-1857
> Project: M
PluginManagement config is not used by plugins enabled in the site generation
phase
---
Key: MNG-1857
URL: http://jira.codehaus.org/browse/MNG-1857
Project: Maven 2
Type: Bug
to develop and
publish an external product web site.
> add a report mojo to create a an effective pom and effective settings report
> (to be used in site generation)
>
&g
blish to a publicly available site...
> add a report mojo to create a an effective pom and effective settings report
> (to be used in site generation)
>
>
> Key: MNG-
add a report mojo to create a an effective pom and effective settings report
(to be used in site generation)
Key: MNG-1531
URL: http://jira.codehaus.org/browse/MNG-1531
[ http://jira.codehaus.org/browse/MNG-912?page=all ]
Brett Porter closed MNG-912:
Assign To: Brett Porter
Resolution: Fixed
applied
> Overzealous "duplicate files" checking during si
uplicate files" checking during site generation
> -
>
> Key: MNG-912
> URL: http://jira.codehaus.org/browse/MNG-912
> Project: Maven 2
> Type: Bug
> Components: maven-site
http://jira.codehaus.org/secure/attachment/16827/site-resources.patch
-q | patch -p0
> Overzealous "duplicate files" checking during site generation
> -
>
> Key: MNG-912
> URL: http://jira.codehaus.org/browse/M
[ http://jira.codehaus.org/browse/MNG-912?page=all ]
Binyan updated MNG-912:
---
Attachment: site-resources.patch
Sure, I was actually wonder which was preferred inline or an attachment.
> Overzealous "duplicate files" checking during si
[ http://jira.codehaus.org/browse/MNG-912?page=comments#action_47298 ]
Brett Porter commented on MNG-912:
--
can you please attach this to the issue instead of pasting it inline?
> Overzealous "duplicate files" checking during si
-String defaultExcludes = StringUtils.join( DEFAULT_EXCLUDES, "," );
List siteFiles = FileUtils.getFileNames( directory, null,
defaultExcludes, false );
for ( Iterator it = siteFiles.iterator(); it.hasNext(); )
{
>
[ http://jira.codehaus.org/browse/MNG-911?page=all ]
Brett Porter closed MNG-911:
Assign To: Brett Porter
Resolution: Fixed
applied, also added .arch-ids to default excludes
> Error during site generation with '.'-file
[ http://jira.codehaus.org/browse/MNG-912?page=all ]
Brett Porter updated MNG-912:
-
Fix Version: 2.0-beta-2
> Overzealous "duplicate files" checking during site generation
> -
>
[ http://jira.codehaus.org/browse/MNG-911?page=all ]
Brett Porter updated MNG-911:
-
Fix Version: 2.0-beta-2
> Error during site generation with '.'-files in src/site/
>
>
>
Overzealous "duplicate files" checking during site generation
-
Key: MNG-912
URL: http://jira.codehaus.org/browse/MNG-912
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions
Error during site generation with '.'-files in src/site/
Key: MNG-911
URL: http://jira.codehaus.org/browse/MNG-911
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions:
[ http://jira.codehaus.org/browse/MPSITE-26?page=all ]
Lukas Theussl closed MPSITE-26:
---
Resolution: Duplicate
Duplicate of MAVEN-847
> Site generation on UNIX: problem with accents in
by many
other plugins. If you want to use clover xref file, you could just not call the
jxr plugin and link to the clover xref files from the navigation bar?
> Add an option to site generation to use clover xref files rather than
[ http://jira.codehaus.org/browse/MPJXR-30?page=all ]
Lukas Theussl moved MPXDOC-67 to MPJXR-30:
--
Key: MPJXR-30 (was: MPXDOC-67)
Project: maven-jxr-plugin (was: maven-xdoc-plugin)
> Add an option to site generation to use clover x
[ http://jira.codehaus.org/browse/MPXDOC-67?page=all ]
Arnaud Heritier updated MPXDOC-67:
--
Assign To: (was: Arnaud Heritier)
> Add an option to site generation to use clover xref files rather than
[ http://jira.codehaus.org/browse/MNG-737?page=all ]
Trygve Laugstol closed MNG-737:
---
Resolution: Fixed
Fix Version: 2.0-beta-1
Fixed, thanks for creating the issue,
> maven 2 site generation page
>
>
>
maven 2 site generation page
Key: MNG-737
URL: http://jira.codehaus.org/browse/MNG-737
Project: Maven 2
Type: Bug
Components: documentation
Versions: 2.0-alpha-3
Reporter: Julian Wood
Priority: Trivial
On this page
[EMAIL PROTECTED] wrote:
>Well, almost. ALL files should be unique when generated.
>I.e.
>
> src/site/apt/alpha/usage.apt -> generated-sources/site/usage.html
> src/site/xdoc/alpha/usage.xml -> generated-sources/site/usage.html
>
>So, not only index files but ALL files!
>
>And since t
> Sent: Tuesday, July 26, 2005 9:12 AM
> > To: Maven Developers List
> > Subject: RE: [jira] Closed: (MNG-588) How to handle identical file names
> > in the site structure for the static site generation?
> >
> > On Tue, 26 Jul 2005, Vincent Siveton wrote:
> >
>
pers List
> Subject: RE: [jira] Closed: (MNG-588) How to handle identical file names
> in the site structure for the static site generation?
>
> On Tue, 26 Jul 2005, Vincent Siveton wrote:
>
> Hi Vincent,
>
> Well, I think it should be checked, at least. It's easy to lo
[ http://jira.codehaus.org/browse/MNG-599?page=all ]
Vincent Siveton closed MNG-599:
---
Resolution: Fixed
Updated the template
> organization name in pom is not used in site generation : 2002-2005, Apache
> Software Foundation is always put i
On Tue, 26 Jul 2005, Vincent Siveton wrote:
Hi Vincent,
Well, I think it should be checked, at least. It's easy to lose oversight
with different directories (see maven-site/src/site/*/developers/).
Perhaps the directories could be merged, and the file extensions determine
the type of file it is
Hi Kenney,
> How about checking for src/apt/page.apt and
> src/xdoc/page.xml ( i.e. -> page.html )?
Actually, the exception is only for an index file (ie index.*).
Do you think that we can do the same thing for all duplicate files?
If you still think it's a good idea, I could implement it.
Che
Resolution: Fixed
>
> Throw an exception if two index files already exist
>
> > How to handle identical file names in the site structure for the static
> > site generation?
> >
>
[ http://jira.codehaus.org/browse/MNG-588?page=all ]
Vincent Siveton closed MNG-588:
---
Resolution: Fixed
Throw an exception if two index files already exist
> How to handle identical file names in the site structure for the static site
> gene
> How to handle identical file names in the site structure for the static site
> generation?
>
>
> Key: MNG-588
> URL: http://jira.codehaus.org/browse/MNG-588
> Proje
[ http://jira.codehaus.org/browse/MNG-599?page=all ]
Brett Porter updated MNG-599:
-
Fix Version: 2.0-beta-1
> organization name in pom is not used in site generation : 2002-2005, Apache
> Software Foundation is always put i
: MPSITE-32)
Project: Maven 2 (was: maven-site-plugin)
> organization name in pom is not used in site generation : 2002-2005, Apache
> Software Foundation is always put i
organization name in pom is not used in site generation : 2002-2005, Apache
Software Foundation is always put in page.
--
Key: MPSITE-32
URL: http
[ http://jira.codehaus.org/browse/MNG-588?page=all ]
Brett Porter updated MNG-588:
-
Fix Version: 2.0-beta-1
> How to handle identical file names in the site structure for the static site
> gene
How to handle identical file names in the site structure for the static site
generation?
Key: MNG-588
URL: http://jira.codehaus.org/browse/MNG-588
Project: Maven 2
Type: Bug
> maven.checkstyle.fail.on.violation make the site generation fail
>
>
> Key: MPCHECKSTYLE-28
> URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-28
> Project: maven
Site generation on UNIX: problem with accents in POM
-
Key: MPSITE-26
URL: http://jira.codehaus.org/browse/MPSITE-26
Project: maven-site-plugin
Type: Bug
Components: plugin
Versions: 1.5.1
Environment
:
-
Key: MPCHECKSTYLE-28
Summary: maven.checkstyle.fail.on.violation make the site generation fail
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-checkstyle-plugin
Versions:
2.5
Yes it works
Thanks a lot Martin!!
Arnaud.
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 25 mai 2004 19:02
> À : [EMAIL PROTECTED]
> Objet : [jira] Commented: (MPXDOC-67) Add an option to site generation to
> use c
:
-
Key: MPXDOC-67
Summary: Add an option to site generation to use clover xref files rather than jxr
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: 4 hours
Time Spent: Unknown
Remaining: 4 hours
Project: maven-xdoc-plugin
Assignee:
Reporter
:
-
Key: MPXDOC-67
Summary: Add an option to site generation to use clover xref files rather than jxr
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: 4 hours
Time Spent: Unknown
Remaining: 4 hours
Project
> I've always liked this idea and actually tried to do it in
> Turbine but nobody went for it. I think it clearly separates
> the docs and we can actually give out perms to doco folk (if
> we ever get some :-)) and not worry about them punching the core.
>
> +1
>
I've put it in JIRA to do for
On Wed, 2003-11-26 at 17:59, Brett Porter wrote:
> > I would say the normal site should point at the current
> > release docs and then use your scheme to point at any number
> > of desired branches.
>
> I agree. This was the original plan I think. I like the way Cactus does it
> too, in the top
> I would say the normal site should point at the current
> release docs and then use your scheme to point at any number
> of desired branches.
I agree. This was the original plan I think. I like the way Cactus does it
too, in the top right nav link.
But in the interim, we just keep doing what
On Wed, 2003-11-26 at 17:25, Vincent Massol wrote:
> Some ideas... :-)
>
> Why not 2 web sites:
>
> - maven.apache.org pointing to HEAD
> - maven.apache.org/1.0/ pointing to MAVEN-1_0-BRANCH
I think we need a site for the current release as well. And I suppose
any number of arbitrary branches th
On Wed, 2003-11-26 at 17:13, Brett Porter wrote:
> Just a thought... should the main site now be generated from
> MAVEN-1_0-BRANCH or HEAD?
>
> I'm +1 for the branch as it is the next release and all changes made there
> will go to HEAD eventually.
Yah, I agree. Whatever branch is slated for the
o add:
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 23:14
> To: Maven Developers List ([EMAIL PROTECTED])
> Subject: site generation
>
> Just a thought... should the main site now be generated from
Just a thought... should the main site now be generated from
MAVEN-1_0-BRANCH or HEAD?
I'm +1 for the branch as it is the next release and all changes made there
will go to HEAD eventually.
I think we need to resurrect that plan for general site publishing rules
from earlier in the year and fle
ssue:
-
Key: MAVEN-226
Summary: Add an option to site generation to use clover xref files rather than jxr
Type: Improvement
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: 4 hours
Pro
98 matches
Mail list logo
