[
http://jira.codehaus.org/browse/MWAS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MWAS-52:
------------------------------------
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
Good catch - I didn't notice the differences when implementing this as the
mojos pretty much reflect the ant tasks - and they have inconsistent attribute
naming:
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.wasee.doc/info/ee/javadoc/ae/com/ibm/websphere/ant/tasks/package-tree.html
Should be able to abstract this in the mojos and map them to either user or
username depending on the task at hand.
I'll try to fix this in the next release by consistently naming the element
"username" in the mojo (and probably support the old element as well, but
deprecate it.
> WsAdminMojo does not work on a secured connection.
> --------------------------------------------------
>
> Key: MWAS-52
> URL: http://jira.codehaus.org/browse/MWAS-52
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: WAS 7.0 standalone server / Windows 32 bits.
> Reporter: Ronald van de Kuil
> Assignee: David J. M. Karlsen
> Fix For: 1.2
>
> Attachments: pom.xml, secured_run.txt, unsecured_run.txt
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I ran the attached pom succesfully on an unsecured WAS 7.0 server.
> The POM runs a jython script, uninstalls an EAR, installs it again and runs
> the jython script again. This works on WAS 7.0.
> Once I secure the server the WsAdminMojo fails. The WsUninstallAppMojo and
> WsInstallAppMojo work.
> The jython script is not special at this moment yet: it prints "hello world"
> to the console.
> I have attached the following files:
> - secured_run.txt - a run on a secured connection;
> - unsecured_run.txt - a run on a unsecured connection;
> - pom.xml - my pom;
> I´d like to run the jython script on a secured server to modify application
> scoped resources. This will allow us to run a nightly build, deploy,
> configire and jmeter test from maven.
> I ran the pom in debug mode and I discovered that the user is null when it
> hits the WsAdminMojo. The other variables like password, host and so on are
> set.
> I will see what I can do to set the user in the WsAdminMojo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
