portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-357) Problems installing a newly generated portal using the js2 maven plugin
Date Tue, 06 Sep 2005 01:32:32 GMT
     [ http://issues.apache.org/jira/browse/JS2-357?page=all ]
     
Ate Douma resolved JS2-357:
---------------------------

    Fix Version: 2.0-M4
     Resolution: Invalid

Your first problem is not valid I think.
If you setup your custom portal project directory structure according to what the maven war
plugin expects, your own code and resources will be
included in the final portal war.
Jetspeed-2 itself uses war:install to include its portal war contents when you call the allBuild
goal (checkout the maven.xml in the project root).
If you need additional project.xml configuration (like non-default java src or resource paths)
you should modify the generated project.xml
The j2:portal.genapp goal *won't* overwrite the project.xml if it already exists, so your
changes will be safe.

While the j2:deploy goal *could* be extended to support 3rd party portlet apps, I'm not inclined
to do so. 
Using the ${pom.groupId} from the generated project.xml would break it if it isn't "jetspeed2"
for the standard j2 portlet apps.
And you can easily provide your own maven.xml with a custom deploy goal for deploying your
own 3rd party apps
(simply copy them to ${org.apache.jetspeed.deploy.war.dir}/${org.apache.jetspeed.portal.artifactId}/WEB-INF/deploy/).


> 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
>      Fix For: 2.0-M4

>
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message