10.1.3 ADF Swing New Features Question

Question

One of the 4 new features for ADF Swing in JDeveloper 10.1.3 is stated as:
"ADF Swing
In the past, deploying an ADF Swing application entailed deploying the ADF runtime libraries, 
and then packaging and deploying your application class files.
This process has been simplified so that you no longer need to deploy the ADF runtime libraries
as a separate step; instead, they are automatically packaged with your application files."Can someone tell me if this is configurable? For instance, you would rarely want the above to occur if deploying using Java Webstart since it would guarantee a FULL download every time you made a small change to any class. This would basically eliminate versioned or incremental downloads of jar files.
Thanks
Erik

Answer 1

Thanks Frank, but your answer is just more confusing.
Here is what the new features document states:
"This process has been simplified so that you no longer need to deploy the ADF runtime libraries
as a separate step; instead, they are automatically packaged with your application files."
Notice the statement in bold.
I would expect that statement to mean that ALL of the ADF classes that are normally contained in their respective jar files will now be "automatically packaged" into MY application jar file, so that I have 1 jar file.
Now looking at your answer:
"If the application class files changed, then only those class files will be jarred and signed. ADF jar files are not signed again."
The statement in bold indicates that the ADF classes will still be contained in their respective jar files. Therefore, can you tell us what "automatically packaged" means in this conext? Normally, I would think it meant packaged inside a jar file, but from your answer, that cannot be correct.
Thanks
Erik