most straightforward and least error prone) is to just fire up Jetty to
> serve files from somewhere as "remote repository" as in that case you are
> 100% in control of what is being served, while with MRM you are not.
>
> HTH
> Tamas
>
>
> On Fri, Jun 23, 2023 at 5:20 PM B
ol of what is being served, while with MRM you are not.
HTH
Tamas
On Fri, Jun 23, 2023 at 5:20 PM Basil Crow wrote:
> I recently attempted to modernize the HPI plugin used in the Jenkins
> project:
>
> https://github.com/jenkinsci/maven-hpi-plugin
>
> This plugin has a Maven baseline
Basil,
I am a Maven committer. If you want to have replies from specific persons,
don't use the developer mailing list. There is no such role as a core
committer. There's only the PMC, which are not necessarily the most active
committers.
To be honest, I don't think "core" committers will give
Hi Benjamin,
Sorry for the confusion, but my question was directed to the Maven
core committers.
Basil
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hello Basil,
I wrote the mail while the ITs were running.
Please note the naming issue is not "minor". It will break the build very
soon.
There's a reason for this:
SEE:
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html
QUOTE:
You will typically name your plugin
Hi Ben,
While the Jenkins project would likely accept patches fixing those
issues, they seem to be of very low priority. If you discover any
issues of substance that ought to be fixed, please let me know.
Basil
-
To
Hi Basil,
the first issue I see when using Maven 3.9.2:
[INFO] --- plugin:3.9.0:descriptor (default-descriptor) @ maven-hpi-plugin ---
[WARNING]
Artifact Ids of the format maven-___-plugin are reserved for
plugins in the Group Id org.apache.maven.plugins
Please change your artifactId
I recently attempted to modernize the HPI plugin used in the Jenkins project:
https://github.com/jenkinsci/maven-hpi-plugin
This plugin has a Maven baseline of 3.8.1. I think I migrated all
usages away from deprecated functionality and onto the recommended
modern Maven functionality.
If a Maven
plugins
plugin
groupIdorg.jvnet.hudson.tools/groupId
artifactIdmaven-hpi-plugin/artifactId
extensionstrue/extensions
configuration
disabledTestInjectiontrue/disabledTestInjection
/configuration
Andrew Harmel-Law wrote:
I am having the exact same problem, having just upgraded my plugin to 1.327.
However, because the file with the illegal escape characters is being auto
generated, I cannot escape them.
As far as I understand, the file is generated by the maven-hpi-plugin,
so
Hi guys,
I was using hpi-plugin version 1.37, and it was working well. And no,
for no special reason, I guess only for evolution and be cool, I tried
to use the latest versions 1.45. I had the following error using the
command clean package hpi:run in eclipse :
[INFO] Scanning for projects
Hi
You need to escape your windows paths with back slashes in java that
is c:\\myfolder\\a and not c:\myfolder\a
On 15/10/2009, Croteau, Jean-Francois j.crot...@cgi.com wrote:
Hi guys,
I was using hpi-plugin version 1.37, and it was working well. And no,
for no special reason, I guess only
12 matches
Mail list logo
