[ANN] Maven Site Plugin 4.0.0-M14 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M14.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M14


** Bug
* [MSITE-1006] - MSITE-723 causes duplicate document rendering and 
log output


** Dependency upgrade
* [MSITE-1003] - Upgrade plugins and components (in ITs)
* [MSITE-1004] - Upgrade org.apache.maven:maven-archiver to 3.6.2
* [MSITE-1005] - Upgrade org.codehaus.plexus:plexus-archiver to 4.9.2


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Configuring canonical URL link elements for maven-site-plugin generated pages

[Greg Chabala]

Only for the Fluido skin, eh?

In the meantime I've hacked together a beanshell monstrosity to add the tag
to any pages that are missing it, which may end up becoming the basis for a
custom plugin.

Re: Configuring canonical URL link elements for maven-site-plugin generated pages

[Michael Osipov]

If you use the Maven Fluido Skin /site/body/head is passed to Velocity's 
RenderTool with '#eval()' and eventuall VTL markup will be rendered. Logically, 
you should have access to all context attributes including the HTML page name 
and all other stuff.

Give it a try.

M

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Configuring canonical URL link elements for maven-site-plugin generated pages

[Greg Chabala]

I'm trying to improve the search engine optimization of my project's
maven-site-plugin generated website by following some best practices. I'm
already using sitemapxml-maven-plugin to produce a sitemap for search
engines.

I'd like to configure a canonical URL link element for each page as well,
but I don't see any hint of such a thing existing in the documentation. I
know it's relatively easy to insert arbitrary elements in the header of ALL
pages, like analytics code, but it seems like adding a unique element to
the header of every page is more challenging, and might need to be
supported directly by the generator.

Is anyone doing this sort of thing? Short of making code changes to
maven-site-plugin and possibly every plugin that generates reports, I think
I might need to insert the canonical URL link elements by parsing the
generated HTML after the fact.

Greg Chabala

[ANN] Maven Site Plugin 4.0.0-M13 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M13.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M13

** Bug
* [MSITE-997] - Non-localized site directory 
DocumentRenderingContext passed
* [MSITE-998] - MavenReport#setReportOutputDirectory(File) is 
called too late


** Dependency upgrade
* [MSITE-999] - Upgrade plugins and components (in ITs)


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M12 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M12.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M12

** Improvement
* [MSITE-987] - Consistently log when skipping report goal execution

** Task
* [MSITE-996] - Rewrite site.xml in ITs for new site model

** Dependency upgrade
* [MSITE-991] - Upgrade to Parent 41
* [MSITE-992] - Upgrade to Doxia Sitetools 2.0.0-M16
* [MSITE-993] - Upgrade to Maven Reporting API 4.0.0-M9
* [MSITE-994] - Upgrade to Maven Reporting Exec 4.0.0-M12
* [MSITE-995] - Upgrade plugins and components (in ITs)


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M11 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M11.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M11

** Dependency upgrade
* [MSITE-981] - Upgrade to Doxia 2.0.0-M8
* [MSITE-982] - Upgrade to Doxia Sitetools 2.0.0-M13
* [MSITE-983] - Upgrade to Maven Reporting API 4.0.0-M8
* [MSITE-984] - Upgrade to Maven Reporting Impl/Exec 4.0.0-M11
* [MSITE-985] - Upgrade plugins and components (in ITs)


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M10 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M10.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M10

** Bug
* [MSITE-971] - Site generation not resolving git.commit.time

** Improvement
* [MSITE-973] - Have ${project.build.outputTimestamp} injected as 
@Parameter


** Task
* [MSITE-975] - Use injected only properties in additional template 
properties


** Dependency upgrade
* [MSITE-976] - Bump plexus-archiver from 4.7.1 to 4.8.0
* [MSITE-979] - Upgrade to Parent 40
* [MSITE-980] - Upgrade plugins and components (in ITs)


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M9 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M9.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M9

** Improvement
* [MSITE-833] - Remove dependency to maven-compat

** Task
* [MSITE-965] - add system requirements history

** Dependency upgrade
* [MSITE-968] - Upgrade plugins and components (in ITs)
* [MSITE-969] - Upgrade to Doxia 2.0.0-M7/Doxia Sitetools 2.0.0-M11
* [MSITE-970] - Upgrade to Maven Reporting API 4.0.0-M7, Maven 
Reporting Impl 4.0.0-M9, Maven Reporting Exec 2.0.0-M9



Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M8 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M8.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M8

** Bug
* [MSITE-951] - Don't abuse report's symbolic output name as filename
* [MSITE-952] - MultiPageSinkFactory does not strip output name for 
extension

* [MSITE-959] - Incorrect assumption of default locale

** New Feature
* [MSITE-953] - Log statistics about rendered non-Doxia documents
* [MSITE-954] - Introduce SitePluginReportDocumentRenderer marker 
interface


** Improvement
* [MSITE-873] - Mark SiteMojo and SiteJarMojo thread-safe
* [MSITE-949] - Properly populate 
DocumentRenderingContext#generator for ReportDocumentRenderer

* [MSITE-955] - Improve DoxiaFilter document source log message
* [MSITE-956] - Pass a sub mojo execution to 
CategorySummaryDocumentRenderer
* [MSITE-957] - Print generation log message in 
CategorySummaryDocumentRenderer like in ReportDocumentRenderer

* [MSITE-958] - Rewrite sitemap generator to a rendender

** Dependency upgrade
* [MSITE-950] - Upgrade to Doxia Sitetools to 2.0.0-M8, Maven 
Reporting API 4.0.0-M6, Maven Reporting Impl/Exec 4.0.0-M7
* [MSITE-962] - Upgrade to Doxia Sitetools to 2.0.0-M10, Maven 
Reporting Impl/Exec 4.0.0-M8, Maven Fluido Skin 2.0.0-M6



Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M7 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M7.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M7

** Bug
* [MSITE-226] - Missing escaping of ${project.name} for default 
site descriptor

* [MSITE-934] - Log output of site:run does not show locale
* [MSITE-937] - Sitemap creates non-consecutive headings
* [MSITE-938] - Sitemap creates empty entry if href is null 
although menu item name isn't
* [MSITE-941] - sitemap.xml is overwritten when multiple locales 
are defined

* [MSITE-942] - Generated localized site content is ignored
* [MSITE-943] - Saved processed site content is overwritten when 
multiple locales are defined
* [MSITE-944] - Site plugin fails if there's a & in the project 
 POM


** Task
* [MSITE-932] - Remove Maven 2 style reports element
* [MSITE-936] - Sort locale tests from non-default to default one
* [MSITE-939] - Replace StringUtils from Plexus Utils with Commons Lang

** Dependency upgrade
* [MSITE-935] - Upgrade to Doxia Sitetools 2.0.0-M7, Maven 
Reporting Impl 4.0.0-M6, Maven Reporting Exec 2.0.0-M6



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M6 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M6.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M6

** Dependency upgrade
* [MSITE-930] - Upgrade plugins and components (in ITs)
* [MSITE-931] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M6, Maven 
Reporting API/Impl 4.0.0-M5, Maven Reporting Exec 2.0.0-M5



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M5 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M5.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M5

** Bug
* [MSITE-220] - site:run mojo will not display Javadoc or JXR 
report results


** Improvement
* [MSITE-872] - Set content type on Doxia output
* [MSITE-924] - Populate SiteRenderingContext#getPublishDate() with 
${project.build.outputTimestamp}

* [MSITE-929] - Make server host configurable

** Task
* [MSITE-920] - Remove Maven 2 compat code

** Dependency upgrade
* [MSITE-925] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M5
* [MSITE-926] - Upgrade to Maven Reporting API/Exec 4.0.0-M4
* [MSITE-927] - Upgrade Parent to 39
* [MSITE-928] - Upgrade plugins and components


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M4 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M4.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M4

** Bug
* [MSITE-639] - sub-project tries to fetch a site_en.xml even 
though no locales are configured

* [MSITE-827] - Site builds rely on HTTP 404
* [MSITE-904] - Unable to generate zh_TW locale of site document
* [MSITE-912] - Reporting plugins never executed if more than one 
locale is configured
* [MSITE-914] - SiteMojo never populates Doxia Sitetools Site 
Renderer supportedLocales Velocity context property


** Wish
* [MSITE-820] - Change localized output from language to full 
locale, like source


** Dependency upgrade
* [MSITE-913] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
* [MSITE-915] - Upgrade Plexus Utils to 3.5.0
* [MSITE-916] - Upgrade Plexus Archiver to 4.6.0
* [MSITE-917] - Upgrade components and plugin in ITs
* [MSITE-918] - Upgrade Maven Reporting API to 4.0.0-M3
* [MSITE-919] - Upgrade Maven Reporting Exec to 2.0.0-M3


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 3.12.1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 3.12.1.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 3.12.1

** Bug
* [MSITE-901] - If preceding standalone report has been run, 
site:jar does not reinvoke site:site


** Dependency upgrade
* [MSITE-897] - Upgrade Plexus Archiver to 4.2.7
* [MSITE-898] - Upgrade Parent to 36
* [MSITE-902] - Upgrade Plexus Utils to 3.4.2
* [MSITE-908] - Upgrade Maven Reporting API to 3.1.1


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M3 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M3.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M3

** Dependency upgrade
* [MSITE-905] - Upgrade Doxia and Maven Reporting stack
* [MSITE-906] - Upgrade plugins and components


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M2.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M2

** Bug
* [MSITE-901] - If preceding standalone report has been run, 
site:jar does not reinvoke site:site


** Dependency upgrade
* [MSITE-900] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M3
* [MSITE-902] - Upgrade Plexus Utils to 3.4.2


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M1.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M1

** Dependency upgrade
* [MSITE-892] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M2
* [MSITE-893] - Upgrade Maven Reporting API to 4.0.0-M1
* [MSITE-894] - Upgrade Maven Reporting Exec to 2.0.0-M1
* [MSITE-895] - Upgrade plugins and components in ITs
* [MSITE-897] - Upgrade Plexus Archiver to 4.2.7
* [MSITE-898] - Upgrade Parent to 36


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 3.12.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 3.12.0.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 3.12.0

** Bug
* [MSITE-857] - Jetty engine fails to resolve web.xml DTD behind 
corporate proxy


** Task
* [MSITE-828] - Upgrade to Java 8
* [MSITE-884] - Drop/replace usage of Commons Lang 3
* [MSITE-887] - Deprecate templateFile parameter

** Dependency upgrade
* [MSITE-829] - Upgrade Jetty to 9.4.x
* [MSITE-885] - Upgrade Commons IO to 2.11.0
* [MSITE-886] - Upgrade Maven Wagon to 3.5.1
* [MSITE-888] - Upgrade to Maven 3.2.5
* [MSITE-889] - Upgrade Plexus Utils to 3.3.1
* [MSITE-890] - Upgrade Jetty to 9.4.46.v20220331
* [MSITE-891] - Upgrade plugins in ITs


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 3.11.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 3.11.0.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 3.11.0

** Task
* [MSITE-880] - AbstractSiteDeployWebDavTest should not log

** Dependency upgrade
* [MSITE-881] - Upgrade Maven Reporting API to 3.1.0
* [MSITE-882] - Upgrade Maven Reporting Exec to 1.6.0
* [MSITE-883] - Upgrade plugins in ITs


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 3.10.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 3.10.0.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 3.10.0

** Improvement
* [MSITE-870] - Mark Maven-exported dependencies as scope provided
* [MSITE-877] - Shared GitHub Actions

** Dependency upgrade
* [MSITE-875] - Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
* [MSITE-878] - Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Need help for maven site plugin for Apache Helix

[Olivier Lamy]

Thanks Hervé!.
@Junkai I have merged Hervé's PR



On Sat, 20 Nov 2021 at 20:31, Hervé BOUTEMY  wrote:

> FYI, on the "SiteToolException: Error parsing site descriptor: TEXT must
> beimmediately followed by END_TAG and not START_TAG" error, the key Maven
> Site
> Plugin version is version 3.5, where the parsing of site.xml changed:
> previously it was parser as XML, and since 3.5 it is parsed as text
>
> the consequence is that in general, you need to surround head and footer
> data
> from site.xml (including parents) with 
>
> that's why Apache parent version is related to maven-site-plugin version
>
> HTH
>
> Hervé
>
> Le samedi 20 novembre 2021, 09:19:41 CET Hervé BOUTEMY a écrit :
> > Hi,
> >
> > Apache parent 13 is so old...
> >
> > see https://github.com/apache/helix/pull/1909
> > upgrading both Apache parent POM and maven-site-plugin seems to do the
> job
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 18 novembre 2021, 00:04:03 CET Junkai Xue a écrit :
> > > Hi,
> > >
> > > I was trying to deploy Apache Helix project website for new releases.
> Got
> > > exception on
> > >
> > > *SiteToolException: The site descriptor cannot be resolved from the
> > > repository: ArtifactResolutionException: Unable to locate site
> descriptor:
> > > Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
> > > mvnrepository.com <http://mvnrepository.com> (
> https://mvnrepository.com
> > > <https://mvnrepository.com>): Access denied to:
> > > https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
> > > <https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml>
> ,
> > > ReasonPhrase:Forbidden.*
> > >
> > > [*ERROR*] *  org.apache:apache:xml:13*
> > >
> > > [*ERROR*]
> > >
> > > [*ERROR*] *from the specified remote repositories:*
> > >
> > > [*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
> > > (https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
> > > releases=true, snapshots=false),*
> > >
> > > [*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
> > > (https://mvnrepository.com <https://mvnrepository.com>, releases=true,
> > > snapshots=false),*
> > >
> > > [*ERROR*] *  central (https://repo.maven.apache.org/maven2
> > > <https://repo.maven.apache.org/maven2>, releases=true,
> snapshots=false),*
> > >
> > > [*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
> > > <http://repository.apache.org/snapshots>, releases=false,
> snapshots=true)*
> > >
> > >
> > > Was this recent change? I tried to upgrade to maven site plugin to
> 3.9.1.
> > > It got error on parsing:
> > >
> > > *SiteToolException: Error parsing site descriptor*: TEXT must be
> > > immediately followed by END_TAG and not START_TAG (position: START_TAG
> > > seen
> > > ...\n  

Re: Need help for maven site plugin for Apache Helix

[Hervé BOUTEMY]

FYI, on the "SiteToolException: Error parsing site descriptor: TEXT must 
beimmediately followed by END_TAG and not START_TAG" error, the key Maven Site 
Plugin version is version 3.5, where the parsing of site.xml changed: 
previously it was parser as XML, and since 3.5 it is parsed as text

the consequence is that in general, you need to surround head and footer data 
from site.xml (including parents) with 

that's why Apache parent version is related to maven-site-plugin version

HTH

Hervé

Le samedi 20 novembre 2021, 09:19:41 CET Hervé BOUTEMY a écrit :
> Hi,
> 
> Apache parent 13 is so old...
> 
> see https://github.com/apache/helix/pull/1909
> upgrading both Apache parent POM and maven-site-plugin seems to do the job
> 
> Regards,
> 
> Hervé
> 
> Le jeudi 18 novembre 2021, 00:04:03 CET Junkai Xue a écrit :
> > Hi,
> > 
> > I was trying to deploy Apache Helix project website for new releases. Got
> > exception on
> > 
> > *SiteToolException: The site descriptor cannot be resolved from the
> > repository: ArtifactResolutionException: Unable to locate site descriptor:
> > Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
> > mvnrepository.com <http://mvnrepository.com> (https://mvnrepository.com
> > <https://mvnrepository.com>): Access denied to:
> > https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
> > <https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml> ,
> > ReasonPhrase:Forbidden.*
> > 
> > [*ERROR*] *  org.apache:apache:xml:13*
> > 
> > [*ERROR*]
> > 
> > [*ERROR*] *from the specified remote repositories:*
> > 
> > [*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
> > (https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
> > releases=true, snapshots=false),*
> > 
> > [*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
> > (https://mvnrepository.com <https://mvnrepository.com>, releases=true,
> > snapshots=false),*
> > 
> > [*ERROR*] *  central (https://repo.maven.apache.org/maven2
> > <https://repo.maven.apache.org/maven2>, releases=true, snapshots=false),*
> > 
> > [*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
> > <http://repository.apache.org/snapshots>, releases=false, snapshots=true)*
> > 
> > 
> > Was this recent change? I tried to upgrade to maven site plugin to 3.9.1.
> > It got error on parsing:
> > 
> > *SiteToolException: Error parsing site descriptor*: TEXT must be
> > immediately followed by END_TAG and not START_TAG (position: START_TAG
> > seen
> > ...\n  

Re: Need help for maven site plugin for Apache Helix

[Hervé BOUTEMY]

Hi,

Apache parent 13 is so old...

see https://github.com/apache/helix/pull/1909
upgrading both Apache parent POM and maven-site-plugin seems to do the job

Regards,

Hervé

Le jeudi 18 novembre 2021, 00:04:03 CET Junkai Xue a écrit :
> Hi,
> 
> I was trying to deploy Apache Helix project website for new releases. Got
> exception on
> 
> *SiteToolException: The site descriptor cannot be resolved from the
> repository: ArtifactResolutionException: Unable to locate site descriptor:
> Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
> mvnrepository.com <http://mvnrepository.com> (https://mvnrepository.com
> <https://mvnrepository.com>): Access denied to:
> https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
> <https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml> ,
> ReasonPhrase:Forbidden.*
> 
> [*ERROR*] *  org.apache:apache:xml:13*
> 
> [*ERROR*]
> 
> [*ERROR*] *from the specified remote repositories:*
> 
> [*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
> (https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
> releases=true, snapshots=false),*
> 
> [*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
> (https://mvnrepository.com <https://mvnrepository.com>, releases=true,
> snapshots=false),*
> 
> [*ERROR*] *  central (https://repo.maven.apache.org/maven2
> <https://repo.maven.apache.org/maven2>, releases=true, snapshots=false),*
> 
> [*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
> <http://repository.apache.org/snapshots>, releases=false, snapshots=true)*
> 
> 
> Was this recent change? I tried to upgrade to maven site plugin to 3.9.1.
> It got error on parsing:
> 
> *SiteToolException: Error parsing site descriptor*: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n  

Re: Need help for maven site plugin for Apache Helix

[Olivier Lamy]

not sure what is the content of your ~/.m2/settings.xml but it may have
some references to some repositories?
such http://restlet.talend.com , http://repository.apache.org/snapshots.
note this http
the recent change might be you upgrading to the last maven core version?

[*INFO*] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.9

[*WARNING*] The repository url 'https://mvnrepository.com' is invalid -
Repository 'mvnrepository.com' will be blacklisted.

this mean you should add a mirror in your ~/.m2/settings.xml

If you cannot deploy the website. Let me know and I can do it (I may still
have all karma on helix)

cheers
Olivier
On Thu, 18 Nov 2021 at 09:04, Junkai Xue  wrote:

> Hi,
>
> I was trying to deploy Apache Helix project website for new releases. Got
> exception on
>
> *SiteToolException: The site descriptor cannot be resolved from the
> repository: ArtifactResolutionException: Unable to locate site descriptor:
> Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
> mvnrepository.com <http://mvnrepository.com> (https://mvnrepository.com
> <https://mvnrepository.com>): Access denied to:
> https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
> <https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml> ,
> ReasonPhrase:Forbidden.*
>
> [*ERROR*] *  org.apache:apache:xml:13*
>
> [*ERROR*]
>
> [*ERROR*] *from the specified remote repositories:*
>
> [*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
> (https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
> releases=true, snapshots=false),*
>
> [*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
> (https://mvnrepository.com <https://mvnrepository.com>, releases=true,
> snapshots=false),*
>
> [*ERROR*] *  central (https://repo.maven.apache.org/maven2
> <https://repo.maven.apache.org/maven2>, releases=true, snapshots=false),*
>
> [*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
> <http://repository.apache.org/snapshots>, releases=false, snapshots=true)*
>
>
> Was this recent change? I tried to upgrade to maven site plugin to 3.9.1.
> It got error on parsing:
>
> *SiteToolException: Error parsing site descriptor*: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n  

Re: Need help for maven site plugin for Apache Helix

[Martin Gainty]

caused by outdated reference to a dead codehaus repo
setting codehaus repository enabled=false should mitigate e.g.




HTH
martin

From: Junkai Xue 
Sent: Wednesday, November 17, 2021 6:04 PM
To: users@maven.apache.org 
Subject: Need help for maven site plugin for Apache Helix

Hi,

I was trying to deploy Apache Helix project website for new releases. Got
exception on

*SiteToolException: The site descriptor cannot be resolved from the
repository: ArtifactResolutionException: Unable to locate site descriptor:
Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
mvnrepository.com <http://mvnrepository.com> (https://mvnrepository.com
<https://mvnrepository.com>): Access denied to:
https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
<https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml> ,
ReasonPhrase:Forbidden.*

[*ERROR*] *  org.apache:apache:xml:13*

[*ERROR*]

[*ERROR*] *from the specified remote repositories:*

[*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
(https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
releases=true, snapshots=false),*

[*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
(https://mvnrepository.com <https://mvnrepository.com>, releases=true,
snapshots=false),*

[*ERROR*] *  central (https://repo.maven.apache.org/maven2
<https://repo.maven.apache.org/maven2>, releases=true, snapshots=false),*

[*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
<http://repository.apache.org/snapshots>, releases=false, snapshots=true)*


Was this recent change? I tried to upgrade to maven site plugin to 3.9.1.
It got error on parsing:

*SiteToolException: Error parsing site descriptor*: TEXT must be
immediately followed by END_TAG and not START_TAG (position: START_TAG seen
...\n  

Need help for maven site plugin for Apache Helix

[Junkai Xue]

Hi,

I was trying to deploy Apache Helix project website for new releases. Got
exception on

*SiteToolException: The site descriptor cannot be resolved from the
repository: ArtifactResolutionException: Unable to locate site descriptor:
Could not transfer artifact org.apache:apache:xml:site_en:13 from/to
mvnrepository.com <http://mvnrepository.com> (https://mvnrepository.com
<https://mvnrepository.com>): Access denied to:
https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml
<https://mvnrepository.com/org/apache/apache/13/apache-13-site_en.xml> ,
ReasonPhrase:Forbidden.*

[*ERROR*] *  org.apache:apache:xml:13*

[*ERROR*]

[*ERROR*] *from the specified remote repositories:*

[*ERROR*] *  restlet.talend.com <http://restlet.talend.com>
(https://maven.restlet.talend.com <https://maven.restlet.talend.com>,
releases=true, snapshots=false),*

[*ERROR*] *  mvnrepository.com <http://mvnrepository.com>
(https://mvnrepository.com <https://mvnrepository.com>, releases=true,
snapshots=false),*

[*ERROR*] *  central (https://repo.maven.apache.org/maven2
<https://repo.maven.apache.org/maven2>, releases=true, snapshots=false),*

[*ERROR*] *  apache.snapshots (http://repository.apache.org/snapshots
<http://repository.apache.org/snapshots>, releases=false, snapshots=true)*


Was this recent change? I tried to upgrade to maven site plugin to 3.9.1.
It got error on parsing:

*SiteToolException: Error parsing site descriptor*: TEXT must be
immediately followed by END_TAG and not START_TAG (position: START_TAG seen
...\n  

[ANN] Apache Maven Site Plugin 3.9.1 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Site Plugin, version 3.9.1

This plugin is used to generate a site for the project. The generated site also 
includes the project's reports that were configured in the POM.

https://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-site-plugin
  3.9.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-site-plugin/download.cgi

Release Notes - Maven Site Plugin - Version 3.9.1

** Bug
* [MSITE-856] - NullPointer on 
org.apache.maven.plugins.site.render.SiteMap.relativePath
* [MSITE-863] - NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when 
running reports with Maven versions < 3.6.1

** Improvement
* [MSITE-845] - Drop Maven 2 support
* [MSITE-862] - log Doxia source when rendering with site:run

** Task
* [MSITE-757] - drop Maven 2 support


Enjoy,

-The Apache Maven team




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Customizing the maven-site-plugin Markdown renderer?

[Hervé BOUTEMY]

sorry, I had a look and wanted to take time to have a minimal Maven site 
generation to compare with your direct test: I just sent you a PR

your test is great to show the objective
my addition shows the current effective result = admonition markup is not 
detected, rendered as-is
I'm quite suprised that the markup is not detected, because 
flexmark-ext-amonition is a Doxia Markdown dependency:
https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/dependencies.html

I did not expect that the html would be rendered as wanted, but at least that 
the markup would have been detected and rendered in some html form

seems it's time to extend the sample to add a customised doxia-module-markdown 
:)

Regards,

Hervé

Le jeudi 16 avril 2020, 14:56:05 CEST Stephan Wissel a écrit :
> Did you have a chance to look at this?
> 
> On Thu, Apr 9, 2020 at 2:10 AM Stephan Wissel  wrote:
> > Hello Hervé,
> > 
> > I created a Flexmark sample that is as close as possible to the way
> > Flexmark is used in Doxia:
> > 
> > https://github.com/Stwissel/maven-site-extension/tree/master/simple-flexma
> > rk-example The result can be seen here:
> > https://projectcastle.io/sample.html
> > (I copied a site-plugin generated page and just removed the body part and
> > replace it with the markdown conversion result)
> > 
> > As it seems, to get Adminition working in the rendering, you need to add a
> > single line (and the import/dependency of course)
> > 
> > https://github.com/Stwissel/maven-site-extension/blob/master/simple-flexma
> > rk-example/src/main/java/com/notessensei/demo/Demo1.java#L78
> > 
> > Would you need more samples?
> > 
> > 
> > Create a nice day!
> > Stephan H. Wissel
> > 
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter
> > <http://twitter.com/notessensei> LinkedIn
> > <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> > 
> > 
> > On Mon, Apr 6, 2020 at 2:42 PM Hervé BOUTEMY 
> > 
> > wrote:
> >> don't hesitate to share every single concrete step, even the flexmark
> >> standalone test: this will ease working together, ensuring we understand
> >> each
> >> other
> >> 
> >> even before updating doxia-module-markdown with an updated version, there
> >> is a
> >> test with a Maven site to be done with the normal Doxia, to show the
> >> result
> >> (perhaps there is a partial failure only): this will be interesting to
> >> compare
> >> the result against the flexmark standalone test.
> >> 
> >> then once we'll be at updating doxia-module-markdown, yes, you can
> >> override
> >> the version used by the maven-site-plugin by setting dependencies in
> >> plugin
> >> definition
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
> >> > Sorry for not being clear. The GitHub part is easy.
> >> > What I'm not sure about is how I can test my modification in the
> >> 
> >> context of
> >> 
> >> > the site plugin.
> >> > Would defining my markdown renderer as dependency of the site plugin
> >> > overwrite the build in renderer or do I have to modify the source of
> >> > the
> >> > site plugin too?
> >> > 
> >> > Create a nice day!
> >> > Stephan H. Wissel
> >> > 
> >> > Phone: +65 96673269
> >> > Blog <https://www.wissel.net/blog> Twitter <
> >> 
> >> http://twitter.com/notessensei>
> >> 
> >> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> >> > <https://www.xing.com/profile/StephanH_Wissel>
> >> > 
> >> > On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY 
> >> 
> >> wrote:
> >> > > you can create a GitHub repository, or a collection of repositories
> >> > > whatever is necessary
> >> > > 
> >> > > Regards,
> >> > > 
> >> > > Hervé
> >> > > 
> >> > > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> >> > > > I did a flexmark standalone test, happy to try to integrate that.
> >> > > > I presume I would define my local moxia modification (after mvn
> >> 
> >> clean
> >> 
> >> > > > install) as a site plugin depe

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Did you have a chance to look at this?

On Thu, Apr 9, 2020 at 2:10 AM Stephan Wissel  wrote:

> Hello Hervé,
>
> I created a Flexmark sample that is as close as possible to the way
> Flexmark is used in Doxia:
>
> https://github.com/Stwissel/maven-site-extension/tree/master/simple-flexmark-example
> The result can be seen here:
> https://projectcastle.io/sample.html
> (I copied a site-plugin generated page and just removed the body part and
> replace it with the markdown conversion result)
>
> As it seems, to get Adminition working in the rendering, you need to add a
> single line (and the import/dependency of course)
>
> https://github.com/Stwissel/maven-site-extension/blob/master/simple-flexmark-example/src/main/java/com/notessensei/demo/Demo1.java#L78
>
> Would you need more samples?
>
>
> Create a nice day!
> Stephan H. Wissel
>
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter
> <http://twitter.com/notessensei> LinkedIn
> <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
>
>
> On Mon, Apr 6, 2020 at 2:42 PM Hervé BOUTEMY 
> wrote:
>
>> don't hesitate to share every single concrete step, even the flexmark
>> standalone test: this will ease working together, ensuring we understand
>> each
>> other
>>
>> even before updating doxia-module-markdown with an updated version, there
>> is a
>> test with a Maven site to be done with the normal Doxia, to show the
>> result
>> (perhaps there is a partial failure only): this will be interesting to
>> compare
>> the result against the flexmark standalone test.
>>
>> then once we'll be at updating doxia-module-markdown, yes, you can
>> override
>> the version used by the maven-site-plugin by setting dependencies in
>> plugin
>> definition
>>
>> Regards,
>>
>> Hervé
>>
>> Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
>> > Sorry for not being clear. The GitHub part is easy.
>> > What I'm not sure about is how I can test my modification in the
>> context of
>> > the site plugin.
>> > Would defining my markdown renderer as dependency of the site plugin
>> > overwrite the build in renderer or do I have to modify the source of the
>> > site plugin too?
>> >
>> > Create a nice day!
>> > Stephan H. Wissel
>> >
>> > Phone: +65 96673269
>> > Blog <https://www.wissel.net/blog> Twitter <
>> http://twitter.com/notessensei>
>> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > <https://www.xing.com/profile/StephanH_Wissel>
>> >
>> > On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY 
>> wrote:
>> > > you can create a GitHub repository, or a collection of repositories
>> > > whatever is necessary
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
>> > > > I did a flexmark standalone test, happy to try to integrate that.
>> > > > I presume I would define my local moxia modification (after mvn
>> clean
>> > > > install) as a site plugin dependency?
>> > > >
>> > > > Along those lines:
>> > > >
>> > > >
>> > > > org.apache.maven.plugins
>> > > > maven-site-plugin
>> > > > ${maven.site.plugin.version}
>> > > > 
>> > > > 
>> > > > org.apache.maven.plugins
>> > > > doxia-module-markdown
>> > > > 1.9.1-stw
>> > > > 
>> > > > 
>> > > > 
>> > > >
>> > > > Would that work for providing a demo?
>> > > >
>> > > > Create a nice day!
>> > > > Stephan H. Wissel
>> > > >
>> > > > Phone: +65 96673269
>> > > > Blog <https://www.wissel.net/blog> Twitter <
>> > >
>> > > http://twitter.com/notessensei>
>> > >
>> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > > > <https://www.xing.com/profile/StephanH_Wissel>
>> > > >
>> > > > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY <
>> herve.bout...@free.fr>
>> > >
>> > > wrote:
>> > > > > nice work: dos it mean that you managed to have the rendering as
>> > >
>&g

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hello Hervé,

I created a Flexmark sample that is as close as possible to the way
Flexmark is used in Doxia:
https://github.com/Stwissel/maven-site-extension/tree/master/simple-flexmark-example
The result can be seen here:
https://projectcastle.io/sample.html
(I copied a site-plugin generated page and just removed the body part and
replace it with the markdown conversion result)

As it seems, to get Adminition working in the rendering, you need to add a
single line (and the import/dependency of course)
https://github.com/Stwissel/maven-site-extension/blob/master/simple-flexmark-example/src/main/java/com/notessensei/demo/Demo1.java#L78

Would you need more samples?


Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Mon, Apr 6, 2020 at 2:42 PM Hervé BOUTEMY  wrote:

> don't hesitate to share every single concrete step, even the flexmark
> standalone test: this will ease working together, ensuring we understand
> each
> other
>
> even before updating doxia-module-markdown with an updated version, there
> is a
> test with a Maven site to be done with the normal Doxia, to show the
> result
> (perhaps there is a partial failure only): this will be interesting to
> compare
> the result against the flexmark standalone test.
>
> then once we'll be at updating doxia-module-markdown, yes, you can
> override
> the version used by the maven-site-plugin by setting dependencies in
> plugin
> definition
>
> Regards,
>
> Hervé
>
> Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
> > Sorry for not being clear. The GitHub part is easy.
> > What I'm not sure about is how I can test my modification in the context
> of
> > the site plugin.
> > Would defining my markdown renderer as dependency of the site plugin
> > overwrite the build in renderer or do I have to modify the source of the
> > site plugin too?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY 
> wrote:
> > > you can create a GitHub repository, or a collection of repositories
> > > whatever is necessary
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> > > > I did a flexmark standalone test, happy to try to integrate that.
> > > > I presume I would define my local moxia modification (after mvn clean
> > > > install) as a site plugin dependency?
> > > >
> > > > Along those lines:
> > > >
> > > >
> > > > org.apache.maven.plugins
> > > > maven-site-plugin
> > > > ${maven.site.plugin.version}
> > > > 
> > > > 
> > > > org.apache.maven.plugins
> > > > doxia-module-markdown
> > > > 1.9.1-stw
> > > > 
> > > > 
> > > > 
> > > >
> > > > Would that work for providing a demo?
> > > >
> > > > Create a nice day!
> > > > Stephan H. Wissel
> > > >
> > > > Phone: +65 96673269
> > > > Blog <https://www.wissel.net/blog> Twitter <
> > >
> > > http://twitter.com/notessensei>
> > >
> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > > <https://www.xing.com/profile/StephanH_Wissel>
> > > >
> > > > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY  >
> > >
> > > wrote:
> > > > > nice work: dos it mean that you managed to have the rendering as
> > >
> > > expected?
> > >
> > > > > Can you create a little demo and share?
> > > > >
> > > > > On making the extension configurable and easy to use, it will be
> > >
> > > complex
> > >
> > > > > from a
> > > > > Maven Site Plugin perspective: its relationship with Doxia (the
> core
> > > > > rendering
> > > > > engine), Doxia Markdown Module (the markdown parser for Doxia),
> Doxia
> > > > > Sitetools and Doxia Skins will bring some challenges
> > > > >
> > > > &

Re: Customizing the maven-site-plugin Markdown renderer?

[Hervé BOUTEMY]

don't hesitate to share every single concrete step, even the flexmark 
standalone test: this will ease working together, ensuring we understand each 
other

even before updating doxia-module-markdown with an updated version, there is a 
test with a Maven site to be done with the normal Doxia, to show the result 
(perhaps there is a partial failure only): this will be interesting to compare 
the result against the flexmark standalone test.

then once we'll be at updating doxia-module-markdown, yes, you can override 
the version used by the maven-site-plugin by setting dependencies in plugin 
definition

Regards,

Hervé

Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
> Sorry for not being clear. The GitHub part is easy.
> What I'm not sure about is how I can test my modification in the context of
> the site plugin.
> Would defining my markdown renderer as dependency of the site plugin
> overwrite the build in renderer or do I have to modify the source of the
> site plugin too?
> 
> Create a nice day!
> Stephan H. Wissel
> 
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
> 
> On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY  wrote:
> > you can create a GitHub repository, or a collection of repositories
> > whatever is necessary
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> > > I did a flexmark standalone test, happy to try to integrate that.
> > > I presume I would define my local moxia modification (after mvn clean
> > > install) as a site plugin dependency?
> > > 
> > > Along those lines:
> > >
> > > 
> > > org.apache.maven.plugins
> > > maven-site-plugin
> > > ${maven.site.plugin.version}
> > > 
> > > 
> > > org.apache.maven.plugins
> > > doxia-module-markdown
> > > 1.9.1-stw
> > > 
> > > 
> > > 
> > > 
> > > Would that work for providing a demo?
> > > 
> > > Create a nice day!
> > > Stephan H. Wissel
> > > 
> > > Phone: +65 96673269
> > > Blog <https://www.wissel.net/blog> Twitter <
> > 
> > http://twitter.com/notessensei>
> > 
> > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > <https://www.xing.com/profile/StephanH_Wissel>
> > > 
> > > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY 
> > 
> > wrote:
> > > > nice work: dos it mean that you managed to have the rendering as
> > 
> > expected?
> > 
> > > > Can you create a little demo and share?
> > > > 
> > > > On making the extension configurable and easy to use, it will be
> > 
> > complex
> > 
> > > > from a
> > > > Maven Site Plugin perspective: its relationship with Doxia (the core
> > > > rendering
> > > > engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> > > > Sitetools and Doxia Skins will bring some challenges
> > > > 
> > > > That's why we'll need ot go step by step: sharing a first result with
> > > > a
> > > > lot of
> > > > manual config first, then looking on improvement to replace manual
> > 
> > config
> > 
> > > > with
> > > > nice parameters
> > > > 
> > > > I would really love to add such extensions, I'll really need your help
> > > > 
> > > > Regards,
> > > > 
> > > > Hervé
> > > > 
> > > > Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > > > > Hi Hervé,
> > > > > 
> > > > > thank you for your reply, appreciate your swift response.
> > > > > It seems to be a little more complex ;-) , but started easy (looked
> > 
> > like
> > 
> > > > 1
> > > > 
> > > > > line and 1 import)
> > > > > 
> > > > > Extensions are loaded like line 145 in the MarkdownParser.class:
> > > > > extensions.add(
> > > > > AdminitionExtension.create() );
> > > > > 
> > > > > I did a quick check on CSS/JS. When I put them in
> > > > > /src/site/resources/css
> > > > > and /src/site/resources/js, they get copied into the target site.
> > > > > Then I added  

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Sorry for not being clear. The GitHub part is easy.
What I'm not sure about is how I can test my modification in the context of
the site plugin.
Would defining my markdown renderer as dependency of the site plugin
overwrite the build in renderer or do I have to modify the source of the
site plugin too?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY  wrote:

> you can create a GitHub repository, or a collection of repositories
> whatever is necessary
>
> Regards,
>
> Hervé
>
> Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> > I did a flexmark standalone test, happy to try to integrate that.
> > I presume I would define my local moxia modification (after mvn clean
> > install) as a site plugin dependency?
> > Along those lines:
> >
> >
> > org.apache.maven.plugins
> > maven-site-plugin
> > ${maven.site.plugin.version}
> > 
> > 
> > org.apache.maven.plugins
> > doxia-module-markdown
> > 1.9.1-stw
> > 
> > 
> > 
> >
> > Would that work for providing a demo?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY 
> wrote:
> > > nice work: dos it mean that you managed to have the rendering as
> expected?
> > > Can you create a little demo and share?
> > >
> > > On making the extension configurable and easy to use, it will be
> complex
> > > from a
> > > Maven Site Plugin perspective: its relationship with Doxia (the core
> > > rendering
> > > engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> > > Sitetools and Doxia Skins will bring some challenges
> > >
> > > That's why we'll need ot go step by step: sharing a first result with a
> > > lot of
> > > manual config first, then looking on improvement to replace manual
> config
> > > with
> > > nice parameters
> > >
> > > I would really love to add such extensions, I'll really need your help
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > > > Hi Hervé,
> > > >
> > > > thank you for your reply, appreciate your swift response.
> > > > It seems to be a little more complex ;-) , but started easy (looked
> like
> > >
> > > 1
> > >
> > > > line and 1 import)
> > > >
> > > > Extensions are loaded like line 145 in the MarkdownParser.class:
> > > > extensions.add(
> > > > AdminitionExtension.create() );
> > > >
> > > > I did a quick check on CSS/JS. When I put them in
> > > > /src/site/resources/css
> > > > and /src/site/resources/js, they get copied into the target site.
> > > > Then I added   
> > > > to the site.xml - which also worked. So the prerequites can be
> handled
> > > > in
> > > > the site.xml without the need to change any code.
> > > >
> > > > However I wouldn't see just to load that one extra plugin always,
> more
> > >
> > > like
> > >
> > > > make it configurable. I see two approaches:
> > > > - read the name of the plugins from a config setting and leave it to
> the
> > > > user - with all consequences - which one they specify
> > > > - pick one (for starters) and have a config true/false flag whether
> to
> > >
> > > load
> > >
> > > > it (default false)
> > > >
> > > > The first might be the more flexible solution, but could add a can of
> > > > (support) worms.
> > > >
> > > > What do you think?
> > > >
> > > > Create a nice day!
> > > > Stephan H. Wissel
> > > >
> > > > Phone: +65 96673269
> > > > Blog <https://www.wissel.net/blog> Twitter <
> > >
> > > http://twitter.com/notessensei>
> > >
> > > > LinkedIn <http:/

Re: Customizing the maven-site-plugin Markdown renderer?

[Hervé BOUTEMY]

you can create a GitHub repository, or a collection of repositories
whatever is necessary

Regards,

Hervé

Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> I did a flexmark standalone test, happy to try to integrate that.
> I presume I would define my local moxia modification (after mvn clean
> install) as a site plugin dependency?
> Along those lines:
> 
>
> org.apache.maven.plugins
> maven-site-plugin
> ${maven.site.plugin.version}
> 
> 
> org.apache.maven.plugins
> doxia-module-markdown
> 1.9.1-stw
> 
> 
> 
> 
> Would that work for providing a demo?
> 
> Create a nice day!
> Stephan H. Wissel
> 
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
> 
> On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY  wrote:
> > nice work: dos it mean that you managed to have the rendering as expected?
> > Can you create a little demo and share?
> > 
> > On making the extension configurable and easy to use, it will be complex
> > from a
> > Maven Site Plugin perspective: its relationship with Doxia (the core
> > rendering
> > engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> > Sitetools and Doxia Skins will bring some challenges
> > 
> > That's why we'll need ot go step by step: sharing a first result with a
> > lot of
> > manual config first, then looking on improvement to replace manual config
> > with
> > nice parameters
> > 
> > I would really love to add such extensions, I'll really need your help
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > > Hi Hervé,
> > > 
> > > thank you for your reply, appreciate your swift response.
> > > It seems to be a little more complex ;-) , but started easy (looked like
> > 
> > 1
> > 
> > > line and 1 import)
> > > 
> > > Extensions are loaded like line 145 in the MarkdownParser.class:
> > > extensions.add(
> > > AdminitionExtension.create() );
> > > 
> > > I did a quick check on CSS/JS. When I put them in
> > > /src/site/resources/css
> > > and /src/site/resources/js, they get copied into the target site.
> > > Then I added   
> > > to the site.xml - which also worked. So the prerequites can be handled
> > > in
> > > the site.xml without the need to change any code.
> > > 
> > > However I wouldn't see just to load that one extra plugin always, more
> > 
> > like
> > 
> > > make it configurable. I see two approaches:
> > > - read the name of the plugins from a config setting and leave it to the
> > > user - with all consequences - which one they specify
> > > - pick one (for starters) and have a config true/false flag whether to
> > 
> > load
> > 
> > > it (default false)
> > > 
> > > The first might be the more flexible solution, but could add a can of
> > > (support) worms.
> > > 
> > > What do you think?
> > > 
> > > Create a nice day!
> > > Stephan H. Wissel
> > > 
> > > Phone: +65 96673269
> > > Blog <https://www.wissel.net/blog> Twitter <
> > 
> > http://twitter.com/notessensei>
> > 
> > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > <https://www.xing.com/profile/StephanH_Wissel>
> > > 
> > > On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY 
> > 
> > wrote:
> > > > Hi Stefan,
> > > > 
> > > > The code for Markdown parsing and extensions activation is in Doxia
> > 
> > > > Markdown module:
> > https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/x
> > 
> > > > ref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
> > > > 
> > > > I don't really reviewed how extensions are really activated, but
> > > > having
> > > > now a quick look at this admonition one, I see that flexmark-java
> > 
> > explains
> > 
> > > > some prerequisites that have not been integrated in Doxia:
> > > > https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
> > > > 
> > > > Then I suppose from the code that:
> > > > 1. adding admonition markup will create some html
> > > > 2. but the ren

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

I did a flexmark standalone test, happy to try to integrate that.
I presume I would define my local moxia modification (after mvn clean
install) as a site plugin dependency?
Along those lines:

   
org.apache.maven.plugins
maven-site-plugin
${maven.site.plugin.version}


org.apache.maven.plugins
doxia-module-markdown
1.9.1-stw




Would that work for providing a demo?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY  wrote:

> nice work: dos it mean that you managed to have the rendering as expected?
> Can you create a little demo and share?
>
> On making the extension configurable and easy to use, it will be complex
> from a
> Maven Site Plugin perspective: its relationship with Doxia (the core
> rendering
> engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> Sitetools and Doxia Skins will bring some challenges
>
> That's why we'll need ot go step by step: sharing a first result with a
> lot of
> manual config first, then looking on improvement to replace manual config
> with
> nice parameters
>
> I would really love to add such extensions, I'll really need your help
>
> Regards,
>
> Hervé
>
> Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > Hi Hervé,
> >
> > thank you for your reply, appreciate your swift response.
> > It seems to be a little more complex ;-) , but started easy (looked like
> 1
> > line and 1 import)
> >
> > Extensions are loaded like line 145 in the MarkdownParser.class:
> > extensions.add(
> > AdminitionExtension.create() );
> >
> > I did a quick check on CSS/JS. When I put them in /src/site/resources/css
> > and /src/site/resources/js, they get copied into the target site.
> > Then I added   
> > to the site.xml - which also worked. So the prerequites can be handled in
> > the site.xml without the need to change any code.
> >
> > However I wouldn't see just to load that one extra plugin always, more
> like
> > make it configurable. I see two approaches:
> > - read the name of the plugins from a config setting and leave it to the
> > user - with all consequences - which one they specify
> > - pick one (for starters) and have a config true/false flag whether to
> load
> > it (default false)
> >
> > The first might be the more flexible solution, but could add a can of
> > (support) worms.
> >
> > What do you think?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY 
> wrote:
> > > Hi Stefan,
> > >
> > > The code for Markdown parsing and extensions activation is in Doxia
> > > Markdown module:
> > >
> > >
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/x
> > > ref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
> > >
> > > I don't really reviewed how extensions are really activated, but having
> > > now a quick look at this admonition one, I see that flexmark-java
> explains
> > > some prerequisites that have not been integrated in Doxia:
> > > https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
> > >
> > > Then I suppose from the code that:
> > > 1. adding admonition markup will create some html
> > > 2. but the rendering will not be ok because prerequisites have not been
> > > integrated
> > > 3. and I fear that the issue will be more complex than these
> prerequisites
> > >
> > > Then it's a full topic to investigate, create samples to test, look at
> > > current result, then debug ot see what improvements are necessary
> > >
> > > I personnally don't have time to work on this, but if a group start
> > > working on this topic, I'd be happy to help
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> > > > Hi there,
> > > >
> > > > We are using Markdown in our Maven generated site
> > > > <http://maven.apache.org/plugins/maven-site-plugin/index.html>

Re: Customizing the maven-site-plugin Markdown renderer?

[Hervé BOUTEMY]

nice work: dos it mean that you managed to have the rendering as expected?
Can you create a little demo and share?

On making the extension configurable and easy to use, it will be complex from a 
Maven Site Plugin perspective: its relationship with Doxia (the core rendering 
engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia 
Sitetools and Doxia Skins will bring some challenges

That's why we'll need ot go step by step: sharing a first result with a lot of 
manual config first, then looking on improvement to replace manual config with 
nice parameters

I would really love to add such extensions, I'll really need your help

Regards,

Hervé

Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> Hi Hervé,
> 
> thank you for your reply, appreciate your swift response.
> It seems to be a little more complex ;-) , but started easy (looked like 1
> line and 1 import)
> 
> Extensions are loaded like line 145 in the MarkdownParser.class:
> extensions.add(
> AdminitionExtension.create() );
> 
> I did a quick check on CSS/JS. When I put them in /src/site/resources/css
> and /src/site/resources/js, they get copied into the target site.
> Then I added   
> to the site.xml - which also worked. So the prerequites can be handled in
> the site.xml without the need to change any code.
> 
> However I wouldn't see just to load that one extra plugin always, more like
> make it configurable. I see two approaches:
> - read the name of the plugins from a config setting and leave it to the
> user - with all consequences - which one they specify
> - pick one (for starters) and have a config true/false flag whether to load
> it (default false)
> 
> The first might be the more flexible solution, but could add a can of
> (support) worms.
> 
> What do you think?
> 
> Create a nice day!
> Stephan H. Wissel
> 
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
> 
> On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY  wrote:
> > Hi Stefan,
> > 
> > The code for Markdown parsing and extensions activation is in Doxia
> > Markdown module:
> > 
> > https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/x
> > ref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
> > 
> > I don't really reviewed how extensions are really activated, but having
> > now a quick look at this admonition one, I see that flexmark-java explains
> > some prerequisites that have not been integrated in Doxia:
> > https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
> > 
> > Then I suppose from the code that:
> > 1. adding admonition markup will create some html
> > 2. but the rendering will not be ok because prerequisites have not been
> > integrated
> > 3. and I fear that the issue will be more complex than these prerequisites
> > 
> > Then it's a full topic to investigate, create samples to test, look at
> > current result, then debug ot see what improvements are necessary
> > 
> > I personnally don't have time to work on this, but if a group start
> > working on this topic, I'd be happy to help
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> > > Hi there,
> > > 
> > > We are using Markdown in our Maven generated site
> > > <http://maven.apache.org/plugins/maven-site-plugin/index.html>. Works
> > 
> > like
> > 
> > > a charm. AFAIK the plugin uses Flexmark
> > > <https://github.com/vsch/flexmark-java> under the hood, which supports
> > > the Admonition
> > > extensions
> > > <https://squidfunk.github.io/mkdocs-material/extensions/admonition/>.
> > > 
> > > We would like to use them too, the infoboxes are quite helpful for
> > > documentation. Our site configuration in the pom.xml looks like this:
> > > 
> > > 
> > > 
> > > org.apache.maven.plugins
> > > maven-site-plugin
> > > 3.8.2
> > > 
> > > How could we configure it to recognise the additional markdown?
> > 
> > > Also can be found here:
> > https://stackoverflow.com/questions/61001709/maven-site-generation-using-a
> > dv> 
> > > anced-markdown
> > > 
> > > Create a nice day!
> > > Stephan H. Wissel
> > > 
> > > Phone: +65 96673269
> > > Blog <https://www.wissel.net/blog> Twitter <
> > 
> > http://twitter.com/notessensei>
> > 
> > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > <https://www.xing.com/profile/StephanH_Wissel>
> > 
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hi Hervé,

thank you for your reply, appreciate your swift response.
It seems to be a little more complex ;-) , but started easy (looked like 1
line and 1 import)

Extensions are loaded like line 145 in the MarkdownParser.class:
extensions.add(
AdminitionExtension.create() );

I did a quick check on CSS/JS. When I put them in /src/site/resources/css
and /src/site/resources/js, they get copied into the target site.
Then I added   
to the site.xml - which also worked. So the prerequites can be handled in
the site.xml without the need to change any code.

However I wouldn't see just to load that one extra plugin always, more like
make it configurable. I see two approaches:
- read the name of the plugins from a config setting and leave it to the
user - with all consequences - which one they specify
- pick one (for starters) and have a config true/false flag whether to load
it (default false)

The first might be the more flexible solution, but could add a can of
(support) worms.

What do you think?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY  wrote:

> Hi Stefan,
>
> The code for Markdown parsing and extensions activation is in Doxia
> Markdown module:
>
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/xref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
>
> I don't really reviewed how extensions are really activated, but having
> now a quick look at this admonition one, I see that flexmark-java explains
> some prerequisites that have not been integrated in Doxia:
> https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
>
> Then I suppose from the code that:
> 1. adding admonition markup will create some html
> 2. but the rendering will not be ok because prerequisites have not been
> integrated
> 3. and I fear that the issue will be more complex than these prerequisites
>
> Then it's a full topic to investigate, create samples to test, look at
> current result, then debug ot see what improvements are necessary
>
> I personnally don't have time to work on this, but if a group start
> working on this topic, I'd be happy to help
>
> Regards,
>
> Hervé
>
> Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> > Hi there,
> >
> > We are using Markdown in our Maven generated site
> > <http://maven.apache.org/plugins/maven-site-plugin/index.html>. Works
> like
> > a charm. AFAIK the plugin uses Flexmark
> > <https://github.com/vsch/flexmark-java> under the hood, which supports
> > the Admonition
> > extensions
> > <https://squidfunk.github.io/mkdocs-material/extensions/admonition/>.
> >
> > We would like to use them too, the infoboxes are quite helpful for
> > documentation. Our site configuration in the pom.xml looks like this:
> >
> > 
> > org.apache.maven.plugins
> > maven-site-plugin
> > 3.8.2
> >
> > How could we configure it to recognise the additional markdown?
> >
> > Also can be found here:
> >
> https://stackoverflow.com/questions/61001709/maven-site-generation-using-adv
> > anced-markdown
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Customizing the maven-site-plugin Markdown renderer?

[Hervé BOUTEMY]

Hi Stefan,

The code for Markdown parsing and extensions activation is in Doxia Markdown 
module:
https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/xref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133

I don't really reviewed how extensions are really activated, but having now a 
quick look at this admonition one, I see that flexmark-java explains some 
prerequisites that have not been integrated in Doxia:
https://github.com/vsch/flexmark-java/wiki/Extensions#admonition

Then I suppose from the code that:
1. adding admonition markup will create some html
2. but the rendering will not be ok because prerequisites have not been 
integrated
3. and I fear that the issue will be more complex than these prerequisites

Then it's a full topic to investigate, create samples to test, look at current 
result, then debug ot see what improvements are necessary

I personnally don't have time to work on this, but if a group start working on 
this topic, I'd be happy to help

Regards,

Hervé

Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> Hi there,
> 
> We are using Markdown in our Maven generated site
> <http://maven.apache.org/plugins/maven-site-plugin/index.html>. Works like
> a charm. AFAIK the plugin uses Flexmark
> <https://github.com/vsch/flexmark-java> under the hood, which supports
> the Admonition
> extensions
> <https://squidfunk.github.io/mkdocs-material/extensions/admonition/>.
> 
> We would like to use them too, the infoboxes are quite helpful for
> documentation. Our site configuration in the pom.xml looks like this:
> 
> 
> org.apache.maven.plugins
> maven-site-plugin
> 3.8.2
> 
> How could we configure it to recognise the additional markdown?
> 
> Also can be found here:
> https://stackoverflow.com/questions/61001709/maven-site-generation-using-adv
> anced-markdown
> 
> Create a nice day!
> Stephan H. Wissel
> 
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hi there,

We are using Markdown in our Maven generated site
<http://maven.apache.org/plugins/maven-site-plugin/index.html>. Works like
a charm. AFAIK the plugin uses Flexmark
<https://github.com/vsch/flexmark-java> under the hood, which supports
the Admonition
extensions
<https://squidfunk.github.io/mkdocs-material/extensions/admonition/>.

We would like to use them too, the infoboxes are quite helpful for
documentation. Our site configuration in the pom.xml looks like this:


org.apache.maven.plugins
    maven-site-plugin
3.8.2

How could we configure it to recognise the additional markdown?

Also can be found here:
https://stackoverflow.com/questions/61001709/maven-site-generation-using-advanced-markdown

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>

[ANN] Apache Maven Site Plugin 3.9.0 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Site Plugin, version 3.9.0
 
This plugin is used to generate a site for the project. The generated site also 
includes the project's reports that were configured in the POM.
 
https://maven.apache.org/plugins/maven-site-plugin/
 
You should specify the version in your project's plugin configuration:
 

  org.apache.maven.plugins
  maven-site-plugin
  3.9.0

 
You can download the appropriate sources etc. from the download page:
 
https://maven.apache.org/plugins/maven-site-plugin/download.cgi
 
Release Notes - Maven Site Plugin - Version 3.9.0

** Bug
* [MSITE-847] - "$prerequisiteMavenVersion" text in plugin's documentation
* [MSITE-853] - Upgrade Doxia to 1.9.1 to have Markdown `code` and ``` 
support

** New Feature
* [MSITE-851] - Reproducible Builds: make entries in output jar files 
reproducible (order + timestamp)

** Improvement
* [MSITE-852] - Upgrade Doxia Site Renderer to 1.9.2 to remove Struts 
dependencies
* [MSITE-855] - make build Reproducible
 
Enjoy,
 
-The Apache Maven team



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 3.8.2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 3.8.2.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 3.8.2

** Bug
* [MSITE-823] - Documentation says JDK 1.6 required, doxia 
dependency requires 1.7
* [MSITE-842] - $currentFileName and $alignedFileName are incorrect 
for Maven Report plugins that use several Sink instances


** Improvement
* [MSITE-824] - Generate (X)HTML5 by default
* [MSITE-830] - Dependency upgrades related to identified security 
reports
* [MSITE-836] - when a report mojo fails with a RuntimeException, 
let m-site-p plugin tell which report is failing

* [MSITE-838] - Include support for confluence/docbook/twiki by default

** Dependency upgrade
* [MSITE-758] - upgrade wagon-api from 1.0 to 3.3.1
* [MSITE-839] - Upgrade to Maven Doxia (Sitetools) 1.9
* [MSITE-841] - Upgrade to Maven Doxia Sitetools 1.9.1
* [MSITE-843] - Update Jetty to 9.2.28
* [MSITE-844] - Update requirement to Java 7


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.7.1 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Apache Maven Site 
Plugin, version 3.7.1

The Maven Site Plugin is a plugin that generates a site for the current 
project.

https://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-site-plugin
  3.7.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-site-plugin/download.cgi

Release Notes - Maven Site Plugin - Version 3.7.1

** Bug
* [MSITE-806] - Site generation does not work when no report configured nor 
Doxia document provided
* [MSITE-809] - Documentation: examples/configuring-reports.html includes 
invalid XML
* [MSITE-812] - Missing '/' in log when deploying documentation by 
site:stage
* [MSITE-817] - inherit edit value in site.xml
* [MSITE-818] - site:run fails to find locale when zh_CN is used

** Improvement
* [MSITE-811] - Upgrade parent to 31
* [MSITE-819] - improve display of site rendering with locale info

** Wish
* [MSITE-815] - highlight skin used to render site and documents 
statistics

** Task
* [MSITE-767] - Revert r1729902 caused by DOXIASITETOOLS-155 and fix ITs as 
soon as parent POMs and site.xml descriptors have been upgraded
* [MSITE-821] - add documentation on site plugin dependencies

Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.7 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Apache Maven Site 
Plugin, version 3.7

The Maven Site Plugin is a plugin that generates a site for the current 
project.

http://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-site-plugin
  3.7


You can download the appropriate sources etc. from the download page:
 
https://maven.apache.org/plugins/maven-site-plugin/download.cgi

Release Notes - Maven Site Plugin - Version 3.7

** Bug
* [MSITE-796] - Unable to generate site with JDK9 - 
java.lang.ExceptionInInitializerError / Caused by: 
java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1

** Improvement
* [MSITE-787] - display what reports are added automatically when no 
reportSet is defined
* [MSITE-791] - upgrade Doxia to 1.8 to benefit from new Markdown parser 
(require Java 7)
* [MSITE-797] - simplify stacktrace in case of report plugin execution 
failure
* [MSITE-804] - update Doxia Site Renderer to 1.8

** Task
* [MSITE-792] - drop reportPlugins parameter ("new format")
* [MSITE-802] - Support more than one directory: improve target/generated-
site documentation
* [MSITE-805] - switch to Git

Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.6 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Site Plugin, version 3.6
 
The Site Plugin is used to generate a site for the project. The generated site 
also includes the project's reports that were configured in the POM.

https://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-site-plugin
  3.6


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-site-plugin/download.cgi

Release Notes - Maven Site Plugin - Version 3.6

** Bug
* [MSITE-654] - Appending a slash to the repository URL makes deploying to 
GitHub impossible
* [MSITE-782] - Support for custom Velocity tools has disappeared
* [MSITE-783] - Bad modules links when 'distributionManagement.site.url' 
comes from settings.xml
* [MSITE-786] - Migrating from 3.4 to 3.5.1, a mvn site run now ask me for  
'META-INF/maven/site.vm'

** Improvement
* [MSITE-775] - add info output to site:attach-descriptor
* [MSITE-776] - Upgrade maven-shared-components parent to version 30
* [MSITE-777] - Upgrade of 'plexus-archiver' to version 3.3.
* [MSITE-778] - Upgrade maven-archiver to 3.1.0
* [MSITE-784] - upgrade maven-reporting-exec
* [MSITE-785] - Documentation of saveProcessedContent parameter is empty

** New Feature
* [MSITE-779] - add color to report generation messages

** Task
* [MSITE-780] - Upgrade of plexus-archiver to 3.4.
* [MSITE-781] - Upgrade of maven-archiver to 3.1.1.

** Wish
* [MSITE-705] - Too much information in maven logs during site:deploy in 
sftp...
 
Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: Maven-Site-Plugin: Generated content?

[Hohl, Gerrit]

Hello Jörg,

eh, yes, it's exactly as you say. I created the following structure:

target/generated-site/apt/example2.apt
target/generated-site/resources/example.html

And as expected I get the following files:

target/site/example.html
target/site/example2.html

And somehow it makes sense that the same structure is expected in the 
target/generated-site folder as in the src/site folder.
Makes me wonder why I didn't try that before. :-(

Anyway, thanks a lot. :-)

Regards
Gerrit


-Ursprüngliche Nachricht-
Von: Jörg Schaible [mailto:joerg.schai...@bpm-inspire.com] 
Gesendet: Montag, 7. November 2016 14:35
An: users@maven.apache.org
Betreff: Re: Maven-Site-Plugin: Generated content?

Hi Gerrit,

Hohl, Gerrit wrote:

> Hello everyone, :-)
> 
>  
> 
> I'm trying to create some content for the Maven site during the Maven 
> build process.
> 
>  
> 
> I recognized that the maven-site-plugin has a  
> configuration property which allows defining a directory which holds 
> such generated content.
> 
> Normally it's the target/generated-site folder.
> 
> So I placed an APT as well as a HTML file there.
> 
> But nothing happened.
> 
> So I defined it in the configuration of the maven-site-plugin in the 
> pluginManagement section:
> 
> ${project.build.directory}/generated-site er
> atedSiteDirectory>
> 
> But also that didn't change anything.
> 
> After the Maven build there is still no file in the target/site folder.
> 
> Neither the rendered APT file nor the HTML file.
> 
>  
> 
> Where is my mistake? :-(

The different formats are nomrally extected in different directories (according 
to 
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html).
 Have you tried to create the same structure for the generated-site directory?

Cheers,
Jörg


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven-Site-Plugin: Generated content?

[Jörg Schaible]

Hi Gerrit,

Hohl, Gerrit wrote:

> Hello everyone, :-)
> 
>  
> 
> I'm trying to create some content for the Maven site during the Maven
> build process.
> 
>  
> 
> I recognized that the maven-site-plugin has a 
> configuration property which allows defining a directory which holds
> such generated content.
> 
> Normally it's the target/generated-site folder.
> 
> So I placed an APT as well as a HTML file there.
> 
> But nothing happened.
> 
> So I defined it in the configuration of the maven-site-plugin in the
> pluginManagement section:
> 
> ${project.build.directory}/generated-site atedSiteDirectory>
> 
> But also that didn't change anything.
> 
> After the Maven build there is still no file in the target/site folder.
> 
> Neither the rendered APT file nor the HTML file.
> 
>  
> 
> Where is my mistake? :-(

The different formats are nomrally extected in different directories 
(according to 
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html).
 Have you tried to create the same 
structure for the generated-site directory?

Cheers,
Jörg


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: AW: Maven-Site-Plugin: Generated content?

[Hohl, Gerrit]

Hello Mark,

yes, I guess there is no other way than using an own reporting plugin.
Still I'm curious for what that option


${project.build.directory}/generated-site

is - if it doesn't have any effect.

Regards,
Gerrit

-Ursprüngliche Nachricht-
Von: Mark Prins [mailto:mc.pr...@gmail.com] 
Gesendet: Samstag, 5. November 2016 10:57
An: Maven Users List
Betreff: Re: AW: Maven-Site-Plugin: Generated content?

You probably want to create a reporting plugin that you can add to your pom to 
create that eXtra content, it 's how maven works

Re: AW: Maven-Site-Plugin: Generated content?

[Mark Prins]

You probably want to create a reporting plugin that you can add to your pom
to create that eXtra content, it 's how maven works

AW: Maven-Site-Plugin: Generated content?

[Hohl, Gerrit]

Hello Chris,

thanks for the fast reply. :-)

I had a peak at your project, but I'm not sure if I explained my problem very 
well.
All of the src/main/site content is rendered perfectly and can be found in the 
target/site folder.
But I also want to create some content during the Maven build which is not 
stored in the src/main/site folder, but in a different folder in the target 
folder (I don't want it to be part of the source code management).
It seems that for such generated content the target/generated-site folder is 
the place to be.
But the maven-site-plugin seems to totally ignore any content in that folder.

Regards
Gerrit

-Ursprüngliche Nachricht-
Von: Christofer Dutz [mailto:christofer.d...@c-ware.de] 
Gesendet: Freitag, 4. November 2016 10:08
An: Maven Users List
Betreff: Re: Maven-Site-Plugin: Generated content?

Hi Gerrit,

I am also heavily using the site-plugin to generate the site of the flex 
project.
I didn’t have to provide the generatedSiteDirectory config option at all ... 
As soon as I run: 

mvn site

It generates the „target/site“ directory with all of the site content.

Eventually you could have a look at the maven-site branch of the flex-site repo:
https://git-wip-us.apache.org/repos/asf?p=flex-site.git;a=tree;h=refs/heads/maven-site;hb=refs/heads/maven-site

If you want to generate the site for an apache project, eventually this could 
help (I wrote down everything needed):
http://flex.apache.org/ng/doc-website.html

Chris


Am 04.11.16, 09:20 schrieb "Hohl, Gerrit" <g.h...@aurenz.de>:

Hello everyone, :-)

 

I'm trying to create some content for the Maven site during the Maven
build process.

 

I recognized that the maven-site-plugin has a 
configuration property which allows defining a directory which holds
such generated content.

Normally it's the target/generated-site folder.

So I placed an APT as well as a HTML file there.

But nothing happened.

So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:

${project.build.directory}/generated-site

But also that didn't change anything.

After the Maven build there is still no file in the target/site folder.

Neither the rendered APT file nor the HTML file.

 

Where is my mistake? :-(

 

Regards

Gerrit

 




---
 ssi,-i e-...@v.aer
rdtn mn,-i e-lmeac.g

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven-Site-Plugin: Generated content?

[Christofer Dutz]

Hi Gerrit,

I am also heavily using the site-plugin to generate the site of the flex 
project.
I didn’t have to provide the generatedSiteDirectory config option at all ... 
As soon as I run: 

mvn site

It generates the „target/site“ directory with all of the site content.

Eventually you could have a look at the maven-site branch of the flex-site repo:
https://git-wip-us.apache.org/repos/asf?p=flex-site.git;a=tree;h=refs/heads/maven-site;hb=refs/heads/maven-site

If you want to generate the site for an apache project, eventually this could 
help (I wrote down everything needed):
http://flex.apache.org/ng/doc-website.html

Chris


Am 04.11.16, 09:20 schrieb "Hohl, Gerrit" <g.h...@aurenz.de>:

Hello everyone, :-)

 

I'm trying to create some content for the Maven site during the Maven
build process.

 

I recognized that the maven-site-plugin has a 
configuration property which allows defining a directory which holds
such generated content.

Normally it's the target/generated-site folder.

So I placed an APT as well as a HTML file there.

But nothing happened.

So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:

${project.build.directory}/generated-site

But also that didn't change anything.

After the Maven build there is still no file in the target/site folder.

Neither the rendered APT file nor the HTML file.

 

Where is my mistake? :-(

 

Regards

Gerrit

 

Maven-Site-Plugin: Generated content?

[Hohl, Gerrit]

Hello everyone, :-)

 

I'm trying to create some content for the Maven site during the Maven
build process.

 

I recognized that the maven-site-plugin has a 
configuration property which allows defining a directory which holds
such generated content.

Normally it's the target/generated-site folder.

So I placed an APT as well as a HTML file there.

But nothing happened.

So I defined it in the configuration of the maven-site-plugin in the
pluginManagement section:

${project.build.directory}/generated-site

But also that didn't change anything.

After the Maven build there is still no file in the target/site folder.

Neither the rendered APT file nor the HTML file.

 

Where is my mistake? :-(

 

Regards

Gerrit

 

maven-site-plugin

[Renato Francesco Miracco]

Hi,

I'm trying to use the maven-site-plugin, i configure it into my pom.xml as:


org.apache.maven.plugins
maven-site-plugin
3.5.1

en,fr,it



I can see the site in different languages, but only if i change the url
path.

For example:

my-site/index.html -> uses the default locale, the first defined into
configuration (en).
my-site/fr/index.html -> uses the fr localized pages.

Is there a way to change the page language, just changing the browser
language?

Best regards,
   Renato Miracco

Re: own Maven Site plugin

[Hervé BOUTEMY]

IIRC, you're trying to create a reporting plugin, ie a report that can 
contribute to a Maven site

maven-reporting-impl is the component you need, with included example:
http://maven.apache.org/shared/maven-reporting-impl/

Regards,

Hervé

Le samedi 25 juin 2016 22:44:01 Philipp Kraus a écrit :
> Hello,
> 
> I try to build my first Maven site plugin.
> I have defined a class based on AbstractMojo and
> put the annotation @Mojo( name = "rrd-antlr4", defaultPhase =
> LifecyclePhase.SITE ) on top.
> 
> I overload the execute-method and put my plugin content to the method. I
> build the plugin and deploy it my local Maven repository. I’m testing my
> plugin in a testing project with the pom content 
> 
> 
> 
> 
> de.flashpixx
> rrd-antlr4
> 0.1.0
> 
> …..
> 
> If I run "mvn site“ I get "[INFO] configuring report plugin
> de.flashpixx:rrd-antlr4:0.1.0“ but the execute method is not run / called.
> 
> How I can debug the plugin or fix the execution of the plugin?
> 
> Thanks
> 
> Phil


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: own Maven Site plugin

[Benson Margulies]

It has to be set up as a 'reporting' plugin. I recommend looking at
examples of other such plugins, such as
https://maven.apache.org/plugins/maven-project-info-reports-plugin/

On Sat, Jun 25, 2016 at 4:44 PM, Philipp Kraus
<philipp.kr...@tu-clausthal.de> wrote:
> Hello,
>
> I try to build my first Maven site plugin.
> I have defined a class based on AbstractMojo and
> put the annotation @Mojo( name = "rrd-antlr4", defaultPhase = 
> LifecyclePhase.SITE )
> on top.
>
> I overload the execute-method and put my plugin content to the method. I 
> build the plugin and deploy
> it my local Maven repository. I’m testing my plugin in a testing project with 
> the pom content
> 
>
> 
>
> 
> de.flashpixx
> rrd-antlr4
> 0.1.0
> 
> …..
>
> If I run "mvn site“ I get "[INFO] configuring report plugin 
> de.flashpixx:rrd-antlr4:0.1.0“ but
> the execute method is not run / called.
>
> How I can debug the plugin or fix the execution of the plugin?
>
> Thanks
>
> Phil

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

own Maven Site plugin

[Philipp Kraus]

Hello,

I try to build my first Maven site plugin.
I have defined a class based on AbstractMojo and
put the annotation @Mojo( name = "rrd-antlr4", defaultPhase = 
LifecyclePhase.SITE )
on top.

I overload the execute-method and put my plugin content to the method. I build 
the plugin and deploy
it my local Maven repository. I’m testing my plugin in a testing project with 
the pom content





de.flashpixx
rrd-antlr4
0.1.0

…..

If I run "mvn site“ I get "[INFO] configuring report plugin 
de.flashpixx:rrd-antlr4:0.1.0“ but
the execute method is not run / called.

How I can debug the plugin or fix the execution of the plugin?

Thanks

Phil

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé Boutemy]

Hi,

I just started a vote for Apache Source Release Assembly Descriptor version 
1.0.6, which is a prerequisite. I'll do the vote for Apache parent pom version 
18 just after.

Regards,

Hervé

Le jeudi 28 avril 2016 10:16:46 Maxim Solodovnik a écrit :
> Hello Hervé,
> 
> sorry bothering do you have any roadmap for 18-SNAPSHOT release?
> It is always better to use release versions :)
> 
> On Sat, Apr 9, 2016 at 1:46 AM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> > I knew I did cleanup in some algorithms, but I didn't expect such an
> > improvement in performance: it's great to see!
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le jeudi 7 avril 2016 12:49:37 Maxim Solodovnik a écrit :
> > > Great thing I can notice: build time was reduced from *5:30 min* to
> > 
> > *03:40*
> > 
> > > min !!
> > > great :)
> > > 
> > > On Thu, Apr 7, 2016 at 12:48 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> > > 
> > > wrote:
> > > > great, thanks for the feedback
> > > > 
> > > > Regards,
> > > > 
> > > > Hervé
> > > > 
> > > > Le jeudi 7 avril 2016 12:45:53 Maxim Solodovnik a écrit :
> > > > > seems to work as expected with
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > site was generated as expected
> > > > > I can see no issues with content or layout
> > > > > 
> > > > > I would say: works for me :)
> > > > > 
> > > > > On Thu, Apr 7, 2016 at 12:39 PM, Maxim Solodovnik <
> > 
> > solomax...@gmail.com>
> > 
> > > > > wrote:
> > > > > > I have changed
> > > > > > parent version to be 18-SNAPSHOT
> > > > > > maven-site version to be 3.5
> > > > > > maven-fluido-skin version to be 1.5
> > > > > > 
> > > > > > it seems my site.xml is not valid anymore the error is
> > > > > > 
> > > > > > [ERROR] Failed to execute goal
> > > > > > org.apache.maven.plugins:maven-site-plugin:3.5:site
> > 
> > (generate-site) on
> > 
> > > > > > project openmeetings-parent: SiteToolException: Error parsing site
> > > > > > descriptor: TEXT must be immediately followed by END_TAG and not
> > > > 
> > > > START_TAG
> > > > 
> > > > > > (position: START_TAG seen ..."text/javascript" src="
> > > > > > http://openmeetings.apache.org/js/site.js;>... @40:83) -> [Help 1]
> > > > > > 
> > > > > > 
> > > > > > here:
> > > > > > 
> > > > > > http://openmeetings.apache.org/js/site.js&quot</a>;>
> > > > > > 
> > > > > > 
> > > > > > Will try to check CHANGELOG for maven-site-plugin
> > > > > > 
> > > > > > 
> > > > > > On Thu, Apr 7, 2016 at 12:29 PM, Maxim Solodovnik <
> > > > 
> > > > solomax...@gmail.com>
> > > > 
> > > > > > wrote:
> > > > > >> Thanks for letting me know
> > > > > >> will test right now
> > > > > >> 
> > > > > >> 
> > > > > >> On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <
> > 
> > herve.bout...@free.fr
> > 
> > > > > >> wrote:
> > > > > >>> Hi Maxim,
> > > > > >>> 
> > > > > >>> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which
> > > > 
> > > > contains
> > > > 
> > > > > >>> early
> > > > > >>> interpolation ${this.*} feature [1]
> > > > > >>> 
> > > > > >>> It would be great to have some tests from end users before I do
> > 
> > the
> > 
> > > > > >>> maven-
> > > > > >>> site-plugin 3.5.1 release
> > > > > >>> 
> > > > > >>> Regards,
> > > > > >>> 
> > > > > >>> Hervé
> > > > > >>> 
> > > > > >>> 
> > > > > >>> [1]
> > 
> > http://maven.apache.org/doxia/doxia-sitetools/doxia-i

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Hello Hervé,

sorry bothering do you have any roadmap for 18-SNAPSHOT release?
It is always better to use release versions :)

On Sat, Apr 9, 2016 at 1:46 AM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:

> I knew I did cleanup in some algorithms, but I didn't expect such an
> improvement in performance: it's great to see!
>
> Regards,
>
> Hervé
>
> Le jeudi 7 avril 2016 12:49:37 Maxim Solodovnik a écrit :
> > Great thing I can notice: build time was reduced from *5:30 min* to
> *03:40*
> > min !!
> > great :)
> >
> > On Thu, Apr 7, 2016 at 12:48 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> >
> > wrote:
> > > great, thanks for the feedback
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 7 avril 2016 12:45:53 Maxim Solodovnik a écrit :
> > > > seems to work as expected with
> > > > 
> > > > 
> > > > 
> > > >
> > > > site was generated as expected
> > > > I can see no issues with content or layout
> > > >
> > > > I would say: works for me :)
> > > >
> > > > On Thu, Apr 7, 2016 at 12:39 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > > >
> > > > wrote:
> > > > > I have changed
> > > > > parent version to be 18-SNAPSHOT
> > > > > maven-site version to be 3.5
> > > > > maven-fluido-skin version to be 1.5
> > > > >
> > > > > it seems my site.xml is not valid anymore the error is
> > > > >
> > > > > [ERROR] Failed to execute goal
> > > > > org.apache.maven.plugins:maven-site-plugin:3.5:site
> (generate-site) on
> > > > > project openmeetings-parent: SiteToolException: Error parsing site
> > > > > descriptor: TEXT must be immediately followed by END_TAG and not
> > >
> > > START_TAG
> > >
> > > > > (position: START_TAG seen ..."text/javascript" src="
> > > > > http://openmeetings.apache.org/js/site.js;>... @40:83) -> [Help 1]
> > > > >
> > > > >
> > > > > here:
> > > > > 
> > > > > http://openmeetings.apache.org/js/site.js&quot</a>;>
> > > > > 
> > > > >
> > > > > Will try to check CHANGELOG for maven-site-plugin
> > > > >
> > > > >
> > > > > On Thu, Apr 7, 2016 at 12:29 PM, Maxim Solodovnik <
> > >
> > > solomax...@gmail.com>
> > >
> > > > > wrote:
> > > > >> Thanks for letting me know
> > > > >> will test right now
> > > > >>
> > > > >>
> > > > >> On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <
> herve.bout...@free.fr
> > > > >>
> > > > >> wrote:
> > > > >>> Hi Maxim,
> > > > >>>
> > > > >>> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which
> > >
> > > contains
> > >
> > > > >>> early
> > > > >>> interpolation ${this.*} feature [1]
> > > > >>>
> > > > >>> It would be great to have some tests from end users before I do
> the
> > > > >>> maven-
> > > > >>> site-plugin 3.5.1 release
> > > > >>>
> > > > >>> Regards,
> > > > >>>
> > > > >>> Hervé
> > > > >>>
> > > > >>>
> > > > >>> [1]
> > >
> > >
> http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/in
> > >
> > > > >>> dex.html>>>
> > > > >>>
> > > > >>> Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> > > > >>> > please let me know if you need any help in testing :)
> > > > >>> >
> > > > >>> > On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr>
> wrote:
> > > > >>> > > 18-SNAPSHOT is ready
> > > > >>> > >
> > > > >>> > > but there are a few feedbacks on edge case issues: I'm torn
> if
> > > > >>> > > we
> > > > >>>
> > > > >>> should
> > > > >>>
> > > > &g

Re: Why did the Maven Site Plugin 3.4.1 vanished

[Oliver B. Fischer]

I found this version number in our POMs before upgrading to 3.5.1. Maybe 
it was only a error in our POMs.


Thx,

Oliver

Am 22.04.16 um 00:28 schrieb Hervé BOUTEMY:

Hi,

3.4.1? This version never existed
http://svn.apache.org/viewvc/maven/plugins/tags/

Didn't you look for 3.5.1?

Regards,

Hervé

Le jeudi 21 avril 2016 23:52:25 Oliver B. Fischer a écrit :

Hi,

I just recognized that version 3.4.1 of the Maven Site Plugin vanished
from Maven Central. Does someone how why?

Oliver


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why did the Maven Site Plugin 3.4.1 vanished

[Hervé BOUTEMY]

Hi,

3.4.1? This version never existed
http://svn.apache.org/viewvc/maven/plugins/tags/

Didn't you look for 3.5.1?

Regards,

Hervé

Le jeudi 21 avril 2016 23:52:25 Oliver B. Fischer a écrit :
> Hi,
> 
> I just recognized that version 3.4.1 of the Maven Site Plugin vanished
> from Maven Central. Does someone how why?
> 
> Oliver


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Why did the Maven Site Plugin 3.4.1 vanished

[Oliver B. Fischer]

Hi,

I just recognized that version 3.4.1 of the Maven Site Plugin vanished 
from Maven Central. Does someone how why?


Oliver

--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.5.1 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Apache Maven Site 
Plugin, version 3.5.1

The Maven Site Plugin is a plugin that generates a site for the current 
project.

http://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-site-plugin
  3.5.1


You can download the appropriate sources etc. from the download page:
 
http://maven.apache.org/plugins/maven-site-plugin/download.cgi


Release Notes - Apache Maven Site Plugin - Version 3.5.1

Bug
* [MSITE-771] FAQ Entry for difference between mvn site and mvn site:site is 
incorrect
* [MSITE-769] Can't use property in breadcrumbs items in child module site 
descriptor

Improvement
* [MSITE-768] Support Velocity's #parse and #include
* [MSITE-700] All inclusion of resources up to ${basedir} when Velocity 1.7 is 
used


Enjoy,

-The Maven team


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé BOUTEMY]

I knew I did cleanup in some algorithms, but I didn't expect such an 
improvement in performance: it's great to see!

Regards,

Hervé

Le jeudi 7 avril 2016 12:49:37 Maxim Solodovnik a écrit :
> Great thing I can notice: build time was reduced from *5:30 min* to *03:40*
> min !!
> great :)
> 
> On Thu, Apr 7, 2016 at 12:48 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> 
> wrote:
> > great, thanks for the feedback
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le jeudi 7 avril 2016 12:45:53 Maxim Solodovnik a écrit :
> > > seems to work as expected with
> > > 
> > > 
> > > 
> > > 
> > > site was generated as expected
> > > I can see no issues with content or layout
> > > 
> > > I would say: works for me :)
> > > 
> > > On Thu, Apr 7, 2016 at 12:39 PM, Maxim Solodovnik <solomax...@gmail.com>
> > > 
> > > wrote:
> > > > I have changed
> > > > parent version to be 18-SNAPSHOT
> > > > maven-site version to be 3.5
> > > > maven-fluido-skin version to be 1.5
> > > > 
> > > > it seems my site.xml is not valid anymore the error is
> > > > 
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-site-plugin:3.5:site (generate-site) on
> > > > project openmeetings-parent: SiteToolException: Error parsing site
> > > > descriptor: TEXT must be immediately followed by END_TAG and not
> > 
> > START_TAG
> > 
> > > > (position: START_TAG seen ..."text/javascript" src="
> > > > http://openmeetings.apache.org/js/site.js;>... @40:83) -> [Help 1]
> > > > 
> > > > 
> > > > here:
> > > > 
> > > > http://openmeetings.apache.org/js/site.js&quot</a>;>
> > > > 
> > > > 
> > > > Will try to check CHANGELOG for maven-site-plugin
> > > > 
> > > > 
> > > > On Thu, Apr 7, 2016 at 12:29 PM, Maxim Solodovnik <
> > 
> > solomax...@gmail.com>
> > 
> > > > wrote:
> > > >> Thanks for letting me know
> > > >> will test right now
> > > >> 
> > > >> 
> > > >> On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <herve.bout...@free.fr
> > > >> 
> > > >> wrote:
> > > >>> Hi Maxim,
> > > >>> 
> > > >>> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which
> > 
> > contains
> > 
> > > >>> early
> > > >>> interpolation ${this.*} feature [1]
> > > >>> 
> > > >>> It would be great to have some tests from end users before I do the
> > > >>> maven-
> > > >>> site-plugin 3.5.1 release
> > > >>> 
> > > >>> Regards,
> > > >>> 
> > > >>> Hervé
> > > >>> 
> > > >>> 
> > > >>> [1]
> > 
> > http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/in
> > 
> > > >>> dex.html>>>
> > > >>> 
> > > >>> Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> > > >>> > please let me know if you need any help in testing :)
> > > >>> > 
> > > >>> > On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:
> > > >>> > > 18-SNAPSHOT is ready
> > > >>> > > 
> > > >>> > > but there are a few feedbacks on edge case issues: I'm torn if
> > > >>> > > we
> > > >>> 
> > > >>> should
> > > >>> 
> > > >>> > > release now or wait for 3.5.1
> > > >>> > > 
> > > >>> > > Regards,
> > > >>> > > 
> > > >>> > > Hervé
> > > >>> > > 
> > > >>> > > - Mail original -
> > > >>> > > De: "Maxim Solodovnik" <solomax...@gmail.com>
> > > >>> > > À: "Maven Users List" <users@maven.apache.org>
> > > >>> > > Envoyé: Jeudi 3 Mars 2016 09:54:10
> > > >>> > > Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
> > > >>> > > 
> > > >>> > > Is it time to re

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Great thing I can notice: build time was reduced from *5:30 min* to *03:40*
min !!
great :)

On Thu, Apr 7, 2016 at 12:48 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> great, thanks for the feedback
>
> Regards,
>
> Hervé
>
> Le jeudi 7 avril 2016 12:45:53 Maxim Solodovnik a écrit :
> > seems to work as expected with
> > 
> > 
> > 
> >
> > site was generated as expected
> > I can see no issues with content or layout
> >
> > I would say: works for me :)
> >
> > On Thu, Apr 7, 2016 at 12:39 PM, Maxim Solodovnik <solomax...@gmail.com>
> >
> > wrote:
> > > I have changed
> > > parent version to be 18-SNAPSHOT
> > > maven-site version to be 3.5
> > > maven-fluido-skin version to be 1.5
> > >
> > > it seems my site.xml is not valid anymore the error is
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-site-plugin:3.5:site (generate-site) on
> > > project openmeetings-parent: SiteToolException: Error parsing site
> > > descriptor: TEXT must be immediately followed by END_TAG and not
> START_TAG
> > > (position: START_TAG seen ..."text/javascript" src="
> > > http://openmeetings.apache.org/js/site.js;>... @40:83) -> [Help 1]
> > >
> > >
> > > here:
> > > 
> > > http://openmeetings.apache.org/js/site.js&quot</a>;>
> > > 
> > >
> > > Will try to check CHANGELOG for maven-site-plugin
> > >
> > >
> > > On Thu, Apr 7, 2016 at 12:29 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > >
> > > wrote:
> > >> Thanks for letting me know
> > >> will test right now
> > >>
> > >>
> > >> On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <herve.bout...@free.fr
> >
> > >>
> > >> wrote:
> > >>> Hi Maxim,
> > >>>
> > >>> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which
> contains
> > >>> early
> > >>> interpolation ${this.*} feature [1]
> > >>>
> > >>> It would be great to have some tests from end users before I do the
> > >>> maven-
> > >>> site-plugin 3.5.1 release
> > >>>
> > >>> Regards,
> > >>>
> > >>> Hervé
> > >>>
> > >>>
> > >>> [1]
> > >>>
> http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/in
> > >>> dex.html>>>
> > >>> Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> > >>> > please let me know if you need any help in testing :)
> > >>> >
> > >>> > On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:
> > >>> > > 18-SNAPSHOT is ready
> > >>> > >
> > >>> > > but there are a few feedbacks on edge case issues: I'm torn if we
> > >>>
> > >>> should
> > >>>
> > >>> > > release now or wait for 3.5.1
> > >>> > >
> > >>> > > Regards,
> > >>> > >
> > >>> > > Hervé
> > >>> > >
> > >>> > > - Mail original -
> > >>> > > De: "Maxim Solodovnik" <solomax...@gmail.com>
> > >>> > > À: "Maven Users List" <users@maven.apache.org>
> > >>> > > Envoyé: Jeudi 3 Mars 2016 09:54:10
> > >>> > > Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
> > >>> > >
> > >>> > > Is it time to release apache parent 18? :)
> > >>> > >
> > >>> > > WBR, Maxim
> > >>> > > (from mobile, sorry for the typos)
> > >>> > >
> > >>> > > On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com>
> > >>>
> > >>> wrote:
> > >>> > > > Thanks a lot!
> > >>> > > > I'll wait for the announce and then will test :)
> > >>> > > >
> > >>> > > > On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <
> > >>>
> > >>> herve.bout...@free.fr>
> > >>>
> > >>> > > > wrote:
> > >>> > > >> Hi,
> > >>>

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé BOUTEMY]

great, thanks for the feedback

Regards,

Hervé

Le jeudi 7 avril 2016 12:45:53 Maxim Solodovnik a écrit :
> seems to work as expected with
> 
> 
> 
> 
> site was generated as expected
> I can see no issues with content or layout
> 
> I would say: works for me :)
> 
> On Thu, Apr 7, 2016 at 12:39 PM, Maxim Solodovnik <solomax...@gmail.com>
> 
> wrote:
> > I have changed
> > parent version to be 18-SNAPSHOT
> > maven-site version to be 3.5
> > maven-fluido-skin version to be 1.5
> > 
> > it seems my site.xml is not valid anymore the error is
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.5:site (generate-site) on
> > project openmeetings-parent: SiteToolException: Error parsing site
> > descriptor: TEXT must be immediately followed by END_TAG and not START_TAG
> > (position: START_TAG seen ..."text/javascript" src="
> > http://openmeetings.apache.org/js/site.js;>... @40:83) -> [Help 1]
> > 
> > 
> > here:
> > 
> > http://openmeetings.apache.org/js/site.js&quot</a>;>
> > 
> > 
> > Will try to check CHANGELOG for maven-site-plugin
> > 
> > 
> > On Thu, Apr 7, 2016 at 12:29 PM, Maxim Solodovnik <solomax...@gmail.com>
> > 
> > wrote:
> >> Thanks for letting me know
> >> will test right now
> >> 
> >> 
> >> On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> >> 
> >> wrote:
> >>> Hi Maxim,
> >>> 
> >>> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which contains
> >>> early
> >>> interpolation ${this.*} feature [1]
> >>> 
> >>> It would be great to have some tests from end users before I do the
> >>> maven-
> >>> site-plugin 3.5.1 release
> >>> 
> >>> Regards,
> >>> 
> >>> Hervé
> >>> 
> >>> 
> >>> [1]
> >>> http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/in
> >>> dex.html>>> 
> >>> Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> >>> > please let me know if you need any help in testing :)
> >>> > 
> >>> > On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:
> >>> > > 18-SNAPSHOT is ready
> >>> > > 
> >>> > > but there are a few feedbacks on edge case issues: I'm torn if we
> >>> 
> >>> should
> >>> 
> >>> > > release now or wait for 3.5.1
> >>> > > 
> >>> > > Regards,
> >>> > > 
> >>> > > Hervé
> >>> > > 
> >>> > > - Mail original -
> >>> > > De: "Maxim Solodovnik" <solomax...@gmail.com>
> >>> > > À: "Maven Users List" <users@maven.apache.org>
> >>> > > Envoyé: Jeudi 3 Mars 2016 09:54:10
> >>> > > Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
> >>> > > 
> >>> > > Is it time to release apache parent 18? :)
> >>> > > 
> >>> > > WBR, Maxim
> >>> > > (from mobile, sorry for the typos)
> >>> > > 
> >>> > > On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com>
> >>> 
> >>> wrote:
> >>> > > > Thanks a lot!
> >>> > > > I'll wait for the announce and then will test :)
> >>> > > > 
> >>> > > > On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <
> >>> 
> >>> herve.bout...@free.fr>
> >>> 
> >>> > > > wrote:
> >>> > > >> Hi,
> >>> > > >> 
> >>> > > >> Not sure there is not a misunderstanding about the new
> >>> 
> >>> dependency: it's
> >>> 
> >>> > > on
> >>> > > 
> >>> > > >> maven-site-plugin to override what I did on ASF v17 [1], not your
> >>> > > 
> >>> > > project
> >>> > > 
> >>> > > >> (hopefully, the build tool requirements don't affect your project
> >>> > > >> 
> >>> > > >> dependencies). That is like Velocity downgrade [2]:
> >>> > > >> 

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Thanks for letting me know
will test right now


On Thu, Apr 7, 2016 at 12:26 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> Hi Maxim,
>
> I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which contains
> early
> interpolation ${this.*} feature [1]
>
> It would be great to have some tests from end users before I do the maven-
> site-plugin 3.5.1 release
>
> Regards,
>
> Hervé
>
>
> [1]
> http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/index.html
>
> Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> > please let me know if you need any help in testing :)
> >
> > On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:
> > > 18-SNAPSHOT is ready
> > >
> > > but there are a few feedbacks on edge case issues: I'm torn if we
> should
> > > release now or wait for 3.5.1
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > - Mail original -----
> > > De: "Maxim Solodovnik" <solomax...@gmail.com>
> > > À: "Maven Users List" <users@maven.apache.org>
> > > Envoyé: Jeudi 3 Mars 2016 09:54:10
> > > Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
> > >
> > > Is it time to release apache parent 18? :)
> > >
> > > WBR, Maxim
> > > (from mobile, sorry for the typos)
> > >
> > > On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com>
> wrote:
> > > > Thanks a lot!
> > > > I'll wait for the announce and then will test :)
> > > >
> > > > On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <
> herve.bout...@free.fr>
> > > >
> > > > wrote:
> > > >> Hi,
> > > >>
> > > >> Not sure there is not a misunderstanding about the new dependency:
> it's
> > >
> > > on
> > >
> > > >> maven-site-plugin to override what I did on ASF v17 [1], not your
> > >
> > > project
> > >
> > > >> (hopefully, the build tool requirements don't affect your project
> > > >>
> > > >> dependencies). That is like Velocity downgrade [2]:
> > > >> 
> > > >>
> > > >>   org.apache.maven.plugins
> > > >>   maven-site-plugin
> > > >>   
> > > >>
> > > >> 
> > > >>
> > > >>   org.apache.maven.doxia
> > > >>   doxia-core
> > > >>   1.7
> > > >>
> > > >> 
> > > >>
> > > >>   
> > > >>
> > > >> 
> > > >>
> > > >> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll
> announce
> > > >> when
> > > >> it is ready.
> > > >>
> > > >> Regards,
> > > >>
> > > >> Hervé
> > > >>
> > > >> [1]
> > >
> > >
> http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#
> > > l234>
> > > >> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
> > > >>
> > > >> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
> > > >> > Hello Hervé,
> > > >> >
> > > >> > Thanks for the quick answer
> > > >> > I'll wait for apache parent #18, don't want to add additional
> > >
> > > dependency
> > >
> > > >> > Are you going to announce #18?
> > > >> >
> > > >> >
> > > >> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <
> > >
> > > herve.bout...@free.fr>
> > >
> > > >> > wrote:
> > > >> > > Hi Maxim,
> > > >> > >
> > > >> > > That's typical of a forced dependency to doxia-core version 1.6
> or
> > > >>
> > > >> less
> > > >>
> > > >> > > (which
> > > >> > > is typical from a project inheriting from an ASF version 17
> parent
> > >
> > > POM
> > >
> > > >> > > because
> > > >> > > of MPOM-69 fix).
> > > >> > >
> > > >> > > I'm still waiting for a little more feedback before releasing
&g

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé BOUTEMY]

Hi Maxim,

I just updated 18-SNAPSHOT to use Doxia Sitetools 1.7.1, which contains early 
interpolation ${this.*} feature [1]

It would be great to have some tests from end users before I do the maven-
site-plugin 3.5.1 release

Regards,

Hervé


[1] 
http://maven.apache.org/doxia/doxia-sitetools/doxia-integration-tools/index.html

Le jeudi 3 mars 2016 22:11:59 Maxim Solodovnik a écrit :
> please let me know if you need any help in testing :)
> 
> On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:
> > 18-SNAPSHOT is ready
> > 
> > but there are a few feedbacks on edge case issues: I'm torn if we should
> > release now or wait for 3.5.1
> > 
> > Regards,
> > 
> > Hervé
> > 
> > - Mail original -
> > De: "Maxim Solodovnik" <solomax...@gmail.com>
> > À: "Maven Users List" <users@maven.apache.org>
> > Envoyé: Jeudi 3 Mars 2016 09:54:10
> > Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
> > 
> > Is it time to release apache parent 18? :)
> > 
> > WBR, Maxim
> > (from mobile, sorry for the typos)
> > 
> > On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com> wrote:
> > > Thanks a lot!
> > > I'll wait for the announce and then will test :)
> > > 
> > > On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> > > 
> > > wrote:
> > >> Hi,
> > >> 
> > >> Not sure there is not a misunderstanding about the new dependency: it's
> > 
> > on
> > 
> > >> maven-site-plugin to override what I did on ASF v17 [1], not your
> > 
> > project
> > 
> > >> (hopefully, the build tool requirements don't affect your project
> > >> 
> > >> dependencies). That is like Velocity downgrade [2]:
> > >> 
> > >> 
> > >>   org.apache.maven.plugins
> > >>   maven-site-plugin
> > >>   
> > >>   
> > >> 
> > >> 
> > >>   org.apache.maven.doxia
> > >>   doxia-core
> > >>   1.7
> > >> 
> > >> 
> > >>   
> > >>   
> > >> 
> > >> 
> > >> 
> > >> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce
> > >> when
> > >> it is ready.
> > >> 
> > >> Regards,
> > >> 
> > >> Hervé
> > >> 
> > >> [1]
> > 
> > http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#
> > l234> 
> > >> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
> > >> 
> > >> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
> > >> > Hello Hervé,
> > >> > 
> > >> > Thanks for the quick answer
> > >> > I'll wait for apache parent #18, don't want to add additional
> > 
> > dependency
> > 
> > >> > Are you going to announce #18?
> > >> > 
> > >> > 
> > >> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <
> > 
> > herve.bout...@free.fr>
> > 
> > >> > wrote:
> > >> > > Hi Maxim,
> > >> > > 
> > >> > > That's typical of a forced dependency to doxia-core version 1.6 or
> > >> 
> > >> less
> > >> 
> > >> > > (which
> > >> > > is typical from a project inheriting from an ASF version 17 parent
> > 
> > POM
> > 
> > >> > > because
> > >> > > of MPOM-69 fix).
> > >> > > 
> > >> > > I'm still waiting for a little more feedback before releasing ASF
> > >> 
> > >> parent
> > >> 
> > >> > > POM
> > >> > > version 18 with maven-site-plugin 3.5 (and no Doxia core version
> > >> 
> > >> forcing).
> > >> 
> > >> > > Now, you should simply add a dependency to maven-site-plugin 3.5 to
> > >> > > doxia-core
> > >> > > version 1.7 and everything will work as expected.
> > >> > > 
> > >> > > Regards,
> > >> > > 
> > >> > > Hervé
> > >> > > 
> > >> > > Le mercredi 24 février 2016 11:21:

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

please let me know if you need any help in testing :)

On Thu, Mar 3, 2016 at 10:07 PM, <herve.bout...@free.fr> wrote:

> 18-SNAPSHOT is ready
>
> but there are a few feedbacks on edge case issues: I'm torn if we should
> release now or wait for 3.5.1
>
> Regards,
>
> Hervé
>
> - Mail original -
> De: "Maxim Solodovnik" <solomax...@gmail.com>
> À: "Maven Users List" <users@maven.apache.org>
> Envoyé: Jeudi 3 Mars 2016 09:54:10
> Objet: Re: maven-site-plugin 3.5 ClassNotFoundException
>
> Is it time to release apache parent 18? :)
>
> WBR, Maxim
> (from mobile, sorry for the typos)
> On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com> wrote:
>
> > Thanks a lot!
> > I'll wait for the announce and then will test :)
> >
> > On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> > wrote:
> >
> >> Hi,
> >>
> >> Not sure there is not a misunderstanding about the new dependency: it's
> on
> >> maven-site-plugin to override what I did on ASF v17 [1], not your
> project
> >> (hopefully, the build tool requirements don't affect your project
> >> dependencies). That is like Velocity downgrade [2]:
> >> 
> >>   org.apache.maven.plugins
> >>   maven-site-plugin
> >>   
> >> 
> >>   org.apache.maven.doxia
> >>   doxia-core
> >>   1.7
> >> 
> >>   
> >> 
> >>
> >>
> >> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce
> >> when
> >> it is ready.
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >> [1]
> >>
> >>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#l234
> >>
> >> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
> >>
> >> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
> >> > Hello Hervé,
> >> >
> >> > Thanks for the quick answer
> >> > I'll wait for apache parent #18, don't want to add additional
> dependency
> >> >
> >> > Are you going to announce #18?
> >> >
> >> >
> >> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <
> herve.bout...@free.fr>
> >> >
> >> > wrote:
> >> > > Hi Maxim,
> >> > >
> >> > > That's typical of a forced dependency to doxia-core version 1.6 or
> >> less
> >> > > (which
> >> > > is typical from a project inheriting from an ASF version 17 parent
> POM
> >> > > because
> >> > > of MPOM-69 fix).
> >> > >
> >> > > I'm still waiting for a little more feedback before releasing ASF
> >> parent
> >> > > POM
> >> > > version 18 with maven-site-plugin 3.5 (and no Doxia core version
> >> forcing).
> >> > >
> >> > > Now, you should simply add a dependency to maven-site-plugin 3.5 to
> >> > > doxia-core
> >> > > version 1.7 and everything will work as expected.
> >> > >
> >> > > Regards,
> >> > >
> >> > > Hervé
> >> > >
> >> > > Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
> >> > > > Hello All,
> >> > > >
> >> > > > I'm trying to switch to maven-site-plugin 3.5
> >> > > > unfortunately I'm getting ClassNotFoundException,
> >> > > >
> >> > > > solomax@solomax-pc:$ *mvn -version*
> >> > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> >> > > > 2015-11-10T22:41:47+06:00)
> >> > > > Maven home: /opt/maven
> >> > > > Java version: 1.8.0_66, vendor: Oracle Corporation
> >> > > > Java home: /opt/jdk1.8.0_66/jre
> >> > > > Default locale: en_US, platform encoding: UTF-8
> >> > > > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64",
> >> family:
> >> > > > "unix"
> >> > > >
> >> > > > solomax@solomax-pc:$ *java -version*
> >> > > > java version "1.8.0_66"
> >> > > > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> >> > > > Java HotSpot(TM

Re: maven-site-plugin 3.5 ClassNotFoundException

[herve . boutemy]

18-SNAPSHOT is ready

but there are a few feedbacks on edge case issues: I'm torn if we should 
release now or wait for 3.5.1

Regards,

Hervé

- Mail original -
De: "Maxim Solodovnik" <solomax...@gmail.com>
À: "Maven Users List" <users@maven.apache.org>
Envoyé: Jeudi 3 Mars 2016 09:54:10
Objet: Re: maven-site-plugin 3.5 ClassNotFoundException

Is it time to release apache parent 18? :)

WBR, Maxim
(from mobile, sorry for the typos)
On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com> wrote:

> Thanks a lot!
> I'll wait for the announce and then will test :)
>
> On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> wrote:
>
>> Hi,
>>
>> Not sure there is not a misunderstanding about the new dependency: it's on
>> maven-site-plugin to override what I did on ASF v17 [1], not your project
>> (hopefully, the build tool requirements don't affect your project
>> dependencies). That is like Velocity downgrade [2]:
>> 
>>   org.apache.maven.plugins
>>   maven-site-plugin
>>   
>> 
>>   org.apache.maven.doxia
>>   doxia-core
>>   1.7
>> 
>>   
>> 
>>
>>
>> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce
>> when
>> it is ready.
>>
>> Regards,
>>
>> Hervé
>>
>> [1]
>>
>> http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#l234
>>
>> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
>>
>> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
>> > Hello Hervé,
>> >
>> > Thanks for the quick answer
>> > I'll wait for apache parent #18, don't want to add additional dependency
>> >
>> > Are you going to announce #18?
>> >
>> >
>> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <herve.bout...@free.fr>
>> >
>> > wrote:
>> > > Hi Maxim,
>> > >
>> > > That's typical of a forced dependency to doxia-core version 1.6 or
>> less
>> > > (which
>> > > is typical from a project inheriting from an ASF version 17 parent POM
>> > > because
>> > > of MPOM-69 fix).
>> > >
>> > > I'm still waiting for a little more feedback before releasing ASF
>> parent
>> > > POM
>> > > version 18 with maven-site-plugin 3.5 (and no Doxia core version
>> forcing).
>> > >
>> > > Now, you should simply add a dependency to maven-site-plugin 3.5 to
>> > > doxia-core
>> > > version 1.7 and everything will work as expected.
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
>> > > > Hello All,
>> > > >
>> > > > I'm trying to switch to maven-site-plugin 3.5
>> > > > unfortunately I'm getting ClassNotFoundException,
>> > > >
>> > > > solomax@solomax-pc:$ *mvn -version*
>> > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> > > > 2015-11-10T22:41:47+06:00)
>> > > > Maven home: /opt/maven
>> > > > Java version: 1.8.0_66, vendor: Oracle Corporation
>> > > > Java home: /opt/jdk1.8.0_66/jre
>> > > > Default locale: en_US, platform encoding: UTF-8
>> > > > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64",
>> family:
>> > > > "unix"
>> > > >
>> > > > solomax@solomax-pc:$ *java -version*
>> > > > java version "1.8.0_66"
>> > > > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
>> > > > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>> > > >
>> > > > Ubuntu 14.04.3 LTS
>> > > >
>> > > > 3.4 works as expecting
>> > > >
>> > > > What am I doing wrong?
>> > > >
>> > > > here is the stack trace:
>> > > >
>> > > > [WARNING] Error injecting:
>> org.apache.maven.plugins.site.render.SiteMojo
>> > > > java.lang.NoClassDefFoundError:
>> > > > org/apache/maven/doxia/sink/impl/XhtmlBaseSink
>> > > > at java.lang.ClassLoader.defineClass1(Native Method)
>> > > > at java.lang.ClassL

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Is it time to release apache parent 18? :)

WBR, Maxim
(from mobile, sorry for the typos)
On Feb 27, 2016 14:04, "Maxim Solodovnik" <solomax...@gmail.com> wrote:

> Thanks a lot!
> I'll wait for the announce and then will test :)
>
> On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> wrote:
>
>> Hi,
>>
>> Not sure there is not a misunderstanding about the new dependency: it's on
>> maven-site-plugin to override what I did on ASF v17 [1], not your project
>> (hopefully, the build tool requirements don't affect your project
>> dependencies). That is like Velocity downgrade [2]:
>> 
>>   org.apache.maven.plugins
>>   maven-site-plugin
>>   
>> 
>>   org.apache.maven.doxia
>>   doxia-core
>>   1.7
>> 
>>   
>> 
>>
>>
>> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce
>> when
>> it is ready.
>>
>> Regards,
>>
>> Hervé
>>
>> [1]
>>
>> http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#l234
>>
>> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
>>
>> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
>> > Hello Hervé,
>> >
>> > Thanks for the quick answer
>> > I'll wait for apache parent #18, don't want to add additional dependency
>> >
>> > Are you going to announce #18?
>> >
>> >
>> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <herve.bout...@free.fr>
>> >
>> > wrote:
>> > > Hi Maxim,
>> > >
>> > > That's typical of a forced dependency to doxia-core version 1.6 or
>> less
>> > > (which
>> > > is typical from a project inheriting from an ASF version 17 parent POM
>> > > because
>> > > of MPOM-69 fix).
>> > >
>> > > I'm still waiting for a little more feedback before releasing ASF
>> parent
>> > > POM
>> > > version 18 with maven-site-plugin 3.5 (and no Doxia core version
>> forcing).
>> > >
>> > > Now, you should simply add a dependency to maven-site-plugin 3.5 to
>> > > doxia-core
>> > > version 1.7 and everything will work as expected.
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
>> > > > Hello All,
>> > > >
>> > > > I'm trying to switch to maven-site-plugin 3.5
>> > > > unfortunately I'm getting ClassNotFoundException,
>> > > >
>> > > > solomax@solomax-pc:$ *mvn -version*
>> > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> > > > 2015-11-10T22:41:47+06:00)
>> > > > Maven home: /opt/maven
>> > > > Java version: 1.8.0_66, vendor: Oracle Corporation
>> > > > Java home: /opt/jdk1.8.0_66/jre
>> > > > Default locale: en_US, platform encoding: UTF-8
>> > > > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64",
>> family:
>> > > > "unix"
>> > > >
>> > > > solomax@solomax-pc:$ *java -version*
>> > > > java version "1.8.0_66"
>> > > > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
>> > > > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>> > > >
>> > > > Ubuntu 14.04.3 LTS
>> > > >
>> > > > 3.4 works as expecting
>> > > >
>> > > > What am I doing wrong?
>> > > >
>> > > > here is the stack trace:
>> > > >
>> > > > [WARNING] Error injecting:
>> org.apache.maven.plugins.site.render.SiteMojo
>> > > > java.lang.NoClassDefFoundError:
>> > > > org/apache/maven/doxia/sink/impl/XhtmlBaseSink
>> > > > at java.lang.ClassLoader.defineClass1(Native Method)
>> > > > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
>> > > > at
>> > >
>> > >
>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>> > >
>> > > > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
>> > > > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
>> > > > at

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Thanks a lot!
I'll wait for the announce and then will test :)

On Thu, Feb 25, 2016 at 12:47 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> Hi,
>
> Not sure there is not a misunderstanding about the new dependency: it's on
> maven-site-plugin to override what I did on ASF v17 [1], not your project
> (hopefully, the build tool requirements don't affect your project
> dependencies). That is like Velocity downgrade [2]:
> 
>   org.apache.maven.plugins
>   maven-site-plugin
>   
> 
>   org.apache.maven.doxia
>   doxia-core
>   1.7
> 
>   
> 
>
>
> I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce
> when
> it is ready.
>
> Regards,
>
> Hervé
>
> [1]
>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#l234
>
> [2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html
>
> Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
> > Hello Hervé,
> >
> > Thanks for the quick answer
> > I'll wait for apache parent #18, don't want to add additional dependency
> >
> > Are you going to announce #18?
> >
> >
> > On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> >
> > wrote:
> > > Hi Maxim,
> > >
> > > That's typical of a forced dependency to doxia-core version 1.6 or less
> > > (which
> > > is typical from a project inheriting from an ASF version 17 parent POM
> > > because
> > > of MPOM-69 fix).
> > >
> > > I'm still waiting for a little more feedback before releasing ASF
> parent
> > > POM
> > > version 18 with maven-site-plugin 3.5 (and no Doxia core version
> forcing).
> > >
> > > Now, you should simply add a dependency to maven-site-plugin 3.5 to
> > > doxia-core
> > > version 1.7 and everything will work as expected.
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
> > > > Hello All,
> > > >
> > > > I'm trying to switch to maven-site-plugin 3.5
> > > > unfortunately I'm getting ClassNotFoundException,
> > > >
> > > > solomax@solomax-pc:$ *mvn -version*
> > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > 2015-11-10T22:41:47+06:00)
> > > > Maven home: /opt/maven
> > > > Java version: 1.8.0_66, vendor: Oracle Corporation
> > > > Java home: /opt/jdk1.8.0_66/jre
> > > > Default locale: en_US, platform encoding: UTF-8
> > > > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64",
> family:
> > > > "unix"
> > > >
> > > > solomax@solomax-pc:$ *java -version*
> > > > java version "1.8.0_66"
> > > > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> > > > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> > > >
> > > > Ubuntu 14.04.3 LTS
> > > >
> > > > 3.4 works as expecting
> > > >
> > > > What am I doing wrong?
> > > >
> > > > here is the stack trace:
> > > >
> > > > [WARNING] Error injecting:
> org.apache.maven.plugins.site.render.SiteMojo
> > > > java.lang.NoClassDefFoundError:
> > > > org/apache/maven/doxia/sink/impl/XhtmlBaseSink
> > > > at java.lang.ClassLoader.defineClass1(Native Method)
> > > > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > > > at
> > >
> > > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > >
> > > > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > > > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > > > at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > > > at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > > > at java.security.AccessController.doPrivileged(Native Method)
> > > > at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> > > > at
> > >
> > >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRe
> > > al>
> > > > m.java:401) at
> > >
> > >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfF
> > &

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé BOUTEMY]

Hi,

Not sure there is not a misunderstanding about the new dependency: it's on 
maven-site-plugin to override what I did on ASF v17 [1], not your project 
(hopefully, the build tool requirements don't affect your project 
dependencies). That is like Velocity downgrade [2]:

  org.apache.maven.plugins
  maven-site-plugin
  

  org.apache.maven.doxia
  doxia-core
  1.7

  



I'm waiting for Fluido 1.5 before releasing ASF v18: yes, I'll announce when 
it is ready.

Regards,

Hervé

[1] 
http://svn.apache.org/viewvc/maven/pom/tags/apache-17/pom.xml?view=markup#l234

[2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html

Le mercredi 24 février 2016 13:47:25 Maxim Solodovnik a écrit :
> Hello Hervé,
> 
> Thanks for the quick answer
> I'll wait for apache parent #18, don't want to add additional dependency
> 
> Are you going to announce #18?
> 
> 
> On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> 
> wrote:
> > Hi Maxim,
> > 
> > That's typical of a forced dependency to doxia-core version 1.6 or less
> > (which
> > is typical from a project inheriting from an ASF version 17 parent POM
> > because
> > of MPOM-69 fix).
> > 
> > I'm still waiting for a little more feedback before releasing ASF parent
> > POM
> > version 18 with maven-site-plugin 3.5 (and no Doxia core version forcing).
> > 
> > Now, you should simply add a dependency to maven-site-plugin 3.5 to
> > doxia-core
> > version 1.7 and everything will work as expected.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
> > > Hello All,
> > > 
> > > I'm trying to switch to maven-site-plugin 3.5
> > > unfortunately I'm getting ClassNotFoundException,
> > > 
> > > solomax@solomax-pc:$ *mvn -version*
> > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > 2015-11-10T22:41:47+06:00)
> > > Maven home: /opt/maven
> > > Java version: 1.8.0_66, vendor: Oracle Corporation
> > > Java home: /opt/jdk1.8.0_66/jre
> > > Default locale: en_US, platform encoding: UTF-8
> > > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64", family:
> > > "unix"
> > > 
> > > solomax@solomax-pc:$ *java -version*
> > > java version "1.8.0_66"
> > > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> > > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> > > 
> > > Ubuntu 14.04.3 LTS
> > > 
> > > 3.4 works as expecting
> > > 
> > > What am I doing wrong?
> > > 
> > > here is the stack trace:
> > > 
> > > [WARNING] Error injecting: org.apache.maven.plugins.site.render.SiteMojo
> > > java.lang.NoClassDefFoundError:
> > > org/apache/maven/doxia/sink/impl/XhtmlBaseSink
> > > at java.lang.ClassLoader.defineClass1(Native Method)
> > > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > > at
> > 
> > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > 
> > > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > > at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > > at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > > at java.security.AccessController.doPrivileged(Native Method)
> > > at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> > > at
> > 
> > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRe
> > al> 
> > > m.java:401) at
> > 
> > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfF
> > ir> 
> > > stStrategy.java:42) at
> > 
> > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(C
> > la> 
> > > ssRealm.java:271) at
> > 
> > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java
> > :2> 
> > > 47) at
> > 
> > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java
> > :2> 
> > > 39) at java.lang.ClassLoader.defineClass1(Native Method)
> > > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > > at
> > 
> > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > 
> > > at java.net.URLClassLoader.defineClass(URLClassLoader.

Re: maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Hello Hervé,

Thanks for the quick answer
I'll wait for apache parent #18, don't want to add additional dependency

Are you going to announce #18?


On Wed, Feb 24, 2016 at 12:58 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> Hi Maxim,
>
> That's typical of a forced dependency to doxia-core version 1.6 or less
> (which
> is typical from a project inheriting from an ASF version 17 parent POM
> because
> of MPOM-69 fix).
>
> I'm still waiting for a little more feedback before releasing ASF parent
> POM
> version 18 with maven-site-plugin 3.5 (and no Doxia core version forcing).
>
> Now, you should simply add a dependency to maven-site-plugin 3.5 to
> doxia-core
> version 1.7 and everything will work as expected.
>
> Regards,
>
> Hervé
>
> Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
> > Hello All,
> >
> > I'm trying to switch to maven-site-plugin 3.5
> > unfortunately I'm getting ClassNotFoundException,
> >
> > solomax@solomax-pc:$ *mvn -version*
> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > 2015-11-10T22:41:47+06:00)
> > Maven home: /opt/maven
> > Java version: 1.8.0_66, vendor: Oracle Corporation
> > Java home: /opt/jdk1.8.0_66/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.13.0-63-generic", arch: "amd64", family:
> > "unix"
> >
> > solomax@solomax-pc:$ *java -version*
> > java version "1.8.0_66"
> > Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> >
> > Ubuntu 14.04.3 LTS
> >
> > 3.4 works as expecting
> >
> > What am I doing wrong?
> >
> > here is the stack trace:
> >
> > [WARNING] Error injecting: org.apache.maven.plugins.site.render.SiteMojo
> > java.lang.NoClassDefFoundError:
> > org/apache/maven/doxia/sink/impl/XhtmlBaseSink
> > at java.lang.ClassLoader.defineClass1(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> > at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassReal
> > m.java:401) at
> >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFir
> > stStrategy.java:42) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(Cla
> > ssRealm.java:271) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> > 47) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> > 39) at java.lang.ClassLoader.defineClass1(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> > at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassReal
> > m.java:401) at
> >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFir
> > stStrategy.java:42) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(Cla
> > ssRealm.java:271) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> > 47) at
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> > 39) at java.lang.Class.getDeclaredMethods0(Native Method)
> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> > at java.lang.Class.getDeclaredMethods(Class.java:1975)
> > at
> >
> com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:
> > 688) at
> >
> com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFiel

Re: maven-site-plugin 3.5 ClassNotFoundException

[Hervé BOUTEMY]

Hi Maxim,

That's typical of a forced dependency to doxia-core version 1.6 or less (which 
is typical from a project inheriting from an ASF version 17 parent POM because 
of MPOM-69 fix).

I'm still waiting for a little more feedback before releasing ASF parent POM 
version 18 with maven-site-plugin 3.5 (and no Doxia core version forcing).

Now, you should simply add a dependency to maven-site-plugin 3.5 to doxia-core 
version 1.7 and everything will work as expected.

Regards,

Hervé

Le mercredi 24 février 2016 11:21:00 Maxim Solodovnik a écrit :
> Hello All,
> 
> I'm trying to switch to maven-site-plugin 3.5
> unfortunately I'm getting ClassNotFoundException,
> 
> solomax@solomax-pc:$ *mvn -version*
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T22:41:47+06:00)
> Maven home: /opt/maven
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: /opt/jdk1.8.0_66/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-63-generic", arch: "amd64", family:
> "unix"
> 
> solomax@solomax-pc:$ *java -version*
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> 
> Ubuntu 14.04.3 LTS
> 
> 3.4 works as expecting
> 
> What am I doing wrong?
> 
> here is the stack trace:
> 
> [WARNING] Error injecting: org.apache.maven.plugins.site.render.SiteMojo
> java.lang.NoClassDefFoundError:
> org/apache/maven/doxia/sink/impl/XhtmlBaseSink
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassReal
> m.java:401) at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFir
> stStrategy.java:42) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(Cla
> ssRealm.java:271) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> 47) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> 39) at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassReal
> m.java:401) at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFir
> stStrategy.java:42) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(Cla
> ssRealm.java:271) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> 47) at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:2
> 39) at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
> at
> com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:
> 688) at
> com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPo
> int.java:380) at
> com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(Co
> nstructorBindingImpl.java:164) at
> com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl
> .java:613) at
> com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:569) at
> com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.ja
> va:555) at
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl
> .java:884) at
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(Inj
> ectorImpl.java:805) at
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.ja
> va:282) at
> com.google.inj

maven-site-plugin 3.5 ClassNotFoundException

[Maxim Solodovnik]

Hello All,

I'm trying to switch to maven-site-plugin 3.5
unfortunately I'm getting ClassNotFoundException,

solomax@solomax-pc:$ *mvn -version*
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T22:41:47+06:00)
Maven home: /opt/maven
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_66/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-63-generic", arch: "amd64", family:
"unix"

solomax@solomax-pc:$ *java -version*
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

Ubuntu 14.04.3 LTS

3.4 works as expecting

What am I doing wrong?

here is the stack trace:

[WARNING] Error injecting: org.apache.maven.plugins.site.render.SiteMojo
java.lang.NoClassDefFoundError:
org/apache/maven/doxia/sink/impl/XhtmlBaseSink
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:688)
at
com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:380)
at
com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:164)
at
com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:613)
at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:569)
at
com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:555)
at
com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:884)
at
com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805)
at
com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282)
at
com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214)
at
com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006)
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038)
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
at
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
at
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53)
at
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision

Re: Maven Fluido Skin incompatibility with new maven-site-plugin 3.5

[Hervé BOUTEMY]

Hi Anthony,

Yes, you're completely right: we're working on it, and tried to make clear 
that Fluido Skin 1.4 is not immediately compatible with Maven Site Plugin 3.5 
[1]

It should be done in 1 or 2 weeks, dependings on the order in which we'll have 
to do the work (perhaps we'll need to to a parent pom release first, I still 
have to wotk on this with Michael Osipov).

In the meantime, you can use the "Velocity 1.5 dependency" workaround I 
documented [2]

Regards,

Hervé

[1] http://maven.apache.org/skins/index.html

[2] http://maven.apache.org/plugins/maven-site-plugin/migrate.html

Le samedi 20 février 2016 05:11:06 Anthony Whitford a écrit :
> I noticed that maven-site-plugin 3.5 does not work with maven-fluido-skin
> 1.4… This looks well known from inspecting the JIRA issues for the skin,
> but when will maven-fluido-skin-1.5 be released?
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven Fluido Skin incompatibility with new maven-site-plugin 3.5

[Anthony Whitford]

I noticed that maven-site-plugin 3.5 does not work with maven-fluido-skin 1.4…
This looks well known from inspecting the JIRA issues for the skin, but when 
will maven-fluido-skin-1.5 be released?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.5 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Site Plugin, version 3.5
 
The Site Plugin is used to generate a site for the project. The generated site 
also includes the project's reports that were configured in the POM.
 
http://maven.apache.org/plugins/maven-site-plugin/
 
Notice there are breaking changes to know when upgrading:
http://maven.apache.org/plugins/maven-site-plugin/migrate.html

You should specify the version in your project's plugin configuration:
 

  org.apache.maven.plugins
  maven-site-plugin
  3.5

 
You can download the appropriate sources etc. from the download page:
 
http://maven.apache.org/plugins/maven-site-plugin/download.cgi
 

Release Notes - Maven Site Plugin - Version 3.5

** Sub-task
* [MSITE-762] - Upgrade Velocity from 1.5 to 1.7

** Bug
* [MSITE-135] - inherited site.xml files are interpolated with the 
originating project's model values and not the consumer project's values
* [MSITE-604] - Properties from settings.xml are not recognized in site 
distribution management 
* [MSITE-694] - When maven.site.skip=true, mvn site:jar doesn't skip the 
generation of the jar
* [MSITE-702] - Overriding skin resources / Duplicate copying of skin 
resources
* [MSITE-724] - An API incompatibility was encountered while executing 
org.apache.maven.plugins:maven-site-plugin:3.4:jar
* [MSITE-743] - Automatic breadcrumbs generates URLs inconsistent with 
menus: should point to index.html
* [MSITE-744] - Regression in 3.4: File in `generated-site/resources/` 
ignored unless there is a file in `generated-site/markdown/` too
* [MSITE-750] - site plugin doesn't override correctly parent 
distributionManagement site url with another one defined in child project when 
dav:
* [MSITE-752] - Cannot use server side includes.
* [MSITE-754] - ConcurrentModificationException when using site:run
* [MSITE-760] - when using templateFile, skin is downloaded and info 
message "Rendering site with skin"

** Improvement
* [MSITE-696] - site:deploy try to deploy the site of a sub module even if 
the property maven.site.skip is set to true
* [MSITE-708] - Doc about filtering incorrect about macros rules
* [MSITE-723] - "About" report generated even though index.apt is 
available in "generated-site"
* [MSITE-727] - MavenProject/MavenSession Injection as a paremeter instead 
as a component.
* [MSITE-729] - Update version of plexus-archiver to 2.9
* [MSITE-740] - Allow multiple extensions for given format
* [MSITE-746] - FAQ contains inaccurate description regarding the site 
life cycle
* [MSITE-755] - Upgrade Doxia Sitetools from 1.6 to 1.7
* [MSITE-765] - upgrade Doxia from 1.6 to 1.7

** New Feature
* [MSITE-756] - add an option to dump Velocity processed Doxia files

** Task
* [MSITE-753] - remove deprecated template and templateDirectory 
parameters
* [MSITE-759] - Update "Configuring the Site Descriptor" page for Doxia 
(Sitetools) 1.7
* [MSITE-763] - Fix issues reported by dependency:analyze
* [MSITE-766] - Upgrade to Commons Lang 3

** Wish
* [MSITE-326] - Make input source file encoding default to platform 
encoding

 
Enjoy,
 
-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven site plugin, turn off copyright notice

[Alex O'Ree]

Is there a way to turn off the copyright notice on the bottom of
generated maven sites?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven site plugin, turn off copyright notice

[Karl Heinz Marbaise]

Hi,

On 10/13/15 9:45 PM, Alex O'Ree wrote:

Is there a way to turn off the copyright notice on the bottom of
generated maven sites?


Which of them do you mean exactly ? Can you show an example and mark 
which you mean? Which skin do you use?



Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven site plugin, turn off copyright notice

[Alex O'Ree]

Maybe, it wasn't obvious to me that "Copyright  " was actually the
default "footer". Although it seem obvious now. Maybe an example of
what the default footer is? It may help lazy people like me when using
Ctrl-F "copyright" ;)

On Tue, Oct 13, 2015 at 4:06 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi,
>
> On 10/13/15 9:57 PM, Alex O'Ree wrote:
>>
>> I think I figured it out. It was being injected into the footer.
>> Overriding the footer in the site descriptor appears to have
>> suppressed it. Took me a few minutes to find the solution in the
>> source, but did see it referenced anywhere on the maven site plugin's
>> website
>
> Hm...
>
> http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Custom_footer
>
> might need an improvement? ...
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
>
>>
>> On Tue, Oct 13, 2015 at 3:55 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
>> wrote:
>>>
>>> Hi,
>>>
>>> On 10/13/15 9:45 PM, Alex O'Ree wrote:
>>>>
>>>>
>>>> Is there a way to turn off the copyright notice on the bottom of
>>>> generated maven sites?
>>>
>>>
>>>
>>> Which of them do you mean exactly ? Can you show an example and mark
>>> which
>>> you mean? Which skin do you use?
>>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven site plugin, turn off copyright notice

[Alex O'Ree]

I think I figured it out. It was being injected into the footer.
Overriding the footer in the site descriptor appears to have
suppressed it. Took me a few minutes to find the solution in the
source, but did see it referenced anywhere on the maven site plugin's
website

On Tue, Oct 13, 2015 at 3:55 PM, Karl Heinz Marbaise  wrote:
> Hi,
>
> On 10/13/15 9:45 PM, Alex O'Ree wrote:
>>
>> Is there a way to turn off the copyright notice on the bottom of
>> generated maven sites?
>
>
> Which of them do you mean exactly ? Can you show an example and mark which
> you mean? Which skin do you use?
>
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven site plugin, turn off copyright notice

[Karl Heinz Marbaise]

Hi,

On 10/13/15 9:57 PM, Alex O'Ree wrote:

I think I figured it out. It was being injected into the footer.
Overriding the footer in the site descriptor appears to have
suppressed it. Took me a few minutes to find the solution in the
source, but did see it referenced anywhere on the maven site plugin's
website

Hm...

http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Custom_footer

might need an improvement? ...

Kind regards
Karl Heinz Marbaise





On Tue, Oct 13, 2015 at 3:55 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:

Hi,

On 10/13/15 9:45 PM, Alex O'Ree wrote:


Is there a way to turn off the copyright notice on the bottom of
generated maven sites?



Which of them do you mean exactly ? Can you show an example and mark which
you mean? Which skin do you use?



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven site plugin 3.4 failing to resolve from reactor when run in release cycle

[Hervé BOUTEMY]

what's the mvn command launched?

Regards,

Hervé

Le lundi 29 décembre 2014 22:33:24 Benson Margulies a écrit :
 This is in release:perform;
 
 [INFO] [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
 project ws-bus: failed to get report for
 org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal
 on project integration-test: Could not resolve dependencies for
 project com.basistech.ws:integration-test:jar:0.5.1: Could not find
 artifact com.basistech.ws:ws-bus-launcher:jar:0.5.1 in Nexus
 (http://maven.basistech.net/nexus/content/groups/public) - [Help 1]
 
 This is a tale of two modules: integration-test depends on launcher.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven site plugin 3.4 failing to resolve from reactor when run in release cycle

[Benson Margulies]

mvn release:perform

I've done some archaeology, and this is a very old story with just
about all the projects we have at my job; we generally turn off
site-deploy from release:perform to avoid it, but I accidently lost
that configuration and hit this again. I could capture a -X, but I
have no idea if I can come up with a small repro. It fails just the
same with 3.2.5 as with 3.0.4 (and 2.2.1 before it).


On Tue, Dec 30, 2014 at 6:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
 what's the mvn command launched?

 Regards,

 Hervé

 Le lundi 29 décembre 2014 22:33:24 Benson Margulies a écrit :
 This is in release:perform;

 [INFO] [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
 project ws-bus: failed to get report for
 org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal
 on project integration-test: Could not resolve dependencies for
 project com.basistech.ws:integration-test:jar:0.5.1: Could not find
 artifact com.basistech.ws:ws-bus-launcher:jar:0.5.1 in Nexus
 (http://maven.basistech.net/nexus/content/groups/public) - [Help 1]

 This is a tale of two modules: integration-test depends on launcher.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven site plugin 3.4 failing to resolve from reactor when run in release cycle

[Benson Margulies]

This is in release:perform;

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project ws-bus: failed to get report for
org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal
on project integration-test: Could not resolve dependencies for
project com.basistech.ws:integration-test:jar:0.5.1: Could not find
artifact com.basistech.ws:ws-bus-launcher:jar:0.5.1 in Nexus
(http://maven.basistech.net/nexus/content/groups/public) - [Help 1]

This is a tale of two modules: integration-test depends on launcher.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Plugins to extend the APT format? (For use with the Maven Site plugin)

[Hervé BOUTEMY]

Le mercredi 13 août 2014 23:22:52 Nick Burch a écrit :
 Hi All
 
 For Apache Tika, we currently use the Maven Site plugin, along with the
 APT format for our site content. We are looking to automatically pull in
 snippets of code from svn into the published site, much as the ASF CMS
 supports https://blogs.apache.org/infra/entry/scaling_down_the_cms_to
 
 I'm fairly happy about how to do the snippet-fetching part, what's
 stumping me is finding an example plugin to allow the Maven Site plugin to
 process additional kinds of markup in the APT format.
extending the markup, ie the syntax? Not possible: each supported markup 
language supported by Doxia is a done through a parser, and i don't know any 
parser that has such extension points (and I don't kow how this would be 
feasible)

 (Or failing that,
 any other simple-ish Maven Site plugin supported formats like Markdown)
there is a external Doxia extension which support including a snippet in 
another markup language: see Doxia :: Include Macro, 
http://doxia-include.sourceforge.net/

 
 Could anyone point me to an example for extending one of the formats like
 this?
the only generic extension solution for Doxia is macros (and IIRC, not 
available in each markup language): see 
http://maven.apache.org/doxia/macros/index.html

Regards,

Hervé

 
 Thanks
 Nick
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Plugins to extend the APT format? (For use with the Maven Site plugin)

[Stephen Connolly]

*Not answering your question* I think we have grown to favour moving away
from APT and towards Markdown or Asciidoc as a format at least on the Maven
team (note that we do not have good tooling for Asciidoc yet) most of our
new documentation is driven through Markdown.

I think there are really two plain text mark up formats left standing:
Markdown and Asciidoc. Of those I think Asciidoc is the better format as it
actually has a proper spec... but it could end up being the Betamax of
formats (i.e. technically the best but looses out due to amount of Markdown
usage out there)


On 13 August 2014 18:22, Nick Burch n...@apache.org wrote:

 Hi All

 For Apache Tika, we currently use the Maven Site plugin, along with the
 APT format for our site content. We are looking to automatically pull in
 snippets of code from svn into the published site, much as the ASF CMS
 supports https://blogs.apache.org/infra/entry/scaling_down_the_cms_to

 I'm fairly happy about how to do the snippet-fetching part, what's
 stumping me is finding an example plugin to allow the Maven Site plugin to
 process additional kinds of markup in the APT format. (Or failing that, any
 other simple-ish Maven Site plugin supported formats like Markdown)

 Could anyone point me to an example for extending one of the formats like
 this?

 Thanks
 Nick

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Plugins to extend the APT format? (For use with the Maven Site plugin)

[Nick Burch]

Hi All

For Apache Tika, we currently use the Maven Site plugin, along with the 
APT format for our site content. We are looking to automatically pull in 
snippets of code from svn into the published site, much as the ASF CMS 
supports https://blogs.apache.org/infra/entry/scaling_down_the_cms_to


I'm fairly happy about how to do the snippet-fetching part, what's 
stumping me is finding an example plugin to allow the Maven Site plugin to 
process additional kinds of markup in the APT format. (Or failing that, 
any other simple-ish Maven Site plugin supported formats like Markdown)


Could anyone point me to an example for extending one of the formats like 
this?


Thanks
Nick

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Site Plugin 3.4 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Site Plugin, version 3.4

The Site Plugin is used to generate a site for the project. The generated site 
also includes the project's reports that were configured in the POM.

http://maven.apache.org/plugins/maven-site-plugin/

You should specify the version in your project's plugin configuration:

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-site-plugin/artifactId
  version3.4/version
/plugin

Release Notes - Maven Site Plugin - Version 3.4

** Bug
* [MSITE-121] - Generated html files contain inconsistent new lines
* [MSITE-665] - Site plugin version 3.2 seems to modify a project's 
classpath.
* [MSITE-716] - update doxia-integration-tools to 1.6
* [MSITE-718] - upgrade Doxia base to 1.6
* [MSITE-719] - upgrade Doxia Site Tools to 1.6

** Improvement
* [MSITE-454] - Don't use aggregator mojos for default report set
* [MSITE-516] - reportPlugins should/could inherit more information from 
pluginManagement
* [MSITE-711] - add report's goal name to output
* [MSITE-713] - improve Error during page generation error message
* [MSITE-714] - display statistics about Doxia documents rendered
* [MSITE-720] - upgrade maven-reporting-exec to 1.2
* [MSITE-722] - align display info on executed reports

** Task
* [MSITE-715] - refactor: split Mojos in sub-packages

Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Dariusz Jurojć]

Too much work to do. I think that I'd better find other way to create reports
I need. 

So Mr maven-site-plugin - i don't like you anymore :)

Regards,
Dariusz


Paul Benedict wrote
 If worst comes to worst, modify the POM. It's your local repository. You
 can do whatever you want to those files. Perhaps you should start by
 removing the parent's pom parent.
 
 Of course, this will be a routine to repeat when you get the vendor's
 latest POM.
 
 Cheers,
 Paul





--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793789.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-site-plugin unhappy with jdk 1.8?

[Hervé BOUTEMY]

AFAIK, the m-site-p itself doesn't have any problem with jdk 8, since it 
doesn't care about jdk
but from the little trace you give, there seem to be a reporting plugin that 
is sensitive to jdk 8: yes, some plugins have problems, we track them here [1]

just look at your error traces and you'll see which report is in cause

Regards,

Hervé


[1] http://jira.codehaus.org/browse/MNG-5551

Le jeudi 15 mai 2014 15:35:31 Andy Abendschein a écrit :
 I have recently udated my jdk from 1.7 to 1.8.
 Now I am having problems with the maven-site-plugin which fails with the
 error:
 
  Error during page generation: Error rendering Maven report:
 Unsupported targetJdk value '1.8'.
 
 Is there a way to specify a different targetJdk value to the plugin?
 Is there a plan to update the plugin to accommodate jdk 1.8?
 
 Thanks,
 Andy
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: maven-site-plugin unhappy with jdk 1.8?

[Martin Gainty]

  


 Date: Thu, 15 May 2014 15:35:31 -0600
 From: aabendsch...@powertagging.com
 To: users@maven.apache.org
 Subject: maven-site-plugin unhappy with jdk 1.8?
 
 I have recently udated my jdk from 1.7 to 1.8.
 Now I am having problems with the maven-site-plugin which fails with the 
 error:
 
 Error during page generation: Error rendering Maven report: 
 Unsupported targetJdk value '1.8'.

MGGIYF: looks like this is targetJdk attribute from maven-pmd-plugin

The target JDK to analyse based on. Should match the target used in the 
compiler plugin. Valid values are currently 1.3, 1.4, 1.5 and 1.6. 
Note: support for 1.6 was added in version 2.3 of this plugin. 



Parameter:
expression=${targetJdk}

MGhttp://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven.plugins/maven-pmd-plugin/2.3/org/apache/maven/plugin/pmd/PmdReport.java#PmdReport.0targetJdk;

 
 Is there a way to specify a different targetJdk value to the plugin?
 Is there a plan to update the plugin to accommodate jdk 1.8?
 
 Thanks,
 Andy
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
  

Re: How to avoid checking parent project in maven-site-plugin

[Dariusz Jurojć]

Sure, i have software vendor's poms in my local repository. But I can't
modify them (mostly because vendor releases new version of poms, so I will
have to change every version of their pom - it doesn't have any sense). And
I can't force vendor to add site configuration to their poms. So I have to
do it in my pom. And I tried various methods and in every one of them maven
tried to download site configuration from parent pom. And I'm trying to
avoid this.



--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793085.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Paul Benedict]

If worst comes to worst, modify the POM. It's your local repository. You
can do whatever you want to those files. Perhaps you should start by
removing the parent's pom parent.

Of course, this will be a routine to repeat when you get the vendor's
latest POM.


Cheers,
Paul


On Thu, May 15, 2014 at 3:31 AM, Dariusz Jurojć dariusz.jur...@daprog.plwrote:

 Sure, i have software vendor's poms in my local repository. But I can't
 modify them (mostly because vendor releases new version of poms, so I will
 have to change every version of their pom - it doesn't have any sense). And
 I can't force vendor to add site configuration to their poms. So I have to
 do it in my pom. And I tried various methods and in every one of them maven
 tried to download site configuration from parent pom. And I'm trying to
 avoid this.



 --
 View this message in context:
 http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793085.html
 Sent from the Maven - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

maven-site-plugin unhappy with jdk 1.8?

[Andy Abendschein]

I have recently udated my jdk from 1.7 to 1.8.
Now I am having problems with the maven-site-plugin which fails with the 
error:


Error during page generation: Error rendering Maven report: 
Unsupported targetJdk value '1.8'.


Is there a way to specify a different targetJdk value to the plugin?
Is there a plan to update the plugin to accommodate jdk 1.8?

Thanks,
Andy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Ron Wheeler]

To get it working make a copy of the parent with the stuff that you need.

This will at least tell you if you are on the right track and perhaps 
give you the settings that you need to override in the module pom.


Ron

On 12/05/2014 5:16 AM, Dariusz Jurojc wrote:
I have small maven project. I'm trying to add generating site by 
maven-site-plugin, but it doesn't work. When I'm building this project 
i get following error:


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
project [MY-PROJECT]: SiteToolException: The site descriptor cannot be 
resolved from the repository: ArtifactResolutionException: Unable to 
locate site descriptor: Could not transfer artifact 
[PARENT-PROJECT]:xml:site_en:1.0 from/to eclipse 
(http://maven.eclipse.org/nexus/content/repositories/testing/): 
Connection tohttp://maven.eclipse.org http://maven.eclipse.org/refused


My project is extension for other project, so in my pom.xml is set 
parent project which isn't mine and I can't add site configuration there.


So is there any chance to skip checking parent project's site in site 
generation?


My pom.xml looks like this:

|project
   parent
artifactId|||[PARENT-PROJECT]|/artifactId
groupId||[PARENT-PROJECT-GROUP]/groupId
version1.0/version
/parent
build
 plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
   version3.3/version
   configuration
  reportPlugins
  /reportPlugins
   /configuration
/plugin
 /plugins
   /build
/project
|

And of course i have site.xml file in src/site directory in my project.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Ron Wheeler]

I am not sure what you mean by can't.
You can make any POM you want.
You could start by having Maven give you the effective pom from your 
project.
You could save that and make the changes that you require to get your 
site produced to that pom as a standalone project .


Once you have this working you will know which of the master poms is 
giving you the problem so you can get them to change it or figure out 
what you need to override when using their poms.


Ron

On 13/05/2014 9:47 AM, Dariusz Jurojć wrote:

I can't do it - as I said - I'm only writing extension to very big project
which is not mine. And I have to use pom from that big project. And that
pom has it's own parent and so on... I can't copy and modify all of them. I
just want to create site with some reports for my project regardless of
parent project.



--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793019.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Dariusz Jurojć]

I can't do it - as I said - I'm only writing extension to very big project
which is not mine. And I have to use pom from that big project. And that
pom has it's own parent and so on... I can't copy and modify all of them. I
just want to create site with some reports for my project regardless of
parent project.



--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793019.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to avoid checking parent project in maven-site-plugin

[Paul Benedict]

You need to have the parent projects available to you in your remote or
local repository. You can't build with them missing because the parent has
configuration which you project (the child) depends upon.
On May 14, 2014 12:48 AM, Dariusz Jurojć dariusz.jur...@daprog.pl wrote:

 I can't do it - as I said - I'm only writing extension to very big project
 which is not mine. And I have to use pom from that big project. And that
 pom has it's own parent and so on... I can't copy and modify all of them. I
 just want to create site with some reports for my project regardless of
 parent project.



 --
 View this message in context:
 http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793019.html
 Sent from the Maven - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

How to avoid checking parent project in maven-site-plugin

[Dariusz Jurojc]

I have small maven project. I'm trying to add generating site by 
maven-site-plugin, but it doesn't work. When I'm building this project i 
get following error:


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
project [MY-PROJECT]: SiteToolException: The site descriptor cannot be 
resolved from the repository: ArtifactResolutionException: Unable to 
locate site descriptor: Could not transfer artifact 
[PARENT-PROJECT]:xml:site_en:1.0 from/to eclipse 
(http://maven.eclipse.org/nexus/content/repositories/testing/): 
Connection tohttp://maven.eclipse.org http://maven.eclipse.org/refused


My project is extension for other project, so in my pom.xml is set 
parent project which isn't mine and I can't add site configuration there.


So is there any chance to skip checking parent project's site in site 
generation?


My pom.xml looks like this:

|project
   parent
artifactId|||[PARENT-PROJECT]|/artifactId
groupId||[PARENT-PROJECT-GROUP]/groupId
version1.0/version
/parent
build
 plugins
plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-site-plugin/artifactId
   version3.3/version
   configuration
  reportPlugins
  /reportPlugins
   /configuration
/plugin
 /plugins
   /build
/project
|

And of course i have site.xml file in src/site directory in my project.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org