Re: [seam-dev] Official Java HotSwap?
by Stuart Douglas
On 28/09/2010, at 3:12 AM, Dan Allen wrote:
> Stuart has mentioned in several threads that fakereplace is very close to JRebel in core features, and in some cases perhaps farther along. The big thing that JRebel has is the integrated tooling support and a product w/ support. I applaud their work, but am still very much in support of Stuart's open source and extensible alternative.
I would not go that far :-) The guys at JRebel have spent years working full time on it, Fakereplace has not made it much past the prototype phase.
Architecture wise I think what is really needed is a JSR that will allow frameworks and hot deployment providers to work together in a loosely coupled way. That way frameworks can write the code to perform any re-initialistion of metadata that is required, and this will work with any hot deployment provider. If the JVM replacement functionality advances far enough Fakereplace's bytecode tricks will no longer be necessary.
Stuart
>
> One way or another, we should definitely be in this space. Perhaps if Stuart finds what the JVM guys are working on interesting, he will be willing to participate or provide feedback. From my understanding, you still need framework support and fakereplace will provide that architecture. So, I'd say that language level would be great, but still just one factor in the whole equation.
>
> -Dan
>
> On Mon, Sep 27, 2010 at 12:16 PM, tech4j(a)gmail.com <tech4j(a)gmail.com> wrote:
> I took a look at JRebel at J1. It looked interesting, but as you said it might be nicer to have VM support. We also have concerns over debug support with JRebel, but would need further review. For us ( RichFaces ) it is only really useful for example development anyway since components are created using the CDK.
>
> On Mon, Sep 27, 2010 at 11:03 AM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com> wrote:
> Hey (particularty Stuart,)
>
> Have you seen this? http://wikis.sun.com/display/mlvm/HotSwap
>
> Looks interesting...
>
> JVM level support might be a lot nicer (less configuration?) than things like JavaRebel, possibly much faster.
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
>
> --
> blog: http://in.relation.to/Bloggers/Jay
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
13 years, 10 months
Optional Dependencies
by Pete Muir
All
I just updated the development guidelines with these notes:
* You should mark a dependency as optional unless you think at least 80% of users are going to need that dependency -- in other words, non-optional dependencies should only be those which none of the code will operate without.
* If you have multiple distinct usages for your module (e.g. consumers of the Drools module might just be interested in DroolsFlow, and not Drools Fusion), then consider creating stack POMs which define the dependencies for each usage. Each stack POM is a separate maven module, and should be placed in the stacks/<usage> directory.
HTH
13 years, 10 months
IRC meeting tomorrow cancelled
by Pete Muir
Hi All
I'm cancelling the meeting tomorrow - both Lincoln and I are out. We'll resume next week :-)
If you wanted to discuss anything, then you could raise it here.
Pete
13 years, 10 months
Seam dist failing: http://hudson.qa.jboss.com/hudson/job/Seam-3.X-dist-nightly
by Martin Gencur
Hi all,
FYI,
this job has been failing for some time because of
seam-remoting-reference-guide dependency missing.
1)
org.jboss.seam.remoting:seam-remoting-reference-guide:zip:sources:3.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.seam.remoting -DartifactId=seam-remoting-reference-guide -Dversion=3.0.0-SNAPSHOT -Dclassifier=sources -Dpackaging=zip -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.seam.remoting -DartifactId=seam-remoting-reference-guide -Dversion=3.0.0-SNAPSHOT -Dclassifier=sources -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam:seam-reference-guide:pom:3.0.0-SNAPSHOT
2) org.jboss.seam.remoting:seam-remoting-reference-guide:zip:sources:3.0.0-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
org.jboss.seam:seam-reference-guide:pom:3.0.0-SNAPSHOT
--
Martin Gencur
Seam QA Associate
13 years, 11 months
