jerome lacoste wrote:
[Hoping that cross posting on both lists is not an issue]
Would rather not. Everyone on mojo-dev should be on maven-dev, I think.
First congrats to all of you for yesterday's release.
Thanks! Sorry for the delayed response.
If I use the webstart plugin in a project, I am assuming that the
install operation will only install the jnlp file, and not the full
working directory, right?
That's what would be expected, the main product of the build is the jnlp
file, and nothing else?
webapp - creates a war, adds the webstart1 and webstart2 artifacts
This will require a fix for the webapp plugin to copy deps somewhere
other than WEB-INF/lib, required for applets as well. There is an open
jira ticket already.
combine war + webstart1 + webstart2.
To keep it simple I assume that this happens in one module)
I'm not sure what you mean here. It looks like 3 modules, with the war
depending on the other 2 and including them?
1- If only the jnlp file was deployed, how do I get hold of the rest
of the generated files. They are still in the working repository, but
my webapp project doesn't know it, or does it?
No, the WAR won't know about it. What information does it need from that
directory that it can't get from the JNLP file?
If the other artifacts are deployed, what is the appropriate
resulting artifact? a zip?
It will really depend on what they are and how they are used. I need to
understand more about it.
2- Should I and if so how can I share the working directory between
webstart1 and webstart2 so that operations on identical files are not
reproduced (e.g. if both webstart modules must sign & pack the same
dependency, better to do the operation only once)
Currently, m2 doesn't delve into that in any way. Remember, a module
should build on its own if possible.
One option is to redo it each time and take the performance hit, the
other is to deploy the modified dependency into the repository and
depend on that, however you can't really do that if you aren't building
the dependency originally.
I guess you could use a shared component that is only instantiated once
and cache the location of generated files so that it is only done once
in the reactor and perhaps can find them across builds, but you'll need
to look after that logic and make sure it gets flushed appropriately and
still works if one project is built in isolation. We're definitely
slating improvements in this area in future versions to further improve
performance from m2.
Of course, I may be misunderstanding this. If these all share one source
tree and the three are built from a single module obviously its a
different story.
3- Should the merging of the generated files happen automatically?
e.g. assuming that all artifacts are installed in the local
repository, if a user specifies a 'jnlp-zip' dependency type in the
webapp pom, the war plugin could automatically search for the set of
artifacts and combine it automatically into its resulting war? Or
should that be a manual operation, i.e. the user must specify and
configure a <plugin> to perform this merging, maybe using the assmbly
?
This still seems a little problematic to me - I'd like to understand it
more. I don't quite get that from the wiki page.
Incidentally, the License for JNLPServlet has that nuclear facility
clause. I'm not sure that package is entirely licensed as BSD and would
require further investigation before inclusion.
Should this be phased to do what the m1 plugin does, then include the
servlet stuff later on?
HTH,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
