[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6317: - Fix Version/s: (was: Upcoming Branch) > Missing BIRT libs in eclipse .classpath file > > > Key: OFBIZ-6317 > URL: https://issues.apache.org/jira/browse/OFBIZ-6317 > Project: OFBiz > Issue Type: Bug > Components: framework, specialpurpose/birt >Affects Versions: Release Branch 14.12, Upcoming Branch >Reporter: Martin Becker >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01 > > Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, > OFBIZ-6317_trunk_framework-base-config.patch > > > Because of missing JARs from the specialpurpose component birt in the eclipse > .classpath file OFBiz could not be startet within eclipse without errors > (NoClassDefFoundError while starting birt component). > With "starting within eclipse" I mean the configuration with hot code > replacement like this: > https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses > I will provide a patch for the .classpath file with 4 added libs from the > specialpurpose/birt/lib folder. > It would be beneficial, at least for simple contribution of jira issue fixes, > if the default configuration of OFBiz from trunk is runnable as is (in a > common development scenario like the above), without the need to modify > config files which are under version control (.classpath for example). The > alternative could be to not put files under version control, that are related > to individual development environments. > By the way, it would also be nice to have the framework/base/config folder as > src in the .classpath file as described in the wiki article above, so that > the configuration of an eclipse debug/run target for starting OFBiz in > eclipse is done by only selecting the project + start-class and giving some > JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6317: - Fix Version/s: (was: Release Branch 14.12) 14.12.01 > Missing BIRT libs in eclipse .classpath file > > > Key: OFBIZ-6317 > URL: https://issues.apache.org/jira/browse/OFBIZ-6317 > Project: OFBiz > Issue Type: Bug > Components: framework, specialpurpose/birt >Affects Versions: Release Branch 14.12, Upcoming Branch >Reporter: Martin Becker >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01, Upcoming Branch > > Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, > OFBIZ-6317_trunk_framework-base-config.patch > > > Because of missing JARs from the specialpurpose component birt in the eclipse > .classpath file OFBiz could not be startet within eclipse without errors > (NoClassDefFoundError while starting birt component). > With "starting within eclipse" I mean the configuration with hot code > replacement like this: > https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses > I will provide a patch for the .classpath file with 4 added libs from the > specialpurpose/birt/lib folder. > It would be beneficial, at least for simple contribution of jira issue fixes, > if the default configuration of OFBiz from trunk is runnable as is (in a > common development scenario like the above), without the need to modify > config files which are under version control (.classpath for example). The > alternative could be to not put files under version control, that are related > to individual development environments. > By the way, it would also be nice to have the framework/base/config folder as > src in the .classpath file as described in the wiki article above, so that > the configuration of an eclipse debug/run target for starting OFBiz in > eclipse is done by only selecting the project + start-class and giving some > JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Becker updated OFBIZ-6317: - Attachment: OFBIZ-6317_14-12.patch Added patch for Branch 14.12 which fixes the current missing/obsolete .classpath entries including birt libs and framework/base/config as stated above and removes in addition the following obsolete entries: * framework/webapp/lib/json-lib-2.2.3-jdk15.jar * framework/bi/src * framework/sql/src So that a fresh checkout is runnable within eclipse without changing the classpath within the run-/debug-configuration. Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Trunk Reporter: Martin Becker Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, OFBIZ-6317_trunk_framework-base-config.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6317: - Affects Version/s: (was: Trunk) Upcoming Branch Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Release Branch 14.12, Upcoming Branch Reporter: Martin Becker Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 14.12, Upcoming Branch Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, OFBIZ-6317_trunk_framework-base-config.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6317: - Fix Version/s: Release Branch 14.12 Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Release Branch 14.12, Trunk Reporter: Martin Becker Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 14.12, Upcoming Branch Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, OFBIZ-6317_trunk_framework-base-config.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6317: - Sprint: Community Day 2 - 2015 Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Trunk Reporter: Martin Becker Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6317.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Becker updated OFBIZ-6317: - Attachment: OFBIZ-6317_trunk_framework-base-config.patch Added patch for adding framework/base/config dir as described above to the .classpath file in trunk Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Trunk Reporter: Martin Becker Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6317.patch, OFBIZ-6317_trunk_framework-base-config.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Becker updated OFBIZ-6317: - Affects Version/s: Release Branch 14.12 Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Release Branch 14.12, Trunk Reporter: Martin Becker Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6317.patch, OFBIZ-6317_14-12.patch, OFBIZ-6317_trunk_framework-base-config.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6317) Missing BIRT libs in eclipse .classpath file
[ https://issues.apache.org/jira/browse/OFBIZ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Becker updated OFBIZ-6317: - Attachment: OFBIZ-6317.patch Missing BIRT libs in eclipse .classpath file Key: OFBIZ-6317 URL: https://issues.apache.org/jira/browse/OFBIZ-6317 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/birt Affects Versions: Trunk Reporter: Martin Becker Priority: Minor Attachments: OFBIZ-6317.patch Because of missing JARs from the specialpurpose component birt in the eclipse .classpath file OFBiz could not be startet within eclipse without errors (NoClassDefFoundError while starting birt component). With starting within eclipse I mean the configuration with hot code replacement like this: https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse#RunningandDebuggingOFBizinEclipse-debuggingInEclipseHotClasses I will provide a patch for the .classpath file with 4 added libs from the specialpurpose/birt/lib folder. It would be beneficial, at least for simple contribution of jira issue fixes, if the default configuration of OFBiz from trunk is runnable as is (in a common development scenario like the above), without the need to modify config files which are under version control (.classpath for example). The alternative could be to not put files under version control, that are related to individual development environments. By the way, it would also be nice to have the framework/base/config folder as src in the .classpath file as described in the wiki article above, so that the configuration of an eclipse debug/run target for starting OFBiz in eclipse is done by only selecting the project + start-class and giving some JVM args. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
