search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Spring Context files not reloaded using "rad" profile #158

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a new alfresco amp module using the Alfresco Maven SDK 1.1.1
2. Import the project into Intellij and configure JRebel
3. Set the JAVA_OPTS an MAVEN_OPTS
3. Build and run the project using the rad and amp-to-war profile
4. Add a new bean to service-context.xml

What is the expected output? What do you see instead?
- The newly created bean should be loaded

What version of the product are you using? On what operating system?
- Alfresco Maven SDK 1.1.1, OSX, Intellij 12, JRebel 5.4.1

The generated rebel.xml file does not add "scr/main/amp/config" to the 
classpath.
I have overridden the "rad" profile and added the above path so the rebel.xml 
file contains the extra location to monitor. The "import" statement in 
module-context.xml should be updated as well because it uses the maven 
placeholders to point to the service-context.xml file. I just replaced the 
placeholder with the module string. After those changes I can update the 
module-context.xml file and JRebel detects those modifications! 
Unfortunately, JRebel doesn't monitor the service-context.xml file... Not sure 
if it is a configuration error or a problem with the import statement.

Do you think it is possible to provide the creation of new WebScripts as well 
if the Spring context reloading works?

Original issue reported on code.google.com by g.vanheu...@aca-it.be on 26 Nov 2013 at 12:03

GoogleCodeExporter commented 8 years ago

Original comment by colum...@gmail.com on 10 Mar 2014 at 7:01

GoogleCodeExporter commented 8 years ago 
Ole, Mau: can we review this as part of the new integration with Spring Loaded?

I think (and Ole agrees) that we should still keep JRebel as a parallel option 
to spring-loaded so we might want to look to fix that (ideally with a property 
activation, but I think we need different profiles explicitly called)

I know Marco did work for the all-in-one, but would be good to test that also 
this one is fixed as part of the JRebel review.

Original comment by colum...@gmail.com on 17 Jul 2014 at 10:37

GoogleCodeExporter commented 8 years ago

Original comment by colum...@gmail.com on 17 Jul 2014 at 10:37