Bug 975957 - Calendar class defined package and directory do not match.
Summary: Calendar class defined package and directory do not match.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 16:41 UTC by Marek Baluch
Modified: 2013-07-29 04:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-20 12:32:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Baluch 2013-06-19 16:41:18 UTC
The class located in knowledge-api/src/main/java/org/drools/time/Calendar.java defines package org.drools.core.time instead of org.drools.time.

Comment 2 Kris Verlaenen 2013-06-19 21:33:27 UTC
Not sure this issue is actually there in Beta3:
https://github.com/droolsjbpm/drools/blob/6.0.0.Beta3/knoweldge-api-legacy5-adapter/src/main/java/org/drools/time/Calendar.java

I guess there might be some confusion with a knowledge-api module that is still there in the droolsjbpm-knowledge repository but that is not part of the built (so the code in there is never built, it's the module inside the drools repository that is producing the knowledge-api jar).

Comment 3 Marek Baluch 2013-06-20 11:29:23 UTC
That's why I included also the link to the class on the call.

https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.0.Beta3/knowledge-api/src/main/java/org/drools/time/Calendar.java

If it's not built then we don't have a problem.

Comment 4 Kris Verlaenen 2013-06-20 12:26:20 UTC
It is not, as you can see here, only the kie-* modules are built:
https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.0.Beta3/pom.xml#L49

I'll check with the rest of the team about safely removing the code.
Feel free to close the issue (NOTABUG?).

Kris


Note You need to log in before you can comment on or make changes to this bug.