I am in the process of writing the underlying MC beans. They are quite similar to the old ones, but do contain some changes. Ideally, I would like to be able to:
1) Replace the "old" underlying beans with my new ones. I don't want to have to maintain two versions of this.
2) Replace the current use-case xml (i.e. aop:aspect) with something more similar to what goes in a jboss-aop.xml file. Alternatively, I could modify the existing AOPBeansSchemaInitializer to use the "new" underlying beans, and create a new SchemaBindingInitializer to parse the "new" use-case.xml.
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103009#4103009
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103009
"alesj" wrote : I mean, how come this didn't get populated during my mvn-release cookbook procedure?
| Missing some settings? Since I don't touch my mvn settings if not necessary. ;-)
|
Or does this last step - 'The deployment is done to the local file system (a local checkout of the jboss maven2 repository), so you will need to commit the new files after they are deployed.' - imply that you also have to commit all this generated artifacts to our mvn2 repo as well?
If so, then it should be noted that you have to commit it to both places - our maven2 repo location + old buildmagic pickup place.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102954#4102954
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102954