portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohnny Moland (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-357) Problems installing a newly generated portal using the js2 maven plugin
Date Mon, 05 Sep 2005 08:55:34 GMT
    [ http://issues.apache.org/jira/browse/JS2-357?page=comments#action_12322642 ] 

Rohnny Moland commented on JS2-357:

One more js2 maven plugin issue:
The js2:deploy goal should be generalized to also support deployment of 3rd party portlets.

That is: Should not use properties like jetspeed.version and plugin.groupId, but rather pom.currentVersion
and pom.groupId. (Or add new properties to allow overriding).

> Problems installing a newly generated portal using the js2 maven plugin
> -----------------------------------------------------------------------
>          Key: JS2-357
>          URL: http://issues.apache.org/jira/browse/JS2-357
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Other
>     Versions: 2.0-M4
>  Environment: SuSE 9.3, tomcat 5.5.9, JS2 head
>     Reporter: Rohnny Moland

> The project.xml files created after running the j2:portal.genapp goal should include
all files that have been generated, and which needs to be included in the portal.war file.
> Now, when I run the war:install goal in my new portal home directory, the portal.war
 only includes the jar files and not my webapp directory. Everything in webapp must be included
and also the properties files under WEB-INF/classes. If I copy the files manually it works,
of course.
> Using svn head.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message