[jira] [Commented] (BATIK-1197) Non optional dependencies on jython and rhino added in 1.9.1

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (BATIK-1197) Non optional dependencies on jython and rhino added in 1.9.1

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/BATIK-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118739#comment-16118739 ]

simon steiner commented on BATIK-1197:
--------------------------------------

The jython/rhino dependencies have been there a long time, they are now included in pom, you for now should exclude them as suggested.

> Non optional dependencies on jython and rhino added in 1.9.1
> ------------------------------------------------------------
>
>                 Key: BATIK-1197
>                 URL: https://issues.apache.org/jira/browse/BATIK-1197
>             Project: Batik
>          Issue Type: Bug
>          Components: Scripting
>            Reporter: Thomas Mortagne
>
> Note: can't find the 1.9.1 version so I did not set it in "Affects Version/s".
> Looks like a big change for a minor version. Is this really expected ?
> Maybe 1.9.1 was release by mistake ? I can only see it in Maven central but can't find a version here on any corresponding tag in http://svn.apache.org/repos/asf/xmlgraphics/batik/tags/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jira] [Commented] (BATIK-1197) Non optional dependencies on jython and rhino added in 1.9.1

Glenn Adams
In ANT builds, the inclusion of jpython/rhino support is conditioned on their presence on the build machine, so past release builds may or may not include compiled classes that reference these dependencies. I haven't studied past release builds to determine which do or do not include these classes.

The current Maven build, however, always include such classes (in the batik-script module), and may require runtime access to these deps. It may be useful to create a variant build of batik-script, call it batik-script-jpython, that does include the jpython interpreter classes and leave the "standard" batik-script module without this dep.

I have not studied this in depth to consider the pros/cons.

On Tue, Aug 8, 2017 at 11:49 AM, simon steiner (JIRA) <[hidden email]> wrote:

    [ https://issues.apache.org/jira/browse/BATIK-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118739#comment-16118739 ]

simon steiner commented on BATIK-1197:
--------------------------------------

The jython/rhino dependencies have been there a long time, they are now included in pom, you for now should exclude them as suggested.

> Non optional dependencies on jython and rhino added in 1.9.1
> ------------------------------------------------------------
>
>                 Key: BATIK-1197
>                 URL: https://issues.apache.org/jira/browse/BATIK-1197
>             Project: Batik
>          Issue Type: Bug
>          Components: Scripting
>            Reporter: Thomas Mortagne
>
> Note: can't find the 1.9.1 version so I did not set it in "Affects Version/s".
> Looks like a big change for a minor version. Is this really expected ?
> Maybe 1.9.1 was release by mistake ? I can only see it in Maven central but can't find a version here on any corresponding tag in http://svn.apache.org/repos/asf/xmlgraphics/batik/tags/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Loading...