mojohaus / mojohaus.github.io

Organization website

Sources of www.mojohaus.org

Site is automatically deployed by GitHub Action after each commit.

mojohaus.github.io's Issues

native-maven-plugin : linkerSecondaryOutputExtensions behaviour - Has it changed recently?

Hi,

Can you please let me know if the behaviour of this option linkerSecondaryOutputExtensions has been recently changed in the native-maven-plugin?

Our build script used to look like this earlier(see below) with two profiles and used to populate linkerSecondaryOutput with a particular value based on either Profile A or B.In one case it was empty/blank.

The way this used to work a few months ago was it used to always produce the dll and because of lib would install corresponding artifact.lib into my local repo in the install phase.
In Profile A linkerSecondaryOutput used to be set to pdb so ${linkerSecondaryOutput} used to do the samething for corresponding artifact.pdb file. For Profile B this was empty so there would be no pdb file.

Now it looks like when the >${linkerSecondaryOutput} has value it seems to overwrite the earlier lib config and thus I end up only getting the pdb in the local repo in this case and not the lib (which earlier used to be installed to my local repo no matter what).

I think I know the workaround now i.e.

1. knockoff the static lib
2. in the profile B have ${linkerSecondaryOutput} set to just lib and in profile A have ${linkerSecondaryOutput} set to lib,pdb

I would appreciate if anyone here can let me know if this behavior got changed recently as I can then justify these pom changes to my team. Please let me know if you have any questions so I can try explaining the issue better.
Btw, we use Maven 3 and
org.codehaus.mojo
native-maven-plugin
1.0-alpha-7
I don’t quite remember if we have maven 2 earlier. Do you think it changed from maven 2 – maven 3.I doubt as we have not changed the version of the native plugin being used.

Regards,
Chetan

  <profiles>
        <profile>
              <id>B</id>
                    <properties>
                          <compilerOptions> /O2 /MT /GS </compilerOptions>
                          <linkerOptions> </linkerOptions>
                          <linkerSecondaryOutput> </linkerSecondaryOutput> <!—Empty because we don’t generate the pdb in this case-- >
                    </properties>                 
        </profile>
        
        <profile>
              <id>A</id>
                    <properties>
                          <compilerOptions> /Od /MTd /GS- </compilerOptions>
                          <linkerOptions> /DEBUG</linkerOptions>
                          <linkerSecondaryOutput>pdb</linkerSecondaryOutput>
                    </properties>                 
        </profile>  
  </profiles>       

org.codehaus.mojo native-maven-plugin 1.0-alpha-7 true win32 org.codehaus.mojo.natives.msvc.MSVC2008x86EnvFactory msvc ${basedir} **\*.c

                          </sources>
                    <compilerOutputDirectory>${project.build.directory}/objs/${project.name}</compilerOutputDirectory>
                          <compilerStartOptions>
                                <compilerStartOption> /D JVMINFO_EXPORTS </compilerStartOption>
                          </compilerStartOptions>
                          <compilerEndOptions>
                                <compilerEndOption>${compilerOptions}</compilerEndOption>
                          </compilerEndOptions>
                          <!-- deploy the accompany .lib file as well -->
                          <linkerSecondaryOutputExtensions>lib</linkerSecondaryOutputExtensions> <!—produce the lib file with dll always -- >                     
                    <linkerSecondaryOutputExtensions>${linkerSecondaryOutput}</linkerSecondaryOutputExtensions> <!—produce the pdb file depending on the maven profile in use during build -- >

                          <linkerStartOptions>
                                <linkerStartOption> /INCREMENTAL:NO /DLL   </linkerStartOption>
                                <linkerStartOption>${linkerOptions}</linkerStartOption>
                          </linkerStartOp

Change scm entry after migration to github.

xmlbeans-maven-plugin is missing

The xmlbeans-maven-plugin is referenced from this page: /plugins.html and it points to /xmlbeans-maven-plugin/ which doesn't exist.

Fix link to codehaus

Link to issues on Github instead of Codehaus.

Prepare page with description how to contribute and help to projects.

Finally we can create CONTRIBUTING.md in .github repo

https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file

http://www.mojohaus.org/plugins.html How to find sources for plugins listed, e.g.

http://www.mojohaus.org/plugins.html
How to find sources for plugins listed, e.g. selenium-maven-plugin

ref SeleniumHQ/selenium#686 (comment)

404 on a lot of links!

A lot of links are broken in this page http://www.mojohaus.org/plugins.html
eg:

• jaxb2
• xmlbeans
• sqlj
• etc...

Update "Submitting a plugin" page

The text on the Submitting a plugin page () needs some updating now after we've moved to Github.
http://www.mojohaus.org/contribution/submitting-a-plugin.html

Move openjpa mojo to graveyard

As the Apache openjpa project has a openjpa plugin which seems to be maintained, I suggest that we move our openjpa plugin to the graveyard.

Java code generation incomplete

gdv_typen2003.zip
I tried to transform the attached xsd to Java. the XSD file contains lots of simple types which should be transformed to java Enums. However, only 5 Java classes out of ~hundreds were generated.

What is going wrong?

Using:

org.codehaus.mojo jaxb2-maven-plugin 2.4 . . . org.codehaus.mojo jaxb2-maven-plugin xjc xjc ${project.basedir}/src/main/java false

Doxia Macro for plugins page

Hi,
I would like to help for the mojohaus web site. I try to write a doxia macro (see https://github.com/ebarboni/mojopagepluginsgen) to get information for maven central using Rest Api (http://search.maven.org/#api).

• This allow to get the last version of a released plugin
• This allow to get a pom

In gray => no url or no issue management
In orange => url pointing to codehaus.org.

I had to migrate the apt to xdoc because the macro was disturbing the table layout.

you can test is with : mvn clean install site.

It's work in progress.
If usefull any idea welcome.

Reporting a vulnerability

Hello!

I hope you are doing well!

We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly. GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.

Can you enable it, so that we can report it?

Thanks in advance!

PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

apt-maven-plugin not working with JDK 8

I am not able to use org.codehaus.mojo:apt-maven-plugin:1.0-alpha-5 with JDK 8. I get the following error while trying to perform a maven build.

[ERROR] Failed to execute goal org.codehaus.mojo:apt-maven-plugin:1.0-alpha-5:process (process) on project <project_name>: Unable to locate the apt compiler in:
[ERROR] /Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/jre/../lib/tools.jar
[ERROR] Please ensure you are using JDK 1.5 or above and
[ERROR] not a JRE (the com.sun.tools.apt.Main class is required).

The problem seems to be because APT compiler has been integrated into javac in JDK 8 and it cannot be invoked via tools.jar.

Using lower versions of JDK is not an option for me as I have some project features which needs JDK 8.

useLastCommittedRevision parameter is not working in buildnumber-maven-plugin

Hi,

I found the useLastCommittedRevision parameter is not working in the buildnumber-maven-plugin at least for the goal "create". Looking into the source code I doubt there is a defect.

Setting the useLastCommittedRevision parameter in my project's maven pom file, and run the "create" goal, the value will be passed to the field useLastCommittedRevision in the class CreateMojo. The value is correct until before calling the method getScmRevision() in the class CreateMojo. But once it enters the getScmRevision() method which is in the AbstractScmMojo class, the value useLastCommittedRevision is overwritten to the default value as false.

I think because in the class AbstractScmMojo, the same parameter is defined as below and it has the problem.

@Parameter( property = "maven.buildNumber.useLastCommittedRevision", defaultValue = "false" )
private boolean useLastCommittedRevision;

Proposed fix is to remove the parameter definition from CreateMojo, since this parameter useLastCommittedRevision is not used in CreateMojo but only used in AbstractScmMojo.

http://www.mojohaus.org/ cannot be opened in China (without VPN)

http://www.mojohaus.org/ cannot be opened in China (without VPN)

Make the site simple deployable

maven-scm-publish-plugin

native-maven-plugin unavailable on GitHub

Dear mojohaus Team,

According to page :
http://www.mojohaus.org/maven-native/native-maven-plugin/source-repository.html

The corresponding GIT repository is not (yet ?) available on GitHub :
https://github.com/mojohaus/maven-native/native-maven-plugin

Regards,

Plugin submission - reusable ide preferences

Hi,

I'd prepared a submission for a new Maven plugin that allows simple management of IDE preferences by deploying them as Maven artifacts and allowing them to be applied using Maven goals.

I've previously posted on the dev mailing list - https://groups.google.com/forum/#!topic/mojohaus-dev/EhFkWJ8V-rc .

The plug-in source code is attached. It is licensed to MojoHaus under the Apache License 2.0 .

reusable-ide-preferences.zip

Using Google CDN makes page load for 2+ minutes in China

Using Google make page load for 2+ minutes in China

This is of course, issue of site plugin. Cat you point to the exact location?

Create favicon.ico for MojoHaus

Source logo:

src/site/resources/images/mojo_logo-new.png

Maven plugin links are broken

Trying to follow links from http://www.mojohaus.org/plugins.html leads to a 404

migrate check to github-actions

Check KEYS file format

The current CI workflow does not check the validity of the keys.

null (org.codehaus.mojo:jaxb2-maven-plugin:2.2:xjc:xjc:generate-sources)

I have the below in the pom.xml, but getting an error in the line of "execution" -

null (org.codehaus.mojo:jaxb2-maven-plugin:2.2:xjc:xjc:generate-sources) org.apache.maven.plugin.MojoExecutionException at
org.codehaus.mojo.jaxb2.javageneration.AbstractJavaGeneratorMojo.performExecution(AbstractJavaGeneratorMojo.java:482) at

org.codehaus.mojo jaxb2-maven-plugin 2.2 xjc xjc ${project.basedir}/src/main/resources/xsd ${project.basedir}/src/main/java false com.domain.test src/main/resources/xsd/POSSvcsSchemaPOSInstallApptStatusSchema.xsd

Prepare - Guide to Testing Development Versions of Plugins

Similar for https://maven.apache.org/guides/development/guide-testing-development-plugins.html
but dedicated for MojoHaus projects

xmlbeans-maven-plugin is not compatible with latest xmlbeans version 5.0.3

I want to upgrade xmlbeans to latest available version 5.0.3. But when I am trying to generate the source from xsd files using this plugin. I am getting below error:

..\xml-model\target\generated-sources\xmlbeans\com\metasolv\oms\orderModel\x2002\x06\x25\SystemHealthPoliciesType.java:144: error: cannot find symbol public static com.metasolv.oms.orderModel.x2002.x06.x25.SystemHealthPoliciesType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException { ^ symbol: class XMLInputStream location: package org.apache.xmlbeans.xml.stream

Is there any other compatible version of this plugin available to achieve this? Or, is there some other plugin altogether to generate the sources.

remove dead link "API signatures"

Probably a link to the animal sniffer plugin, which has its own menu item.

Remove hard-coded version info from plugins page

Very often I find that the (latest) version info on the plugins page is incorrect. This is because it's a manual task part of the release process, which is easily forgotten.
I suggest that we remove this hard-coded info on this page. (The latest version info can be found in the mojo's github repo or by searching central.)

TLS on mojohaus.org

Hi there,

I look after the @OWASP Top 10, and we want to link to Versions in our standard (it's currently in A9:2017 Known Vulnerabilities). As part of OWASP's commitment to securing the Internet, there will not be any unencrypted links in the OWASP Top 10 going forward.

Unfortunately, your TLS configuration is not functional for this link:

https://www.mojohaus.org/versions-maven-plugin/

Your current TLS configuration status:
https://www.ssllabs.com/ssltest/analyze.html?d=www.mojohaus.org&hideResults=on&latest

The OWASP Top 10 has until November 13 to fix any broken links. Do you think you could have a go at fixing the TLS certificate on your site? This will also help with folks using your plugin trust the data it receives from your tool as well.

I'd strongly suggest your site is only reachable by encrypted means (certbot does this) for all your domains, because version dependency checks are critical to the safety of the Internet at large. If someone can inject a URL for a trojaned dependency in a response from your servers, attackers can run arbitrary code on victim servers. It's critical that projects such as yourselves, Maven, and so on are only reachable via TLS.

<build> should have closing tag as </build>

Hi Team,

A forward slash is missing in example xml file. Please click the below link
http://www.mojohaus.org/jaxb2-maven-plugin/Documentation/v2.2/example_xjc_basic.html

go to "Example 1: Generate Java code within provided package",
The close tag of should be

with regards
Jaswanth Reddy

Update the plugins page to reflect the plugins actually moved

The plugins listing on the MojoHaus plugins page contains quite a few plugins which have not been moved to MojoHaus.

I will wait for a few days and then simply restructure the page to reflect updated/current reality.

We do not use SVN anymore, remove all mentions