hi Spencer,
Updating the J2EE level might help (right-click the project > Java EE >
J2EE Migration Wizard).
By the way, what products to you have installed? Is it just RDi 7.5 or did
you also install RAD7.5 or any other 7.5 products?
thank you,
Hania Abd-El-Razik
From: Spencer Elliott <spencer@xxxxxxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 19/12/2008 07:30 PM
Subject: Re: [WDSCI-L] RDi 7.5 Rational Desktop Migration nag message
Hi,
I ran the migration again and here is the log:
Validating project: wv31
Running validator: Facet Consistency (id= FacetConsistencyValidator)
project nature: org.eclipse.wst.common.project.facet.core.nature
exists=true
project file:
.settings/org.eclipse.wst.common.project.facet.core.xml exists=true
verified that both nature and settings file exist. (both must
exist, or neither exist)
successfully loaded IFacetedProject model object
Finished running validator: Facet Consistency (id=
FacetConsistencyValidator)
Running validator: Component Consistency (id=
ComponentConsistencyValidator)
project nature:
org.eclipse.wst.common.modulecore.ModuleCoreNature exists=true
project file: .settings/org.eclipse.wst.common.component exists=true
verified that both nature and settings file exist. (both must
exist, or neither exist)
successfully loaded IVirtualComponent model object
Finished running validator: Component Consistency (id=
ComponentConsistencyValidator)
Running validator: Orphaned J2EE Meta-Data (id=
OrphanedJ2EEMetaDataValidator)
back level j2ee meta-data is consistent, file: .j2ee exists and
the following back level nature(s) is(are) defined:
com.ibm.etools.j2ee.WebNature, com.ibm.wtp.web.WebNature
back level web meta-data is consistent, file: .websettings exists
and the following back level nature(s) is(are) defined:
com.ibm.etools.j2ee.WebNature, com.ibm.wtp.web.WebNature
Finished running validator: Orphaned J2EE Meta-Data (id=
OrphanedJ2EEMetaDataValidator)
Running validator: Application Client Consistency (id=
AppClientConsistencyValidator)
This project is not identified as an Application Client project
Finished running validator: Application Client Consistency (id=
AppClientConsistencyValidator)
Running validator: Application Client Forward Consistency (id=
AppClientForwardValidator)
This project is not identified as a backlevel Application Client
project
Finished running validator: Application Client Forward Consistency
(id= AppClientForwardValidator)
Running validator: Connector Consistency (id=
ConnectorConsistencyValidator)
This project is not identified as a Connector project
Finished running validator: Connector Consistency (id=
ConnectorConsistencyValidator)
Running validator: Connector Forward Consistency (id=
ConnectorForwardConsistencyValidator)
This project is not identified as a backlevel Connector project
Finished running validator: Connector Forward Consistency (id=
ConnectorForwardConsistencyValidator)
Running validator: EAR consistency (id= EARConsistencyValidator)
This project is not identified as an EAR project
Finished running validator: EAR consistency (id=
EARConsistencyValidator)
Running validator: EAR Forward Consistency (id=
EARForwardConsistencyValidator)
This project is not identified as a backlevel EAR project
Finished running validator: EAR Forward Consistency (id=
EARForwardConsistencyValidator)
Running validator: Web Consistency (id= WebConsistencyValidator)
this project contains facet: Dynamic Web Module 2.2
checking for incompatible facets
facet: Utility Module not present
facet: J2C Module not present
facet: Static Web Module not present
facet: EAR not present
facet: EJB Module not present
facet: Application Client module not present
finished checking for incompatible facets
found file: WebContent/WEB-INF/web.xml
successfully loaded web.xml model object
WEB facet and web.xml versions are consistently: 2.2
Finished running validator: Web Consistency (id=
WebConsistencyValidator)
Running validator: Web Forward Consistency (id=
WebForwardConsistencyValidator)
detected backlevel WEB nature: com.ibm.etools.j2ee.WebNature
detected backlevel WEB nature: com.ibm.wtp.web.WebNature
checking for incompatible natures
nature: com.ibm.wtp.ejb.EJBNature not present
nature: com.ibm.etools.j2ee.EJB2_0Nature not present
nature: com.ibm.etools.j2ee.ApplicationClient_J2EE13_Nature not
present
nature: com.ibm.etools.j2ee.EARNature not present
nature: com.ibm.wtp.j2ee.EARNature not present
nature: com.ibm.etools.j2ee.EAR13Nature not present
nature: com.ibm.wtp.jca.ConnectorNature not present
nature: com.ibm.etools.j2ee.ApplicationClientNature not present
nature: com.ibm.wtp.j2ee.ApplicationClientNature not present
nature: com.ibm.etools.j2ee.ConnectorNature not present
nature: com.ibm.etools.j2ee.EJBNature not present
finished checking for incompatible natures
this project contains facet: Dynamic Web Module 2.2
back level WEB version consistent with forward level WEB facet
version
checking migration of Web Lib dependencies.
finished checking migration of Web Lib dependencies.
Finished running validator: Web Forward Consistency (id=
WebForwardConsistencyValidator)
Running validator: JSF Consistency (id= JsfConsistencyValidator)
This project is not identified as a JSF project
Finished running validator: JSF Consistency (id=
JsfConsistencyValidator)
Running validator: EJB Mapping Validator (id= EjbMappingValidator)
The project has no EJB model associated with it. EJB mapping
backend validation will not be performed.
Finished running validator: EJB Mapping Validator (id=
EjbMappingValidator)
Running validator: WebSphere Facet Validator (id=
WebSphereFacetValidator)
The project has no WebSphere runtime associated with it.
WebSphere facet validation will not be performed.
Finished running validator: WebSphere Facet Validator (id=
WebSphereFacetValidator)
Running validator: WebSphere Runtime Validator (id=
WebSphereRuntimeValidator)
The project has no WebSphere runtime associated with it.
WebSphere runtime validation will not be performed.
Finished running validator: WebSphere Runtime Validator (id=
WebSphereRuntimeValidator)
Running validator: EJB Consistency (id= EJBConsistencyValidator)
This project is not identified as an EJB project
Finished running validator: EJB Consistency (id=
EJBConsistencyValidator)
Running validator: EJB Forward Consistency (id=
EJBForwardConsistencyValidator)
This project is not identified as a backlevel EJB project
Finished running validator: EJB Forward Consistency (id=
EJBForwardConsistencyValidator)
Finished validating project: wv31
Spencer
Hania Abd-El-Razik wrote:
Hi Spencer,
After going through the migration wizard, were there any errors reported
in
the Migration Results view?
Thank you,
Hania Abd-El-Razik
"Spencer Elliott" <spencer@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.10865.1229700802.13295.wdsci-l@xxxxxxxxxxxx>...
Hi,
It keeps listing a web project that I have migrated 3 times.
Spencer
Spencer Elliott wrote:
Every time I start RDi 7.5 I get a window that says that I have
projects
that need migrating to the new version. I have run the migration
(sever
times)but still get the message.
Does anyone know how to make this thing go away?
Spencer
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
