[jira] Commented: (COCOON-1838) Always use 3-digit version number

2006-05-17 Thread Reinhard Poetz (JIRA)
[ http://issues.apache.org/jira/browse/COCOON-1838?page=comments#action_12412135 ] Reinhard Poetz commented on COCOON-1838: If a version or a groupId is missing, the values are taken from the parent artifact. Taking this into consideration, do you

[jira] Commented: (COCOON-1838) Always use 3-digit version number

2006-05-17 Thread Ben Pope (JIRA)
[ http://issues.apache.org/jira/browse/COCOON-1838?page=comments#action_12412136 ] Ben Pope commented on COCOON-1838: -- A while go I had a look at all the pom files, but I wasn't entirely sure how they worked with respect to the missing version numbers,

[jira] Commented: (COCOON-1838) Always use 3-digit version number

2006-04-18 Thread Jorg Heymans (JIRA)
[ http://issues.apache.org/jira/browse/COCOON-1838?page=comments#action_12374997 ] Jorg Heymans commented on COCOON-1838: -- It was decided that module poms do not need to carry a 3 digit version number. Their sole responsibility is to group other

[jira] Commented: (COCOON-1838) Always use 3-digit version number

2006-04-18 Thread Ben Pope (JIRA)
[ http://issues.apache.org/jira/browse/COCOON-1838?page=comments#action_12375010 ] Ben Pope commented on COCOON-1838: -- Ah, thats a different story... much harder! There are a few places where there is a missing groupId or version number altogether. Is