[MAGNOLIA-3076] On Windows, XDoclet plugin fails in building CMS Tag Library Created: 12/Feb/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build, templating |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Diego Schivo | Assignee: | Magnolia International |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows XP Professional 2002, Service Pack 3 |
||
| Attachments: |
|
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
See attachment: build-error.txt. The problematic setting is in trunk/pom.xml: <restrictedpath>file://${settings.localRepository}</restrictedpath>
I think the prefix "file://" is system-dependent, because method QDoxPlugin.setRestrictedpath() [qdox-1.9.jar] uses the "restrictedpath" value as a file location (not an URL): String f = new File(folder).getCanonicalPath(); So, fore example, in windows:
Removing the prefix "file://" does not help, because a similar error occurs a bit later: see build-error2.txt. jar:file:/E:/magnolia/repository/info/magnolia/magnolia-taglib-cms/4.3-SNAPSHOT/magnolia-taglib-cms-4.3-SNAPSHOT-sources.jar!/info/magnolia/cms/util/Resource.java where "jar" is considered as the protocol, and "file:/..." as the file. I fixed the problem on my windows environment by rebuilding generama-1.2.4.jar with a patched QDoxPlugin class (also attached). |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |