The official decision is not done, but we have already kinda decided to put them back in the branch. The idea is of course to make them work again in
the branch.
They would though not be available in the next 13.07 release (ie R13.07.0.2), but in sync in the release branch since, after reintroduction, there
will not be any new features in the branch, but as normal only bug fixes.
http://markmail.org/message/fmmnvpzrf4sxmnvy
So it would be easy and safe to integrate them in a released package using a
simple copy.
Or to keep in sync with bug fixes svn external like I did for the demo (not at the moment)
https://svn.apache.org/viewvc/ofbiz/trunk/tools/demo-backup/branch13.7-demo.patch?revision=1613049&view=markup
(the port.https.enabled=N property is only for the demo)
This also suggest that it's easier to work from the branch than from a released
package, think about it
This is not how things are normally handled at the ASF (other projects are
often actually libs).
So we could suggest this way to do in our download page?
As discussed in above thread, another possibility is to create sub projects.
But for now the most active committers are rather against. Which does not mean
it will never happen...
Jacques
Le 13/11/2014 01:48, Ron Wheeler a écrit :
Another reason to get them into sub-projects.
Ron
On 12/11/2014 6:43 PM, Mike Z wrote:
Pierre has a point. Throwing little used components in trunk will just
make them completely unsupported and unable to compile, then just try to
get them fixed. If a developer changes code in a branch so much that it
renders a component in trunk to not compile, then soon none of them will
work (like scrum).
Put them back in the branch so they will force the committer to fix them so
they at least compile.
My 2 cents.
Sent from my BlackBerry® PlayBook™
www.blackberry.com
------------------------------
*From:* "Jacques Le Roux" <jacques.le.r...@les7arts.com>
*To:* "user@ofbiz.apache.org" <user@ofbiz.apache.org>
*Sent:* November 12, 2014 2:15 PM
*Subject:* Re: New to Ofbiz and Ofbiz POS
It's r1627929
Jacques
Le 12/11/2014 22:45, Pierre Smits a écrit :
Hi Mandeep,
You'll have to find a specific revision of trunk to checkout and use with
r13.07. Changes were implemented in special purpose components that depend
on changes in framework components not incorporated in r13.07.x
I experienced the same with scrum. And it is most likely to happen with the
other special purpose components excluded in r13.07.x.
Regards,
Pierre Smits
*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Wed, Nov 12, 2014 at 4:32 PM, mandeepmavi wrote:
HI
If i add POS to new release or SVN. getting error with ant command.
copy-derby-props:
ofbiz-init:
build:
[echo] [build] ========== Start Building (Compile) =========>>
build-framework:
init:
prepare:
classes:
jar:
init:
prepare:
gen-src:
classes:
jar:
init:
prepare:
gen-src:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
stubs:
main-jar:
rmi-jar:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
build-applications:
init:
prepare:
classes:
[javac16] Compiling 1 source file to
c:\ofbiz\applications\content\build\class
es
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
jar:
build-specialpurpose:
init:
prepare:
classes:
jar:
init:
prepare:
classes:
[javac16] Compiling 62 source files to
c:\ofbiz\specialpurpose\pos\build\class
es
[javac16]
c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:59
: cannot find symbol
[javac16] symbol : class EntityQuery
[javac16] location: package org.ofbiz.entity.util
[javac16] import org.ofbiz.entity.util.EntityQuery;
[javac16] ^
[javac16]
c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:59
: cannot find symbol
[javac16] symbol : class EntityQuery
[javac16] location: package org.ofbiz.entity.util
[javac16] import org.ofbiz.entity.util.EntityQuery;
[javac16] ^
[javac16]
c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:43
7: cannot find symbol
[javac16] symbol : variable EntityQuery
[javac16] location: class org.ofbiz.pos.PosTransaction
[javac16] product >>
EntityQuery.use(delegator).from("Product").whe
re("productId", productId).cache().queryOne();
[javac16] ^
[javac16]
c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:49
6: cannot find symbol
[javac16] symbol : variable EntityQuery
[javac16] location: class org.ofbiz.pos.PosTransaction
[javac16] product >>
EntityQuery.use(delegator).from("Product").whe
re("productId", productId).cache().queryOne();
[javac16] ^
[javac16]
c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\config\ButtonEventConf
ig.java:55: warning: [deprecation] getXmlRootElement(java.lang.String) in
org.of
biz.base.config.ResourceLoader has been deprecated
[javac16] Element root >>
ResourceLoader.getXmlRootElement(ButtonEventC
onfig.BUTTON_EVENT_CONFIG);
[javac16] ^
[javac16] 3 errors
[javac16] 1 warning
BUILD FAILED
c:\ofbiz\build.xml:230: The following error occurred while executing this
line:
c:\ofbiz\build.xml:252: The following error occurred while executing this
line:
c:\ofbiz\macros.xml:39: The following error occurred while executing this
line:
c:\ofbiz\common.xml:91: Compile failed; see the compiler error output for
detail
s.
Total time: 7 seconds
c:\ofbiz>
Mandeep
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/New-to-Ofbiz-and-Ofbiz-POS-tp4647653p4658123.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
