[MAGNOLIA-1200] tools: extracting spider for jsps Created: 10/Nov/06  Updated: 10/Jan/14  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.0 Final
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

In the deployment page (found in Tools menu point) one can start a periodically extraction of files (copy files from jars:mgnl-files to the filesystem). This allows editing jsps even if they are stored in the classpath.

This code has to be improved:

  • if magnolia.develop is true we should start it at startup (in the tools module)
  • checks modifiaction date (no extracting otherwise)
  • use ranking for checking (check recentely changed files more often)
  • rank jsp higher than images or similar
  • dynamic sleep period (check faster if the system is not overloaded)


 Comments   
Comment by Philipp Bracher [ 15/Aug/07 ]

temporary solution (eclipse)

create an ant build.xml file containing:

<project>
<target name="deploy">
<copy todir="../magnolia/src/main/webapp">
<fileset dir="src/main/resources/mgnl-files"/>
</copy>
</target>
</project>

Add a builder (Project, Properties, Builders), select ant build and execute deploy target on auto builds.

This will copy the files to the webapp when ever you change a file (jsps for example)

Comment by Philipp Bärfuss [ 03/Dec/13 ]

Hi,

Thanks for reporting and/or commenting on this issue. We are currently reviewing issues that have had no or minimal activity for several years. Magnolia has evolved tremendously since this issue was reported; in order to focus our work, we are closing such issues.

We realize that some of these might still be valid today - and we ask for your cooperation here. In some cases, we will be linking to overarching stories, or simply more up-to-date similar issues. If you believe this issue is still relevant today, please leave a comment below and we will get back to you.

Cheers,

Generated at Mon Feb 12 03:24:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.