Re: 2.1 linker changes

Should appName.nocache.js be one of the Artifacts obtained via
artifacts.find(EmittedArtifact.class)?

In 2.04 it was emitted in the link method but in 2.1 it isn't!!!!

Is this by design? If so, what is the design?!?

Shawn

>> Later the log reports  "Emitting resource projectName.nocache.js"
>
> Just to clarify.
>
> Version 2.0.4 includes appName.nocache.js in the ArtifactSet passed
> into the link method of a class that extends AbstractLinker AND
> reports writing it to disk "Emitting resource appName.nocache.js" and
> writes it to disk
>
> Version 2.1 DOES NOT include appName.nocache.js in the ArtifactSet
> passed into the link method of a class that extends AbstractLinker BUT
> DOES report writing it to disk "Emitting resource appName.nocache.js"
> and writes it to disk
>
> What I can't understand is why artifacts.find(EmittedArtifact.class)
> does not now find appName.nocache.js.  EmittedArtifacts are defined in
> the api (both 2.04 and 2.1) as "An artifact that will be emitted into
> the output. All EmittedArtifacts contained in the ArtifactSet at the
> end of the Linking process will be emitted by the compiler into the
> module's output directory."
>
> appName.nocache.js IS emitted into the output so WHY IS IT NO LONGER
> IN THE ARTIFACT SET?????
>
> Shawn
>

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.