Hi Team,
By downloading settings.xml manually I could able to run this successfully.
I got project with two sub modules, can you tell me how can we take these and
use in other IDEs (like jdeveloper)as existing modules.
Regards,
Lalitha
-----Original Message-----
From: Lalitha Bourishetty
Sent: Thursday, June 11, 2015 2:26 PM
To: Jetspeed Developers List
Subject: RE: Regarding Jetspeed migration
Hi Team,
When we try to run this
mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate \
-DarchetypeGroupId=org.apache.portals.jetspeed-2 \
-DarchetypeArtifactId=jetspeed-archetype \
-DarchetypeVersion=2.2.2 \
-DartifactId=jetexpress \
-Dpackage=org.apache.portals.tutorials \
-DgroupId=org.apache.portals.tutorials \
-Dversion=1.0-SNAPSHOT
We are facing build failure error. Please find the attached screenshot of error.
Please let me know if you have any clue how this can be resolved.
Regards,
Lalitha
-----Original Message-----
From: DavidSeanTaylor [mailto:[email protected]]
Sent: Wednesday, June 10, 2015 8:02 PM
To: Jetspeed Developers List
Subject: Re: Regarding Jetspeed migration
> When we use eclipse IDE how should we create these folders?
The folders are created with a Maven archetype as described here (the first
step of the tutorial):
https://portals.apache.org/jetspeed-2/tutorial/01/genapp.html
<https://portals.apache.org/jetspeed-2/tutorial/01/genapp.html>
mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate \
-DarchetypeGroupId=org.apache.portals.jetspeed-2 \
-DarchetypeArtifactId=jetspeed-archetype \
-DarchetypeVersion=2.2.2 \
-DartifactId=jetexpress \
-Dpackage=org.apache.portals.tutorials \
-DgroupId=org.apache.portals.tutorials \
-Dversion=1.0-SNAPSHOT
> On Jun 10, 2015, at 3:40 AM, Lalitha Bourishetty
> <[email protected]> wrote:
>
> Hi Team,
>
> I am trying to implement example given at
> https://portals.apache.org/jetspeed-2/tutorial/01/project-structure.html here
> it says jetexpress-pa, jetexpress-portal are submodules inside jetexpress
> project.
>
> When we use eclipse IDE how should we create these folders?
> Should we create jetexpress webproject and within that web project should
> we create jetexpress-pa, jetexpress-portal two web projects ?
>
> Please guide me on this.
>
>
> Regards,
> Lalitha
>
> -----Original Message-----
> From: DavidSeanTaylor [mailto:[email protected]]
> Sent: Tuesday, June 09, 2015 11:55 PM
> To: Jetspeed Developers List
> Subject: Re: Regarding Jetspeed migration
>
>> In the similar way do we need to map portlet.xml to web.xml ?
>
> No. The portlet.xml and web.xml coexist. Both are required. The
> portlet.xml is required by the Portlet Spec, and the web.xml by the
> Servlet Spec (although technically neither is required when using
> annotations on newer versions of both specs)
>
> So portlet entries in the xreg files need to be converted to portlet
> entries in portlet.xml
>
> <portlet-entry name="WeatherPortlet" hidden="false" type="ref"
> parent="Velocity" application="false">
> <parameter name="template" value="weather" hidden="true"/>
> </portlet-entry>
>
>
> The portlet.xml will hold your list of portlets (amongst other things)
> - so its
>
> <portlet id="weather">
> <description>Weather Underground Portlet. Go to edit mode to configure the
> weather for your city.</description>
> <portlet-name>WeatherPortlet</portlet-name>
> <display-name>Weather</display-name>
>
> <portlet-class>org.apache.portals.applications.desktop.WeatherPortlet</portlet-class>
> <init-param>
> <name>ViewPage</name>
> <value>/WEB-INF/view/weather.vm</value>
> </init-param>
> <init-param>
> <name>EditPage</name>
> <value>/WEB-INF/view/edit-prefs.vm</value>
> </init-param>
> <init-param>
> <name>portlet-icon</name>
> <value>weather-showers.png</value>
> </init-param>
> <expiration-cache>300</expiration-cache>
> <supports>
> <mime-type>text/html</mime-type>
> <portlet-mode>VIEW</portlet-mode>
> <portlet-mode>EDIT</portlet-mode>
> </supports>
> <supported-locale>en</supported-locale>
> <portlet-info>
> <title>Weather</title>
> <short-title>Weather</short-title>
> <keywords>weather,tools,desktop</keywords>
> </portlet-info>
> <portlet-preferences>
> <preference>
> <name>weather_state</name>
> <value>CA</value>
> </preference>
> <preference>
> <name>weather_city</name>
> <value>Oakland</value>
> </preference>
> <preference>
> <name>weather_station</name>
>
>> On Jun 9, 2015, at 3:26 AM, Lalitha Bourishetty
>> <[email protected]> wrote:
>>
>> i am following http://portals.apache.org/jetspeed-2/j1-migration.html.
>>
>> In jetspeed 1 inside xreg files we have url tag what is the equivalent tag
>> for this in jetspeed 2.
>> In jetspeed 1 we are mapping TurbineResource.properties in web.xml ,
>> In the similar way do we need to map portlet.xml to web.xml ?
>> Please confirm.
>>
>> Regards,
>> Lalitha
>>
>> -----Original Message-----
>> From: Ron Wheeler [mailto:[email protected]]
>> Sent: Thursday, June 04, 2015 7:23 PM
>> To: [email protected]
>> Subject: Re: Regarding Jetspeed migration
>>
>> What have you done so far?
>> Have you looked at one of your portlets to see what the impact is based on
>> your reading of the migration page?
>> Have you tried to build a Jetspeed-2 example?
>>
>> If you want someone to walk you through the process, you should contract
>> with BlueSunrise for a support contract.
>> http://www.bluesunrise.com/#/services
>>
>> Ron
>>
>> On 04/06/2015 5:27 AM, Lalitha Bourishetty wrote:
>>> Hi Team,
>>>
>>>
>>>
>>> We have a project which is in jetspeed 1. We would like to migrate.
>>>
>>> In portal I got http://portals.apache.org/jetspeed-2/j1-migration.html.
>>> Can any one help how exactly I can start with migration.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Lalitha
>>>
>>>
>>>
>>
>>
>> --
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: [email protected]
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
