Issues: AxonFramework/AxonFramework
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Support SpEL on an Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
@ProcessingGroup
annotation equivalent
Priority 4: Would
#1266
opened Nov 6, 2019 by
jangalinski
Provide SQL for all Entities
Ideal for Contribution
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#1258
opened Nov 2, 2019 by
jangalinski
Granular Axon Starter "use case" selection
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Feature
Use to signal an issue is completely new to the project.
#1256
opened Oct 29, 2019 by
jangalinski
Provide axon-bom
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Status: Duplicate
Use to signal this issue is a duplicate of another. Please refer to the other issue.
Type: Dependency Upgrade
Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
#1254
by jangalinski
was closed Dec 6, 2019
Allow disabling AxonServerAutoConfiguration via properties
Ideal for Contribution
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
#1247
by jangalinski
was closed Dec 30, 2019
spring-boot-starter: EventProcessingAutoConfiguration cannot be enhanced by bean postprocessor
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
#1246
by jangalinski
was closed Oct 16, 2019
Open InMemoryEventStorageEngine for customization
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Enhance SubscriptionQueryResult to concat initial and update Results (if identical)
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#674
by jangalinski
was closed Aug 6, 2019
UpdateQueryEmitter - trigger via annotation on Event Handler
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Feature
Use to signal an issue is completely new to the project.
#666
by jangalinski
was closed Aug 6, 2019
Provide API for QuerySubscription with ResponseType equal to UpdateType
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#665
by jangalinski
was closed Aug 6, 2019
Introduce maven wrapper
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Spring Boot autoconfigure should add EventUpcaster
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Support Kafka as EventBus
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
AMQP-Client version conflict between axon-amp and spring-boot-starter-amqp
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Dependency Upgrade
Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
ProTip!
Follow long discussions with comments:>50.