[ 
https://issues.apache.org/jira/browse/MYFACES-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559273#action_12559273
 ] 

Wolf Benz commented on MYFACES-1794:
------------------------------------

After check-out of MyFacesCore-trunk_1.2.x, as M2 project, trying mvn install, 
I get this Maven error: 
"[INFO] Error scanning for extensions: Error building model lineage in order to 
pre-scan for extensions: Cannot find artifact for parent POM: 
org.apache.myfaces:myfaces::5-SNAPSHOT for project org.apac
he.myfaces.core:myfaces-core-project:pom:1.2.1-SNAPSHOT "

I changed the local pom by adding this repo 
<repository>
        <id>Apache Repo</id>
        <url>http://svn.apache.org/repos/asf/myfaces</url>
     </repository>
, but to no avail. 
I don't see the myfaces-core-project either. 
What am I doing wrong? 

> MF Core causes resources not found(404) errors (recently also corrected in 
> Sun RI for JSF 1.2)
> ----------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-1794
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1794
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions:  1.2.0
>         Environment: JSF 1.2 (failures mostly happen with extensions like 
> with Trinidad e.g.)
>            Reporter: Wolf Benz
>             Fix For: 1.2.1
>
>
> Cf. the MF mailing list: topics like "Dialog issue during ADF->Trinidad 
> migration"
> I came across it using tr:inputDate but in the list topic I mentioned above, 
> so I first thought it was a Trinidad issue, but people more knowledgeable 
> with the JSF spec(Adam Winer) pointed out it was a MF 1.2 core issue, and 
> that the Sun RI had also sufferend from it, yet in the RI, this bug has 
> recently been corrected. 
> The error I got was when clicking the calendar icon and expecting a cal 
> popup. Instead I got: 
> "description The requested resource (.../__ADFv__.jsp) is not available."
> As it potentially affects a lot of other components beyond this trinidad one, 
> I marked it major as these components just don't work anymore.
> E.g. MF mailing list with topic "RE: [Trinidad] HTTP 404 (file not found) 
> while using DialogFramework" points that out.
> --Wolf

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to