Rapid portlet development with Pluto and Maven

[Johannes Lehtinen <jo...@iki.fi>]

Hi! I am new to this mailing list but I have used Apache Pluto for some
time as the portal platform when developing and prototyping generic Java
portlets. I have been searching for an easy way to run portlets in a
Pluto portal during the development phase and decided to share my
thoughts and work on this mailing list in case others are interested or
can suggest better solutions.


Some time ago I was looking for an easy and a convenient way to
prototype and run generic Java portlets being developed in a Maven based
software project. Apache Pluto seemed like the portal platform to use
but the Maven integration solutions I found were outdated or not very
convenient.

I wanted to have a Maven plugin that can be used to run the portlet or
portlets being developed in a Pluto portal. The portlets should be run
directly from the Maven project source so that JSP files and other
portlet content could be edited on-the-fly without having to redeploy
the portlet after simple user interface modifications.

Therefore I implemented some simple Portlet Tools for Maven [1] to make
it easier to prototype portlets in a Pluto portal when using Maven for
build management.

[1] http://www.jlehtinen.net/portlet-tools/

This was just my initial attempt at solving the problem so the plugin is
not yet available from the central repository.


Please let me know if there are better ways to solve the same problem.

The idea behind these tools was copied from the
"maven-jetty-pluto-embedded" Maven plugin [2]. However, the problem with
this plugin was that due to conflicting dependencies, I could not run
Pluto in the same web application as my own application. I also wanted
to have a tool that would be less invasive and more automated from
pom.xml perspective.

[2] http://bekkopensource.lighthouseapp.com/projects/22517/home


Best regards, Johannes

-- 
Johannes Lehtinen <jo...@iki.fi>

Re: Rapid portlet development with Pluto and Maven

[David Sean Taylor <d....@onehippo.com>]

I think that the Jetty plugin is limited to one web application. If
you are having class loader conflicts with Pluto and your portlet
application, its probably best to use Tomcat. I haven't seen any
tomcat plugins for maven, but I did find this discussion at stack
overflow, might be a starting point:

http://stackoverflow.com/questions/640022/howto-embed-tomcat-6

Also, just thinking out loud, it might be interesting to host a
portlet-tools project here at Apache Portals....

On Sun, Apr 25, 2010 at 12:10 AM, Johannes Lehtinen
<jo...@iki.fi> wrote:
> Hi! I am new to this mailing list but I have used Apache Pluto for some
> time as the portal platform when developing and prototyping generic Java
> portlets. I have been searching for an easy way to run portlets in a
> Pluto portal during the development phase and decided to share my
> thoughts and work on this mailing list in case others are interested or
> can suggest better solutions.
>
>
> Some time ago I was looking for an easy and a convenient way to
> prototype and run generic Java portlets being developed in a Maven based
> software project. Apache Pluto seemed like the portal platform to use
> but the Maven integration solutions I found were outdated or not very
> convenient.
>
> I wanted to have a Maven plugin that can be used to run the portlet or
> portlets being developed in a Pluto portal. The portlets should be run
> directly from the Maven project source so that JSP files and other
> portlet content could be edited on-the-fly without having to redeploy
> the portlet after simple user interface modifications.
>
> Therefore I implemented some simple Portlet Tools for Maven [1] to make
> it easier to prototype portlets in a Pluto portal when using Maven for
> build management.
>
> [1] http://www.jlehtinen.net/portlet-tools/
>
> This was just my initial attempt at solving the problem so the plugin is
> not yet available from the central repository.
>
>
> Please let me know if there are better ways to solve the same problem.
>
> The idea behind these tools was copied from the
> "maven-jetty-pluto-embedded" Maven plugin [2]. However, the problem with
> this plugin was that due to conflicting dependencies, I could not run
> Pluto in the same web application as my own application. I also wanted
> to have a tool that would be less invasive and more automated from
> pom.xml perspective.
>
> [2] http://bekkopensource.lighthouseapp.com/projects/22517/home
>
>
> Best regards, Johannes
>
> --
> Johannes Lehtinen <jo...@iki.fi>
>