Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
hmmm, the main benefit of having seperate Jira projects is that we can
have seperate version numbering schemes for each project. But looking
at e.g. COCOONM2 I don't see how this can be achieved because all
modules that it contains already have different version numbers. If I
want to report a bug I don't know which version number I have to choose.
So what can we do? Split into more projects?
honestly, I don't know what's the best solution for our situation is. Looking at
the latest release we would need following Jira projects:
COCOON_CORE
- org.apache.cocoon:cocoon-pipeline-api:1.0.0-RC1
- org.apache.cocoon:cocoon-util:1.0.0-RC1
- org.apache.cocoon:cocoon-xml-api:1.0.0-RC1
- org.apache.cocoon:cocoon-pipeline-impl:1.0.0-RC1
- org.apache.cocoon:cocoon-xml-impl:1.0.0-RC1
- org.apache.cocoon:cocoon-pipeline-components:1.0.0-RC1
- org.apache.cocoon:cocoon-sitemap-api:1.0.0-RC1
- org.apache.cocoon:cocoon-thread-api:1.0.0-RC1
- org.apache.cocoon:cocoon-sitemap-impl:1.0.0-RC1
- org.apache.cocoon:cocoon-sitemap-components:1.0.0-RC1
- org.apache.cocoon:cocoon-xml-resolver:1.0.0-RC1
- org.apache.cocoon:cocoon-store-impl:1.0.0-RC1
- org.apache.cocoon:cocoon-thread-impl:1.0.0-RC1
- org.apache.cocoon:cocoon-core:2.2.0-RC1
COCOON_SERVLETSERVICE
- org.apache.cocoon:cocoon-servlet-service-components:1.0.0-M2
- org.apache.cocoon:cocoon-servlet-service-impl:1.0.0-M2
COCOON_FORMS
- org.apache.cocoon:cocoon-flowscript-impl:1.0.0-RC1
COCOON_TEMPLATE
- org.apache.cocoon:cocoon-template-impl:1.0.0-RC1
COCOON_APPLES
- org.apache.cocoon:cocoon-apples-impl:1.0.0-RC1
COCOON_LINKREWRITE
- org.apache.cocoon:cocoon-linkrewriter-impl:1.0.0-RC1
COCOON_AUTH
- org.apache.cocoon:cocoon-auth-api:1.0.0-RC1
- org.apache.cocoon:cocoon-auth-impl:1.0.0-RC1
COCOON_BATIK
- org.apache.cocoon:cocoon-batik-impl:1.0.0-RC1
COCOON_CAPTCHA
- org.apache.cocoon:cocoon-captcha-impl:1.0.0-RC1
COCOON_DATABASE
- org.apache.cocoon:cocoon-databases-mocks:1.0.0-RC1
- org.apache.cocoon:cocoon-databases-impl:1.0.0-RC1
COCOON_HSQLDB
- org.apache.cocoon:cocoon-databases-hsqldb-client:1.0.0-RC1
- org.apache.cocoon:cocoon-databases-hsqldb-server:1.0.0-RC1
COCOON_FLOWSCRIPT
- org.apache.cocoon:cocoon-flowscript-impl:1.0.0-RC1
COCOON_FOP
- org.apache.cocoon:cocoon-fop-impl:1.0.0-RC1
COCOON_HTML
- org.apache.cocoon:cocoon-html-impl:1.0.0-RC1
COCOON_MAIL
- org.apache.cocoon:cocoon-mail-impl:1.0.0-RC1
COCOON_FORMS
- org.apache.cocoon:cocoon-forms-impl:1.0.0-M3
COCOON_AJAX
- org.apache.cocoon:cocoon-ajax-impl:1.0.0-M3
COCOON_M2
- org.apache.cocoon:cocoon-maven-plugin:1.0.0-M1
- org.apache.cocoon:cocoon-rcl-spring-reloader:1.0.0-M1
- org.apache.cocoon:cocoon-rcl-webapp-wrapper:1.0.0-M1
COCOON_M2_ARCHETYPES
- org.apache.cocoon:cocoon-22-archetype-block:1.0.0-RC1
- org.apache.cocoon:cocoon-22-archetype-block-plain:1.0.0-RC1
- org.apache.cocoon:cocoon-22-archetype-webapp:1.0.0-RC1 #
COCOON_CONFIGURATION
- org.apache.cocoon:cocoon-configuration-api:1.0.0
- org.apache.cocoon:spring-configurator:1.0.0
COCOON_BLOCKS
-> the rest of the issues which belong to a block that hasn't it's
own Jira project yet because it is not ready to be released.
These are ~20 Jira projects. IMO we should either create them all or don't
change anything because I don't understand what the benefit of having multiple
Jira projects is if we can't use correct version numbers.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
