[jira] [Commented] (MPLUGINTESTING-57) plugin.xml is needed
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440543#comment-16440543 ] Gerrit Hohl commented on MPLUGINTESTING-57: --- Thanks, will try that. > plugin.xml is needed > > > Key: MPLUGINTESTING-57 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-57 > Project: Maven Plugin Testing > Issue Type: Improvement > Components: plugin-testing-harness >Affects Versions: 3.3.0 >Reporter: Gerrit Hohl >Priority: Major > > For the test being executable the plugin.xml created by the > maven-plugin-plugin is needed. But this plugin only runs during the build > time of the Maven project of your plugin. If I use e.g. Eclipse and JUnit I > don't have this file. But I guess it should be possible to get all the needed > information also during runtime of the test as the maven-plugin-plugin also > doesn't have any extra sources beside the Mojo and its annotations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPLUGINTESTING-56) @Parameter is ignored
[
https://issues.apache.org/jira/browse/MPLUGINTESTING-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440538#comment-16440538
]
Gerrit Hohl commented on MPLUGINTESTING-56:
---
Have to look for the plugin.xml as I'm already working on a different project.
I'm aware that the test suite doesn't directly evaluate the Maven annotations,
but the plugin.xml. But last week I dug into the code a little bit and had to
realize, that the test suite does need the plugin.xml, but the parameters are
injected purely by Java reflection. It doesn't care for any information of the
plugin.xml in aspect of parameters.
> @Parameter is ignored
> -
>
> Key: MPLUGINTESTING-56
> URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-56
> Project: Maven Plugin Testing
> Issue Type: Bug
> Components: plugin-testing-harness
>Affects Versions: 3.3.0
>Reporter: Gerrit Hohl
>Priority: Major
>
> I tried to test a Mojo which had the following property (example):
> {{@Parameter(name="hardDiskDrive")}}
> {{private String hdd;}}
> The test couldn't find the parameter always saying that there is no
> "hardDiskDrive" parameter:
> {{org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Cannot find 'hardDiskDrive' in class test.example.MyMojo}}
> {{ at
> org.eclipse.sisu.plexus.CompositeBeanHelper.setProperty(CompositeBeanHelper.java:252)}}
> {{ at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:101)}}
> {{ at
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:34)}}
> {{ at
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:44)}}
> {{ at
> org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupConfiguredMojo(AbstractMojoTestCase.java:484)}}
> {{ at
> org.apache.maven.plugin.testing.MojoRule.lookupConfiguredMojo(MojoRule.java:197)}}
> {{ [...]}}
> The same applies also to the required option of the @Parameter annotation. It
> also is totally ignored and you'll get a NullPointerException somewhere in
> your code instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MPLUGINTESTING-57) plugin.xml is needed
Gerrit Hohl created MPLUGINTESTING-57: - Summary: plugin.xml is needed Key: MPLUGINTESTING-57 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-57 Project: Maven Plugin Testing Issue Type: Improvement Components: plugin-testing-harness Affects Versions: 3.3.0 Reporter: Gerrit Hohl For the test being executable the plugin.xml created by the maven-plugin-plugin is needed. But this plugin only runs during the build time of the Maven project of your plugin. If I use e.g. Eclipse and JUnit I don't have this file. But I guess it should be possible to get all the needed information also during runtime of the test as the maven-plugin-plugin also doesn't have any extra sources beside the Mojo and its annotations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPLUGINTESTING-56) @Parameter is ignored
Gerrit Hohl created MPLUGINTESTING-56:
-
Summary: @Parameter is ignored
Key: MPLUGINTESTING-56
URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-56
Project: Maven Plugin Testing
Issue Type: Bug
Components: plugin-testing-harness
Affects Versions: 3.3.0
Reporter: Gerrit Hohl
I tried to test a Mojo which had the following property (example):
{{@Parameter(name="hardDiskDrive")}}
{{private String hdd;}}
The test couldn't find the parameter always saying that there is no
"hardDiskDrive" parameter:
{{org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot find 'hardDiskDrive' in class test.example.MyMojo}}
{{ at
org.eclipse.sisu.plexus.CompositeBeanHelper.setProperty(CompositeBeanHelper.java:252)}}
{{ at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:101)}}
{{ at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:34)}}
{{ at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:44)}}
{{ at
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupConfiguredMojo(AbstractMojoTestCase.java:484)}}
{{ at
org.apache.maven.plugin.testing.MojoRule.lookupConfiguredMojo(MojoRule.java:197)}}
{{ [...]}}
The same applies also to the required option of the @Parameter annotation. It
also is totally ignored and you'll get a NullPointerException somewhere in your
code instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WAGON-415) wagon-ssh doesn't load known_hosts from Jenkins home directory
[ https://issues.apache.org/jira/browse/WAGON-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136408#comment-16136408 ] Gerrit Hohl commented on WAGON-415: --- I'm sorry as I haven't given any response yet. But in the meantime I worked on other projects. And it also seems that I won't have time for testing it in the near future. I'm really sorry about this. Seems that in the meantime even maven-wagon v3.0.0 was released. > wagon-ssh doesn't load known_hosts from Jenkins home directory > -- > > Key: WAGON-415 > URL: https://issues.apache.org/jira/browse/WAGON-415 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 2.6 > Environment: Windows Server 2008 R2 Standard > Apache Tomcat 7.0.26 Server > Jenkins v1.527 > Maven 3.0.4 > maven-site-plugin 3.3 > wagon-ssh 2.6 >Reporter: Gerrit Hohl > > For some people this might be only an improvement, for myself it is a bug. > I'm trying to do a site-deploy using wagon-ssh. I have configured the server > including the username and password in the settings.xml of Maven. > If I try this locally Maven asks me if I want to continue establishing the > connection showing me the RSA key fingerprint of the server. If I agree by > typing 'yes' it creates the file C:\Users\[MY-USER]\.ssh\known_hosts and > doesn't ask me ever again. > But if I try this using Jenkins I can't accept the RSA key fingerprint as > there is no interactive mode. I thought I could copy (or create) the > known_hosts file on the server. I tried doing this in > [JENKINS-HOME]\.ssh\known_hosts, but it didn't work. > Then I tried to run Maven in the verbose mode (-X / --debug). I got a huge > log file, but I don't see any path in which wagon-ssh expects the > known_hosts_file also here. But without that I don't know how I should > determine where to put. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WAGON-415) wagon-ssh doesn't load known_hosts from Jenkins home directory
[ https://issues.apache.org/jira/browse/WAGON-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692540#comment-15692540 ] Gerrit Hohl commented on WAGON-415: --- Thanks Dan. https://issues.apache.org/jira/browse/WAGON-467 If I understand it correctly that fix / workaround will be available in version 2.11. https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven.wagon%22%20AND%20a%3A%22wagon-ssh%22 Do you know when that version will be available? The current version is still 2.10 (09-Sep-2015). > wagon-ssh doesn't load known_hosts from Jenkins home directory > -- > > Key: WAGON-415 > URL: https://issues.apache.org/jira/browse/WAGON-415 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 2.6 > Environment: Windows Server 2008 R2 Standard > Apache Tomcat 7.0.26 Server > Jenkins v1.527 > Maven 3.0.4 > maven-site-plugin 3.3 > wagon-ssh 2.6 >Reporter: Gerrit Hohl > > For some people this might be only an improvement, for myself it is a bug. > I'm trying to do a site-deploy using wagon-ssh. I have configured the server > including the username and password in the settings.xml of Maven. > If I try this locally Maven asks me if I want to continue establishing the > connection showing me the RSA key fingerprint of the server. If I agree by > typing 'yes' it creates the file C:\Users\[MY-USER]\.ssh\known_hosts and > doesn't ask me ever again. > But if I try this using Jenkins I can't accept the RSA key fingerprint as > there is no interactive mode. I thought I could copy (or create) the > known_hosts file on the server. I tried doing this in > [JENKINS-HOME]\.ssh\known_hosts, but it didn't work. > Then I tried to run Maven in the verbose mode (-X / --debug). I got a huge > log file, but I don't see any path in which wagon-ssh expects the > known_hosts_file also here. But without that I don't know how I should > determine where to put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WAGON-415) wagon-ssh doesn't load known_hosts from Jenkins home directory
[
https://issues.apache.org/jira/browse/WAGON-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519133#comment-14519133
]
Gerrit Hohl commented on WAGON-415:
---
Roland Hauser mailed me the following workaround this Monday:
{quote}
Hi Gerrit
Please update your task with a comment referencing following link:
http://www.inqa.be/en/content/jenkins-authenticity-host-cant-be-established
You'll find an article how to work around the connection issue:
There is a maven issue which prevents the deployment of a maven site with
Ubuntu LTS 12. By default ECDSA keys are stored in the known_hosts file. When
scp'ing files from the jenkins account, using wagon-ssh, the build hangs with
The authenticity of host hostname can't be established.
The reason for this problem is the EDCSA entry in the known_hosts file. For
now, maven apparently requires a ssh-rsa entry. You can obtain the ssh-rsa
entry by issuing
ssh-keyscan -t rsa hostname known_hosts
Regards,
Roland
{quote}
I have to admit that I haven't tested it yet. And it's only a workaround, not a
real solution (at least in my opinion). The error message should be improved
and non-RSA keys supported.
wagon-ssh doesn't load known_hosts from Jenkins home directory
--
Key: WAGON-415
URL: https://issues.apache.org/jira/browse/WAGON-415
Project: Maven Wagon
Issue Type: Bug
Components: wagon-ssh
Affects Versions: 2.6
Environment: Windows Server 2008 R2 Standard
Apache Tomcat 7.0.26 Server
Jenkins v1.527
Maven 3.0.4
maven-site-plugin 3.3
wagon-ssh 2.6
Reporter: Gerrit Hohl
For some people this might be only an improvement, for myself it is a bug.
I'm trying to do a site-deploy using wagon-ssh. I have configured the server
including the username and password in the settings.xml of Maven.
If I try this locally Maven asks me if I want to continue establishing the
connection showing me the RSA key fingerprint of the server. If I agree by
typing 'yes' it creates the file C:\Users\[MY-USER]\.ssh\known_hosts and
doesn't ask me ever again.
But if I try this using Jenkins I can't accept the RSA key fingerprint as
there is no interactive mode. I thought I could copy (or create) the
known_hosts file on the server. I tried doing this in
[JENKINS-HOME]\.ssh\known_hosts, but it didn't work.
Then I tried to run Maven in the verbose mode (-X / --debug). I got a huge
log file, but I don't see any path in which wagon-ssh expects the
known_hosts_file also here. But without that I don't know how I should
determine where to put.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] (WAGON-415) wagon-ssh doesn't load known_hosts from Jenkins home directory
Gerrit Hohl created WAGON-415: - Summary: wagon-ssh doesn't load known_hosts from Jenkins home directory Key: WAGON-415 URL: https://jira.codehaus.org/browse/WAGON-415 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 2.6 Environment: Windows Server 2008 R2 Standard Apache Tomcat 7.0.26 Server Jenkins v1.527 Maven 3.0.4 maven-site-plugin 3.3 wagon-ssh 2.6 Reporter: Gerrit Hohl For some people this might be only an improvement, for myself it is a bug. I'm trying to do a site-deploy using wagon-ssh. I have configured the server including the username and password in the settings.xml of Maven. If I try this locally Maven asks me if I want to continue establishing the connection showing me the RSA key fingerprint of the server. If I agree by typing 'yes' it creates the file C:\Users\[MY-USER]\.ssh\known_hosts and doesn't ask me ever again. But if I try this using Jenkins I can't accept the RSA key fingerprint as there is no interactive mode. I thought I could copy (or create) the known_hosts file on the server. I tried doing this in [JENKINS-HOME]\.ssh\known_hosts, but it didn't work. Then I tried to run Maven in the verbose mode (-X / --debug). I got a huge log file, but I don't see any path in which wagon-ssh expects the known_hosts_file also here. But without that I don't know how I should determine where to put. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-415) wagon-ssh doesn't load known_hosts from Jenkins home directory
[ https://jira.codehaus.org/browse/WAGON-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348667#comment-348667 ] Gerrit Hohl commented on WAGON-415: --- Here the part of the log: INFO: --- maven-site-plugin:3.3:deploy (default-deploy) @ webfox-pom --- [DEBUG] Configuring mojo org.apache.maven.plugins:maven-site-plugin:3.3:deploy from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-site-plugin:3.3, parent: sun.misc.Launcher$AppClassLoader@8244f74] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-site-plugin:3.3:deploy' with basic configurator -- [DEBUG] (f) chmod = true [DEBUG] (f) chmodMode = g+w,a+rX [DEBUG] (f) chmodOptions = -Rf [DEBUG] (f) inputDirectory = c:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\target\site [DEBUG] (f) inputEncoding = UTF-8 [DEBUG] (f) localRepository =id: local url: file:///C:/Java/Maven/.m2/repository/ layout: none [DEBUG] (f) locales = en [DEBUG] (f) reactorProjects = [MavenProject: de.aurenz.webfox:webfox-pom:4.6.0 @ c:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-component:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-component\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-util:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-util\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-i18n:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-i18n\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-logging:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-logging\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-net:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-net\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-persistence:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-persistence\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-auth:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-auth\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-security:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-security\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-directoryservice:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-directoryservice\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-auth-directoryservice:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-auth-directoryservice\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-auth-proxyauth:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-auth-proxyauth\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-lifecycle:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-lifecycle\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-protocol:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-protocol\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-servlet:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-servlet\pom.xml, MavenProject: de.aurenz.webfox:aurenz-commons-struts1:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\aurenz-commons-struts1\pom.xml, MavenProject: de.aurenz.webfox:webfox-commons-debug:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-commons-debug\pom.xml, MavenProject: de.aurenz.webfox:webfox-commons:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-commons\pom.xml, MavenProject: de.aurenz.webfox:webfox-core:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-core\pom.xml, MavenProject: de.aurenz.webfox:webfox-install-tool:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-install-tool\pom.xml, MavenProject: de.aurenz.webfox:webfox-installer:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-installer\pom.xml, MavenProject: de.aurenz.webfox:webfox-proxy-api:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-proxy-api\pom.xml, MavenProject: de.aurenz.webfox:webfox-server:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-server\pom.xml, MavenProject: de.aurenz.webfox:webfox-cold-cases:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-cold-cases\pom.xml, MavenProject: de.aurenz.webfox:webfox-web:4.6.0 @ C:\jenkins_data\workspace\WebFox-4.6-00-POM-Nightly\webfox-pom\webfox-web\pom.xml] [DEBUG] (f) siteDirectory =
