You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2006/09/10 02:06:22 UTC
[jira] Created: (PLUTO-257) Pluto 1.1 plugin for the deployment of
custom portlets does not work
Pluto 1.1 plugin for the deployment of custom portlets does not work
--------------------------------------------------------------------
Key: PLUTO-257
URL: http://issues.apache.org/jira/browse/PLUTO-257
Project: Pluto
Issue Type: Bug
Components: deployer
Affects Versions: 1.1.0-beta1
Reporter: Craig Doremus
Fix For: 1.1.0
Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (PLUTO-257) Pluto 1.1 plugin for the deployment
of custom portlets does not work
Posted by "David H. DeWolf" <dd...@apache.org>.
can you add details as to what does not work / stack traces, etc. . .
Thanks.
David
Craig Doremus (JIRA) wrote:
> Pluto 1.1 plugin for the deployment of custom portlets does not work
> --------------------------------------------------------------------
>
> Key: PLUTO-257
> URL: http://issues.apache.org/jira/browse/PLUTO-257
> Project: Pluto
> Issue Type: Bug
> Components: deployer
> Affects Versions: 1.1.0-beta1
> Reporter: Craig Doremus
> Fix For: 1.1.0
>
>
> Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
>
[jira] Commented: (PLUTO-257) Pluto 1.1 plugin for the deployment
of custom portlets does not work
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-257?page=comments#action_12458341 ]
David DeWolf commented on PLUTO-257:
------------------------------------
The publish is no longer needed and can simply be removed.
> Pluto 1.1 plugin for the deployment of custom portlets does not work
> --------------------------------------------------------------------
>
> Key: PLUTO-257
> URL: http://issues.apache.org/jira/browse/PLUTO-257
> Project: Pluto
> Issue Type: Bug
> Components: deployer
> Affects Versions: 1.1.0-beta1
> Reporter: Craig Doremus
> Fix For: 1.1.0
>
>
> Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (PLUTO-257) Pluto 1.1 plugin for the deployment of
custom portlets does not work
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-257?page=all ]
David DeWolf resolved PLUTO-257.
--------------------------------
Resolution: Fixed
Removed both.
> Pluto 1.1 plugin for the deployment of custom portlets does not work
> --------------------------------------------------------------------
>
> Key: PLUTO-257
> URL: http://issues.apache.org/jira/browse/PLUTO-257
> Project: Pluto
> Issue Type: Bug
> Components: deployer
> Affects Versions: 1.1.0-beta1
> Reporter: Craig Doremus
> Fix For: 1.1.0
>
>
> Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-257) Pluto 1.1 plugin for the deployment
of custom portlets does not work
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-257?page=comments#action_12458346 ]
David DeWolf commented on PLUTO-257:
------------------------------------
Now that we don't require publishing, we should not duplicate deployment facilities for all app servers. The only plugin and/or ant task we should provide is the assembly one. That's pluto specific - deployment is app server specific and has been implemented by other plugins.
> Pluto 1.1 plugin for the deployment of custom portlets does not work
> --------------------------------------------------------------------
>
> Key: PLUTO-257
> URL: http://issues.apache.org/jira/browse/PLUTO-257
> Project: Pluto
> Issue Type: Bug
> Components: deployer
> Affects Versions: 1.1.0-beta1
> Reporter: Craig Doremus
> Fix For: 1.1.0
>
>
> Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-257) Pluto 1.1 plugin for the deployment
of custom portlets does not work
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-257?page=comments#action_12433703 ]
Craig Doremus commented on PLUTO-257:
-------------------------------------
Here are runs of the pluto:deploy and pluto:publish goals with error stacktraces turned on.
Run of pluto:deploy goal:
C:\eclipse32-workspace\HelloWorldPortlet>mvn -e pluto:deploy -DinstallDir=c:\plu
to-1.1.0-SNAPSHOT
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'pluto'.
[INFO] -------------------------------------------------------------------------
---
[INFO] Building HelloWorldPortlet
[INFO] task-segment: [pluto:deploy]
[INFO] -------------------------------------------------------------------------
---
Downloading: http://repo1.maven.org/maven2/castor/castor/1.0/castor-1.0.pom
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] [pluto:deploy]
installationDirectory: c:\pluto-1.1.0-SNAPSHOT
deployment: C:\eclipse32-workspace\HelloWorldPortlet\target\null.war
DeployerClass: org.apache.pluto.util.deploy.file.Tomcat5FileSystemDeployer
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Deployment must be specified.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Deployment must be speci
fied.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Deployment must be sp
ecified.
at org.apache.pluto.maven.DeployMojo.doValidate(DeployMojo.java:72)
at org.apache.pluto.maven.AbstractPlutoMojo.execute(AbstractPlutoMojo.ja
va:46)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 16 more
Run of pluto:publish
C:\eclipse32-workspace\HelloWorldPortlet>mvn -e pluto:publish -DinstallDir=c:\pl
uto-1.1.0-SNAPSHOT
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'pluto'.
[INFO] -------------------------------------------------------------------------
---
[INFO] Building HelloWorldPortlet
[INFO] task-segment: [pluto:publish]
[INFO] -------------------------------------------------------------------------
---
Downloading: http://repo1.maven.org/maven2/castor/castor/1.0/castor-1.0.pom
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] [pluto:publish]
/pluto/admin/Publish?context=HelloWorldPortlet
Sep 10, 2006 9:05:58 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request:
Connection refused: connect
Sep 10, 2006 9:05:58 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: Retrying request
Sep 10, 2006 9:05:59 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request:
Connection refused: connect
Sep 10, 2006 9:05:59 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: Retrying request
Sep 10, 2006 9:06:00 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request:
Connection refused: connect
Sep 10, 2006 9:06:00 AM org.apache.commons.httpclient.HttpMethodDirector execute
WithRetry
INFO: Retrying request
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to publish. Connection refused: connect
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to publish. Conne
ction refused: connect
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to publish. Co
nnection refused: connect
at org.apache.pluto.maven.PublishMojo.execute(PublishMojo.java:96)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Sun Sep 10 09:06:01 EDT 2006
[INFO] Final Memory: 3M/7M
[INFO] ------------------------------------------------------------------------
> Pluto 1.1 plugin for the deployment of custom portlets does not work
> --------------------------------------------------------------------
>
> Key: PLUTO-257
> URL: http://issues.apache.org/jira/browse/PLUTO-257
> Project: Pluto
> Issue Type: Bug
> Components: deployer
> Affects Versions: 1.1.0-beta1
> Reporter: Craig Doremus
> Fix For: 1.1.0
>
>
> Deployment of custom portlets using the Pluto 1.1 plugin does not work. This includes the pluto:deploy (DeployMojo) and pluto:publish (PublishMojo) goals.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira