Building and unit-testing MR Jars, easily

[Russell Gold]

I have just developed a new and easier way for building MR Jars 
, while waiting for the 
capability to be built into Maven. 

This approach is not only simple to set up (just use the designated parent POM, 
if you can), it lets you unit test for any supported JDK. For example:

jdk7 && mvn -Dmulti_release clean test
jdk10 && mvn -Dmulti_release clean test

where jdk7 and jdk10 set the appropriate versions for maven to use. Either will 
run against the appropriate additional code.

To build an MR JAR you set a property on the command line

mvn -Dmulti_release clean install

which happens automatically when doing a release.

I have also explained how it works at Easier Than It Looks 

Re: Dependency is missed while using maven-assembly-plugin

[Сергей Вайсман]

Hello, Thorsten

Thank you very much for the help! Yes, this is the reason of my problem.

I tested it on next releases of batik and found that the dependency 
structure

changed in next versions and there's no batik-js in dependency tree.
Unfortunately, I couldn't upgrade version because in real project these
batik 1.7 libraries are used in some third-party plugin used by our
GUI developers.

For my case it was convenient to use exclusions for batik-script and
batik-bridge. And use these excluded dependencies external.
Like this.

    
        
            internal-module-groupId
internal-module-artifactId
            
                
org.apache.xmlgraphics
batik-bridge
                
                
org.apache.xmlgraphics
batik-script
                
            
        
        
            org.apache.xmlgraphics
            batik-script
            1.7
        
        
            org.apache.xmlgraphics
            batik-bridge
            1.7
        
    


Anyway, thank you for your responses!
Have a nice day!


--
Regards,
Sergey Vaysman


On 03.04.2018 14:05, Thorsten Heit wrote:

Hi Sergey,


I updated to the latest maven version 3.5.3 and configured the project
to use
the latest maven-assembly-plugin version 3.1.0.

You seem to be hit by
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-782.

In short: You have circular dependencies in Batik 1.7:
batik-bridge -> batik-script -> batik-bridge...

Can you use a newer version of batik-transcoder such as 1.8, 1.9 or 1.9.1
(all available on Maven Central)?


Regards

Thorsten



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Re: Dependency is missed while using maven-assembly-plugin

[Thorsten Heit]

Hi Sergey,

> I updated to the latest maven version 3.5.3 and configured the project 
> to use
> the latest maven-assembly-plugin version 3.1.0.

You seem to be hit by 
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-782.

In short: You have circular dependencies in Batik 1.7:
batik-bridge -> batik-script -> batik-bridge...

Can you use a newer version of batik-transcoder such as 1.8, 1.9 or 1.9.1 
(all available on Maven Central)?


Regards

Thorsten

Re: Re: Dependency is missed while using maven-assembly-plugin

[Thorsten Heit]

Hi,

> The first thing I need to mention that I gave you a wrong version of 
> maven-assembly-plugin.
> Maven-assembly-plugin version: 2.2-beta-5
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
> 2014-12-14T20:29:23+03:00)
> Maven home: C:\soft\apache-maven-3.2.5
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> Default locale: ru_RU, platform encoding: Cp1251
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

Can you try with with m-assembly-p 3.1.0 and see whether this behaves 
different?
Could you switch to a newer version of Maven, i.e. 3.5.3 (the newest?


Regards

Thorsten