You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2006/03/15 18:52:58 UTC

[jira] Created: (JCR-354) Use a pre-generated version of XPath.jjt

Use a pre-generated version of XPath.jjt
----------------------------------------

         Key: JCR-354
         URL: http://issues.apache.org/jira/browse/JCR-354
     Project: Jackrabbit
        Type: Improvement
  Components: xpath  
    Versions: 0.9    
    Reporter: Jukka Zitting
 Assigned to: Jukka Zitting 
    Priority: Minor
     Fix For: 1.0


The workaround described in JCR-46 is still causing extra steps for Java 5 users. I'd like to solve this issue by including a pre-generated version of the XPath.jjt file as a normal source file. This will avoid the need for XSL transformations during normal builds and thus remove the need for the extra steps.

I'll create a patch for this and unless anyone objects, I'm planning to include it in the 1.0 branch as well as the svn trunk.

-- 
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


[jira] Commented: (JCR-354) Use a pre-generated version of XPath.jjt

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/JCR-354?page=comments#action_12370695 ] 

Marcel Reutegger commented on JCR-354:
--------------------------------------

Makes sense. I think this is a very good approach to avoid the build troubles.

+1

> Use a pre-generated version of XPath.jjt
> ----------------------------------------
>
>          Key: JCR-354
>          URL: http://issues.apache.org/jira/browse/JCR-354
>      Project: Jackrabbit
>         Type: Improvement
>   Components: xpath
>     Versions: 0.9
>     Reporter: Jukka Zitting
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.0
>  Attachments: pregenerated-xpath-jjt.patch
>
> The workaround described in JCR-46 is still causing extra steps for Java 5 users. I'd like to solve this issue by including a pre-generated version of the XPath.jjt file as a normal source file. This will avoid the need for XSL transformations during normal builds and thus remove the need for the extra steps.
> I'll create a patch for this and unless anyone objects, I'm planning to include it in the 1.0 branch as well as the svn trunk.

-- 
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


[jira] Resolved: (JCR-354) Use a pre-generated version of XPath.jjt

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-354?page=all ]
     
Jukka Zitting resolved JCR-354:
-------------------------------

    Resolution: Fixed

Patch committed in revision 386412. Merged to the 1.0 branch in revision 386413.

> Use a pre-generated version of XPath.jjt
> ----------------------------------------
>
>          Key: JCR-354
>          URL: http://issues.apache.org/jira/browse/JCR-354
>      Project: Jackrabbit
>         Type: Improvement
>   Components: xpath
>     Versions: 0.9
>     Reporter: Jukka Zitting
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.0
>  Attachments: pregenerated-xpath-jjt.patch
>
> The workaround described in JCR-46 is still causing extra steps for Java 5 users. I'd like to solve this issue by including a pre-generated version of the XPath.jjt file as a normal source file. This will avoid the need for XSL transformations during normal builds and thus remove the need for the extra steps.
> I'll create a patch for this and unless anyone objects, I'm planning to include it in the 1.0 branch as well as the svn trunk.

-- 
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


[jira] Updated: (JCR-354) Use a pre-generated version of XPath.jjt

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-354?page=all ]

Jukka Zitting updated JCR-354:
------------------------------

    Attachment: pregenerated-xpath-jjt.patch

Attached a patch containing the pre-generated XPath.jjt file. The source XML and XSL files are very static so this should not cause any noticeable development trouble.

In addition to containing the XPath.jjt file, this patch changes the related maven.xml scripting and removes the Java 5 notices from README.txt and the "Building Jackrabbit" documentation page.

> Use a pre-generated version of XPath.jjt
> ----------------------------------------
>
>          Key: JCR-354
>          URL: http://issues.apache.org/jira/browse/JCR-354
>      Project: Jackrabbit
>         Type: Improvement
>   Components: xpath
>     Versions: 0.9
>     Reporter: Jukka Zitting
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.0
>  Attachments: pregenerated-xpath-jjt.patch
>
> The workaround described in JCR-46 is still causing extra steps for Java 5 users. I'd like to solve this issue by including a pre-generated version of the XPath.jjt file as a normal source file. This will avoid the need for XSL transformations during normal builds and thus remove the need for the extra steps.
> I'll create a patch for this and unless anyone objects, I'm planning to include it in the 1.0 branch as well as the svn trunk.

-- 
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