L.S.,
Just two questions/remarks:
- We still need to add the previous.releases somewhere to get the
spring.schemas files to contain the necessary entries for earlier
releases as well. I would propose to add it to the components root
pom.xml, but we would have to keep the same property in the root
pom.xml for the ServiceMix 3 container as well (for the core and audit
xsd files).
- Does it make sense to add the archetypes to this components
hierarchy? Wouldn't it be better to add them to a separate
tooling/archetypes project and release all archetypes in a single
release but separately from their components? They probably won't need
to change as much as their components and we also have a few archetypes
that do not match any component (servicemix-project-root,
servicemix-binding-component, ...)
Regards,
Gert
Hiram Chirino wrote:
Hi Everyone,
if you get a chance please review the 2 components ported over to the
new per component release structure.
Just checkout:
https://svn.apache.org/repos/asf/servicemix/components/components-pom/trunk/
I'm happy with it. And I'm eager to do the same for the rest of the
components in the smx3 trunk branch. Please let me know if I should
hold of in doing the rest of the components.
Should we do a release of the 2 that have been ported to test the
release process?
Regards,
Hiram
