aspose file tools*
The moose likes Java in General and the fly likes Migration report findings Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "Migration report findings" Watch "Migration report findings" New topic
Author

Migration report findings

gaurav avhad
Greenhorn

Joined: Jul 21, 2014
Posts: 7
I am migrating my current project using jdeveloper and while doing that i got 6 report findings which are about third party dependencies..

So i would like to know if there any alternate jar files for the following jars so that the code is not affected

1-struts.jar
2-standard.jar
3-tools.jar
4-commons-logging.jar
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42282
    
  64
Why do you want to use other versions instead of the ones you're using now? What kind of migration is this? Also, the choice of IDE should not have any impact on the choice of libraries a project uses.


Ping & DNS - my free Android networking tools app
gaurav avhad
Greenhorn

Joined: Jul 21, 2014
Posts: 7
the source code was developed way back in 2009 i think...and the java version it works on is 1.4

one of the the reasons given is

struts.jar contains the following Third Party dependencies: ValidWhenLexer.class on [antlr.collections.impl.BitSet, antlr.InputBuffer, antlr.LexerSharedInputState, antlr.Token, antlr.ByteBuffer, antlr.CharBuffer, antlr.ANTLRHashString, antlr.NoViableAltForCharException, antlr.RecognitionException, antlr.TokenStreamRecognitionException, antlr.CharStreamException, antlr.CharStreamIOException, antlr.TokenStreamIOException, antlr.TokenStreamException, antlr.CharScanner, antlr.TokenStream, antlr.ANTLRStringBuffer] ValidWhenParser.class on [antlr.collections.impl.BitSet, antlr.TokenBuffer, antlr.TokenStream, antlr.ParserSharedInputState, antlr.NoViableAltException, antlr.LLkParser, antlr.RecognitionException, antlr.TokenStreamException, antlr.Token] ValidWhen.class on [antlr.TokenStream]

Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42282
    
  64
What do you perceive to be a "reason" in there?

So the migration in question is from a Java 1.4 JVM to a newer JVM? For starters, the old libraries should still all run (due to Java's backwards compatibility). If the project is still being developed, it may make sense to update the dependencies to newer versions. In that case you should start by identifying the dependencies, and then check whether there are newer versions that provide some benefit to the project (bug fixes, security fixes, new features etc.) If so, you'd replace the old library with the new one.
gaurav avhad
Greenhorn

Joined: Jul 21, 2014
Posts: 7
The project was developed in INTELLIJ IDEA.

I would like to know the new libraries or any alternate libraries for the same
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42282
    
  64
You can examine the contents of a jar file on the command line via "jar -tf ...". That will tell you what classes a file contains, and from the package names you should be able to deduce where you can find current versions.
 
Consider Paul's rocket mass heater.
 
subject: Migration report findings