Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0029629Openbravo ERPA. Platformpublic2015-04-16 10:052015-04-22 09:50
Reporterjecharri 
Assigned Toinigosanchez 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version3.0PR15Q1.4Fixed in Version3.0PR15Q1.4 
Merge Request Status
Review Assigned Toalostale
OBNetwork customer
Web browserGoogle Chrome
ModulesCore
Support ticket
Regression levelProduction - QA Approved
Regression date2014-11-18
Regression introduced in release3.0PR15Q1
Regression introduced by commithttp://code.openbravo.com/erp/devel/pi/rev/f7b4f6a3f08247b63fa6448a07187614d49de952 [^]
Triggers an Emergency PackNo
Summary0029629: The new way to create to do the setup is not taking into account the context name that users are configuring
DescriptionThe new way to create to do the setup is not taking into account the context name that users are configuring. The context name in eclipse always will be openbravo instead of the name that users decide to configure
Steps To Reproduce-in a environment with higher version than Q1 execute ant setup
-decide to configure step by step
-set the context name as "test"
-set also context URL to "http://localhost/test" [^]
-mount the environment in eclipse
-verify that after running tomcat the URL to go to Openbravo is
http://localhost:8080/openbravo [^]
instead of
http://localhost:8080/test [^]
Proposed SolutionI think that the problem is that the new process is not updating file
org.eclipse.wst.common.component
Additional Information
TagsApproved
Relationships
blocks defect 00296073.0PR15Q3 closed inigosanchez The new way to create to do the setup is not taking into account the context name that users are configuring 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-04-17 14:33inigosanchezTypedefect => backport
2015-04-17 14:33inigosanchezTarget Version3.0PR15Q3 => 3.0PR15Q1.4
2015-04-17 15:17dmitry_mezentsevTag Attached: Approved
2015-04-20 09:59inigosanchezIssue Monitored: alostale
2015-04-20 10:00hgbotCheckin
2015-04-20 10:00hgbotNote Added: 0076621
2015-04-20 10:00hgbotStatusscheduled => resolved
2015-04-20 10:00hgbotResolutionopen => fixed
2015-04-20 10:00hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/devel/pi/rev/392e1fbd55bfac1b07ad9e26027e66d5d735ba91 [^] => http://code.openbravo.com/erp/backports/3.0PR15Q1.4/rev/ab18a16987492fbcd5a11a50ff598f7e79ab02b4 [^]
2015-04-22 09:50alostaleNote Added: 0076677
2015-04-22 09:50alostaleStatusresolved => closed
2015-04-22 09:50alostaleFixed in Version => 3.0PR15Q1.4

Notes
(0076621)
hgbot   
2015-04-20 10:00   
Repository: erp/backports/3.0PR15Q1.4
Changeset: ab18a16987492fbcd5a11a50ff598f7e79ab02b4
Author: Inigo Sanchez <inigo.sanchez <at> openbravo.com>
Date: Mon Apr 20 09:32:25 2015 +0200
URL: http://code.openbravo.com/erp/backports/3.0PR15Q1.4/rev/ab18a16987492fbcd5a11a50ff598f7e79ab02b4 [^]

Fixed bug 29629: setup application is not taking into account the context name

The setup application is not taking into account the context name that users
are configuring. The values of "deploy-name" and "context-root" properties
of org.eclipse.wst.common.component are not updating.

Now it has been solved and if user set "context-name" in setup application.
this value is updating in org.eclipse.wst.common.component. For example if
a user set the context name as "test" the URL to go to Openbravo is
"http://localhost:8080/test" [^] instead of default one "http://localhost:8080/openbravo". [^]

---
M src/org/openbravo/configuration/ConfigurationApp.java
---
(0076677)
alostale   
2015-04-22 09:50   
code reviewed + tested