The term exploded in exploded-image refers to how the class files are
stored. In the exploded image, they are just files on disk while in the
JDK or JRE image, they are packaged. In JDK 8 and older, it used to be
in jars, but in JDK 9 it's a new format called jimage.
/Erik
On 2016-05-03 17:17
What is exploded vs not exploded?
On 5/3/16 4:55 AM, Erik Joelsson wrote:
>
>
> On 2016-05-03 07:46, Alan Bateman wrote:
>>
>>
>> On 03/05/2016 02:48, David Holmes wrote:
>>>
>>> So what build target will ensure the exploded image is created and
>>> up to date?
>> `make` without any target, that h
On 2016-05-03 07:46, Alan Bateman wrote:
On 03/05/2016 02:48, David Holmes wrote:
So what build target will ensure the exploded image is created and up
to date?
`make` without any target, that has always been the default.
Note that if you use Jib, the default target is remapped to build
On 03/05/2016 02:48, David Holmes wrote:
So what build target will ensure the exploded image is created and up
to date?
`make` without any target, that has always been the default.
-Alan
Hi Erik,
On 3/05/2016 1:31 AM, Erik Joelsson wrote:
On 2016-05-02 17:18, Pete Brunet wrote:
On 4/30/16 2:32 AM, David Holmes wrote:
On 30/04/2016 4:18 PM, Alan Bateman wrote:
On 30/04/2016 00:46, Pete Brunet wrote:
Even small edits to code in the jdk source tree result in very long
time
b
On 2016-05-02 17:18, Pete Brunet wrote:
On 4/30/16 2:32 AM, David Holmes wrote:
On 30/04/2016 4:18 PM, Alan Bateman wrote:
On 30/04/2016 00:46, Pete Brunet wrote:
Even small edits to code in the jdk source tree result in very long
time
build times now that jigsaw is merged in. Is anyone wo
On 4/30/16 2:32 AM, David Holmes wrote:
> On 30/04/2016 4:18 PM, Alan Bateman wrote:
>> On 30/04/2016 00:46, Pete Brunet wrote:
>>> Even small edits to code in the jdk source tree result in very long
>>> time
>>> build times now that jigsaw is merged in. Is anyone working on trying
>>> to improv
On Sat, Apr 30, 2016 at 10:14:42AM +0100, Alan Bateman wrote:
>
> On 30/04/2016 09:52, Ioi Lam wrote:
> >
> >Maybe the build system can generate more fine grained dependencies?
> >
> >If only private or non exported classes/packages are updated, no other
> >modules need to be rebuilt
> >
> >If on
On 02/05/2016 03:14, David Holmes wrote:
So jlink basically copies what is needed for a given configuration
into the "image" destination? So where previously this was handled in
the makefile and only what had changed needed copying, jlink will
re-copy everything?
Class files and resources g
On 1/05/2016 4:22 PM, Alan Bateman wrote:
On 01/05/2016 05:21, David Holmes wrote:
The native code - java.c. Can't see any reason for jmods to be
recreated every time I recompile that!
The packaged modules contain the tools/launcher for that module. So if
you touch java.c then the launchers
On 01/05/2016 05:21, David Holmes wrote:
The native code - java.c. Can't see any reason for jmods to be
recreated every time I recompile that!
The packaged modules contain the tools/launcher for that module. So if
you touch java.c then the launchers for every tool are re-generated and
thus
On 30/04/2016 5:53 PM, Alan Bateman wrote:
On 30/04/2016 08:32, David Holmes wrote:
Just to add my concerns here, I was changing the launcher and building
images and that caused the jmods to be rebuilt as well. I would not
expect that so do we have missing dependency information in the build?
On 30/04/2016 09:52, Ioi Lam wrote:
Maybe the build system can generate more fine grained dependencies?
If only private or non exported classes/packages are updated, no other modules
need to be rebuilt
If only an exported package is updated, then only other modules that import
this package
> On Apr 30, 2016, at 3:53 PM, Alan Bateman wrote:
>
>> On 30/04/2016 08:32, David Holmes wrote:
>>
>> Just to add my concerns here, I was changing the launcher and building
>> images and that caused the jmods to be rebuilt as well. I would not expect
>> that so do we have missing dependency
On 30/04/2016 08:32, David Holmes wrote:
Just to add my concerns here, I was changing the launcher and building
images and that caused the jmods to be rebuilt as well. I would not
expect that so do we have missing dependency information in the build?
By "changing the launcher" then do you mean
On 30/04/2016 4:18 PM, Alan Bateman wrote:
On 30/04/2016 00:46, Pete Brunet wrote:
Even small edits to code in the jdk source tree result in very long time
build times now that jigsaw is merged in. Is anyone working on trying
to improve that? Is there a workaround?
When you touch code in a m
On 30/04/2016 00:46, Pete Brunet wrote:
Even small edits to code in the jdk source tree result in very long time
build times now that jigsaw is merged in. Is anyone working on trying
to improve that? Is there a workaround?
When you touch code in a module then you can use "make " to just
rebui
Even small edits to code in the jdk source tree result in very long time
build times now that jigsaw is merged in. Is anyone working on trying
to improve that? Is there a workaround?
Thanks, Pete
18 matches
Mail list logo
