Older
-
-
-
-
-
-
-
-
-
-
-
-
r107
(release v1.0 artifacts commited) committed by dev.apostiglioni
- release v1.0 artifacts commited
release v1.0 artifacts commited
-
r106
(clean v1.0 release artifacts) committed by dev.apostiglioni
- clean v1.0 release artifacts
clean v1.0 release artifacts
-
-
-
-
-
-
-
r99
(license disclaymer and credits) committed by dev.apostiglioni
- license disclaymer and credits
license disclaymer and credits
-
r98
(release 1.0 commited in repository) committed by dev.apostiglioni
- release 1.0 commited in repository
release 1.0 commited in repository
-
r97
([maven-release-plugin] prepare for next development iteratio...) committed by dev.apostiglioni
- [maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare for next development iteration
-
r96
([maven-release-plugin] copy for tag aconcagua-flex-1.0) committed by dev.apostiglioni
- [maven-release-plugin] copy for tag aconcagua-flex-1.0
[maven-release-plugin] copy for tag aconcagua-flex-1.0
-
r95
([maven-release-plugin] prepare release aconcagua-flex-1.0) committed by dev.apostiglioni
- [maven-release-plugin] prepare release aconcagua-flex-1.0
[maven-release-plugin] prepare release aconcagua-flex-1.0
-
r94
(project version rolled back to version 1.0-SNAPSHOT because ...) committed by dev.apostiglioni
- project version rolled back to version 1.0-SNAPSHOT because of an error on the release:prepare
plugin
project version rolled back to version 1.0-SNAPSHOT because of an error on the release:prepare
plugin
-
r93
([maven-release-plugin] prepare release aconcagua-flex-1.0) committed by dev.apostiglioni
- [maven-release-plugin] prepare release aconcagua-flex-1.0
[maven-release-plugin] prepare release aconcagua-flex-1.0
-
r92
(aconcagua dependencies set to current version instead of a f...) committed by dev.apostiglioni
- aconcagua dependencies set to current version instead of a fixed version
aconcagua dependencies set to current version instead of a fixed version
-
-
r90
(Dummy file that to trigger maven's profile) committed by dev.apostiglioni
- Dummy file that to trigger maven's profile
Dummy file that to trigger maven's profile
-
-
-
-
r86
(weird bug when logging. removed parameter) committed by dev.apostiglioni
- weird bug when logging. removed parameter
weird bug when logging. removed parameter
-
-
-
r83
(pom.xml, assembly-descriptor.xml and project files) committed by dev.apostiglioni
- pom.xml, assembly-descriptor.xml and project files
pom.xml, assembly-descriptor.xml and project files
-
-
r81
(update poms to use latest flex-mojos plugin) committed by dev.apostiglioni
- update poms to use latest flex-mojos plugin
update poms to use latest flex-mojos plugin
-
r80
(GestureHandler.command property renamed to handler, to suppo...) committed by dev.apostiglioni
- GestureHandler.command property renamed to handler, to support mediators
GestureHandler.command property renamed to handler, to support mediators
-
r79
(new features:
- Controller class now supports Mediators!!
...) committed by dev.apostiglioni
- new features:
- Controller class now supports Mediators!!
- HelloWorld example illustrates use of Mediator class and bindings.
refactors:
- new class BeanDefinitionRegistrarSupport created on aconcagua-beans to be used as base class for
all beanDefinitionRegistrars
- refactor class Bean. Now extends BeanDefinitionRegistrarSupport
- refactor class CommandFactory. Now extends BeanDefinitionRegistrarSupport
- new class GestureHandler extends BeanDefinitionRegistrarSupport to be used as base class of
Mediator and Command
- refactor class Command. Now extends GestureHandler
- new class Mediator.
new features:
- Controller class now supports Mediators!!
- HelloWorld example illustrates use of Mediator class and bindings.
refactors:
- new class BeanDefinitionRegistrarSupport created on aconcagua-beans to be used as base class for
all beanDefinitionRegistrars
- refactor class Bean. Now extends BeanDefinitionRegistrarSupport
- refactor class CommandFactory. Now extends BeanDefinitionRegistrarSupport
- new class GestureHandler extends BeanDefinitionRegistrarSupport to be used as base class of
Mediator and Command
- refactor class Command. Now extends GestureHandler
- new class Mediator.
-
-
r77
(Enhacement: Support multiple commands listening to a gesture...) committed by dev.apostiglioni
- Enhacement: Support multiple commands listening to a gesture.
Enhacement: Support multiple commands listening to a gesture.
-
r76
(Performance fix. Properties are initialized set only when in...) committed by dev.apostiglioni
- Performance fix. Properties are initialized set only when initializing a definition.
Performance fix. Properties are initialized set only when initializing a definition.
-
r75
(Added logging information) committed by dev.apostiglioni
- Added logging information
Added logging information
-
-
r73
(svn:ignore properties set) committed by dev.apostiglioni
- svn:ignore properties set
svn:ignore properties set
-
r72
(Add support to split MXMLBeanFactories definitions into mult...) committed by dev.apostiglioni
- Add support to split MXMLBeanFactories definitions into multiple files.
BeanDefinitionFactory renamed to BeanDefinitionRegistrar.
Add method registerAlias on BeanDefinitionRegistrar to fix bug on Alias class.
Add support to split MXMLBeanFactories definitions into multiple files.
BeanDefinitionFactory renamed to BeanDefinitionRegistrar.
Add method registerAlias on BeanDefinitionRegistrar to fix bug on Alias class.
-
r71
(Bindings are now Bean Metadata. This means they can be inclu...) committed by dev.apostiglioni
- Bindings are now Bean Metadata. This means they can be included in the bean definition the same way
as Property's and ConstructorArg's.
There's a difference between declaring bindings in the context:binding section and as bean metadata.
Bean metadata is processed at bean initialization, which, for lazy beans will only happen once the
getBean method is called. Trying to add a binding metadata on a prototype bean will throw an
exception.
On the other hand, bindings at context:bindings will be processed at context initialization, and
will result in initializing lazy beans. Setting a binding on a prototype will not throw an
exception, but it is still not valid and may not produce the expected results.
Bindings are now Bean Metadata. This means they can be included in the bean definition the same way
as Property's and ConstructorArg's.
There's a difference between declaring bindings in the context:binding section and as bean metadata.
Bean metadata is processed at bean initialization, which, for lazy beans will only happen once the
getBean method is called. Trying to add a binding metadata on a prototype bean will throw an
exception.
On the other hand, bindings at context:bindings will be processed at context initialization, and
will result in initializing lazy beans. Setting a binding on a prototype will not throw an
exception, but it is still not valid and may not produce the expected results.
-
r70
(distributionManagement section added to pom.xml) committed by dev.apostiglioni
- distributionManagement section added to pom.xml
distributionManagement section added to pom.xml
-
|