Re: [ANN] Maven Surefire 3.2.1 released

[Maxim Solodovnik]

Just have upgraded this plugin whithout any issues :)

from mobile (sorry for typos ;)


On Wed, Oct 25, 2023, 19:30 Garret Wilson  wrote:

> Could you clarify whether this means that the plugin will not work
> correctly, and whether we should wait for a patch version that uses the
> correct dependencies instead of upgrading our POMs to use this announced
> version 3.2.1?
>
> Thanks,
>
> Garret
>
> On 10/24/2023 7:42 AM, Thomas Broyer wrote:
> > This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
> > downgraded to 3.0.0?
> > (
> >
> https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
> > says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
> > been released after that commit?)
> >
> > Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
> > but that's another story) and this brings maven-xml-impl et al. that are
> > flagged as not being in the correct scope (brought in as "compile",
> should
> > be "provided"). My tests pass with that version, but I've explicitly
> > downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency
> on
> > plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
> > that.
> >
> > On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov 
> wrote:
> >
> >> The Apache Maven team is pleased to announce the release of the Maven
> >> Surefire version 3.2.1.
> >>
> >> https://maven.apache.org/surefire/
> >>
> >>
> >> Release Notes - Maven Surefire - Version 3.2.1
> >>
> >> ** Bug
> >>   * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
> >> surefire
> >>   * [SUREFIRE-2196] -
> >> maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
> >> braces in the pattern
> >>   * [SUREFIRE-2202] - NullPointerException if super class meets
> >> specific condition
> >>
> >> ** New Feature
> >>   * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
> >> environmentVariables when used in parallel mvn builds
> >>
> >> ** Improvement
> >>   * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5
> versions
> >>   * [SUREFIRE-2178] - classpathDependencyExcludes should support
> >> classifiers
> >>   * [SUREFIRE-2179] - additionalClasspathElements should support
> >> Maven coordinates
> >>   * [SUREFIRE-2182] - Log starter implementation on DEBUG level
> >>
> >> ** Dependency upgrade
> >>   * [SUREFIRE-2188] - Upgrade to Parent 40
> >>
> >>
> >> Enjoy,
> >>
> >> -The Apache Maven team
> >>
> >> -
> >> 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: [ANN] Apache Maven 3.9.1 released

[Maxim Solodovnik]

The subject should be "[ANN] Apache Maven 3.9.2 released" :))

On Thu, 11 May 2023 at 14:25, Tamás Cservenák  wrote:
>
> The Apache Maven team is pleased to announce the release of the
> Apache Maven 3.9.2
>
> Apache Maven is a software project management and comprehension tool. Based
> on the concept of a project object model (POM), Maven can manage a
> project's build, reporting and documentation from a central piece of
> information.
>
> Maven 3.9.2 is available via https://maven.apache.org/download.cgi
>
> The core release is independent of plugin releases. Further releases of
> plugins will be made separately.
>
> If you have any questions, please consult:
>
> - the web site: https://maven.apache.org/
> - the maven-user mailing list: https://maven.apache.org/mailing-lists.html
> - the reference documentation: https://maven.apache.org/ref/3.9.2/
>
> For more information read
> https://maven.apache.org/docs/3.9.2/release-notes.html
>
> Release Notes - Maven - Version 3.9.2
>
> ** Bug
> * [MNG-7750] - Interpolated properties in originalModel in an active
> profile.
> * [MNG-7759] - java.lang.NullPointerException at
> org.apache.maven.repository.internal.DefaultModelCache.newInstance
> (DefaultModelCache.java:37)
> ** Improvement
> * [MNG-7712] - Core should issue a warning if plugin depends on
> maven-compat
> * [MNG-7741] - Add more information when using
> -Dmaven.repo.local.recordReverseTree=true
> * [MNG-7754] - Improvement and extension of plugin validation
> * [MNG-7767] - Tone down plugin validation report
> * [MNG-7778] - Maven should print suppressed exceptions when a mojo
> fails
> ** Task
> * [MNG-7749] - Upgrade animal-sniffer from 1.21 to 1.23
> * [MNG-7774] - Maven config and command line interpolation
>
> Have fun!
> - The Maven Team



-- 
Best regards,
Maxim

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

Re: [ANN] Maven Checkstyle Plugin 3.2.2 released

[Maxim Solodovnik]

Hello,

For whatever reason both 3.2.1 and 3.2.2 are released with

9.3

While latest version ATM 10.9.3

Why to release with outdated dependency?

from mobile (sorry for typos ;)


On Fri, Apr 21, 2023, 02:04 Michael Osipov  wrote:

> The Apache Maven team is pleased to announce the release of the Maven
> Checkstyle Plugin, version 3.2.2.
>
> https://maven.apache.org/plugins/maven-checkstyle-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>org.apache.maven.plugins
>>maven-checkstyle-plugin
>3.2.2
> 
>
>
> Release Notes - Maven Checkstyle Plugin - Version 3.2.2
>
> ** Bug
>  * [MCHECKSTYLE-432] - Inline configuration does not work when
> creating site reports with multiple locales
>
> ** Improvement
>  * [MCHECKSTYLE-426] - Don't use Sink#figure()/Sink#figureCaption()
> since it distorts the output
>
> ** Dependency upgrade
>  * [MCHECKSTYLE-427] - Upgrade m-invoker-plugin to 3.5.0
>
>
> Enjoy,
>
> -The Apache Maven team
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [m-site-plugin] Error reading site descriptor

[Maxim Solodovnik]

Interesting side-effect: Jenkins build are failing and I see no clear
way to fix it :(

On Tue, 4 Apr 2023 at 20:18, Konrad Windszus  wrote:
>
> I created https://issues.apache.org/jira/browse/DOXIASITETOOLS-301 to handle 
> this issue more gracefully.
> Konrad
>
> > On 4. Apr 2023, at 11:00, Michael Osipov  wrote:
> >
> > On 2023/04/03 03:41:28 Maxim Solodovnik wrote:
> >> Hello Michael,
> >>
> >> surprisingly it helped!
> >> Thanks a million! :))
> >
> > Not a surprise, this is on purpose: 
> > https://issues.apache.org/jira/browse/DOXIASITETOOLS-294
> > Read the issue description. The resolution is now done right.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>


-- 
Best regards,
Maxim

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

Re: [m-site-plugin] Error reading site descriptor

[Maxim Solodovnik]

Hello Michael,

surprisingly it helped!
Thanks a million! :))

On Sun, 2 Apr 2023 at 04:10, Michael Osipov  wrote:
>
> rm -rf ~/.m2/repository and try again.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>


-- 
Best regards,
Maxim

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

[m-site-plugin] Error reading site descriptor

[Maxim Solodovnik]

Hello All,

Recently I have updated to 4.0.0-M6
And now I'm getting following output [1]
Everything works as expected with 4.0.0-M5

Is it expected?

What additional info can I provide? :)

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /opt/maven
Java version: 17.0.6, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-67-generic", arch: "amd64", family: "unix"


[1]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:4.0.0-M6:site
(generate-site) on project openmeetings-parent: SiteToolException:
Error reading site descriptor: input contained no data -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:4.0.0-M6:site
(generate-site) on project openmeetings-parent: SiteToolException:
Error reading site descriptor
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:347)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:160)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:73)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:260)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:172)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:100)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException:
SiteToolException: Error reading site descriptor
at 
org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel
(AbstractSiteDescriptorMojo.java:94)
at 
org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext
(AbstractSiteRenderingMojo.java:246)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:138)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:123)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:160)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:73)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:53)
at 

Re: [m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

from mobile (sorry for typos ;)


On Mon, Mar 27, 2023, 16:20 Tamás Cservenák  wrote:

> Maxim,
>
> Sorry, but please be more patient with us :)
> The project team is made of volunteers, and they are doing their best.
>

Thanks for all your hard work and contributions :)

But my first email was sent Feb 14 
Now it is the end of March :))

I did my best to not pushing :))


> Thanks
> Tamas
>
> On Mon, Mar 27, 2023 at 3:46 AM Maxim Solodovnik 
> wrote:
>
> > I get zero responses for my emails :((
> > Maybe I should provide more details?
> > Or my English is not good enough? :(
> >
> > This issue blocks our release process, I'd love to get some help
> >
> > Thanks in advance :)
> >
> > On Sat, 25 Mar 2023 at 23:34, Maxim Solodovnik 
> > wrote:
> > >
> > > Here is the sample project: https://github.com/solomax/javadoc-exclude
> > >
> > > The issue is NOT reproducible if "Automatic-Module-Name" is absent
> > >
> > > On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik 
> > wrote:
> > > >
> > > > Same results with version 3.5.0
> > > >
> > > > On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik  >
> > wrote:
> > > > >
> > > > > Hello All,
> > > > >
> > > > > I'm getting following error while running `javadoc:3.4.1:jar`:
> > > > >
> > > > > [ERROR] Failed to execute goal
> > > > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
> > > > > (attach-javadocs) on project openmeetings-util: Execution
> > > > > attach-javadocs of goal
> > > > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed:
> > Unable
> > > > > to derive module descriptor for
> > > > >
> >
> /home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
> > > > > jool.java.8: Invalid module name: '8' is not a Java identifier ->
> > > > > [Help 1]
> > > > >
> > > > > this "broken" jar is transitive dependency I would like to exclude
> > > > > from javadoc generation
> > > > >
> > > > > [INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util
> > ---
> > > > > [INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
> > > > > [INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
> > > > > [INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
> > > > > [INFO] |  +-
> org.apache.commons:commons-collections4:jar:4.4:compile
> > > > > [INFO] |  +- commons-validator:commons-validator:jar:1.7:compile
> > > > > [INFO] |  |  +-
> commons-beanutils:commons-beanutils:jar:1.9.4:compile
> > > > > [INFO] |  |  +- commons-digester:commons-digester:jar:2.1:compile
> > > > > [INFO] |  |  +- commons-logging:commons-logging:jar:1.2:compile
> > > > > [INFO] |  |  \-
> > commons-collections:commons-collections:jar:3.2.2:compile
> > > > > [INFO] |  +- org.threeten:threeten-extra:jar:1.7.0:compile
> > > > > [INFO] |  \- org.jooq:jool-java-8:jar:0.9.14:compile
> > > > >
> > > > > How this can be achived?
> > > > >
> > > > > I've already tried
> > > > > 
> > > > > 
> > > > >
> > > > > with no luck
> > > > >
> > > > >  has default value `false`
> > > > >
> > > > > Will appreciate any help :)))
> > > > >
> > > > > My configuration is
> > > > >
> > > > > Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> > > > > Maven home: /opt/maven
> > > > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > > > /usr/lib/jvm/java-17-openjdk-amd64
> > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > OS name: "linux", version: "5.15.0-60-generic", arch: "amd64",
> > family: "unix"
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Maxim
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Re: [m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

Thanks a lot for the answer!

I'll try to contact authors of problematic library.

It is weirs this library causing the issue, since it's classes are not
being used directly
(it it is transitive dependency)
Compilation is successful and only Javadoc is failing ...

On Mon, 27 Mar 2023 at 09:17, Daniel Widdis  wrote:
>
> The root of the problem is the automatic module name generation of the 
> jool-java-8 jar file.  By default it becomes jool.java.8 and a number by 
> itself is an illegal portion of a module name.
>
> Without using "Automatic-Module-Name" your project builds on the classpath as 
> always.  When including that, it attempts to build on the module path and the 
> Javadoc plugin apparently does not handle that well.
>
> I fought similar issues for a while and eventually got rid of the problematic 
> dependency.
>
> You might try moditect to insert a module name of your choice.  You might try 
> approaching the authors of jool-java-8 and requesting they provide a valid 
> automatic module name.
>
> On 3/26/23, 6:46 PM, "Maxim Solodovnik"  <mailto:solo...@apache.org>> wrote:
>
>
> I get zero responses for my emails :((
> Maybe I should provide more details?
> Or my English is not good enough? :(
>
>
> This issue blocks our release process, I'd love to get some help
>
>
> Thanks in advance :)
>
>
> On Sat, 25 Mar 2023 at 23:34, Maxim Solodovnik  <mailto:solomax...@gmail.com>> wrote:
> >
> > Here is the sample project: https://github.com/solomax/javadoc-exclude 
> > <https://github.com/solomax/javadoc-exclude>
> >
> > The issue is NOT reproducible if "Automatic-Module-Name" is absent
> >
> > On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik  > <mailto:solomax...@gmail.com>> wrote:
> > >
> > > Same results with version 3.5.0
> > >
> > > On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik  > > <mailto:solomax...@gmail.com>> wrote:
> > > >
> > > > Hello All,
> > > >
> > > > I'm getting following error while running `javadoc:3.4.1:jar`:
> > > >
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
> > > > (attach-javadocs) on project openmeetings-util: Execution
> > > > attach-javadocs of goal
> > > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed: Unable
> > > > to derive module descriptor for
> > > > /home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
> > > > jool.java.8: Invalid module name: '8' is not a Java identifier ->
> > > > [Help 1]
> > > >
> > > > this "broken" jar is transitive dependency I would like to exclude
> > > > from javadoc generation
> > > >
> > > > [INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util ---
> > > > [INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
> > > > [INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
> > > > [INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
> > > > [INFO] | +- org.apache.commons:commons-collections4:jar:4.4:compile
> > > > [INFO] | +- commons-validator:commons-validator:jar:1.7:compile
> > > > [INFO] | | +- commons-beanutils:commons-beanutils:jar:1.9.4:compile
> > > > [INFO] | | +- commons-digester:commons-digester:jar:2.1:compile
> > > > [INFO] | | +- commons-logging:commons-logging:jar:1.2:compile
> > > > [INFO] | | \- commons-collections:commons-collections:jar:3.2.2:compile
> > > > [INFO] | +- org.threeten:threeten-extra:jar:1.7.0:compile
> > > > [INFO] | \- org.jooq:jool-java-8:jar:0.9.14:compile
> > > >
> > > > How this can be achived?
> > > >
> > > > I've already tried
> > > > 
> > > > 
> > > >
> > > > with no luck
> > > >
> > > >  has default value `false`
> > > >
> > > > Will appreciate any help :)))
> > > >
> > > > My configuration is
> > > >
> > > > Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> > > > Maven home: /opt/maven
> > > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > > /usr/lib/jvm/java-17-openjdk-amd64
> > > > Default locale: en_US, platform encoding: UTF-8
> > > > OS name: "linux", version: "5.15.0-60-generic", arch: "amd64", family: 
> > > > "unix"
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
> <mailto:users-unsubscr...@maven.apache.org>
> For additional commands, e-mail: users-h...@maven.apache.org 
> <mailto: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

Re: [m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

I get zero responses for my emails :((
Maybe I should provide more details?
Or my English is not good enough? :(

This issue blocks our release process, I'd love to get some help

Thanks in advance :)

On Sat, 25 Mar 2023 at 23:34, Maxim Solodovnik  wrote:
>
> Here is the sample project: https://github.com/solomax/javadoc-exclude
>
> The issue is NOT reproducible if "Automatic-Module-Name" is absent
>
> On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik  wrote:
> >
> > Same results with version 3.5.0
> >
> > On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik  wrote:
> > >
> > > Hello All,
> > >
> > > I'm getting following error while running `javadoc:3.4.1:jar`:
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
> > > (attach-javadocs) on project openmeetings-util: Execution
> > > attach-javadocs of goal
> > > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed: Unable
> > > to derive module descriptor for
> > > /home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
> > > jool.java.8: Invalid module name: '8' is not a Java identifier ->
> > > [Help 1]
> > >
> > > this "broken" jar is transitive dependency I would like to exclude
> > > from javadoc generation
> > >
> > > [INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util ---
> > > [INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
> > > [INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
> > > [INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
> > > [INFO] |  +- org.apache.commons:commons-collections4:jar:4.4:compile
> > > [INFO] |  +- commons-validator:commons-validator:jar:1.7:compile
> > > [INFO] |  |  +- commons-beanutils:commons-beanutils:jar:1.9.4:compile
> > > [INFO] |  |  +- commons-digester:commons-digester:jar:2.1:compile
> > > [INFO] |  |  +- commons-logging:commons-logging:jar:1.2:compile
> > > [INFO] |  |  \- commons-collections:commons-collections:jar:3.2.2:compile
> > > [INFO] |  +- org.threeten:threeten-extra:jar:1.7.0:compile
> > > [INFO] |  \- org.jooq:jool-java-8:jar:0.9.14:compile
> > >
> > > How this can be achived?
> > >
> > > I've already tried
> > > 
> > > 
> > >
> > > with no luck
> > >
> > >  has default value `false`
> > >
> > > Will appreciate any help :)))
> > >
> > > My configuration is
> > >
> > > Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> > > Maven home: /opt/maven
> > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > /usr/lib/jvm/java-17-openjdk-amd64
> > > Default locale: en_US, platform encoding: UTF-8
> > > OS name: "linux", version: "5.15.0-60-generic", arch: "amd64", family: 
> > > "unix"
> > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim

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

Re: [m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

Here is the sample project: https://github.com/solomax/javadoc-exclude

The issue is NOT reproducible if "Automatic-Module-Name" is absent

On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik  wrote:
>
> Same results with version 3.5.0
>
> On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik  wrote:
> >
> > Hello All,
> >
> > I'm getting following error while running `javadoc:3.4.1:jar`:
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
> > (attach-javadocs) on project openmeetings-util: Execution
> > attach-javadocs of goal
> > org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed: Unable
> > to derive module descriptor for
> > /home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
> > jool.java.8: Invalid module name: '8' is not a Java identifier ->
> > [Help 1]
> >
> > this "broken" jar is transitive dependency I would like to exclude
> > from javadoc generation
> >
> > [INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util ---
> > [INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
> > [INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
> > [INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
> > [INFO] |  +- org.apache.commons:commons-collections4:jar:4.4:compile
> > [INFO] |  +- commons-validator:commons-validator:jar:1.7:compile
> > [INFO] |  |  +- commons-beanutils:commons-beanutils:jar:1.9.4:compile
> > [INFO] |  |  +- commons-digester:commons-digester:jar:2.1:compile
> > [INFO] |  |  +- commons-logging:commons-logging:jar:1.2:compile
> > [INFO] |  |  \- commons-collections:commons-collections:jar:3.2.2:compile
> > [INFO] |  +- org.threeten:threeten-extra:jar:1.7.0:compile
> > [INFO] |  \- org.jooq:jool-java-8:jar:0.9.14:compile
> >
> > How this can be achived?
> >
> > I've already tried
> > 
> > 
> >
> > with no luck
> >
> >  has default value `false`
> >
> > Will appreciate any help :)))
> >
> > My configuration is
> >
> > Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> > Maven home: /opt/maven
> > Java version: 17.0.5, vendor: Private Build, runtime:
> > /usr/lib/jvm/java-17-openjdk-amd64
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "5.15.0-60-generic", arch: "amd64", family: 
> > "unix"
> >
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim



-- 
Best regards,
Maxim

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

Re: [m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

Same results with version 3.5.0

On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik  wrote:
>
> Hello All,
>
> I'm getting following error while running `javadoc:3.4.1:jar`:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
> (attach-javadocs) on project openmeetings-util: Execution
> attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed: Unable
> to derive module descriptor for
> /home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
> jool.java.8: Invalid module name: '8' is not a Java identifier ->
> [Help 1]
>
> this "broken" jar is transitive dependency I would like to exclude
> from javadoc generation
>
> [INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util ---
> [INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
> [INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
> [INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
> [INFO] |  +- org.apache.commons:commons-collections4:jar:4.4:compile
> [INFO] |  +- commons-validator:commons-validator:jar:1.7:compile
> [INFO] |  |  +- commons-beanutils:commons-beanutils:jar:1.9.4:compile
> [INFO] |  |  +- commons-digester:commons-digester:jar:2.1:compile
> [INFO] |  |  +- commons-logging:commons-logging:jar:1.2:compile
> [INFO] |  |  \- commons-collections:commons-collections:jar:3.2.2:compile
> [INFO] |  +- org.threeten:threeten-extra:jar:1.7.0:compile
> [INFO] |  \- org.jooq:jool-java-8:jar:0.9.14:compile
>
> How this can be achived?
>
> I've already tried
> 
> 
>
> with no luck
>
>  has default value `false`
>
> Will appreciate any help :)))
>
> My configuration is
>
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /opt/maven
> Java version: 17.0.5, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-60-generic", arch: "amd64", family: "unix"
>
>
>
>
> --
> Best regards,
> Maxim



-- 
Best regards,
Maxim

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

[m-javadoc-plugin] how to exclude transitive dependency

[Maxim Solodovnik]

Hello All,

I'm getting following error while running `javadoc:3.4.1:jar`:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
(attach-javadocs) on project openmeetings-util: Execution
attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar failed: Unable
to derive module descriptor for
/home/solomax/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:
jool.java.8: Invalid module name: '8' is not a Java identifier ->
[Help 1]

this "broken" jar is transitive dependency I would like to exclude
from javadoc generation

[INFO] --- dependency:3.5.0:tree (default-cli) @ openmeetings-util ---
[INFO] org.apache.openmeetings:openmeetings-util:jar:7.1.0-SNAPSHOT
[INFO] +- org.dom4j:dom4j:jar:2.1.4:compile
[INFO] +- org.mnode.ical4j:ical4j:jar:4.0.0-beta5:compile
[INFO] |  +- org.apache.commons:commons-collections4:jar:4.4:compile
[INFO] |  +- commons-validator:commons-validator:jar:1.7:compile
[INFO] |  |  +- commons-beanutils:commons-beanutils:jar:1.9.4:compile
[INFO] |  |  +- commons-digester:commons-digester:jar:2.1:compile
[INFO] |  |  +- commons-logging:commons-logging:jar:1.2:compile
[INFO] |  |  \- commons-collections:commons-collections:jar:3.2.2:compile
[INFO] |  +- org.threeten:threeten-extra:jar:1.7.0:compile
[INFO] |  \- org.jooq:jool-java-8:jar:0.9.14:compile

How this can be achived?

I've already tried



with no luck

 has default value `false`

Will appreciate any help :)))

My configuration is

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /opt/maven
Java version: 17.0.5, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-60-generic", arch: "amd64", family: "unix"




-- 
Best regards,
Maxim

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

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

maven-javadoc-plugin:3.4.1 - same error :(((

On Wed, 20 Jul 2022 at 22:19, Maxim Solodovnik  wrote:
>
> done,
>
> same error :(
>
> On Wed, 20 Jul 2022 at 22:13, Maxim Solodovnik  wrote:
> >
> > well,
> >
> > m-javadoc-plugin is being called at `*db` module only which is only
> > depends on `*util` module
> > both has `module-info.java`
> >
> > let me add `module-info.java` to all modules (not sure why) so we can
> > ensure this is not a problem :)
> >
> > On Wed, 20 Jul 2022 at 21:51, Daniel Widdis  wrote:
> > >
> > > Some modules have module-info.java and some don’t.  That’s exactly what 
> > > the error says.
> > >
> > > > On Jul 20, 2022, at 7:24 AM, Maxim Solodovnik  
> > > > wrote:
> > > >
> > > > On Tue, 19 Jul 2022 at 17:20, Olivier Lamy  wrote:
> > > >>
> > > >>> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik  
> > > >>> wrote:
> > > >>>
> > > >>> On Tue, 19 Jul 2022 at 13:16, Daniel Widdis  wrote:
> > > >>>>
> > > >>>>> The only problem of having both is redundancy :)
> > > >>>>
> > > >>>> Technically speaking, you always have an automatic module name even 
> > > >>>> if
> > > >>> you don't explicitly name it.  It will use your jar filename to deduce
> > > >>> one.   Unless you use a reserved word in your jar, and then the world
> > > >>> breaks. __
> > > >>>
> > > >>> I thought maybe this is the issue in m-javadoc-plugin: it is weird to
> > > >>> check `automatic module name` in manifest if module-info.java present
> > > >>>
> > > >>
> > > >> Sounds possibly a bug.
> > > >> Do you have an easy project to reproduce you could provide?
> > > >>
> > > >
> > > > sorry for delay :)
> > > > here is very simple example project:
> > > > https://github.com/solomax/multimodule-with-war
> > > >
> > > >>
> > > >>
> > > >>>
> > > >>>
> > > >>>>
> > > >>>> On 7/18/22, 11:07 PM, "Maxim Solodovnik"  
> > > >>>> wrote:
> > > >>>>
> > > >>>>Thanks for the answer Daniel :)
> > > >>>>
> > > >>>>On Tue, 19 Jul 2022 at 13:03, Daniel Widdis 
> > > >>> wrote:
> > > >>>>>
> > > >>>>> I think you're asking on the right list.  And it's not a "basic"
> > > >>> question but it isn't an obvious answer either.
> > > >>>>>
> > > >>>>> I'm not sure your question has enough detail for anyone to deduce
> > > >>> the answer.  Linking to your project may help you get more attention 
> > > >>> on it.
> > > >>>>>
> > > >>>>> FWIW, I have both an automatic module name and module-info in my
> > > >>> modular projects and it doesn't cause any problems, but that's 
> > > >>> clearly not
> > > >>> your problem.
> > > >>>>
> > > >>>>The only problem of having both is redundancy :)
> > > >>>>(and they should be in-sync)
> > > >>>>
> > > >>>>everything works as expected in case `Automatic-Module-Name` is in
> > > >>> manifest
> > > >>>>
> > > >>>>I'll try to create simple project to illustrate the problem :)
> > > >>>>
> > > >>>>>
> > > >>>>> On 7/18/22, 10:55 PM, "Maxim Solodovnik" 
> > > >>> wrote:
> > > >>>>>
> > > >>>>>Hello,
> > > >>>>>
> > > >>>>>Is the question too basic?
> > > >>>>>Or maybe I'm asking wrong list? :)
> > > >>>>>
> > > >>>>>On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik <
> > > >>> solomax...@gmail.com> wrote:
> > > >>>>>>
> > > >>>>>> Hello All,
> > > >>>>>>
> > > >>>>>> I'm trying to migra

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

done,

same error :(

On Wed, 20 Jul 2022 at 22:13, Maxim Solodovnik  wrote:
>
> well,
>
> m-javadoc-plugin is being called at `*db` module only which is only
> depends on `*util` module
> both has `module-info.java`
>
> let me add `module-info.java` to all modules (not sure why) so we can
> ensure this is not a problem :)
>
> On Wed, 20 Jul 2022 at 21:51, Daniel Widdis  wrote:
> >
> > Some modules have module-info.java and some don’t.  That’s exactly what the 
> > error says.
> >
> > > On Jul 20, 2022, at 7:24 AM, Maxim Solodovnik  
> > > wrote:
> > >
> > > On Tue, 19 Jul 2022 at 17:20, Olivier Lamy  wrote:
> > >>
> > >>> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik  
> > >>> wrote:
> > >>>
> > >>> On Tue, 19 Jul 2022 at 13:16, Daniel Widdis  wrote:
> > >>>>
> > >>>>> The only problem of having both is redundancy :)
> > >>>>
> > >>>> Technically speaking, you always have an automatic module name even if
> > >>> you don't explicitly name it.  It will use your jar filename to deduce
> > >>> one.   Unless you use a reserved word in your jar, and then the world
> > >>> breaks. __
> > >>>
> > >>> I thought maybe this is the issue in m-javadoc-plugin: it is weird to
> > >>> check `automatic module name` in manifest if module-info.java present
> > >>>
> > >>
> > >> Sounds possibly a bug.
> > >> Do you have an easy project to reproduce you could provide?
> > >>
> > >
> > > sorry for delay :)
> > > here is very simple example project:
> > > https://github.com/solomax/multimodule-with-war
> > >
> > >>
> > >>
> > >>>
> > >>>
> > >>>>
> > >>>> On 7/18/22, 11:07 PM, "Maxim Solodovnik"  wrote:
> > >>>>
> > >>>>Thanks for the answer Daniel :)
> > >>>>
> > >>>>On Tue, 19 Jul 2022 at 13:03, Daniel Widdis 
> > >>> wrote:
> > >>>>>
> > >>>>> I think you're asking on the right list.  And it's not a "basic"
> > >>> question but it isn't an obvious answer either.
> > >>>>>
> > >>>>> I'm not sure your question has enough detail for anyone to deduce
> > >>> the answer.  Linking to your project may help you get more attention on 
> > >>> it.
> > >>>>>
> > >>>>> FWIW, I have both an automatic module name and module-info in my
> > >>> modular projects and it doesn't cause any problems, but that's clearly 
> > >>> not
> > >>> your problem.
> > >>>>
> > >>>>The only problem of having both is redundancy :)
> > >>>>(and they should be in-sync)
> > >>>>
> > >>>>everything works as expected in case `Automatic-Module-Name` is in
> > >>> manifest
> > >>>>
> > >>>>I'll try to create simple project to illustrate the problem :)
> > >>>>
> > >>>>>
> > >>>>> On 7/18/22, 10:55 PM, "Maxim Solodovnik" 
> > >>> wrote:
> > >>>>>
> > >>>>>Hello,
> > >>>>>
> > >>>>>Is the question too basic?
> > >>>>>Or maybe I'm asking wrong list? :)
> > >>>>>
> > >>>>>On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik <
> > >>> solomax...@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Hello All,
> > >>>>>>
> > >>>>>> I'm trying to migrate our project to JPMS
> > >>>>>> After adding module-info.java to my modules (and removing
> > >>> explicitly
> > >>>>>> set `Automatic-Module-Name`)
> > >>>>>> I'm getting:
> > >>>>>>
> > >>>>>> [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork
> > >>> (default)
> > >>>>>> [ERROR] Creating an aggregated report for both named and
> > >>> unnamed
> > >>>>>> modules is not possible.
> > >>>>>> [ERROR] Ensure that every module has a module descriptor 

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

well,

m-javadoc-plugin is being called at `*db` module only which is only
depends on `*util` module
both has `module-info.java`

let me add `module-info.java` to all modules (not sure why) so we can
ensure this is not a problem :)

On Wed, 20 Jul 2022 at 21:51, Daniel Widdis  wrote:
>
> Some modules have module-info.java and some don’t.  That’s exactly what the 
> error says.
>
> > On Jul 20, 2022, at 7:24 AM, Maxim Solodovnik  wrote:
> >
> > On Tue, 19 Jul 2022 at 17:20, Olivier Lamy  wrote:
> >>
> >>> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik  
> >>> wrote:
> >>>
> >>> On Tue, 19 Jul 2022 at 13:16, Daniel Widdis  wrote:
> >>>>
> >>>>> The only problem of having both is redundancy :)
> >>>>
> >>>> Technically speaking, you always have an automatic module name even if
> >>> you don't explicitly name it.  It will use your jar filename to deduce
> >>> one.   Unless you use a reserved word in your jar, and then the world
> >>> breaks. __
> >>>
> >>> I thought maybe this is the issue in m-javadoc-plugin: it is weird to
> >>> check `automatic module name` in manifest if module-info.java present
> >>>
> >>
> >> Sounds possibly a bug.
> >> Do you have an easy project to reproduce you could provide?
> >>
> >
> > sorry for delay :)
> > here is very simple example project:
> > https://github.com/solomax/multimodule-with-war
> >
> >>
> >>
> >>>
> >>>
> >>>>
> >>>> On 7/18/22, 11:07 PM, "Maxim Solodovnik"  wrote:
> >>>>
> >>>>Thanks for the answer Daniel :)
> >>>>
> >>>>On Tue, 19 Jul 2022 at 13:03, Daniel Widdis 
> >>> wrote:
> >>>>>
> >>>>> I think you're asking on the right list.  And it's not a "basic"
> >>> question but it isn't an obvious answer either.
> >>>>>
> >>>>> I'm not sure your question has enough detail for anyone to deduce
> >>> the answer.  Linking to your project may help you get more attention on 
> >>> it.
> >>>>>
> >>>>> FWIW, I have both an automatic module name and module-info in my
> >>> modular projects and it doesn't cause any problems, but that's clearly not
> >>> your problem.
> >>>>
> >>>>The only problem of having both is redundancy :)
> >>>>(and they should be in-sync)
> >>>>
> >>>>everything works as expected in case `Automatic-Module-Name` is in
> >>> manifest
> >>>>
> >>>>I'll try to create simple project to illustrate the problem :)
> >>>>
> >>>>>
> >>>>> On 7/18/22, 10:55 PM, "Maxim Solodovnik" 
> >>> wrote:
> >>>>>
> >>>>>Hello,
> >>>>>
> >>>>>Is the question too basic?
> >>>>>Or maybe I'm asking wrong list? :)
> >>>>>
> >>>>>On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik <
> >>> solomax...@gmail.com> wrote:
> >>>>>>
> >>>>>> Hello All,
> >>>>>>
> >>>>>> I'm trying to migrate our project to JPMS
> >>>>>> After adding module-info.java to my modules (and removing
> >>> explicitly
> >>>>>> set `Automatic-Module-Name`)
> >>>>>> I'm getting:
> >>>>>>
> >>>>>> [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork
> >>> (default)
> >>>>>> [ERROR] Creating an aggregated report for both named and
> >>> unnamed
> >>>>>> modules is not possible.
> >>>>>> [ERROR] Ensure that every module has a module descriptor or
> >>> is a jar
> >>>>>> with a MANIFEST.MF containing an Automatic-Module-Name.
> >>>>>>
> >>>>>> I thought `Automatic-Module-Name` should be added only if
> >>>>>> `module-info.java` is missing
> >>>>>> Is it bug in maven-javadoc-plugin or maybe I'm doing
> >>> something wrong? :)
> >>>>>>
> >>>>>> java 17
> >>>>>> Apache Maven 3.8.5
> >>>>>>
> >>>>&

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

On Tue, 19 Jul 2022 at 17:20, Olivier Lamy  wrote:
>
> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik  wrote:
>
> > On Tue, 19 Jul 2022 at 13:16, Daniel Widdis  wrote:
> > >
> > > > The only problem of having both is redundancy :)
> > >
> > > Technically speaking, you always have an automatic module name even if
> > you don't explicitly name it.  It will use your jar filename to deduce
> > one.   Unless you use a reserved word in your jar, and then the world
> > breaks. __
> >
> > I thought maybe this is the issue in m-javadoc-plugin: it is weird to
> > check `automatic module name` in manifest if module-info.java present
> >
>
> Sounds possibly a bug.
> Do you have an easy project to reproduce you could provide?
>

sorry for delay :)
here is very simple example project:
https://github.com/solomax/multimodule-with-war

>
>
> >
> >
> > >
> > > On 7/18/22, 11:07 PM, "Maxim Solodovnik"  wrote:
> > >
> > > Thanks for the answer Daniel :)
> > >
> > > On Tue, 19 Jul 2022 at 13:03, Daniel Widdis 
> > wrote:
> > > >
> > > > I think you're asking on the right list.  And it's not a "basic"
> > question but it isn't an obvious answer either.
> > > >
> > > > I'm not sure your question has enough detail for anyone to deduce
> > the answer.  Linking to your project may help you get more attention on it.
> > > >
> > > > FWIW, I have both an automatic module name and module-info in my
> > modular projects and it doesn't cause any problems, but that's clearly not
> > your problem.
> > >
> > >     The only problem of having both is redundancy :)
> > > (and they should be in-sync)
> > >
> > > everything works as expected in case `Automatic-Module-Name` is in
> > manifest
> > >
> > > I'll try to create simple project to illustrate the problem :)
> > >
> > > >
> > > > On 7/18/22, 10:55 PM, "Maxim Solodovnik" 
> > wrote:
> > > >
> > > > Hello,
> > > >
> > > > Is the question too basic?
> > > > Or maybe I'm asking wrong list? :)
> > > >
> > > > On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik <
> > solomax...@gmail.com> wrote:
> > > > >
> > > > > Hello All,
> > > > >
> > > > > I'm trying to migrate our project to JPMS
> > > > > After adding module-info.java to my modules (and removing
> > explicitly
> > > > > set `Automatic-Module-Name`)
> > > > > I'm getting:
> > > > >
> > > > > [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork
> > (default)
> > > > > [ERROR] Creating an aggregated report for both named and
> > unnamed
> > > > > modules is not possible.
> > > > > [ERROR] Ensure that every module has a module descriptor or
> > is a jar
> > > > > with a MANIFEST.MF containing an Automatic-Module-Name.
> > > > >
> > > > > I thought `Automatic-Module-Name` should be added only if
> > > > > `module-info.java` is missing
> > > > > Is it bug in maven-javadoc-plugin or maybe I'm doing
> > something wrong? :)
> > > > >
> > > > > java 17
> > > > > Apache Maven 3.8.5
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Maxim
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > > >
> > > >
> >  -
> > > > 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
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> > >
> > > -
> > > 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
> > >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >



-- 
Best regards,
Maxim

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

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

On Tue, 19 Jul 2022 at 13:16, Daniel Widdis  wrote:
>
> > The only problem of having both is redundancy :)
>
> Technically speaking, you always have an automatic module name even if you 
> don't explicitly name it.  It will use your jar filename to deduce one.   
> Unless you use a reserved word in your jar, and then the world breaks. __

I thought maybe this is the issue in m-javadoc-plugin: it is weird to
check `automatic module name` in manifest if module-info.java present


>
> On 7/18/22, 11:07 PM, "Maxim Solodovnik"  wrote:
>
> Thanks for the answer Daniel :)
>
> On Tue, 19 Jul 2022 at 13:03, Daniel Widdis  wrote:
> >
> > I think you're asking on the right list.  And it's not a "basic" 
> question but it isn't an obvious answer either.
> >
> > I'm not sure your question has enough detail for anyone to deduce the 
> answer.  Linking to your project may help you get more attention on it.
> >
> > FWIW, I have both an automatic module name and module-info in my 
> modular projects and it doesn't cause any problems, but that's clearly not 
> your problem.
>
> The only problem of having both is redundancy :)
> (and they should be in-sync)
>
> everything works as expected in case `Automatic-Module-Name` is in 
> manifest
>
> I'll try to create simple project to illustrate the problem :)
>
> >
> > On 7/18/22, 10:55 PM, "Maxim Solodovnik"  wrote:
> >
>     > Hello,
> >
> > Is the question too basic?
> > Or maybe I'm asking wrong list? :)
> >
> > On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik 
>  wrote:
> > >
> > > Hello All,
> > >
> > > I'm trying to migrate our project to JPMS
> > > After adding module-info.java to my modules (and removing 
> explicitly
> > > set `Automatic-Module-Name`)
> > > I'm getting:
> > >
> > > [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
> > > [ERROR] Creating an aggregated report for both named and unnamed
> > > modules is not possible.
> > > [ERROR] Ensure that every module has a module descriptor or is a 
> jar
> > > with a MANIFEST.MF containing an Automatic-Module-Name.
> > >
> > > I thought `Automatic-Module-Name` should be added only if
> > > `module-info.java` is missing
> > > Is it bug in maven-javadoc-plugin or maybe I'm doing something 
> wrong? :)
> > >
> > > java 17
> > > Apache Maven 3.8.5
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > 
> -
> > 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
> >
>
>
> --
> Best regards,
> Maxim
>
> -
> 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
>


-- 
Best regards,
Maxim

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

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

Thanks for the answer Daniel :)

On Tue, 19 Jul 2022 at 13:03, Daniel Widdis  wrote:
>
> I think you're asking on the right list.  And it's not a "basic" question but 
> it isn't an obvious answer either.
>
> I'm not sure your question has enough detail for anyone to deduce the answer. 
>  Linking to your project may help you get more attention on it.
>
> FWIW, I have both an automatic module name and module-info in my modular 
> projects and it doesn't cause any problems, but that's clearly not your 
> problem.

The only problem of having both is redundancy :)
(and they should be in-sync)

everything works as expected in case `Automatic-Module-Name` is in manifest

I'll try to create simple project to illustrate the problem :)

>
> On 7/18/22, 10:55 PM, "Maxim Solodovnik"  wrote:
>
> Hello,
>
> Is the question too basic?
> Or maybe I'm asking wrong list? :)
>
> On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik  
> wrote:
> >
> > Hello All,
> >
> > I'm trying to migrate our project to JPMS
> > After adding module-info.java to my modules (and removing explicitly
> > set `Automatic-Module-Name`)
> > I'm getting:
> >
> > [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
> > [ERROR] Creating an aggregated report for both named and unnamed
> > modules is not possible.
> > [ERROR] Ensure that every module has a module descriptor or is a jar
> > with a MANIFEST.MF containing an Automatic-Module-Name.
> >
> > I thought `Automatic-Module-Name` should be added only if
> > `module-info.java` is missing
> > Is it bug in maven-javadoc-plugin or maybe I'm doing something wrong? :)
> >
> > java 17
> > Apache Maven 3.8.5
> >
> > --
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim
>
> -
> 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
>


-- 
Best regards,
Maxim

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

Re: m-javadoc-plugin with JPMS

[Maxim Solodovnik]

Hello,

Is the question too basic?
Or maybe I'm asking wrong list? :)

On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik  wrote:
>
> Hello All,
>
> I'm trying to migrate our project to JPMS
> After adding module-info.java to my modules (and removing explicitly
> set `Automatic-Module-Name`)
> I'm getting:
>
> [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
> [ERROR] Creating an aggregated report for both named and unnamed
> modules is not possible.
> [ERROR] Ensure that every module has a module descriptor or is a jar
> with a MANIFEST.MF containing an Automatic-Module-Name.
>
> I thought `Automatic-Module-Name` should be added only if
> `module-info.java` is missing
> Is it bug in maven-javadoc-plugin or maybe I'm doing something wrong? :)
>
> java 17
> Apache Maven 3.8.5
>
> --
> Best regards,
> Maxim



-- 
Best regards,
Maxim

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

m-javadoc-plugin with JPMS

[Maxim Solodovnik]

Hello All,

I'm trying to migrate our project to JPMS
After adding module-info.java to my modules (and removing explicitly
set `Automatic-Module-Name`)
I'm getting:

[INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
[ERROR] Creating an aggregated report for both named and unnamed
modules is not possible.
[ERROR] Ensure that every module has a module descriptor or is a jar
with a MANIFEST.MF containing an Automatic-Module-Name.

I thought `Automatic-Module-Name` should be added only if
`module-info.java` is missing
Is it bug in maven-javadoc-plugin or maybe I'm doing something wrong? :)

java 17
Apache Maven 3.8.5

-- 
Best regards,
Maxim

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

Re: Any plans to release maven-checkstyle-plugin?

[Maxim Solodovnik]

BTW org.apache.velocity:velocity used in 3.1.2 is reported as
vulnerable here:
https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-checkstyle-plugin/3.1.2

On Fri, 22 Apr 2022 at 10:42, Maxim Solodovnik  wrote:
>
> 3.2.0-SNAPSHOT works as expected
> at least "Instanceof pattern matching" seems to pass checkstyle :)
>
> On Thu, 21 Apr 2022 at 19:21, Falko Modler  wrote:
> >
> > Hi Maxim,
> >
> > it works for me when adding checkstyle 9.3 (or other recent versions) as
> > a plugin dependency, overriding the one that is shipped by the plugin.
>
> This might be the option, but this way I should do manual updates all
> the time :(
> maven-checkstyle-plugin was released 2021-01-23 (more than a year ago)
> IMO it's time to release :)
>
> >
> > I never wait for plugin updates to update checkstyle, because checkstlye
> > is updated way more often than the plugin.
> >
> > Cheers,
> >
> > Falko
> >
> > Am 21.04.2022 um 11:51 schrieb Maxim Solodovnik:
> > > Hello All,
> > >
> > > I would like to switch to the latest Java17 LTS
> > > But it seems latest maven-checkstyle-plugin doesn't work with new
> > > java17 features :(
> > >
> > > Maybe it would be possible to release new version?
> > >
> > > Thanks in advance :)
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
> --
> Best regards,
> Maxim



-- 
Best regards,
Maxim

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

Re: Any plans to release maven-checkstyle-plugin?

[Maxim Solodovnik]

3.2.0-SNAPSHOT works as expected
at least "Instanceof pattern matching" seems to pass checkstyle :)

On Thu, 21 Apr 2022 at 19:21, Falko Modler  wrote:
>
> Hi Maxim,
>
> it works for me when adding checkstyle 9.3 (or other recent versions) as
> a plugin dependency, overriding the one that is shipped by the plugin.

This might be the option, but this way I should do manual updates all
the time :(
maven-checkstyle-plugin was released 2021-01-23 (more than a year ago)
IMO it's time to release :)

>
> I never wait for plugin updates to update checkstyle, because checkstlye
> is updated way more often than the plugin.
>
> Cheers,
>
> Falko
>
> Am 21.04.2022 um 11:51 schrieb Maxim Solodovnik:
> > Hello All,
> >
> > I would like to switch to the latest Java17 LTS
> > But it seems latest maven-checkstyle-plugin doesn't work with new
> > java17 features :(
> >
> > Maybe it would be possible to release new version?
> >
> > Thanks in advance :)
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>


-- 
Best regards,
Maxim

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

Any plans to release maven-checkstyle-plugin?

[Maxim Solodovnik]

Hello All,

I would like to switch to the latest Java17 LTS
But it seems latest maven-checkstyle-plugin doesn't work with new
java17 features :(

Maybe it would be possible to release new version?

Thanks in advance :)

-- 
Best regards,
Maxim

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

Re: maven-javadoc and reproducible builds

[Maxim Solodovnik]

Done: https://issues.apache.org/jira/browse/MJAVADOC-684 :)

On Sat, 17 Jul 2021 at 19:13, Michael Osipov  wrote:

> Am 2021-07-17 um 09:51 schrieb Maxim Solodovnik:
> > Hello Michael,
> >
> > Shall I file JIRA at https://issues.apache.org/jira/projects/MJAVADOC/ ?
> > Or some other project?
>
> MJAVADOC
>
> > On Sat, 17 Jul 2021 at 14:46, Michael Osipov 
> wrote:
> >
> >> Am 2021-07-17 um 02:55 schrieb Maxim Solodovnik:
> >>> Hello All,
> >>>
> >>> I'm a bit confused with documentation
> >>>
> >>> This [1] guide instruct me to set
> >>>   1
> >>> and add
> >>>   true
> >>> to javadoc configuration in pluginManagement
> >>>
> >>> as a result I'm getting
> >>>
> >>> Caused by: java.time.format.DateTimeParseException: Text '1' could not
> be
> >>> parsed at index 0
> >>>   at java.time.format.DateTimeFormatter.parseResolved0
> >>> (DateTimeFormatter.java:2046)
> >>>   at java.time.format.DateTimeFormatter.parse
> >>> (DateTimeFormatter.java:1874)
> >>>   at
> >> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getBottomText
> >>> (AbstractJavadocMojo.java:3007)
> >>>   at
> >>>
> >>
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
> >>> (AbstractJavadocMojo.java:5549)
> >>>
> >>> and this seems to be "by design" [2]:
> >>>
> >>> Shall I specify some additional custom property? (bottom?)
> >>> or maybe outputTimestamp should be set to some other value?
> >>>
> >>> and documentation definitely need to be updated :(((
> >>>
> >>> [1]
> https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> >>> [2]
> >>>
> >>
> https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3004
> >>>
> >>
> >> This is a bug. Please report.
> >>
> >> -
> >> 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
>
>

-- 
Best regards,
Maxim

Re: maven-javadoc and reproducible builds

[Maxim Solodovnik]

Hello Michael,

Shall I file JIRA at https://issues.apache.org/jira/projects/MJAVADOC/ ?
Or some other project?

On Sat, 17 Jul 2021 at 14:46, Michael Osipov  wrote:

> Am 2021-07-17 um 02:55 schrieb Maxim Solodovnik:
> > Hello All,
> >
> > I'm a bit confused with documentation
> >
> > This [1] guide instruct me to set
> >  1
> > and add
> >  true
> > to javadoc configuration in pluginManagement
> >
> > as a result I'm getting
> >
> > Caused by: java.time.format.DateTimeParseException: Text '1' could not be
> > parsed at index 0
> >  at java.time.format.DateTimeFormatter.parseResolved0
> > (DateTimeFormatter.java:2046)
> >  at java.time.format.DateTimeFormatter.parse
> > (DateTimeFormatter.java:1874)
> >  at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getBottomText
> > (AbstractJavadocMojo.java:3007)
> >  at
> >
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
> > (AbstractJavadocMojo.java:5549)
> >
> > and this seems to be "by design" [2]:
> >
> > Shall I specify some additional custom property? (bottom?)
> > or maybe outputTimestamp should be set to some other value?
> >
> > and documentation definitely need to be updated :(((
> >
> > [1] https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> > [2]
> >
> https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3004
> >
>
> This is a bug. Please report.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Best regards,
Maxim

Re: maven-javadoc and reproducible builds

[Maxim Solodovnik]

Thanks a million!

 
${maven.build.timestamp}
works for me (after following property was removed)
  /MM/dd
HH:mm

not sure how this will help in creating reproducible build
but now the builds should work :)))

hooray!


On Sat, 17 Jul 2021 at 11:52, Lasse Lindqvist 
wrote:

> It is a weird example, but based on the code, the property should be in
> timestamp format. For example:
>
> 2021-07-17T01:02:00Z
> Now, this is not a constant, so it could not be added to the pom.xml
> directly like this. Your CI could pass this to the build from command line.
> There is also a property called maven.build.timestamp, I wonder if that can
> be used here since based on docs it is
> *the UTC timestamp of build start, in -MM-dd'T'HH:mm:ss'Z' default
> format *
> So,
>
> ${maven.build.timestamp}
>
> might work.
>
> la 17. heinäk. 2021 klo 3.55 Maxim Solodovnik (solomax...@gmail.com)
> kirjoitti:
>
> > Hello All,
> >
> > I'm a bit confused with documentation
> >
> > This [1] guide instruct me to set
> > 1
> > and add
> > true
> > to javadoc configuration in pluginManagement
> >
> > as a result I'm getting
> >
> > Caused by: java.time.format.DateTimeParseException: Text '1' could not be
> > parsed at index 0
> > at java.time.format.DateTimeFormatter.parseResolved0
> > (DateTimeFormatter.java:2046)
> > at java.time.format.DateTimeFormatter.parse
> > (DateTimeFormatter.java:1874)
> > at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getBottomText
> > (AbstractJavadocMojo.java:3007)
> > at
> >
> >
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
> > (AbstractJavadocMojo.java:5549)
> >
> > and this seems to be "by design" [2]:
> >
> > Shall I specify some additional custom property? (bottom?)
> > or maybe outputTimestamp should be set to some other value?
> >
> > and documentation definitely need to be updated :(((
> >
> > [1] https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> > [2]
> >
> >
> https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3004
> >
> > --
> > Best regards,
> > Maxim
> >
>


-- 
Best regards,
Maxim

maven-javadoc and reproducible builds

[Maxim Solodovnik]

Hello All,

I'm a bit confused with documentation

This [1] guide instruct me to set
1
and add
true
to javadoc configuration in pluginManagement

as a result I'm getting

Caused by: java.time.format.DateTimeParseException: Text '1' could not be
parsed at index 0
at java.time.format.DateTimeFormatter.parseResolved0
(DateTimeFormatter.java:2046)
at java.time.format.DateTimeFormatter.parse
(DateTimeFormatter.java:1874)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getBottomText
(AbstractJavadocMojo.java:3007)
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
(AbstractJavadocMojo.java:5549)

and this seems to be "by design" [2]:

Shall I specify some additional custom property? (bottom?)
or maybe outputTimestamp should be set to some other value?

and documentation definitely need to be updated :(((

[1] https://maven.apache.org/guides/mini/guide-reproducible-builds.html
[2]
https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3004

-- 
Best regards,
Maxim

Re: maven-resources-plugin:3.2.0 fails with weird error

[Maxim Solodovnik]

Done: https://issues.apache.org/jira/browse/MRESOURCES-272

On Sat, 5 Dec 2020 at 18:13, Michael Osipov  wrote:
>
> Am 2020-12-04 um 09:05 schrieb Maxim Solodovnik:
> > Thanks a lot Michael,
> >
> > Adding more extensions to  solves my problem
> > Sorry for the noise
> >
> > the only thing can be improved: diagnostic messages :)
>
> I agree, file an issue please.
>
> > On Fri, 13 Nov 2020 at 16:59, Maxim Solodovnik  wrote:
> >
> >> Thanks Michael,
> >>
> >> I'll double-check my POM
> >> lots of previous versions works as expected 
> >>
> >> On Fri, 13 Nov 2020 at 16:55, Michael Osipov  wrote:
> >>
> >>> Am 2020-11-12 um 18:12 schrieb Maxim Solodovnik:
> >>>> Hello All,
> >>>>
> >>>> I've just updated our project [1] to maven-resources-plugin:3.2.0
> >>>> And start getting following error:
> >>>>
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
> >>>> (prepare-test-resources) on project openmeetings-web: Input length = 1
> >>> ->
> >>>> [Help 1]
> >>>> [ERROR]
> >>>
> >>> I have closed recently a false positive with a similar description. You
> >>> are trying to filter a file which does not correspond to the input
> >>> encoding. It was a binary file.
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >>>
> >>
> >> --
> >> Best regards,
> >> Maxim
> >>
> >
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>


-- 
Best regards,
Maxim

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

Re: maven-resources-plugin:3.2.0 fails with weird error

[Maxim Solodovnik]

Thanks a lot Michael,

Adding more extensions to  solves my problem
Sorry for the noise

the only thing can be improved: diagnostic messages :)

On Fri, 13 Nov 2020 at 16:59, Maxim Solodovnik  wrote:

> Thanks Michael,
>
> I'll double-check my POM
> lots of previous versions works as expected 
>
> On Fri, 13 Nov 2020 at 16:55, Michael Osipov  wrote:
>
>> Am 2020-11-12 um 18:12 schrieb Maxim Solodovnik:
>> > Hello All,
>> >
>> > I've just updated our project [1] to maven-resources-plugin:3.2.0
>> > And start getting following error:
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
>> > (prepare-test-resources) on project openmeetings-web: Input length = 1
>> ->
>> > [Help 1]
>> > [ERROR]
>>
>> I have closed recently a false positive with a similar description. You
>> are trying to filter a file which does not correspond to the input
>> encoding. It was a binary file.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> --
> Best regards,
> Maxim
>


-- 
Best regards,
Maxim

Re: maven-resources-plugin:3.2.0 fails with weird error

[Maxim Solodovnik]

Thanks Michael,

I'll double-check my POM
lots of previous versions works as expected 

On Fri, 13 Nov 2020 at 16:55, Michael Osipov  wrote:

> Am 2020-11-12 um 18:12 schrieb Maxim Solodovnik:
> > Hello All,
> >
> > I've just updated our project [1] to maven-resources-plugin:3.2.0
> > And start getting following error:
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
> > (prepare-test-resources) on project openmeetings-web: Input length = 1 ->
> > [Help 1]
> > [ERROR]
>
> I have closed recently a false positive with a similar description. You
> are trying to filter a file which does not correspond to the input
> encoding. It was a binary file.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Best regards,
Maxim

Re: maven-resources-plugin:3.2.0 fails with weird error

[Maxim Solodovnik]

Here is the output with `-e`:

*mvn -version*
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/maven
Java version: 11.0.9, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-53-generic", arch: "amd64", family: "unix"

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
(prepare-test-resources) on project openmeetings-web: Input length = 1 ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
(prepare-test-resources) on project openmeetings-web: Input length = 1
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Input length = 1
at org.apache.maven.plugins.resources.ResourcesMojo.execute
(ResourcesMojo.java:362)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Input
length = 1
at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
(DefaultMavenFileFilter.java:113)
at
org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
(DefaultMavenResourcesFiltering.java:262)
at org.apache.maven.plugins.resources.ResourcesMojo.execute

maven-resources-plugin:3.2.0 fails with weird error

[Maxim Solodovnik]

Hello All,

I've just updated our project [1] to maven-resources-plugin:3.2.0
And start getting following error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-resources-plugin:3.2.0:copy-resources
(prepare-test-resources) on project openmeetings-web: Input length = 1 ->
[Help 1]
[ERROR]

not very informative :(

the build is successful if maven-resources-plugin:3.1.0 is used

https://github.com/apache/openmeetings/

-- 
Best regards,
Maxim

Re: Version ranges: bug or feature

[Maxim Solodovnik]

Thanks for your answers

Unfortunately I feel the main question remains unanswered :(
I'll try to re-phrase it:

Is it possible to specify the range in a way it will check release versions
only

So if [1.0.0, 10.0.0) is specified

2.1.0-SNAPSHOT, 3.1.1-SNAPSHOT, etc. will NOT be checked?

by checking I mean downloading metadata every day etc.


On Wed, 11 Nov 2020 at 17:47, Florian Schmaus  wrote:

> On 11/10/20 2:54 PM, Maxim Solodovnik wrote:
> > Hello Maven experts,
> >
> > one sub-dependencies of our project has following
> >[6.7.0,7.0.0-SNAPSHOT)
>
> I think you may want to use
>
> [6.7.0, 6..)
>
> instead.
>
> - Florian
>


-- 
Best regards,
Maxim

Re: Version ranges: bug or feature

[Maxim Solodovnik]

So ranges can't be used in release artifacts?

I thought maybe `SNAPSHOT` in range will turn on some Maven magic
and it will check snapshots in addition to releases ...

On Wed, 11 Nov 2020 at 06:29, Tomo Suzuki 
wrote:

> I expect Maven to check all possible versions that match the range criteria
> and to pick the highest one. (Sorry if I might not grasp your question)
>
> The suffixes (-SNAPSHOT) in version ranges do not work as a filter.
> (Probably this is not the point?)
>
> The mentioned version strings (6.7.1-SNAPSHOT, 6.7.2-SNAPSHOT and
> 6.7.3-SNAPSHOT) are all higher than “6.7.0” and lower than
> “7.0.0-SNAPSHOT“.
>
>
> On Tue, Nov 10, 2020 at 10:34 Maxim Solodovnik 
> wrote:
>
> > Thanks for the quick answer Tomo,
> >
> > According to out build logs (available for ex. here [1])
> > `7.0.0-SNAPSHOT` in the range results in checking all snapshot versions
> in
> > all snapshot repositories available
> >
> > so 6.7.1-SNAPSHOT, 6.7.2-SNAPSHOT, 6.7.3-SNAPSHOT etc are being checked
> ...
> > Is this expected
> >
> >
> >
> https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/133/consoleFull
> >
> >
> >
> > On Tue, 10 Nov 2020 at 21:49, Tomo Suzuki 
> > wrote:
> >
> > > I avoid using version ranges because it introduces unexpected results
> in
> > > the dependency graphs.
> > >
> > > > [6.7.0,7.0.0-SNAPSHOT)
> > >
> > > I felt the intention of the range is the highest version before
> > > 7.0.0-SNAPSHOT (without including 7.0.0-SNAPSHOT version).
> > > As per [1], this range includes versions such as "7.0.0-alpha" and
> > > "7.0.0-rc".
> > >
> > > [1]:
> > >
> > >
> >
> https://maven.apache.org/ref/3.6.3/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
> > > ,
> > >
> > >
> > >
> > > On Tue, Nov 10, 2020 at 8:54 AM Maxim Solodovnik  >
> > > wrote:
> > >
> > > > Hello Maven experts,
> > > >
> > > > one sub-dependencies of our project has following
> > > >   [6.7.0,7.0.0-SNAPSHOT)
> > > > [1]
> > > >
> > > > as a result metadata for all available SNAPSHOT version is being
> > checked
> > > in
> > > > all SNAPSHOT repositories
> > > > this takes time
> > > > (full story is here
> https://groups.google.com/g/kurento/c/7B5k_cZ2Ya0)
> > > >
> > > > this is reproducible using both local build and build at
> > > > ci-builds.apache.org
> > > >
> > > > Is this expected behavior?
> > > > Is it Ok to use range dependency with SNAPSHOT in release version of
> > > > library?
> > > >
> > > >
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://repo1.maven.org/maven2/org/kurento/kms-api-elements/6.15.0/kms-api-elements-6.15.0.pom
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > Tomo
> > >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> --
> Regards,
> Tomo
>


-- 
Best regards,
Maxim

Re: Version ranges: bug or feature

[Maxim Solodovnik]

Thanks for the quick answer Tomo,

According to out build logs (available for ex. here [1])
`7.0.0-SNAPSHOT` in the range results in checking all snapshot versions in
all snapshot repositories available

so 6.7.1-SNAPSHOT, 6.7.2-SNAPSHOT, 6.7.3-SNAPSHOT etc are being checked ...
Is this expected

https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/133/consoleFull



On Tue, 10 Nov 2020 at 21:49, Tomo Suzuki 
wrote:

> I avoid using version ranges because it introduces unexpected results in
> the dependency graphs.
>
> > [6.7.0,7.0.0-SNAPSHOT)
>
> I felt the intention of the range is the highest version before
> 7.0.0-SNAPSHOT (without including 7.0.0-SNAPSHOT version).
> As per [1], this range includes versions such as "7.0.0-alpha" and
> "7.0.0-rc".
>
> [1]:
>
> https://maven.apache.org/ref/3.6.3/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
> ,
>
>
>
> On Tue, Nov 10, 2020 at 8:54 AM Maxim Solodovnik 
> wrote:
>
> > Hello Maven experts,
> >
> > one sub-dependencies of our project has following
> >   [6.7.0,7.0.0-SNAPSHOT)
> > [1]
> >
> > as a result metadata for all available SNAPSHOT version is being checked
> in
> > all SNAPSHOT repositories
> > this takes time
> > (full story is here https://groups.google.com/g/kurento/c/7B5k_cZ2Ya0)
> >
> > this is reproducible using both local build and build at
> > ci-builds.apache.org
> >
> > Is this expected behavior?
> > Is it Ok to use range dependency with SNAPSHOT in release version of
> > library?
> >
> >
> >
> > [1]
> >
> >
> https://repo1.maven.org/maven2/org/kurento/kms-api-elements/6.15.0/kms-api-elements-6.15.0.pom
> >
> > --
> > Best regards,
> > Maxim
> >
>
>
> --
> Regards,
> Tomo
>


-- 
Best regards,
Maxim

Version ranges: bug or feature

[Maxim Solodovnik]

Hello Maven experts,

one sub-dependencies of our project has following
  [6.7.0,7.0.0-SNAPSHOT)
[1]

as a result metadata for all available SNAPSHOT version is being checked in
all SNAPSHOT repositories
this takes time
(full story is here https://groups.google.com/g/kurento/c/7B5k_cZ2Ya0)

this is reproducible using both local build and build at
ci-builds.apache.org

Is this expected behavior?
Is it Ok to use range dependency with SNAPSHOT in release version of
library?



[1]
https://repo1.maven.org/maven2/org/kurento/kms-api-elements/6.15.0/kms-api-elements-6.15.0.pom

-- 
Best regards,
Maxim

Re: [ANN] Apache Maven WAR Plugin 3.3.0 Released

[Maxim Solodovnik]

Done: https://issues.apache.org/jira/browse/MWAR-434
Thanks :))

On Wed, 10 Jun 2020 at 23:42, Hervé BOUTEMY  wrote:

> Hello,
>
> No: please open a Jira issue with sample project, expected + effective
> result
> so we can fix and add an IT to avoid future regressions
>
> Regards,
>
> Hervé
>
> Le mercredi 10 juin 2020, 10:15:07 CEST Maxim Solodovnik a écrit :
> > Hello,
> >
> > I just have switched from 3.2.3 to this new version and it seems
> >
> https://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#archive
> > Classes Is not working anymore :(
> >
> > Is it intended?
> >
> > On Tue, 9 Jun 2020 at 18:43, Hervé Boutemy  wrote:
> > > The Maven team is pleased to announce the release of the Apache Maven
> WAR
> > > Plugin, version 3.3.0
> > >
> > > This plugin builds a Web Application Archive (WAR) file from the
> project
> > > output and its dependencies.
> > >
> > > https://maven.apache.org/plugins/maven-war-plugin/
> > >
> > > You should specify the version in your project's plugin configuration:
> > >
> > > 
> > >
> > >   org.apache.maven.plugins
> > >   maven-war-plugin
> > >   3.3.0
> > >
> > > 
> > >
> > >
> > > Release Notes - Apache Maven WAR Plugin - Version 3.3.0
> > >
> > > Bug
> > > * [MWAR-429] Failed to execute goal
> > > org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded
> > > (pre-exploded-war)
> > > on project alfresco-platform
> > > * [MWAR-427] WAR plugin includes the same artifact twice if used
> without
> > > clean
> > > * [MWAR-314] failOnMissingWebXml ignored when webXml set
> > >
> > > Improvement
> > > * [MWAR-431] make build Reproducible
> > > * [MWAR-430] support JakartaEE namespace: remove or adapt hardcoded
> > > reference to javax.servlet package
> > > * [MWAR-375] Remove the useCache with its implementation
> > >
> > > New Feature
> > > * [MWAR-432] Reproducible Builds: make entries in output jar files
> > > reproducible (order + timestamp)
> > >
> > >
> > > Enjoy,
> > >
> > > -The Maven team
> > >
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Best regards,
Maxim

Re: [ANN] Apache Maven WAR Plugin 3.3.0 Released

[Maxim Solodovnik]

Hello,

I just have switched from 3.2.3 to this new version and it seems
https://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#archiveClasses
Is not working anymore :(

Is it intended?


On Tue, 9 Jun 2020 at 18:43, Hervé Boutemy  wrote:

> The Maven team is pleased to announce the release of the Apache Maven WAR
> Plugin, version 3.3.0
>
> This plugin builds a Web Application Archive (WAR) file from the project
> output and its dependencies.
>
> https://maven.apache.org/plugins/maven-war-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>   org.apache.maven.plugins
>   maven-war-plugin
>   3.3.0
> 
>
>
> Release Notes - Apache Maven WAR Plugin - Version 3.3.0
>
> Bug
> * [MWAR-429] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded (pre-exploded-war)
> on project alfresco-platform
> * [MWAR-427] WAR plugin includes the same artifact twice if used without
> clean
> * [MWAR-314] failOnMissingWebXml ignored when webXml set
>
> Improvement
> * [MWAR-431] make build Reproducible
> * [MWAR-430] support JakartaEE namespace: remove or adapt hardcoded
> reference to javax.servlet package
> * [MWAR-375] Remove the useCache with its implementation
>
> New Feature
> * [MWAR-432] Reproducible Builds: make entries in output jar files
> reproducible (order + timestamp)
>
>
> Enjoy,
>
> -The Maven team
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Best regards,
Maxim

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Maxim Solodovnik]

Thanks :))

On Wed, 27 May 2020 at 15:44, Michael Osipov  wrote:

> Am 2020-05-27 um 03:44 schrieb Maxim Solodovnik:
> > Hello,
> >
> > for whatever reason this plugin is missing in central
> >
> https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
> > Can you please check?
>
> Good question, I have released the staging repo 10 hours ago. I will get
> in touch with INFRA and MVNCENTRAL.
>
> > On Wed, 27 May 2020 at 04:24, Michael Osipov 
> wrote:
> >
> >> The Apache Maven team is pleased to announce the release of the Maven
> >> Project Info Reports Plugin version 3.1.0.
> >>
> >> https://maven.apache.org/plugins/maven-project-info-reports-plugin/
> >>
> >> You should specify the version in your project's plugin configuration:
> >>
> >> 
> >> org.apache.maven.plugins
> >> maven-project-info-reports-plugin
> >> 3.1.0
> >> 
> >>
> >>
> >> Release Notes - Maven Project Info Reports Plugin - Version 3.1.0
> >>
> >> ** Bug
> >>   * [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional
> warning
> >>   * [MPIR-374] - Unknown packaging: bundle when creating report
> >>   * [MPIR-376] - LightweightHttpsWagon is always used
> >>   * [MPIR-380] - Emails in developers section of pom are improperly
> >> handled
> >>   * [MPIR-385] - Emails in mailing list section of pom are
> improperly
> >> handled
> >>   * [MPIR-386] - Project building errors with plugins and central
> >> repository override
> >>
> >> ** New Feature
> >>   * [MPIR-375] - add plugin excludes feature for plugin-management
> >> report
> >>
> >> ** Improvement
> >>   * [MPIR-381] - Improve russian localization
> >>   * [MPIR-384] - Use PatternExcludesArtifactFilter to exclude
> >> artifacts in PluginManagement
> >>   * [MPIR-387] - make build Reproducible
> >>   * [MPIR-390] - Verify build by Github action
> >>
> >> ** Dependency upgrade
> >>   * [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove
> >> dependency on Struts
> >>   * [MPIR-389] - Upgrade Doxia to 1.9.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
> >>
> >>
> >
>
>

-- 
Best regards,
Maxim

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Maxim Solodovnik]

Hello,

for whatever reason this plugin is missing in central
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
Can you please check?

On Wed, 27 May 2020 at 04:24, Michael Osipov  wrote:

> The Apache Maven team is pleased to announce the release of the Maven
> Project Info Reports Plugin version 3.1.0.
>
> https://maven.apache.org/plugins/maven-project-info-reports-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>org.apache.maven.plugins
>maven-project-info-reports-plugin
>3.1.0
> 
>
>
> Release Notes - Maven Project Info Reports Plugin - Version 3.1.0
>
> ** Bug
>  * [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional warning
>  * [MPIR-374] - Unknown packaging: bundle when creating report
>  * [MPIR-376] - LightweightHttpsWagon is always used
>  * [MPIR-380] - Emails in developers section of pom are improperly
> handled
>  * [MPIR-385] - Emails in mailing list section of pom are improperly
> handled
>  * [MPIR-386] - Project building errors with plugins and central
> repository override
>
> ** New Feature
>  * [MPIR-375] - add plugin excludes feature for plugin-management
> report
>
> ** Improvement
>  * [MPIR-381] - Improve russian localization
>  * [MPIR-384] - Use PatternExcludesArtifactFilter to exclude
> artifacts in PluginManagement
>  * [MPIR-387] - make build Reproducible
>  * [MPIR-390] - Verify build by Github action
>
> ** Dependency upgrade
>  * [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove
> dependency on Struts
>  * [MPIR-389] - Upgrade Doxia to 1.9.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
>
>

-- 
Best regards,
Maxim

Re: OS

[Maxim Solodovnik]

Similar questions were asked at
OpenJpa https://issues.apache.org/jira/browse/OPENJPA-2787
Commons https://markmail.org/thread/56fxvspp62kgvnrl
Felix https://markmail.org/thread/so6b3jf5qo6rjpqx

On Thu, 18 Apr 2019 at 10:38, Tibor Digana  wrote:
>
> It is, Surefire on Windows.
> Why you are asking?
>
> T
>
>
> On Thu, Apr 18, 2019 at 3:50 AM liname...@outlook.com 
> wrote:
>
> >
> > Hello, I am doing an investigation.
> > Does Windows Server 2019 support the following products:
> >
> > maven-surefire-plugin  2.17
> >
> > Is the other version supported?
> > Can you tell me, thank you very much.
> >
> >



-- 
WBR
Maxim aka solomax

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

Re: Using maven-dependency-plugin:unpack in "mvn compile" build

[Maxim Solodovnik]

Hello Chris,

Maybe true of maven-war-plugin
can help?

On Fri, 22 Mar 2019 at 20:12, Christofer Dutz 
wrote:

> Hi,
>
> we are currently having a little problem with our build.
> A user complained about not being able to build with a “mvn compile”.
> The reason is that we have one module that builds a web-client (bundled as
> war) and a server module to which the client is copied.
> We are using the maven-dependency-plugin:unpack to unpack the artifact
> into the server war. This works fine as long as we built to at least the
> “package” phase.
> If the user builds to something before that, the build fails as the
> pointer to the client pints to a directory instead of an archive.
>
> Is there a way to do some sort of “unpack-or-copy” that copies if it’s
> just a pre-package phase and does the normal unpack if the archives have
> been created.
>
> Would be happy to not tell them “just don’t do a `mvn compile` but at
> least a `mvn package`.
>
>
> Chris
>


-- 
WBR
Maxim aka solomax

Re: Handling emails in pom.xml

[Maxim Solodovnik]

Done: https://issues.apache.org/jira/projects/MPIR/issues/MPIR-380
Will check if I can create PR
Maven is something I'm unable to fix :(

On Sat, 19 Jan 2019 at 17:15, Robert Scholte  wrote:

> Congratulations, you found a bug in the team-report code.
>
> Please file an issue at MPIR[1]
> Consider creating a pull request[2] too, this one isn't that hard to
> solve
> (but don't forget to add a test to prevent regression in the future).
>
> thanks,
> Robert
>
> [1] https://issues.apache.org/jira/browse/MPIR
> [2] https://github.com/apache/maven-project-info-reports-plugin/
>
> On Sat, 19 Jan 2019 05:27:05 +0100, Maxim Solodovnik
>  wrote:
>
> > Hello Robert,
> >
> > Thanks for quick answer
> > It seems I wasn't clear enough (I'm not native English speaker)
> >
> > To it seems to be the issue with maven-project-info-reports-plugin
> >
> > Here is test case can be used:
> > 1) download this [1] pom file to the new folder
> > 2) run `mvn clean site`
> > 3) open target/site/team-list.html in browser
> > Result: email is converted to "mailto:; link
> >
> > 4) open this file in your favorite text editor
> > 5) uncomment line 13 
> > 6) comment line
> > 14
> >
> 2.9
> > 7) uncomment line 81 
> > 8) comment line 82 project-team
> > 9) run `mvn clean site`
> > 10) open target/site/team.html in browser
> > Result: email is displayed as plain link to nowhere
> >
> > Does it make sense?
> >
> > [1] https://gist.github.com/solomax/2ce33116bb56cc5c5b1942f245f6d1b8
> >
> >
> > On Sat, 19 Jan 2019 at 01:21, Robert Scholte 
> > wrote:
> >
> >> We might be more explicit in the definition, but it should be
> >> j...@example.com
> >>
> >> the mailto: is only an URI scheme for email addresses, but here we
> >> already
> >> know we're working with an email.
> >>
> >> Not sure what must done to help you manually fix your team-page.
> >>
> >> thanks,
> >> Robrt
> >>
> >> On Fri, 18 Jan 2019 18:15:32 +0100, Maxim Solodovnik
> >>  wrote:
> >>
> >> > Maybe version 3.0 of maven-project-info-reports-plugin shouldn't be
> >> used
> >> > for project site generation?
> >> >
> >> > I have to manually fix "team" page after each release, please help me
> >> >
> >> > On Mon, 17 Dec 2018 at 22:46, Maxim Solodovnik 
> >> > wrote:
> >> >
> >> >> Maybe I should write to some other mailing list?
> >> >>
> >> >> On Mon, 10 Dec 2018 at 16:11, Maxim Solodovnik  >
> >> >> wrote:
> >> >>
> >> >>> Thanks for the quick response
> >> >>> To illustrate the issue I have modified pom [1] to have both
> >> prefixed
> >> >>> and
> >> >>> non prefixed emails
> >> >>> The result is here: [2] as you can see prefixed emails are correctly
> >> >>> being displayed as mailto: links, but has wrong text
> >> >>> Not prefixed has valid text, but wrong links ...
> >> >>>
> >> >>> According to Frederich's investigation available here [3] this was
> >> >>> working with previous versions of maven report plugin
> >> >>> I'm OK with changing the pom.xml, but unfortunately it seems both
> >> ways
> >> >>> are wrong :(
> >> >>>
> >> >>> [1] https://github.com/apache/openmeetings/blob/master/pom.xml#L150
> >> >>> [2]
> >> >>>
> >>
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html
> >> >>> [3]
> >> >>>
> >>
> https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386
> >> >>>
> >> >>>
> >> >>> On Mon, 10 Dec 2018 at 15:08, Andreas Sewe <
> >> >>> s...@st.informatik.tu-darmstadt.de> wrote:
> >> >>>
> >> >>>> Hi Maxim,
> >> >>>>
> >> >>>> > Recently I noticed the issue with site generation [1]
> >> >>>> > 
> >> >>>> > 
> >> >>>> > mailto:mailaddrr
> >> >>>>
> >> >>>> AFAIK, the  element takes just the plain e-mail address,
> >> not a
> >> >>>> (mailto) URI:
> >> >>>>
> >> >>>>  j...@example.com
> >> >>>>
> >> >>>> See [1] for a longer example.
> >> >>>>
> >> >>>> Hope that helps.
> >> >>>>
> >> >>>> Andreas
> >> >>>>
> >> >>>> [1] <https://maven.apache.org/pom.html#Developers>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>> --
> >> >>> WBR
> >> >>> Maxim aka solomax
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> WBR
> >> >> Maxim aka solomax
> >> >>
> >> >
> >>
> >> -
> >> 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
>
>

-- 
WBR
Maxim aka solomax

Re: Handling emails in pom.xml

[Maxim Solodovnik]

Hello Robert,

Thanks for quick answer
It seems I wasn't clear enough (I'm not native English speaker)

To it seems to be the issue with maven-project-info-reports-plugin

Here is test case can be used:
1) download this [1] pom file to the new folder
2) run `mvn clean site`
3) open target/site/team-list.html in browser
Result: email is converted to "mailto:; link

4) open this file in your favorite text editor
5) uncomment line 13 
6) comment line
14 
2.9
7) uncomment line 81 
8) comment line 82 project-team
9) run `mvn clean site`
10) open target/site/team.html in browser
Result: email is displayed as plain link to nowhere

Does it make sense?

[1] https://gist.github.com/solomax/2ce33116bb56cc5c5b1942f245f6d1b8


On Sat, 19 Jan 2019 at 01:21, Robert Scholte  wrote:

> We might be more explicit in the definition, but it should be
> j...@example.com
>
> the mailto: is only an URI scheme for email addresses, but here we
> already
> know we're working with an email.
>
> Not sure what must done to help you manually fix your team-page.
>
> thanks,
> Robrt
>
> On Fri, 18 Jan 2019 18:15:32 +0100, Maxim Solodovnik
>  wrote:
>
> > Maybe version 3.0 of maven-project-info-reports-plugin shouldn't be used
> > for project site generation?
> >
> > I have to manually fix "team" page after each release, please help me
> >
> > On Mon, 17 Dec 2018 at 22:46, Maxim Solodovnik 
> > wrote:
> >
> >> Maybe I should write to some other mailing list?
> >>
> >> On Mon, 10 Dec 2018 at 16:11, Maxim Solodovnik 
> >> wrote:
> >>
> >>> Thanks for the quick response
> >>> To illustrate the issue I have modified pom [1] to have both prefixed
> >>> and
> >>> non prefixed emails
> >>> The result is here: [2] as you can see prefixed emails are correctly
> >>> being displayed as mailto: links, but has wrong text
> >>> Not prefixed has valid text, but wrong links ...
> >>>
> >>> According to Frederich's investigation available here [3] this was
> >>> working with previous versions of maven report plugin
> >>> I'm OK with changing the pom.xml, but unfortunately it seems both ways
> >>> are wrong :(
> >>>
> >>> [1] https://github.com/apache/openmeetings/blob/master/pom.xml#L150
> >>> [2]
> >>>
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html
> >>> [3]
> >>>
> https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386
> >>>
> >>>
> >>> On Mon, 10 Dec 2018 at 15:08, Andreas Sewe <
> >>> s...@st.informatik.tu-darmstadt.de> wrote:
> >>>
> >>>> Hi Maxim,
> >>>>
> >>>> > Recently I noticed the issue with site generation [1]
> >>>> > 
> >>>> > 
> >>>> > mailto:mailaddrr
> >>>>
> >>>> AFAIK, the  element takes just the plain e-mail address, not a
> >>>> (mailto) URI:
> >>>>
> >>>>  j...@example.com
> >>>>
> >>>> See [1] for a longer example.
> >>>>
> >>>> Hope that helps.
> >>>>
> >>>> Andreas
> >>>>
> >>>> [1] <https://maven.apache.org/pom.html#Developers>
> >>>>
> >>>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
WBR
Maxim aka solomax

Re: Handling emails in pom.xml

[Maxim Solodovnik]

Maybe version 3.0 of maven-project-info-reports-plugin shouldn't be used
for project site generation?

I have to manually fix "team" page after each release, please help me

On Mon, 17 Dec 2018 at 22:46, Maxim Solodovnik  wrote:

> Maybe I should write to some other mailing list?
>
> On Mon, 10 Dec 2018 at 16:11, Maxim Solodovnik 
> wrote:
>
>> Thanks for the quick response
>> To illustrate the issue I have modified pom [1] to have both prefixed and
>> non prefixed emails
>> The result is here: [2] as you can see prefixed emails are correctly
>> being displayed as mailto: links, but has wrong text
>> Not prefixed has valid text, but wrong links ...
>>
>> According to Frederich's investigation available here [3] this was
>> working with previous versions of maven report plugin
>> I'm OK with changing the pom.xml, but unfortunately it seems both ways
>> are wrong :(
>>
>> [1] https://github.com/apache/openmeetings/blob/master/pom.xml#L150
>> [2]
>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html
>> [3]
>> https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386
>>
>>
>> On Mon, 10 Dec 2018 at 15:08, Andreas Sewe <
>> s...@st.informatik.tu-darmstadt.de> wrote:
>>
>>> Hi Maxim,
>>>
>>> > Recently I noticed the issue with site generation [1]
>>> > 
>>> > 
>>> > mailto:mailaddrr
>>>
>>> AFAIK, the  element takes just the plain e-mail address, not a
>>> (mailto) URI:
>>>
>>>  j...@example.com
>>>
>>> See [1] for a longer example.
>>>
>>> Hope that helps.
>>>
>>> Andreas
>>>
>>> [1] <https://maven.apache.org/pom.html#Developers>
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: How to interpolate a value in a Maven plugin

[Maxim Solodovnik]

I was able to perform some properties manipulation with inline groovy script
similar to this answer: https://stackoverflow.com/a/35731118/3571661

On Thu, 27 Dec 2018 at 15:54, Robert Scholte  wrote:

> Hi,
>
> try to find a plugin which does similar things and have a look at its
> sources.
> In this case help:evaluate[1]
>
> thanks,
> Robert
>
> [1] https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html
>
> On Wed, 26 Dec 2018 22:36:32 +0100, Jochen Wiedmann
>  wrote:
>
> > Hi,
> >
> > I have written a Maven plugin, which must interpret values like
> > ${project.artifactId}, and the like.
> > My first attempt was to use
> > project.getProperties().get("project.artifactId"), but that seems
> > to work only for the values, which are configured in the POM's
> > property section. So, what would be a better approach?
> >
> > Thanks,
> >
> > Jochen
> >
> > -
> > 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
>
>

-- 
WBR
Maxim aka solomax

Re: Handling emails in pom.xml

[Maxim Solodovnik]

Maybe I should write to some other mailing list?

On Mon, 10 Dec 2018 at 16:11, Maxim Solodovnik  wrote:

> Thanks for the quick response
> To illustrate the issue I have modified pom [1] to have both prefixed and
> non prefixed emails
> The result is here: [2] as you can see prefixed emails are correctly being
> displayed as mailto: links, but has wrong text
> Not prefixed has valid text, but wrong links ...
>
> According to Frederich's investigation available here [3] this was working
> with previous versions of maven report plugin
> I'm OK with changing the pom.xml, but unfortunately it seems both ways are
> wrong :(
>
> [1] https://github.com/apache/openmeetings/blob/master/pom.xml#L150
> [2]
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html
> [3]
> https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386
>
>
> On Mon, 10 Dec 2018 at 15:08, Andreas Sewe <
> s...@st.informatik.tu-darmstadt.de> wrote:
>
>> Hi Maxim,
>>
>> > Recently I noticed the issue with site generation [1]
>> > 
>> > 
>> > mailto:mailaddrr
>>
>> AFAIK, the  element takes just the plain e-mail address, not a
>> (mailto) URI:
>>
>>  j...@example.com
>>
>> See [1] for a longer example.
>>
>> Hope that helps.
>>
>> Andreas
>>
>> [1] <https://maven.apache.org/pom.html#Developers>
>>
>>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Handling emails in pom.xml

[Maxim Solodovnik]

Thanks for the quick response
To illustrate the issue I have modified pom [1] to have both prefixed and
non prefixed emails
The result is here: [2] as you can see prefixed emails are correctly being
displayed as mailto: links, but has wrong text
Not prefixed has valid text, but wrong links ...

According to Frederich's investigation available here [3] this was working
with previous versions of maven report plugin
I'm OK with changing the pom.xml, but unfortunately it seems both ways are
wrong :(

[1] https://github.com/apache/openmeetings/blob/master/pom.xml#L150
[2]
https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html
[3]
https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386


On Mon, 10 Dec 2018 at 15:08, Andreas Sewe <
s...@st.informatik.tu-darmstadt.de> wrote:

> Hi Maxim,
>
> > Recently I noticed the issue with site generation [1]
> > 
> > 
> > mailto:mailaddrr
>
> AFAIK, the  element takes just the plain e-mail address, not a
> (mailto) URI:
>
>  j...@example.com
>
> See [1] for a longer example.
>
> Hope that helps.
>
> Andreas
>
> [1] 
>
>

-- 
WBR
Maxim aka solomax

Handling emails in pom.xml

[Maxim Solodovnik]

Hello All,

Recently I noticed the issue with site generation [1]


mailto:mailaddrr


Section is not being properly processed after switching to maven report
plugin 3.0 (please see [2])

What is the proper way to get well formatted emails?

[1]
https://github.com/devacfr/reflow-maven-skin/issues/40#issuecomment-445304386
[2]
https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/site/openmeetings-server/team.html

-- 
WBR
Maxim aka solomax

Tests fails after switching to maven-surefire-plugin 3.0.0-M1

[Maxim Solodovnik]

Hello,

At Apache Wicket we hit issue described here
https://stackoverflow.com/a/53016532/1676516
(tests fails when OpenJDK 8u181 is used)

To fix it we have tried to update maven-surefire-plugin (2.20 -> 3.0.0-M1)
Tests for one module (CDI-1.1) fails for both OpenJDK and OracleJDK
I tried to fix these tests - no luck
Then I have added false to
surefire-plugin configuration and tests become green

So I guess this should be maven-surefire-plugin issue

The issue can be checked using Apache Wicket sources available here
https://github.com/apache/wicket/tree/wicket-8.x (please NOTE `wicket-8.x`
branch)

Please let me know if any additional details are required

-- 
WBR
Maxim aka solomax

Re: Unknown packaging: bundle while building dependency report

[Maxim Solodovnik]

Thanks for the reply,

My search gave me no results except for advice "to move
maven-bundle-plugin out of pluginManagement section of the pom"
I'll try to investigate this
On Sat, 20 Oct 2018 at 02:11, Michael Osipov  wrote:
>
> Am 2018-10-16 um 08:17 schrieb Maxim Solodovnik:
> > Hello All,
> >
> > I'm getting lot's of exceptions like the one below during the build.
> > These exceptions are not affecting build status but polluting the logs
> >
> > Maybe you know how it can be fixed?
> >
> > maven-bundle-plugin version: 4.0.0
> > maven-project-info-reports-plugin version: 3.0.0
>
> These issues have already been reported. I do believe that Maven does
> not read extensions in that mode and therefore reports the packaging as
> invalid. Robert has left some ideas how this can be solved for MPIR. I
> haven't found anytime yet to have a look at it. If you do, I'll highly
> appreciate a PR.
>
> Michael



-- 
WBR
Maxim aka solomax

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

Re: Unknown packaging: bundle while building dependency report

[Maxim Solodovnik]

Maybe I should provide some other details?
Or ask different mailing list?
On Tue, 16 Oct 2018 at 13:17, Maxim Solodovnik  wrote:
>
> Hello All,
>
> I'm getting lot's of exceptions like the one below during the build.
> These exceptions are not affecting build status but polluting the logs
>
> Maybe you know how it can be fixed?
>
> maven-bundle-plugin version: 4.0.0
> maven-project-info-reports-plugin version: 3.0.0
>
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-18T01:33:14+07:00)
> Maven home: /opt/maven
> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-137-generic", arch: "amd64", family: "unix"
>
> Thanks in advance
>
> Caused by: org.apache.maven.model.building.ModelBuildingException: 1
> problem was encountered while building the effective model for
> org.postgresql:postgresql:42.2.5
> [ERROR] Unknown packaging: bundle @ line 11, column 14
>
> at 
> org.apache.maven.model.building.DefaultModelProblemCollector.newModelBuildingException
> (DefaultModelProblemCollector.java:197)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:482)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:424)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:158)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderArtifactRow
> (DependenciesRenderer.java:799)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDependenciesForScope
> (DependenciesRenderer.java:749)
>
>
> --
> WBR
> Maxim aka solomax



-- 
WBR
Maxim aka solomax

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

Unknown packaging: bundle while building dependency report

[Maxim Solodovnik]

Hello All,

I'm getting lot's of exceptions like the one below during the build.
These exceptions are not affecting build status but polluting the logs

Maybe you know how it can be fixed?

maven-bundle-plugin version: 4.0.0
maven-project-info-reports-plugin version: 3.0.0

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T01:33:14+07:00)
Maven home: /opt/maven
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-137-generic", arch: "amd64", family: "unix"

Thanks in advance

Caused by: org.apache.maven.model.building.ModelBuildingException: 1
problem was encountered while building the effective model for
org.postgresql:postgresql:42.2.5
[ERROR] Unknown packaging: bundle @ line 11, column 14

at 
org.apache.maven.model.building.DefaultModelProblemCollector.newModelBuildingException
(DefaultModelProblemCollector.java:197)
at org.apache.maven.model.building.DefaultModelBuilder.build
(DefaultModelBuilder.java:482)
at org.apache.maven.model.building.DefaultModelBuilder.build
(DefaultModelBuilder.java:424)
at org.apache.maven.model.building.DefaultModelBuilder.build
(DefaultModelBuilder.java:414)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:158)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:327)
at 
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
(RepositoryUtils.java:125)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderArtifactRow
(DependenciesRenderer.java:799)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDependenciesForScope
(DependenciesRenderer.java:749)


-- 
WBR
Maxim aka solomax

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

Re: javadoc:jar and generated sources

[Maxim Solodovnik]

I can confirm this :(
Spent several hours trying to release
Finaly fixed all javadoc warnings 

WBR, Maxim
(from mobile, sorry for the typos)

On Wed, Mar 14, 2018, 00:57 Laird Nelson  wrote:

> I am finding that the sourcepath for javadoc:jar (when run as part of the
> release profile) is different from the sourcepath for javadoc:javadoc in my
> project that involves (protoc-) generated sources.
>
> (The net effect is that at release time, everything works fine up until
> release:perform, which fails (!) during the attach-javadocs execution I've
> configured following the documentation (
>
> https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html#Configuring_Maven_Javadoc_Plugin
> )
> ).
>
> I have a  stanza centralizing my maven-javadoc-plugin
> configuration that does not mention sourcepath in any way.
>
> mvn help:effective-pom -Prelease shows exactly what I would expect, and no
> additional maven-javadoc-plugin configuration.
>
> Somehow, the sourcepath for javadoc:javadoc has the generated-sources
> directory in it; the sourcepath for javadoc:jar does not.
>
> Here is the pluginManagement section (it's quite ordinary):
>
> 
>   maven-javadoc-plugin
>   3.0.0-M1
>   
> -missing
>   
> 
>
> When I run mvn -X javadoc:javadoc and inspect the options file, I see this:
>
> -sourcepath
> '/Users/ljnelson/Projects/frob/src/main/java:
>
> */Users/ljnelson/Projects/frob/target/generated-sources/protobuf/java:/Users/ljnelson/Projects/frob/target/generated-sources/protobuf/grpc-java*
> :/Users/ljnelson/Projects/frob/src/main/javadoc'
>
> When I run mvn -X javadoc:jar and inspect the options file, I see only
> this:
>
> -sourcepath
>
> '/Users/ljnelson/Projects/frob/src/main/java:/Users/ljnelson/Projects/frob/src/main/javadoc'
>
> The javadoc:jar goal outputs a bunch of warnings.  When I run it locally
> (mvn javadoc:jar), they show up as warnings.  When it is run as part of the
> maven-release-plugin's perform goal, it fails the build.
>
> I'm at a loss as to how to go about fixing this.  Is it, perhaps, the job
> of the plugin in charge of generating the sources to do something here?
>
> Best,
> Laird
>

Re: Is there a plugin that allows me to modify existing jar manifest?

[Maxim Solodovnik]

Hello Eric,

we are using assembly plugin to achieve this:
https://github.com/apache/openmeetings/blob/master/openmeetings-screenshare/pom.xml#L158

On Tue, Nov 14, 2017 at 8:53 AM, Eric B  wrote:

> Martin,
>
> Thanks, but the jar-plugin only allows to build a jar from the current
> project (and set appropriate Manifest entries).  I'm looking to modify an
> existing jar.  I could use the dependency plugin to retrieve the jar, and
> unpack it, then point the jar-plugin to the unpacked dependency and have it
> repkg the dependency from the unpacked classes, but was hoping for
> something a little less manual.  For multiple dependencies, I would need to
> write a different execution config for the jar-plugin which becomes quite
> bloatsome for my pom.  I was just hoping for a cleaner/easier approach.
>
> I started looking at the shade plugin with a manifest transformer, but that
> too becomes individual execution configs.
>
> Thanks,
>
> Eric
>
> On Mon, Nov 13, 2017 at 8:03 PM, Martin Gainty 
> wrote:
>
> >
> >
> > 
> > From: Eric B 
> > Sent: Monday, November 13, 2017 5:51 PM
> > To: Maven Users List
> > Subject: Is there a plugin that allows me to modify existing jar
> manifest?
> >
> > I'm looking to modify an existing third-party JAR's Manifest file in my
> > maven build.  Specifically, I have an Applet which has a dependency on
> > these third party jars, and need to add some entries/permissions to the
> > Manifest before I sign them for my Applet to use.
> >
> > I'm looking to add the following:
> >
> >all-permissions
> > *
> >
> > * > Library-Allowable-Codebase>
> > true
> > MyApp
> >
> > *
> >
> > MG>Eric...did you try  configuration parameter of
> > maven-jar-plugin ?
> > https://maven.apache.org/plugins/maven-jar-plugin/examples/
> > manifest-customization.html
> > Apache Maven JAR Plugin – Manifest customization > ache.org/plugins/maven-jar-plugin/examples/manifest-customization.html>
> > maven.apache.org
> > The default contents of the manifest is described in the documentation
> for
> > Maven Archiver. Starting with version 2.1, the maven-jar-plugin uses
> Maven
> > Archiver 3.1.1 ...
> >
> > MG>https://maven.apache.org/shared/maven-archiver/index.html
> > Apache Maven Archiver – Reference > .org/shared/maven-archiver/index.html>
> > maven.apache.org
> > Apache Maven Archiver. The Maven Archiver is mainly used by plugins to
> > handle packaging. The version numbers referenced in the Since column on
> > this page are the ...
> >
> >
> >
> >
> > I realize that these aren't particularly secure parameters, but right now
> > I'm just trying to see what it will take to get this working.
> >
> > Is there a plugin that will allow me to modify an existing jar?  I'm
> using
> > the dependency plugin to retrieve them from Maven, but once I have them
> > locally, I'm not sure what to use to update the MANIFEST.  Is this
> > something the assembly plugin can do easily?  I've looked at the assmbly
> > descriptor reference, but don't see where/how it can be leveraged for
> this.
> >
> > Thanks,
> >
> > Eric
> >
>



-- 
WBR
Maxim aka solomax

Re: Maven Docker Images

[Maxim Solodovnik]

I would start with filing INFRA ticket :)

On Fri, Oct 20, 2017 at 12:40 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> awesome: there is some common practice we should get into
>
> do you know if there some docs somewhere?
> I suppose there are some credentials associated to publishing to Dockerhub
>
> Regards,
>
> Hervé
>
> Le vendredi 20 octobre 2017, 11:39:22 CEST Maxim Solodovnik a écrit :
> > In this case dockerhub is preferable :)
> >
> > On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <
> bindulbhow...@gmail.com>
> >
> > wrote:
> > > Maxim,
> > >
> > > On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > >
> > > wrote:
> > > > Hello,
> > > >
> > > > here is the place for Apache docker images managed by infra and
> Apache
> > > > projects https://bintray.com/apache/ :)
> > >
> > > From what I have seen, while there are 4 projects with docker
> > > repositories on bintray, there seem to be a lot more at dockerhub [1].
> > > I did a quick search on INFRA JIRA and found that infra has set a few
> > > projects up on dockerhub recently [2], for example INFRA-14756 [3] for
> > > bookkeeper.
> > >
> > > Bindul
> > >
> > > [1] https://hub.docker.com/r/apache/
> > > [2] https://issues.apache.org/jira/issues/?jql=component%20%
> > > 3D%20Docker%20AND%20project%20%3D%20INFRA
> > > [3] https://issues.apache.org/jira/browse/INFRA-14756
> > >
> > > > On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY <
> herve.bout...@free.fr>
> > > >
> > > > wrote:
> > > > > great idea
> > > > >
> > > > > ok, we need a git repo at ASF
> > > > >
> > > > > what else?
> > > > > Is there some sort of release process? some sort of source to
> release?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > > > > > Thanks for the pointer, Carlos! I had searched the archives, but
> > >
> > > maybe I
> > >
> > > > > > didn't go back far enough.
> > > > > >
> > > > > > I think moving these Dockerfiles into an ASF repo would be great
> for
> > > > >
> > > > > their
> > > > >
> > > > > > maintainability.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Mike
> > > > > >
> > > > > > On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote:
> > > > > > > Arnaud is correct, I sent an email to users@ back on Fri, Nov
> 7,
> > > > >
> > > > > 2014,>
> > > > >
> > > > > > > 00:23 when I created the image>
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com>
> > >
> > > wrote:>
> > >
> > > > > > > > These images are kindly managed by a PMC member of our
> project
> > > > >
> > > > > (Carlos)
> > > > >
> > > > > > but>
> > > > > >
> > > > > > > > yes they aren't managed directly by the project>
> > > > > > > >
> > > > > > > > We can easily see with him to improve this IMO.>
> > > > > > > >
> > > > > > > > When he started that (several years ago) Docker wasn't what
> it
> > > > > > > > is
> > > > > >
> > > > > > nowadays.>
> > > > > >
> > > > > > > > With docker being mainstream I agree that we can reconsider
> > >
> > > this.>
> > >
> > > > > > > > The docker image build/distribution could perhaps be part of
> our
> > > > > >
> > > > > > release>
> > > > > >
> > > > > > > > process.>
> > > > > > > >
> > > > > > > > WDYT Carlos ?>
> > > > > > > >
> > > > > > > > On Thu, Oct 19, 2017 at 4:16 AM, Mik

Re: Maven Docker Images

[Maxim Solodovnik]

In this case dockerhub is preferable :)

On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <bindulbhow...@gmail.com>
wrote:

> Maxim,
>
> On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> >
> > Hello,
> >
> > here is the place for Apache docker images managed by infra and Apache
> > projects https://bintray.com/apache/ :)
>
> From what I have seen, while there are 4 projects with docker
> repositories on bintray, there seem to be a lot more at dockerhub [1].
> I did a quick search on INFRA JIRA and found that infra has set a few
> projects up on dockerhub recently [2], for example INFRA-14756 [3] for
> bookkeeper.
>
> Bindul
>
> [1] https://hub.docker.com/r/apache/
> [2] https://issues.apache.org/jira/issues/?jql=component%20%
> 3D%20Docker%20AND%20project%20%3D%20INFRA
> [3] https://issues.apache.org/jira/browse/INFRA-14756
>
> >
> > On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY <herve.bout...@free.fr>
> > wrote:
> >
> > > great idea
> > >
> > > ok, we need a git repo at ASF
> > >
> > > what else?
> > > Is there some sort of release process? some sort of source to release?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > > > Thanks for the pointer, Carlos! I had searched the archives, but
> maybe I
> > > > didn't go back far enough.
> > > >
> > > > I think moving these Dockerfiles into an ASF repo would be great for
> > > their
> > > > maintainability.
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > > > On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote:
> > > > > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7,
> > > 2014,>
> > > > > 00:23 when I created the image>
> > > > >
> > > > >
> > > > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com>
> wrote:>
> > > > >
> > > > > > These images are kindly managed by a PMC member of our project
> > > (Carlos)
> > > >
> > > > but>
> > > >
> > > > > > yes they aren't managed directly by the project>
> > > > > >
> > > > > > We can easily see with him to improve this IMO.>
> > > > > >
> > > > > > When he started that (several years ago) Docker wasn't what it is
> > > >
> > > > nowadays.>
> > > >
> > > > > > With docker being mainstream I agree that we can reconsider
> this.>
> > > > > >
> > > > > > The docker image build/distribution could perhaps be part of our
> > > >
> > > > release>
> > > >
> > > > > > process.>
> > > > > >
> > > > > > WDYT Carlos ?>
> > > > > >
> > > > > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob <md...@apache.org>
> > > wrote:>
> > > > > >
> > > > > > > I guess the natural follow-on question is whether the Maven
> > > >
> > > > community>
> > > >
> > > > > > > would consider publishing an official set of images? Or
> > > >
> > > > alternatively>
> > > >
> > > > > > > whether they should send a takedown notice to protect their
> brand
> > > >
> > > > and>
> > > >
> > > > > > > trademarks...>
> > > > > > >
> > > > > > > On 2017-10-18 18:36, "Manfred Moser" <ma...@simpligility.com>
> > > wrote:>
> > > > > > >
> > > > > > > > No. As you can see from the github URL this is NOT an apache
> > > URL.>
> > > > > > > >
> > > > > > > > https://github.com/carlossg/docker-maven>
> > > > > > > >
> > > > > > > >
> > > > > > > > Mike Drob wrote on 2017-10-18 16:32:>
> > > > > > > >
> > > > > > > > > Hello,>
> > > > > > > > >
> > > > > > > > > Are the images at https://

Re: Maven Docker Images

[Maxim Solodovnik]

Hello,

here is the place for Apache docker images managed by infra and Apache
projects https://bintray.com/apache/ :)

On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY 
wrote:

> great idea
>
> ok, we need a git repo at ASF
>
> what else?
> Is there some sort of release process? some sort of source to release?
>
> Regards,
>
> Hervé
>
> Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > Thanks for the pointer, Carlos! I had searched the archives, but maybe I
> > didn't go back far enough.
> >
> > I think moving these Dockerfiles into an ASF repo would be great for
> their
> > maintainability.
> >
> > Thanks,
> >
> > Mike
> >
> > On 2017-10-19 03:50, Carlos Sanchez  wrote:
> > > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7,
> 2014,>
> > > 00:23 when I created the image>
> > >
> > >
> > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier  wrote:>
> > >
> > > > These images are kindly managed by a PMC member of our project
> (Carlos)
> >
> > but>
> >
> > > > yes they aren't managed directly by the project>
> > > >
> > > > We can easily see with him to improve this IMO.>
> > > >
> > > > When he started that (several years ago) Docker wasn't what it is
> >
> > nowadays.>
> >
> > > > With docker being mainstream I agree that we can reconsider this.>
> > > >
> > > > The docker image build/distribution could perhaps be part of our
> >
> > release>
> >
> > > > process.>
> > > >
> > > > WDYT Carlos ?>
> > > >
> > > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob 
> wrote:>
> > > >
> > > > > I guess the natural follow-on question is whether the Maven
> >
> > community>
> >
> > > > > would consider publishing an official set of images? Or
> >
> > alternatively>
> >
> > > > > whether they should send a takedown notice to protect their brand
> >
> > and>
> >
> > > > > trademarks...>
> > > > >
> > > > > On 2017-10-18 18:36, "Manfred Moser" 
> wrote:>
> > > > >
> > > > > > No. As you can see from the github URL this is NOT an apache
> URL.>
> > > > > >
> > > > > > https://github.com/carlossg/docker-maven>
> > > > > >
> > > > > >
> > > > > > Mike Drob wrote on 2017-10-18 16:32:>
> > > > > >
> > > > > > > Hello,>
> > > > > > >
> > > > > > > Are the images at https://hub.docker.com/r/_/maven/
> considered to
> >
> > be>
> >
> > > > > official>
> > > > >
> > > > > > > maven docker images and blessed/published by the PMC?>
> > > > > > >
> > > > > > > Thanks,>
> > > > > > > Mike>
> >
> > ->
> >
> > > > > > > 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>
> > > >
> > > > -->
> > > > ->
> > > > Arnaud H�ritier>
> > > > http://aheritier.net>
> > > > Mail/GTalk: aheritier AT gmail DOT com>
> > > > Twitter/Skype : aheritier>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Producing java8 and java7 versions

[Maxim Solodovnik]

I don't have computer right now, so I can't check
I believe you can check pom in their repo or ask their mailing list :)

Additional option might me: having version X.a.b.c for java7 and version
Y.a.b.c for java8

Apache Wicket uses such naming ...

WBR, Maxim
(from mobile, sorry for the typos)

On Jun 8, 2017 11:11, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

> So, they are adding the java version as a suffix to the version of the
> artifact … don’t quite know if I really like that solution. I think It
> would break some version related automatisms, but it is definitely a safer
> solution as the classifier solution. But how would such a build look like?
> Using version properties everywhere except the pom type artifacts which are
> used as parents by the leaf artifacts? That could work, but would it break
> anything with the release-plugin?
>
> Chris
>
>
> Am 08.06.17, 11:04 schrieb "Maxim Solodovnik" <solomax...@gmail.com>:
>
> Hello Chris,
>
> Here is one example:
> https://repo1.maven.org/maven2/org/postgresql/postgresql/
>
> WBR, Maxim
> (from mobile, sorry for the typos)
>
> On Jun 8, 2017 10:44, "Christofer Dutz" <christofer.d...@c-ware.de>
> wrote:
>
> > Hi,
> >
> > Currently the Edgent project produces two tar.gz files … one for
> java7 and
> > one for java8. Now they would like to produce artifacts for
> Maven-Central.
> >
> > I’m currently trying to help them with their build by migrating this
> to
> > maven. I think that there currently is no clean way to provide both
> java7
> > and java8 versions. We could add classifiers, but that would mess up
> the
> > dependency resolution mechanism.
> >
> > Do you guys know how other projects do this sort of thing?
> >
> > Chris
> >
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

Re: Producing java8 and java7 versions

[Maxim Solodovnik]

Hello Chris,

Here is one example:
https://repo1.maven.org/maven2/org/postgresql/postgresql/

WBR, Maxim
(from mobile, sorry for the typos)

On Jun 8, 2017 10:44, "Christofer Dutz"  wrote:

> Hi,
>
> Currently the Edgent project produces two tar.gz files … one for java7 and
> one for java8. Now they would like to produce artifacts for Maven-Central.
>
> I’m currently trying to help them with their build by migrating this to
> maven. I think that there currently is no clean way to provide both java7
> and java8 versions. We could add classifiers, but that would mess up the
> dependency resolution mechanism.
>
> Do you guys know how other projects do this sort of thing?
>
> Chris
>

Re: Issue with maven-war-plugin

[Maxim Solodovnik]

Done: https://issues.apache.org/jira/browse/MWAR-407

Thanks!

On Sat, May 20, 2017 at 1:24 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Will do,
> Thanks :)
>
> On Sat, May 20, 2017 at 1:23 PM, Anders Hammar <and...@hammar.net> wrote:
>
>> The best option is to create an example project demonstrating the problem.
>> The create a jira issue describing the issue and attach the example
>> project
>> there.
>>
>> You may very well follow up on the ticket on this list, but it makes
>> things
>> easier if we have a ticket if it is an issue. It's also a convenient place
>> to upload the example project.
>>
>> /Anders
>>
>> On Sat, May 20, 2017 at 7:45 AM, Maxim Solodovnik <solomax...@gmail.com>
>> wrote:
>>
>> > Can someone please confirm this?
>> > Should I create quick-start application demonstrating this?
>> >
>> > On Fri, May 19, 2017 at 10:45 AM, Maxim Solodovnik <
>> solomax...@gmail.com>
>> > wrote:
>> >
>> > > Hello All,
>> > >
>> > > Recently I have updated maven-war-plugin version to be 3.1.0 and found
>> > > out filteringDeploymentDescriptors behaviour was changed.
>> > > Instead of filtering deployment descriptors only (web.xml) it is not
>> > > filtering ALL files in webapp folder including binary (*.ico, *.mp3,
>> > > etc)
>> > >
>> > > Since 3.0.0 works as expected I believe it is caused by the fix for
>> [1]
>> > > Is there any option to workaround this somehow?
>> > >
>> > >
>> > > [1] https://issues.apache.org/jira/browse/MWAR-404
>> > >
>> > > --
>> > > WBR
>> > > Maxim aka solomax
>> > >
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>> >
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: Issue with maven-war-plugin

[Maxim Solodovnik]

Will do,
Thanks :)

On Sat, May 20, 2017 at 1:23 PM, Anders Hammar <and...@hammar.net> wrote:

> The best option is to create an example project demonstrating the problem.
> The create a jira issue describing the issue and attach the example project
> there.
>
> You may very well follow up on the ticket on this list, but it makes things
> easier if we have a ticket if it is an issue. It's also a convenient place
> to upload the example project.
>
> /Anders
>
> On Sat, May 20, 2017 at 7:45 AM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
> > Can someone please confirm this?
> > Should I create quick-start application demonstrating this?
> >
> > On Fri, May 19, 2017 at 10:45 AM, Maxim Solodovnik <solomax...@gmail.com
> >
> > wrote:
> >
> > > Hello All,
> > >
> > > Recently I have updated maven-war-plugin version to be 3.1.0 and found
> > > out filteringDeploymentDescriptors behaviour was changed.
> > > Instead of filtering deployment descriptors only (web.xml) it is not
> > > filtering ALL files in webapp folder including binary (*.ico, *.mp3,
> > > etc)
> > >
> > > Since 3.0.0 works as expected I believe it is caused by the fix for [1]
> > > Is there any option to workaround this somehow?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/MWAR-404
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



-- 
WBR
Maxim aka solomax

Re: Issue with maven-war-plugin

[Maxim Solodovnik]

Can someone please confirm this?
Should I create quick-start application demonstrating this?

On Fri, May 19, 2017 at 10:45 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Hello All,
>
> Recently I have updated maven-war-plugin version to be 3.1.0 and found
> out filteringDeploymentDescriptors behaviour was changed.
> Instead of filtering deployment descriptors only (web.xml) it is not
> filtering ALL files in webapp folder including binary (*.ico, *.mp3,
> etc)
>
> Since 3.0.0 works as expected I believe it is caused by the fix for [1]
> Is there any option to workaround this somehow?
>
>
> [1] https://issues.apache.org/jira/browse/MWAR-404
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Issue with maven-war-plugin

[Maxim Solodovnik]

Hello All,

Recently I have updated maven-war-plugin version to be 3.1.0 and found
out filteringDeploymentDescriptors behaviour was changed.
Instead of filtering deployment descriptors only (web.xml) it is not
filtering ALL files in webapp folder including binary (*.ico, *.mp3,
etc)

Since 3.0.0 works as expected I believe it is caused by the fix for [1]
Is there any option to workaround this somehow?


[1] https://issues.apache.org/jira/browse/MWAR-404

-- 
WBR
Maxim aka solomax

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

Re: generate a POM with dependencies only?

[Maxim Solodovnik]

I would like to ask related question here

Is it possible to get dependency version?
I'm creating one big jar for all dependencies using assembly plugin, but
org.bouncycastle:bcprov-jdk15on cannot be repacked
So I need to manually track it's version :(
Would be great if I can get bcprov version and automatically set it using
xslt transformation

On Thu, May 4, 2017 at 1:39 AM, Richard Sand  wrote:

> Woohoo!
>
> Thanks Robert!
>
> -Richard
>
>
>
>
> -- Original Message --
> From: "Robert Scholte" 
> To: "Maven Users List" 
> Sent: 5/3/2017 2:38:56 PM
> Subject: Re: generate a POM with dependencies only?
>
> Yes, http://www.mojohaus.org/flatten-maven-plugin/
>>
>> On Wed, 03 May 2017 20:37:52 +0200, Richard Sand 
>> wrote:
>>
>> Is there a plugin/goal that will generate a "reduced" POM for a project
>>> that only contains the dependencies, but none of the other build/profile
>>> or any other tags?
>>>
>>> May sound like a strange ask - but the scenario I'm facing is that I'm
>>> building a particular set of jars/wars/zips (using assembly plugin), and
>>> the POMs for these artifacts all rely on a heirarchy of parent POMs  which
>>> have many dependencyManagement, build, and profile elements. My  customers
>>> have their own internal Maven repositories, and are not  connecting to my
>>> company's private repos, so their ask is that I provide  the POM for each
>>> artifact we distribute in the zip file. So basically I  want to give them a
>>> stripped down POM that only has the dependencies in  it so that they can
>>> upload the artifacts into their internal repos and  include them in their
>>> projects. They will never actually be building our  artifacts.
>>>
>>> Best regards,
>>>
>>> Richard
>>>
>>>
>>> -
>>> 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
>
>


-- 
WBR
Maxim aka solomax

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

Hello Hervé,

Thanks for your detailed reply :)
Here is the current site: http://openmeetings.apache.org
Sites for the sub-projects are:
http://openmeetings.apache.org/openmeetings-util/
http://openmeetings.apache.org/openmeetings-web/
some others.

Your suggestion with  works very well, unfortunately
It produces _huge_ bottom menu
And I'm unable to filter it :((
reflowSkin seems not to be actively developed, will try to ask question on
their github project

On Fri, Feb 17, 2017 at 9:19 AM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> Hi Maxim,
>
> Sorry, was in vacations and lost the conversation... but let's continue
>
> First, you gave great links to source code: do you have a published result
> somewhere? (= a demo of the result you want, even if currently the code to
> have such result is too complex and you're looking to make it simpler)
>
> As first reaction from what I see in https://github.com/apache/
> openmeetings/
> blob/3.2.x/openmeetings-util/src/site/site.xml, instead of:
>   
> you should use
>   
>
> see http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/
> decoration.html#class_menu for reference documentation
>
>
> Maven has a bunch of such multi-module component sites:
> - Maven core:
>   result = http://maven.apache.org/ref/3-LATEST/
>   source = https://github.com/apache/maven
>
> - Doxia Sitetools (which is a key component of maven-site-plugin to do the
> site menus...):
>   result = http://maven.apache.org/doxia/doxia-sitetools/
>   source = https://github.com/apache/maven-doxia-sitetools
>
> I'm struggling for years to make easy doc do describe clearly relationship
> between maven-site-plugin, Doxia and Doxia Sitetools: any feedback on how
> to
> improve our documentation is welcome
>
> Regards,
>
> Hervé
>
> Le lundi 6 février 2017, 10:20:55 CET Maxim Solodovnik a écrit :
> > Hello Hervé,
> >
> > Thanks for the quick reply,
> >
> > Few words about project structure:
> > project root: https://github.com/apache/openmeetings/tree/3.2.x
> >
> > main site.xml
> > https://github.com/apache/openmeetings/blob/3.2.x/src/site/site.xml
> > contains skin definitions and links being displayed by all modules
> >
> > "standard" site.xml
> > https://github.com/apache/openmeetings/blob/3.2.x/
> openmeetings-util/src/site
> > /site.xml
> >
> > one of the modules:
> > https://github.com/apache/openmeetings/tree/3.2.x/openmeetings-server
> > performing final assembly, and contains main site with all xdocs etc.:
> > https://github.com/apache/openmeetings/blob/3.2.x/
> openmeetings-server/src/si
> > te/site.xml
> >
> > I'm not advanced maven user and still learning, so would appreciate any
> > suggestions :)
> >
> > On Fri, Feb 3, 2017 at 6:41 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> wrote:
> > > in all the cases I know of , since there is site.xml inheritance for
> > > shared
> > > parts, site.xml for modules are not necessary.
> > >
> > > Can you share the "standard" site.xml?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 3 février 2017, 16:31:14 CET Maxim Solodovnik a écrit :
> > > > Actually I have multi-module project
> > > > I have "main site" with some how-tos, announces etc.
> > > > and "standard" sites for all sub-modules: info, rat-report, javadocs,
> > > > dependencies etc.
> > > > Currently I have exactly the same site.xml for all these "standard"
> > >
> > > sites,
> > >
> > > > and I don't really like to have 7 copies of the same file :(
> > > >
> > > > On Fri, Feb 3, 2017 at 4:20 PM, Hervé BOUTEMY <herve.bout...@free.fr
> >
> > >
> > > wrote:
> > > > > you're the first one I see who does that: I never imagined to
> support
> > >
> > > this
> > >
> > > > > scenario
> > > > >
> > > > > Then I'd say: it's by design :)
> > > > >
> > > > > I don't know if adding this feature would be hard or not
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le jeudi 2 février 2017, 01:02:33 CET Maxim Solodovnik a écrit :
> > > > > > One additional question,
> > > > > >
> > > > > > I'm generating site.xml during pre-site phase and storing it into
> > > > > > target/generated-site/si

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

Hello Hervé,

Thanks for the quick reply,

Few words about project structure:
project root: https://github.com/apache/openmeetings/tree/3.2.x

main site.xml
https://github.com/apache/openmeetings/blob/3.2.x/src/site/site.xml
contains skin definitions and links being displayed by all modules

"standard" site.xml
https://github.com/apache/openmeetings/blob/3.2.x/openmeetings-util/src/site/site.xml

one of the modules:
https://github.com/apache/openmeetings/tree/3.2.x/openmeetings-server
performing final assembly, and contains main site with all xdocs etc.:
https://github.com/apache/openmeetings/blob/3.2.x/openmeetings-server/src/site/site.xml

I'm not advanced maven user and still learning, so would appreciate any
suggestions :)

On Fri, Feb 3, 2017 at 6:41 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:

> in all the cases I know of , since there is site.xml inheritance for shared
> parts, site.xml for modules are not necessary.
>
> Can you share the "standard" site.xml?
>
> Regards,
>
> Hervé
>
> Le vendredi 3 février 2017, 16:31:14 CET Maxim Solodovnik a écrit :
> > Actually I have multi-module project
> > I have "main site" with some how-tos, announces etc.
> > and "standard" sites for all sub-modules: info, rat-report, javadocs,
> > dependencies etc.
> > Currently I have exactly the same site.xml for all these "standard"
> sites,
> > and I don't really like to have 7 copies of the same file :(
> >
> > On Fri, Feb 3, 2017 at 4:20 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> wrote:
> > > you're the first one I see who does that: I never imagined to support
> this
> > > scenario
> > >
> > > Then I'd say: it's by design :)
> > >
> > > I don't know if adding this feature would be hard or not
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 2 février 2017, 01:02:33 CET Maxim Solodovnik a écrit :
> > > > One additional question,
> > > >
> > > > I'm generating site.xml during pre-site phase and storing it into
> > > > target/generated-site/site.xml
> > > > But it seems to be not used
> > > > Is it by design? Or maybe I'm doing something wrong?
> > > >
> > > > On Wed, Feb 1, 2017 at 8:16 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > >
> > > wrote:
> > > > > Thanks a lot!
> > > > > Works as expected!
> > > > >
> > > > > On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl <ltheu...@gmail.com>
> > >
> > > wrote:
> > > > >> Heya,
> > > > >>
> > > > >> Try ${project.build.directory}/generated-site or change the
> > > > >> generatedSiteDirectory parameter, see
> > > > >>
> > > > >> https://maven.apache.org/plugins/maven-site-plugin/
> > >
> > > site-mojo.html#generat
> > >
> > > > >> edSiteDirectory
> > > > >>
> > > > >> HTH,
> > > > >> -Lukas
> > > > >>
> > > > >> Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
> > > > >>> Hello Karl,
> > > > >>>
> > > > >>> Thanks a lot for the quick response
> > > > >>> pre-site phase is being called if I'm using "mvn site"
> > > > >>> but XML files from target/generated-sources/site/xdoc/ are not
> being
> > > > >>> used while site generation ...
> > > > >>> Should it be generated to the different folder?
> > > > >>>
> > > > >>> On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <
> > >
> > > khmarba...@gmx.de>
> > >
> > > > >>> wrote:
> > > > >>>> Hi,
> > > > >>>>
> > > > >>>> On 01/02/17 06:52, Maxim Solodovnik wrote:
> > > > >>>>> Hello All,
> > > > >>>>>
> > > > >>>>> I wonder is it possible to generate content for maven site
> plugin?
> > > > >>>>> We are using xdoc for our site. I would like to generate source
> > >
> > > using
> > >
> > > > >>>>> xml-maven-plugin.
> > > > >>>>>
> > > > >>>>> Right now I do it in generate-sources phase and polluting
> > > > >>>>> src/site/xdoc/
> > > &

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

Actually I have multi-module project
I have "main site" with some how-tos, announces etc.
and "standard" sites for all sub-modules: info, rat-report, javadocs,
dependencies etc.
Currently I have exactly the same site.xml for all these "standard" sites,
and I don't really like to have 7 copies of the same file :(


On Fri, Feb 3, 2017 at 4:20 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:

> you're the first one I see who does that: I never imagined to support this
> scenario
>
> Then I'd say: it's by design :)
>
> I don't know if adding this feature would be hard or not
>
> Regards,
>
> Hervé
>
> Le jeudi 2 février 2017, 01:02:33 CET Maxim Solodovnik a écrit :
> > One additional question,
> >
> > I'm generating site.xml during pre-site phase and storing it into
> > target/generated-site/site.xml
> > But it seems to be not used
> > Is it by design? Or maybe I'm doing something wrong?
> >
> > On Wed, Feb 1, 2017 at 8:16 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> > > Thanks a lot!
> > > Works as expected!
> > >
> > > On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl <ltheu...@gmail.com>
> wrote:
> > >> Heya,
> > >>
> > >> Try ${project.build.directory}/generated-site or change the
> > >> generatedSiteDirectory parameter, see
> > >>
> > >> https://maven.apache.org/plugins/maven-site-plugin/
> site-mojo.html#generat
> > >> edSiteDirectory
> > >>
> > >> HTH,
> > >> -Lukas
> > >>
> > >> Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
> > >>> Hello Karl,
> > >>>
> > >>> Thanks a lot for the quick response
> > >>> pre-site phase is being called if I'm using "mvn site"
> > >>> but XML files from target/generated-sources/site/xdoc/ are not being
> > >>> used while site generation ...
> > >>> Should it be generated to the different folder?
> > >>>
> > >>> On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <
> khmarba...@gmx.de>
> > >>>
> > >>> wrote:
> > >>>> Hi,
> > >>>>
> > >>>> On 01/02/17 06:52, Maxim Solodovnik wrote:
> > >>>>> Hello All,
> > >>>>>
> > >>>>> I wonder is it possible to generate content for maven site plugin?
> > >>>>> We are using xdoc for our site. I would like to generate source
> using
> > >>>>> xml-maven-plugin.
> > >>>>>
> > >>>>> Right now I do it in generate-sources phase and polluting
> > >>>>> src/site/xdoc/
> > >>>>> folder
> > >>>>> I tried to change the process as follows:
> > >>>>> 1) generate site source in pre-site phase
> > >>>>> 2) put generated content into
> > >>>>> ${project.build.directory}/generated-sources/site/xdoc/
> > >>>>>
> > >>>>> unfortunately it doesn't work this way :(
> > >>>>> It seems pre-site phase is not being called during mvn site:site :(
> > >>>>> What am I doing wrong?
> > >>>>
> > >>>> If you call site:site you call the goal of the plugin and NOT the
> life
> > >>>> cycle. You need to call mvn site instead than pre-site and site life
> > >>>> cycle
> > >>>> phases will run...
> > >>>>
> > >>>>
> > >>>> 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
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

I have tried to to set siteDirectory to be target/generated-site
But it doesn't work very well on my multi-module project

On Thu, Feb 2, 2017 at 1:02 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> One additional question,
>
> I'm generating site.xml during pre-site phase and storing it into
> target/generated-site/site.xml
> But it seems to be not used
> Is it by design? Or maybe I'm doing something wrong?
>
> On Wed, Feb 1, 2017 at 8:16 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> > Thanks a lot!
> > Works as expected!
> >
> > On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl <ltheu...@gmail.com>
> wrote:
> >>
> >> Heya,
> >>
> >> Try ${project.build.directory}/generated-site or change the
> >> generatedSiteDirectory parameter, see
> >>
> >> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#
> generatedSiteDirectory
> >>
> >> HTH,
> >> -Lukas
> >>
> >>
> >>
> >> Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
> >>>
> >>> Hello Karl,
> >>>
> >>> Thanks a lot for the quick response
> >>> pre-site phase is being called if I'm using "mvn site"
> >>> but XML files from target/generated-sources/site/xdoc/ are not being
> >>> used while site generation ...
> >>> Should it be generated to the different folder?
> >>>
> >>> On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <khmarba...@gmx.de
> >
> >>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> On 01/02/17 06:52, Maxim Solodovnik wrote:
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I wonder is it possible to generate content for maven site plugin?
> >>>>> We are using xdoc for our site. I would like to generate source using
> >>>>> xml-maven-plugin.
> >>>>>
> >>>>> Right now I do it in generate-sources phase and polluting
> src/site/xdoc/
> >>>>> folder
> >>>>> I tried to change the process as follows:
> >>>>> 1) generate site source in pre-site phase
> >>>>> 2) put generated content into
> >>>>> ${project.build.directory}/generated-sources/site/xdoc/
> >>>>>
> >>>>> unfortunately it doesn't work this way :(
> >>>>> It seems pre-site phase is not being called during mvn site:site :(
> >>>>> What am I doing wrong?
> >>>>>
> >>>> If you call site:site you call the goal of the plugin and NOT the life
> >>>> cycle. You need to call mvn site instead than pre-site and site life
> >>>> cycle
> >>>> phases will run...
> >>>>
> >>>>
> >>>> 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
> >>
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

One additional question,

I'm generating site.xml during pre-site phase and storing it into
target/generated-site/site.xml
But it seems to be not used
Is it by design? Or maybe I'm doing something wrong?

On Wed, Feb 1, 2017 at 8:16 PM, Maxim Solodovnik <solomax...@gmail.com> wrote:
> Thanks a lot!
> Works as expected!
>
> On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl <ltheu...@gmail.com> wrote:
>>
>> Heya,
>>
>> Try ${project.build.directory}/generated-site or change the
>> generatedSiteDirectory parameter, see
>>
>> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
>>
>> HTH,
>> -Lukas
>>
>>
>>
>> Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
>>>
>>> Hello Karl,
>>>
>>> Thanks a lot for the quick response
>>> pre-site phase is being called if I'm using "mvn site"
>>> but XML files from target/generated-sources/site/xdoc/ are not being
>>> used while site generation ...
>>> Should it be generated to the different folder?
>>>
>>> On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On 01/02/17 06:52, Maxim Solodovnik wrote:
>>>>>
>>>>> Hello All,
>>>>>
>>>>> I wonder is it possible to generate content for maven site plugin?
>>>>> We are using xdoc for our site. I would like to generate source using
>>>>> xml-maven-plugin.
>>>>>
>>>>> Right now I do it in generate-sources phase and polluting src/site/xdoc/
>>>>> folder
>>>>> I tried to change the process as follows:
>>>>> 1) generate site source in pre-site phase
>>>>> 2) put generated content into
>>>>> ${project.build.directory}/generated-sources/site/xdoc/
>>>>>
>>>>> unfortunately it doesn't work this way :(
>>>>> It seems pre-site phase is not being called during mvn site:site :(
>>>>> What am I doing wrong?
>>>>>
>>>> If you call site:site you call the goal of the plugin and NOT the life
>>>> cycle. You need to call mvn site instead than pre-site and site life
>>>> cycle
>>>> phases will run...
>>>>
>>>>
>>>> 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
>>
>
>
>
> --
> WBR
> Maxim aka solomax



-- 
WBR
Maxim aka solomax

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

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

Thanks a lot!
Works as expected!

On Wed, Feb 1, 2017 at 7:03 PM, Lukas Theussl <ltheu...@gmail.com> wrote:
>
> Heya,
>
> Try ${project.build.directory}/generated-site or change the
> generatedSiteDirectory parameter, see
>
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
>
> HTH,
> -Lukas
>
>
>
> Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
>>
>> Hello Karl,
>>
>> Thanks a lot for the quick response
>> pre-site phase is being called if I'm using "mvn site"
>> but XML files from target/generated-sources/site/xdoc/ are not being
>> used while site generation ...
>> Should it be generated to the different folder?
>>
>> On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
>> wrote:
>>>
>>> Hi,
>>>
>>> On 01/02/17 06:52, Maxim Solodovnik wrote:
>>>>
>>>> Hello All,
>>>>
>>>> I wonder is it possible to generate content for maven site plugin?
>>>> We are using xdoc for our site. I would like to generate source using
>>>> xml-maven-plugin.
>>>>
>>>> Right now I do it in generate-sources phase and polluting src/site/xdoc/
>>>> folder
>>>> I tried to change the process as follows:
>>>> 1) generate site source in pre-site phase
>>>> 2) put generated content into
>>>> ${project.build.directory}/generated-sources/site/xdoc/
>>>>
>>>> unfortunately it doesn't work this way :(
>>>> It seems pre-site phase is not being called during mvn site:site :(
>>>> What am I doing wrong?
>>>>
>>> If you call site:site you call the goal of the plugin and NOT the life
>>> cycle. You need to call mvn site instead than pre-site and site life
>>> cycle
>>> phases will run...
>>>
>>>
>>> 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
>



-- 
WBR
Maxim aka solomax

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

Re: Generating xdoc content to be included into site

[Maxim Solodovnik]

Hello Karl,

Thanks a lot for the quick response
pre-site phase is being called if I'm using "mvn site"
but XML files from target/generated-sources/site/xdoc/ are not being
used while site generation ...
Should it be generated to the different folder?

On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi,
>
> On 01/02/17 06:52, Maxim Solodovnik wrote:
>>
>> Hello All,
>>
>> I wonder is it possible to generate content for maven site plugin?
>> We are using xdoc for our site. I would like to generate source using
>> xml-maven-plugin.
>>
>> Right now I do it in generate-sources phase and polluting src/site/xdoc/
>> folder
>> I tried to change the process as follows:
>> 1) generate site source in pre-site phase
>> 2) put generated content into
>> ${project.build.directory}/generated-sources/site/xdoc/
>>
>> unfortunately it doesn't work this way :(
>> It seems pre-site phase is not being called during mvn site:site :(
>> What am I doing wrong?
>>
>
> If you call site:site you call the goal of the plugin and NOT the life
> cycle. You need to call mvn site instead than pre-site and site life cycle
> phases will run...
>
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
WBR
Maxim aka solomax

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

Generating xdoc content to be included into site

[Maxim Solodovnik]

Hello All,

I wonder is it possible to generate content for maven site plugin?
We are using xdoc for our site. I would like to generate source using
xml-maven-plugin.

Right now I do it in generate-sources phase and polluting src/site/xdoc/ folder
I tried to change the process as follows:
1) generate site source in pre-site phase
2) put generated content into
${project.build.directory}/generated-sources/site/xdoc/

unfortunately it doesn't work this way :(
It seems pre-site phase is not being called during mvn site:site :(
What am I doing wrong?

-- 
WBR
Maxim aka solomax

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

Re: [ANN] Apache Maven WAR Plugin Version 3.0.0 Released

[Maxim Solodovnik]

Hello Karl,

sorry for the late response
I finally was able to find time and create quick-start for this issue:
https://github.com/solomax/multimodule-with-war

the following command
mvn -Dom.quick.build=true install -pl multimodule-with-war-web -pl
multimodule-with-war-server

works as expected with maven-war-plugin:2.6 and fails with
maven-war-plugin:3.0.0

On Mon, Aug 29, 2016 at 10:58 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi,
>
> do you have an example project which shows the behaviour ?
>
> May be you create it on github ? Or create a JIRA and attach the example
> project to it?
>
> Kind regards
> Karl Heinz Marbaise
>
>
> On 29/08/16 15:28, Maxim Solodovnik wrote:
>>
>> After switching to this version I got weird error on multi-module project:
>>
>> full build is OK
>> in case I'm building only some sub-projects using "-pl" option I got
>> build command is "mvn install -P quick,allModules,mysql -pl
>> openmeetings-web" (I'm not using install:install)
>>
>> Failed to execute goal
>> org.apache.maven.plugins:maven-install-plugin:2.5.2:install
>> (default-install) on project openmeetings-web: The packaging for this
>> project did not assign a file to the build artifact -> [Help 1]
>>
>> everything works as expected with 2.6
>>
>> Maybe you can suggest what need to be changed to fix the issue?
>>
>> Thanks in advance
>>
>>
>> On Sun, Aug 28, 2016 at 5:54 PM, Karl Heinz Marbaise
>> <khmarba...@apache.org>
>> wrote:
>>
>>> The Apache Maven team is pleased to announce the release of the
>>> Apache Maven WAR Plugin, version 3.0.0.
>>>
>>> The WAR Plugin is responsible for collecting all artifact dependencies,
>>> classes
>>> and resources of the web application and packaging them into a web
>>> application
>>> archive.
>>>
>>> http://maven.apache.org/plugins/maven-war-plugin/
>>>
>>> You should specify the version in your project's plugin configuration:
>>>
>>> 
>>>   org.apache.maven.plugins
>>>   maven-war-plugin
>>>   3.0.0
>>> 
>>>
>>> You can download the appropriate sources etc. from the download page:
>>>
>>> https://maven.apache.org/plugins/maven-war-plugin/download.cgi
>>>
>>> Important Note:
>>>
>>>  * Maven 3.X only
>>>  * JDK 6 minimum requirement
>>>
>>> Release Notes - Maven WAR Plugin - Version 3.0.0
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12318121=12331760
>>>
>>> Bugs:
>>>
>>>  * [MWAR-367] - Overlay removes /META-INF/context.xml
>>>  * [MWAR-369] - Upgrade to XStream 1.4.9
>>>  * [MWAR-379] - manifest goal violates general Maven principle and
>>> creates
>>> file into src/main/..
>>>
>>> Documentation:
>>>
>>>  * [MWAR-346] - Fix broken links
>>>
>>> Improvements:
>>>
>>>  * [MWAR-225] - Add support for customizing filtering delimiters like the
>>> resources plugin
>>>  * [MWAR-262] -  default value should be false for
>>> Servlet level > 2.5 projects
>>>  * [MWAR-326] - Add LifecycleMapping and ArtifactHandler from maven-core
>>> to target packaging plugin
>>>  * [MWAR-328] - Upgrade to Maven 3.0 compatiblity / JDK 6
>>>  * [MWAR-347] - Upgrade plexus-io to 2.6
>>>  * [MWAR-348] - Upgrade maven-invoker-plugin to 1.10
>>>  * [MWAR-349] - Upgrade to fluido skin 1.4.0
>>>  * [MWAR-361] - Removed unused dependencies in project
>>>  * [MWAR-362] - Bump version to 3.0.0-SNAPSHOT
>>>  * [MWAR-363] - Removed hard coded version for maven-invoker-plugin
>>>  * [MWAR-364] - Upgrade plexus-utils to 3.0.22
>>>  * [MWAR-365] - Upgrade plexus-archiver from 3.0.1 to 3.0.3
>>>  * [MWAR-366] - Change package to org.apache.maven.plugins to prevent
>>> conflict with Maven Core
>>>  * [MWAR-370] - Upgrade plexus-archiver 3.0.3 to 3.1.1
>>>  * [MWAR-372] - Upgrade maven-archiver to 3.0.1
>>>  * [MWAR-373] - Make finalName readonly parameter
>>>  * [MWAR-376] - Remove param properties that doesn't make sense for CLI
>>> usage
>>>  * [MWAR-380] - Filtered resources folder should be changed
>>>  * [MWAR-381] - Upgrade maven-archiver to 3.0.2
>>>  * [MWAR-382] - Upgrade plexus-utils to 3.0.24
>>>  * [MWAR-383] - Upgrade plexus-archiver to 3.2 / commons-io to 2.5
>>>  * [MWAR-385] - Upgrade 

Re: [ANN] Apache Maven WAR Plugin Version 3.0.0 Released

[Maxim Solodovnik]

After switching to this version I got weird error on multi-module project:

full build is OK
in case I'm building only some sub-projects using "-pl" option I got
build command is "mvn install -P quick,allModules,mysql -pl
openmeetings-web" (I'm not using install:install)

Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.5.2:install
(default-install) on project openmeetings-web: The packaging for this
project did not assign a file to the build artifact -> [Help 1]

everything works as expected with 2.6

Maybe you can suggest what need to be changed to fix the issue?

Thanks in advance


On Sun, Aug 28, 2016 at 5:54 PM, Karl Heinz Marbaise 
wrote:

> The Apache Maven team is pleased to announce the release of the
> Apache Maven WAR Plugin, version 3.0.0.
>
> The WAR Plugin is responsible for collecting all artifact dependencies,
> classes
> and resources of the web application and packaging them into a web
> application
> archive.
>
> http://maven.apache.org/plugins/maven-war-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>   org.apache.maven.plugins
>   maven-war-plugin
>   3.0.0
> 
>
> You can download the appropriate sources etc. from the download page:
>
> https://maven.apache.org/plugins/maven-war-plugin/download.cgi
>
> Important Note:
>
>  * Maven 3.X only
>  * JDK 6 minimum requirement
>
> Release Notes - Maven WAR Plugin - Version 3.0.0
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318121=12331760
>
> Bugs:
>
>  * [MWAR-367] - Overlay removes /META-INF/context.xml
>  * [MWAR-369] - Upgrade to XStream 1.4.9
>  * [MWAR-379] - manifest goal violates general Maven principle and creates
> file into src/main/..
>
> Documentation:
>
>  * [MWAR-346] - Fix broken links
>
> Improvements:
>
>  * [MWAR-225] - Add support for customizing filtering delimiters like the
> resources plugin
>  * [MWAR-262] -  default value should be false for
> Servlet level > 2.5 projects
>  * [MWAR-326] - Add LifecycleMapping and ArtifactHandler from maven-core
> to target packaging plugin
>  * [MWAR-328] - Upgrade to Maven 3.0 compatiblity / JDK 6
>  * [MWAR-347] - Upgrade plexus-io to 2.6
>  * [MWAR-348] - Upgrade maven-invoker-plugin to 1.10
>  * [MWAR-349] - Upgrade to fluido skin 1.4.0
>  * [MWAR-361] - Removed unused dependencies in project
>  * [MWAR-362] - Bump version to 3.0.0-SNAPSHOT
>  * [MWAR-363] - Removed hard coded version for maven-invoker-plugin
>  * [MWAR-364] - Upgrade plexus-utils to 3.0.22
>  * [MWAR-365] - Upgrade plexus-archiver from 3.0.1 to 3.0.3
>  * [MWAR-366] - Change package to org.apache.maven.plugins to prevent
> conflict with Maven Core
>  * [MWAR-370] - Upgrade plexus-archiver 3.0.3 to 3.1.1
>  * [MWAR-372] - Upgrade maven-archiver to 3.0.1
>  * [MWAR-373] - Make finalName readonly parameter
>  * [MWAR-376] - Remove param properties that doesn't make sense for CLI
> usage
>  * [MWAR-380] - Filtered resources folder should be changed
>  * [MWAR-381] - Upgrade maven-archiver to 3.0.2
>  * [MWAR-382] - Upgrade plexus-utils to 3.0.24
>  * [MWAR-383] - Upgrade plexus-archiver to 3.2 / commons-io to 2.5
>  * [MWAR-385] - Upgrade maven-plugins to version 30
>  * [MWAR-387] - Upgrade of 'plexus-archiver' to version 3.3.
>  * [MWAR-388] - Upgrade maven-archiver to 3.1.0
>  * [MWAR-389] - Upgrade maven-filtering to 3.1.1
>
> New Feature:
>
>  * [MWAR-350] - Add Skip Parameter to Skip the process
> Task
>  * [MWAR-391] - Upgrade of plexus-archiver to 3.4.
>  * [MWAR-392] - Upgrade of plexus-interpolation to 1.22.
>  * [MWAR-393] - Upgrade of maven-archiver 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
>
>


-- 
WBR
Maxim aka solomax

Re: Questions regarding License Maven Plugin

[Maxim Solodovnik]

Thanks for clarifications, wrote the post to the correspondent google-group

On Fri, May 27, 2016 at 7:27 PM, Mark H. Wood  wrote:

> On Thu, May 26, 2016 at 10:34:28AM +0100, Stian Soiland-Reyes wrote:
> > license-maven-plugin is not maintained by Apache, and have its own
> mailing
> > list which should be able to help you further:
>
> More generally:  a plugin with a name like FOO-maven-plugin is not
> maintained by the Maven project, and it would be good to see if it has
> its own mailing list.  A plugin with a name like maven-FOO-plugin
> probably *is* maintained by the Maven project.
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749
> www.ulib.iupui.edu
>



-- 
WBR
Maxim aka solomax

Re: Questions regarding License Maven Plugin

[Maxim Solodovnik]

Hm,
According to [1], this is the only user list available
So I hope to get some answers to my questions here

[1] http://www.mojohaus.org/license-maven-plugin/mail-lists.html

On Thu, May 26, 2016 at 3:53 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> sorry for posting to the wrong list
> The plugin was announced here, this is why I wrote here :(
> Will write to the correct list
>
> On Thu, May 26, 2016 at 3:34 PM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
>
>> Hi,
>>
>> license-maven-plugin is not maintained by Apache, and have its own mailing
>> list which should be able to help you further:
>>
>> http://www.mojohaus.org/license-maven-plugin/mail-lists.html
>>
>> Some documentation for each goal:
>>
>> http://www.mojohaus.org/license-maven-plugin/plugin-info.html
>> On 26 May 2016 5:19 a.m., "Maxim Solodovnik" <solomax...@gmail.com>
>> wrote:
>>
>> > Hello All,
>> >
>> > I'm trying to integrate license-maven-plugin and have couple of
>> questions:
>> >
>> > 1) it seems like "aggregate-add-third-party" goal with "useMissingFile"
>> > option is not generating "src/license/THIRD-PARTY.properties" files, is
>> > this by design?
>> >
>> > 2) it seems "groupByLicense" option is not available for
>> > "aggregate-add-third-party"
>> > goal, maybe it can be added?
>> >
>> > 3) Is it possible to generate LICENSE file like [1] using this plugin?
>> >
>> > so there will be blocks like:
>> > license name
>> > affected libraries
>> > license text
>> >
>> >
>> > Thanks in advance for the answers :)
>> >
>> > [1]
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=blob_plain;f=LICENSE;hb=HEAD
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>> >
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: Questions regarding License Maven Plugin

[Maxim Solodovnik]

sorry for posting to the wrong list
The plugin was announced here, this is why I wrote here :(
Will write to the correct list

On Thu, May 26, 2016 at 3:34 PM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> Hi,
>
> license-maven-plugin is not maintained by Apache, and have its own mailing
> list which should be able to help you further:
>
> http://www.mojohaus.org/license-maven-plugin/mail-lists.html
>
> Some documentation for each goal:
>
> http://www.mojohaus.org/license-maven-plugin/plugin-info.html
> On 26 May 2016 5:19 a.m., "Maxim Solodovnik" <solomax...@gmail.com> wrote:
>
> > Hello All,
> >
> > I'm trying to integrate license-maven-plugin and have couple of
> questions:
> >
> > 1) it seems like "aggregate-add-third-party" goal with "useMissingFile"
> > option is not generating "src/license/THIRD-PARTY.properties" files, is
> > this by design?
> >
> > 2) it seems "groupByLicense" option is not available for
> > "aggregate-add-third-party"
> > goal, maybe it can be added?
> >
> > 3) Is it possible to generate LICENSE file like [1] using this plugin?
> >
> > so there will be blocks like:
> > license name
> > affected libraries
> > license text
> >
> >
> > Thanks in advance for the answers :)
> >
> > [1]
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=blob_plain;f=LICENSE;hb=HEAD
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



-- 
WBR
Maxim aka solomax

Questions regarding License Maven Plugin

[Maxim Solodovnik]

Hello All,

I'm trying to integrate license-maven-plugin and have couple of questions:

1) it seems like "aggregate-add-third-party" goal with "useMissingFile"
option is not generating "src/license/THIRD-PARTY.properties" files, is
this by design?

2) it seems "groupByLicense" option is not available for
"aggregate-add-third-party"
goal, maybe it can be added?

3) Is it possible to generate LICENSE file like [1] using this plugin?

so there will be blocks like:
license name
affected libraries
license text


Thanks in advance for the answers :)

[1]
https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=blob_plain;f=LICENSE;hb=HEAD

-- 
WBR
Maxim aka solomax

Re: maven-jar-plugin-3.0.0 compatiblity/regression?

[Maxim Solodovnik]

Thanks a lot!
will wait for the updated version :)
not sure how plugin in eclipse can be updated with snapshot version :(

On Mon, May 23, 2016 at 11:44 AM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:

> Hi Maxim,
>
> I've already created an issue for m2e:
>
> https://github.com/tesla/m2eclipse-mavenarchiver/issues/8
>
> Kind regards
> Karl Heinz Marbaise
>
> On 5/23/16 5:54 AM, Maxim Solodovnik wrote:
>
>> Hello Karl,
>>
>> do I need to create JIRA issue? or maybe you can point me to the correct
>> tracker I can file issue against m2e?
>>
>> On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise <khmarba...@gmx.de>
>> wrote:
>>
>> Hi,
>>>
>>>
>>> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>>>
>>> I got following errors in eclipse:
>>>>
>>>>
>>>>
>>>> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
>>>> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
>>>> /openmeetings-core line 1 Maven Configuration Problem
>>>>
>>>> command line build works as expected
>>>>
>>>>
>>> This is a problem in M2E ...
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
>>>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <dant...@gmail.com> wrote:
>>>>
>>>> Hi
>>>>
>>>>>
>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>>>> throws this error
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>> them. -> [Help 1]
>>>>>
>>>>>
>>>>> This is a valid use case where I can have mutiple artifact extensions
>>>>> without the need to use classifiers
>>>>>
>>>>>
>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>
>>>>>
>>>>> I hope this is not intentional
>>>>>
>>>>>
>>>>> My appology, i should have tested the during its voting period
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> -Dan
>>>>>
>>>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: maven-jar-plugin-3.0.0 compatiblity/regression?

[Maxim Solodovnik]

Hello Karl,

do I need to create JIRA issue? or maybe you can point me to the correct
tracker I can file issue against m2e?

On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:

> Hi,
>
>
> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>
>> I got following errors in eclipse:
>>
>>
>> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
>> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
>> /openmeetings-core line 1 Maven Configuration Problem
>>
>> command line build works as expected
>>
>
> This is a problem in M2E ...
>
> Kind regards
> Karl Heinz Marbaise
>
>>
>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <dant...@gmail.com> wrote:
>>
>> Hi
>>>
>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>> throws this error
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>> to attach supplemental artifacts to the project instead of replacing
>>> them. -> [Help 1]
>>>
>>>
>>> This is a valid use case where I can have mutiple artifact extensions
>>> without the need to use classifiers
>>>
>>>
>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>
>>>
>>> I hope this is not intentional
>>>
>>>
>>> My appology, i should have tested the during its voting period
>>>
>>>
>>> Thanks
>>>
>>>
>>> -Dan
>>>
>>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: maven-jar-plugin-3.0.0 compatiblity/regression?

[Maxim Solodovnik]

I got following errors in eclipse:

org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
/openmeetings-core line 1 Maven Configuration Problem

command line build works as expected

On Fri, May 20, 2016 at 11:16 AM, Dan Tran  wrote:

> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
> (project-jar-for-docker) on project xxx: You have to use a classifier
> to attach supplemental artifacts to the project instead of replacing
> them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions
> without the need to use classifiers
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
>
>
> I hope this is not intentional
>
>
> My appology, i should have tested the during its voting period
>
>
> Thanks
>
>
> -Dan
>



-- 
WBR
Maxim aka solomax

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: 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

[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

[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

[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

[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

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.provision(ProvisionListenerStackCallback.java:133)
at

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

[Maxim Solodovnik]

+1

WBR, Maxim
(from mobile, sorry for the typos)
On Dec 26, 2015 02:54, "Mirko Friedenhagen"  wrote:

> +1
>
> Regards
> Mirko
> --
> Sent from my mobile
> Am 24.12.2015 23:34 schrieb "Michael Osipov" <1983-01...@gmx.net>:
>
> > Hi,
> >
> > as previously suggested, it makes sense to retire those skins because
> > they haven't been updated for a long time and we don't have the resources
> > to maintain them properly [1].
> >
> > Last releases:
> > Maven Application Skin: 2012-01-18
> > Maven Classic Skin: 2012-01-18
> > Maven Stylus Skin: 2012-07-30
> >
> > I therefore propose that we retire these skins.
> >
> > If this vote is successful I will make one final release of the skin,
> > making
> > it clear on the skin site that it has been retired. After that the source
> > code
> > will be moved into the "retired" area in our Subversion repository.
> >
> > The process for retiring a skin is described here:
> > http://maven.apache.org/developers/retirement-plan-plugins.html
> > (Though these aren't plugins, the process is universal)
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> >
> > I would ask kindly those who have already cast their vote to revote to
> > make it
> > "official".
> >
> > [1]
> >
> http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E
> >
> > Michael
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Re: Java 7 and 8 features

[Maxim Solodovnik]

We are just moved to java7 and start using new features
I personally don't like the idea of moving all code to new java, I move the
areas I currently work on

On Tue, Oct 27, 2015 at 10:57 PM, Gary Gregory 
wrote:

> Hi,
>
> What I see, is that most projects are struggling to move to Java 7, Java 8
> seems out of range. There are a lot of opinions and both sides of each Java
> version for and against. At the end of the day, it's about user feedback
> and committer community involvement. The projects I help on also lack
> manpower and maintaining more than one version is not I see folks wanting
> to do. For myself, I usually want to work on the current version in
> master/trunk and move that along. My work$ development is on Java 7 and
> slated to switch to Java 8 in 2016 I would guess.
>
> Gary
>
> On Tue, Oct 27, 2015 at 9:37 AM, Oliver B. Fischer <
> o.b.fisc...@swe-blog.net> wrote:
>
>> Hi Vinicius,
>>
>> it is mostly to allow people which are bound (for any reason) to older
>> JDK versions to use our software. There is a plenty number of projects
>> which are not able to use newer JDK versions. I know that this is a
>>  controversial topic I think that the majority of us would like to use all
>> these features. But we must not forget the people using our software in
>> their daily work.
>>
>> BYe,
>>
>> Oliver
>>
>> Am 27.10.15 um 16:49 schrieb Vinicius Corrêa de Almeida:
>>
>>> I analized some releases and i noticed that not using java 7 features
>>> like
>>> multi catch and in java 8 do not use lambda expressions and others
>>> features, so i came by this email to know why the developers not using
>>> this
>>> features?
>>>
>>>
>> --
>> 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
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
WBR
Maxim aka solomax

Re: [ANN] Apache Maven SCM Version 1.9.4 Released

[Maxim Solodovnik]

yfv ,jhtw yt ye;ty

On Thu, Apr 2, 2015 at 12:39 PM, Karl Heinz Marbaise khmarba...@apache.org
wrote:

 The Apache Maven team is pleased to announce the release of the
 Apache Maven SCM, version 1.9.4

 Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other
 tools (e.g. Continuum) by providing them with a common API for doing SCM
 operations.

 http://maven.apache.org/scm/

 Release Notes - Maven SCM - Version 1.9.4

 Bugs:

  * [SCM-764] - username and credentials shown as INFO on commadline
  * [SCM-780] - Duplicate connection url's properties
  * [SCM-786] - Missing dependency on JUnit

 Improvements:

  * [SCM-778] - Upgrade junit and hamcrest
  * [SCM-793] - Upgrade maven-modello-plugin to 1.8.2
  * [SCM-794] - Configure maven release plugin to autoVersionSubmodules

 Task:

  * [SCM-789] - Upgrade to maven-parent version 26

 Wish:

  * [SCM-785] - Upgrade Plugin Required Maven Version to 2.2.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




-- 
WBR
Maxim aka solomax

Re: [ANN] Apache Maven SCM Version 1.9.4 Released

[Maxim Solodovnik]

sorry for crappy message :(

On Thu, Apr 2, 2015 at 12:55 PM, Maxim Solodovnik solomax...@gmail.com
wrote:

 yfv ,jhtw yt ye;ty

 On Thu, Apr 2, 2015 at 12:39 PM, Karl Heinz Marbaise 
 khmarba...@apache.org wrote:

 The Apache Maven team is pleased to announce the release of the
 Apache Maven SCM, version 1.9.4

 Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other
 tools (e.g. Continuum) by providing them with a common API for doing SCM
 operations.

 http://maven.apache.org/scm/

 Release Notes - Maven SCM - Version 1.9.4

 Bugs:

  * [SCM-764] - username and credentials shown as INFO on commadline
  * [SCM-780] - Duplicate connection url's properties
  * [SCM-786] - Missing dependency on JUnit

 Improvements:

  * [SCM-778] - Upgrade junit and hamcrest
  * [SCM-793] - Upgrade maven-modello-plugin to 1.8.2
  * [SCM-794] - Configure maven release plugin to autoVersionSubmodules

 Task:

  * [SCM-789] - Upgrade to maven-parent version 26

 Wish:

  * [SCM-785] - Upgrade Plugin Required Maven Version to 2.2.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




 --
 WBR
 Maxim aka solomax




-- 
WBR
Maxim aka solomax

Re: about source and target in maven-compiler-plugin

[Maxim Solodovnik]

Hello Lin,

We had this issue in this project: https://github.com/Red5/red5-server
Here is the report:
https://groups.google.com/d/msg/red5interest/EbVFdFkEGWE/1N_eqcz5K-UJ

Somehow class was missing in runtime after building with Java8
rebuilding with Java7 fixes the problem

On Mon, Mar 30, 2015 at 1:38 PM, Lin Ma lin...@gmail.com wrote:

 Hi Maxim,

 Why compiler will not fail? Supposing StringBuilder is a class in JDK 1.6,
 but we force compiler to use 1.5 which has no such class? Please feel free
 to correct me if I am wrong.

 regards,
 Lin

 On Mon, Mar 30, 2015 at 12:33 AM, Maxim Solodovnik solomax...@gmail.com
 wrote:

  If I'm not mistaken compiler will not fail in this case
  BUT the application will fail in runtime (in case Java 1.5 is used)
  due to StringBuilder
  class is missing in JDK
 
  On Mon, Mar 30, 2015 at 1:20 PM, Lin Ma lin...@gmail.com wrote:
 
   Thanks Sebastian,
  
   1. I am using JDK 1.7/1.8 for both development and deployment in
 runtime,
   shall I change 1.5 of source and target to 1.7/1.8?
  
   2. In your example, for example you can write source code using a JDK
  1.6
   which is compliant to Java 1.5. However you can also use the
  StringBuilder
   class which does not exist in Java 1.5, I think using JDK 1.6 specific
   feature but using 1.5 complier will fail? No? Please feel free to
 correct
   me.
  
   regards,
   Lin
  
   On Mon, Mar 30, 2015 at 12:14 AM, Sebastian Oerding 
   sebastian.oerd...@robotron.de wrote:
  
source - The level (JDK version) to which the source code must be
compliant to, for example you can write source code using a JDK 1.6
  which
is compliant to Java 1.5. However you can also use the StringBuilder
   class
which does not exist in Java 1.5
target - The class version of the generated class files. The class
   format
changes with some Java version, for example as some stuff may be
 added
   for
performance reason. For example if a new byte code instruction comes
 up
(like 'invokedynamic') this really makes a change. Or another example
   (I'm
not really sure about it): As far as I think a stack map has been
 added
from Java 5 to Java 1.6. This should improve performance and makes
  subtle
differences when ClassNotFoundException are thrown. You can use a JDK
  to
compile code for different but lower versions. This way can benefit
  from
some optimizations which weren't available with the old JDK and are
compatible.
   
With regards
Sebastian
   
-Ursprüngliche Nachricht-
Von: Lin Ma [mailto:lin...@gmail.com]
Gesendet: Montag, 30. März 2015 07:46
An: Maven Users List
Betreff: about source and target in maven-compiler-plugin
   
Hello Maven masters,
   
For maven-compiler-plugin(a sample below), have a quick question. I
  read
this document (
 http://maven.apache.org/plugins/maven-compiler-plugin/
  ),
and confused what means source and target 1.5 here, it seems it is an
internal version number of Maven, independent of JDK?
   
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
   
thanks in advance,
Lin
   
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
   
  
 
 
 
  --
  WBR
  Maxim aka solomax
 




-- 
WBR
Maxim aka solomax

Re: about source and target in maven-compiler-plugin

[Maxim Solodovnik]

If I'm not mistaken compiler will not fail in this case
BUT the application will fail in runtime (in case Java 1.5 is used)
due to StringBuilder
class is missing in JDK

On Mon, Mar 30, 2015 at 1:20 PM, Lin Ma lin...@gmail.com wrote:

 Thanks Sebastian,

 1. I am using JDK 1.7/1.8 for both development and deployment in runtime,
 shall I change 1.5 of source and target to 1.7/1.8?

 2. In your example, for example you can write source code using a JDK 1.6
 which is compliant to Java 1.5. However you can also use the StringBuilder
 class which does not exist in Java 1.5, I think using JDK 1.6 specific
 feature but using 1.5 complier will fail? No? Please feel free to correct
 me.

 regards,
 Lin

 On Mon, Mar 30, 2015 at 12:14 AM, Sebastian Oerding 
 sebastian.oerd...@robotron.de wrote:

  source - The level (JDK version) to which the source code must be
  compliant to, for example you can write source code using a JDK 1.6 which
  is compliant to Java 1.5. However you can also use the StringBuilder
 class
  which does not exist in Java 1.5
  target - The class version of the generated class files. The class
 format
  changes with some Java version, for example as some stuff may be added
 for
  performance reason. For example if a new byte code instruction comes up
  (like 'invokedynamic') this really makes a change. Or another example
 (I'm
  not really sure about it): As far as I think a stack map has been added
  from Java 5 to Java 1.6. This should improve performance and makes subtle
  differences when ClassNotFoundException are thrown. You can use a JDK to
  compile code for different but lower versions. This way can benefit from
  some optimizations which weren't available with the old JDK and are
  compatible.
 
  With regards
  Sebastian
 
  -Ursprüngliche Nachricht-
  Von: Lin Ma [mailto:lin...@gmail.com]
  Gesendet: Montag, 30. März 2015 07:46
  An: Maven Users List
  Betreff: about source and target in maven-compiler-plugin
 
  Hello Maven masters,
 
  For maven-compiler-plugin(a sample below), have a quick question. I read
  this document (http://maven.apache.org/plugins/maven-compiler-plugin/),
  and confused what means source and target 1.5 here, it seems it is an
  internal version number of Maven, independent of JDK?
 
  plugin
  artifactIdmaven-compiler-plugin/artifactId
  version2.3.2/version
  configuration
  source1.5/source
  target1.5/target
  /configuration
  /plugin
 
  thanks in advance,
  Lin
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 




-- 
WBR
Maxim aka solomax

Re: [VOTE] Change project logo and adopt owl as mascot

[Maxim Solodovnik]

+1

WBR, Maxim
(from mobile, sorry for the typos)
On Nov 25, 2014 5:31 PM, domi d...@fortysix.ch wrote:

 +1

 On 25.11.2014, at 11:57, Stephen Connolly stephen.alan.conno...@gmail.com
 wrote:

 


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

Re: Important Notice for all users of the parallel build feature

[Maxim Solodovnik]

Is it possible to include this jar to maven distribution? Because it is not
always possible to change it on build servers .

On 19 October 2014 01:22, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:

 Thanks to an excellent testcase provided by a JIRA user, a significant
 source of thread safety bugs has been located and fixed. The problem
 has an extensive reach, and can be the source of practically *any*
 issue in parallel builds, and is probably the root cause of most JIRA
 issues filed wrt parallel build problems.

 Fortunately, there is a very simple fix by putting the following
 inside your plugin configuration:

 plugin
   ...
   dependencies
 dependency
   groupIdorg.codehaus.plexus/groupId
   artifactIdplexus-interpolation/artifactId
   version1.21/version
 /dependency
   /dependencies
 /plugin


 You should also put this jar file in the lib/ext folder of your maven
 installation:


 http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interpolation/1.21/plexus-interpolation-1.21.jar


 Which plugins are affected ? It's almost easier to tell which is /not/
 affected. See the relates link on
 https://jira.codehaus.org/browse/PLXCOMP-258 to see which
 plugins/tools are affected.

 Kristian

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




-- 
WBR
Maxim aka solomax

Re: Don't want to repeat plugin version for both build and reporting

[Maxim Solodovnik]

just learn something new
Thanks!

On 4 October 2014 00:46, Paul Benedict pbened...@apache.org wrote:

 pluginManagement only affects plugins -- it does not affect
 reporting:
 https://jira.codehaus.org/browse/MNG-3385

 Cheers,
 Paul

 On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik solomax...@gmail.com
 wrote:

  we using pluginManagement for this
 
  On 3 October 2014 07:24, Kathryn Huxtable kath...@kathrynhuxtable.org
  wrote:
 
   I’ve always used properties, but would it work to use
   buildDependencies? -K
  
   On Oct 2, 2014, at 7:02 PM, Paul Benedict pbened...@apache.org
 wrote:
  
I use the maven-javadoc-plugin in both build and reporting. I
 don't
want to fall back to properties to share the plugin version. Is
  there a
better way than using properties?
   
Cheers,
Paul
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
 
 
  --
  WBR
  Maxim aka solomax
 




-- 
WBR
Maxim aka solomax

Re: Don't want to repeat plugin version for both build and reporting

[Maxim Solodovnik]

we using pluginManagement for this

On 3 October 2014 07:24, Kathryn Huxtable kath...@kathrynhuxtable.org
wrote:

 I’ve always used properties, but would it work to use
 buildDependencies? -K

 On Oct 2, 2014, at 7:02 PM, Paul Benedict pbened...@apache.org wrote:

  I use the maven-javadoc-plugin in both build and reporting. I don't
  want to fall back to properties to share the plugin version. Is there a
  better way than using properties?
 
  Cheers,
  Paul


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




-- 
WBR
Maxim aka solomax