[jira] Created: (JCRCMIS-1) Move parent/version/dependencies to latest Jackrabbit development version
Move parent/version/dependencies to latest Jackrabbit development version - Key: JCRCMIS-1 URL: https://issues.apache.org/jira/browse/JCRCMIS-1 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro POM files still refer to Jackrabbit 1.5-SNAPSHOT as parent, using 1.5-SNAPSHOT as version and 1.4 in certain dependencies. It's suggestable to have 1.6-SNAPSHOT as project version, as parent version of Jackrabbit and in Jackrabbit dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCRCMIS-2) Create separate Jira components for this 'Jackrabbit CMIS Sandbox' project
Create separate Jira components for this 'Jackrabbit CMIS Sandbox' project -- Key: JCRCMIS-2 URL: https://issues.apache.org/jira/browse/JCRCMIS-2 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro Being this project quite clearly dividable in components, we could create 4 components: - atompub-server - atompub-client - ws-server - ws-client leaving common issues without component (e.g. those related to the generic JCR-CMIS mapping) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCRCMIS-1) Move parent/version/dependencies to latest Jackrabbit development version
[ https://issues.apache.org/jira/browse/JCRCMIS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriele Columbro updated JCRCMIS-1: Attachment: JCRCMIS-1.diff Moved all versions/dependencies/parents to Jackrabbit-1.6-SNAPSHOT. > Move parent/version/dependencies to latest Jackrabbit development version > - > > Key: JCRCMIS-1 > URL: https://issues.apache.org/jira/browse/JCRCMIS-1 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro > Attachments: JCRCMIS-1.diff > > > POM files still refer to Jackrabbit 1.5-SNAPSHOT as parent, using > 1.5-SNAPSHOT as version and 1.4 in certain dependencies. > It's suggestable to have 1.6-SNAPSHOT as project version, as parent version > of Jackrabbit and in Jackrabbit dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCRCMIS-3) Start shared design (text file) for JCR-CMIS mapping to be shared by both AtomPub and WS implementation
Start shared design (text file) for JCR-CMIS mapping to be shared by both AtomPub and WS implementation --- Key: JCRCMIS-3 URL: https://issues.apache.org/jira/browse/JCRCMIS-3 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro Priority: Critical Earlier in the lists it was suggested to start a design to share a generic JCR-CMIS mapping between the two WS and AtomPub implementations. A possible table of contents could be: - High level domain objects mapping (e.g. what's a repo? what's a policy? what's an object?) - Metadata mapping (jackrabbit properties from/to cmis properties) - CMIS service call one step deeper mapping to JCR functionalities This may very well evolve in a 3rd maven sub-module depended upon by the two 'ws' and 'atompub' modules which implements *only* ths generic mapping JCR->CMIS and viceversa. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCRCMIS-4) Validate copyright/license coverage
Validate copyright/license coverage --- Key: JCRCMIS-4 URL: https://issues.apache.org/jira/browse/JCRCMIS-4 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Paolo Mottadelli The copyright and license on CMIS Specification have to be managed. At the moment we are adding a copyright-notice.txt file at the root of the CMIS sandbox, reporting the same notice provided in the CMIS Specification document -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRCMIS-1) Move parent/version/dependencies to latest Jackrabbit development version
[ https://issues.apache.org/jira/browse/JCRCMIS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658826#action_12658826 ] Paolo Mottadelli commented on JCRCMIS-1: Patch applied. Thanks > Move parent/version/dependencies to latest Jackrabbit development version > - > > Key: JCRCMIS-1 > URL: https://issues.apache.org/jira/browse/JCRCMIS-1 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro > Attachments: JCRCMIS-1.diff > > > POM files still refer to Jackrabbit 1.5-SNAPSHOT as parent, using > 1.5-SNAPSHOT as version and 1.4 in certain dependencies. > It's suggestable to have 1.6-SNAPSHOT as project version, as parent version > of Jackrabbit and in Jackrabbit dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCRCMIS-5) [WS] Setup integration testing framework at build time
[WS] Setup integration testing framework at build time -- Key: JCRCMIS-5 URL: https://issues.apache.org/jira/browse/JCRCMIS-5 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro For the AtomPub component a programmatic Jetty server creation approach was used (still hanging ATM). Another way (generically used by maven projects) is to startup jetty embedded server in maven and run integration testing from there. We'll test this approach for the WS server component and then investigate if the approach can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml) This task comprises: - Find a mean to separate unit from integration tests (e.g. add integration tests in a specific package, e.g. org.apache.jackrabbit.*.integration*) - Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing) - Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase and deploy the jackrabbit.war with the jcr-cmis-ws extension - Have surefire run all integration tests in the 'integration-test' phase against the running server (using some cxf ws-client support) - Configure jetty to be stopped just after that in the 'post-integration-test' phase -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRCMIS-3) Start shared design (text file) for JCR-CMIS mapping to be shared by both AtomPub and WS implementation
[ https://issues.apache.org/jira/browse/JCRCMIS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658838#action_12658838 ] Gabriele Columbro commented on JCRCMIS-3: - As a source of inspiration we may have a look here: http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/design/ > Start shared design (text file) for JCR-CMIS mapping to be shared by both > AtomPub and WS implementation > --- > > Key: JCRCMIS-3 > URL: https://issues.apache.org/jira/browse/JCRCMIS-3 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro >Priority: Critical > Original Estimate: 24h > Remaining Estimate: 24h > > Earlier in the lists it was suggested to start a design to share a generic > JCR-CMIS mapping between the two WS and AtomPub implementations. > A possible table of contents could be: > - High level domain objects mapping (e.g. what's a repo? what's a policy? > what's an object?) > - Metadata mapping (jackrabbit properties from/to cmis properties) > - CMIS service call one step deeper mapping to JCR functionalities > This may very well evolve in a 3rd maven sub-module depended upon by the two > 'ws' and 'atompub' modules which implements *only* ths generic mapping > JCR->CMIS and viceversa. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCRCMIS-5) [WS] Setup integration testing framework at build time
[ https://issues.apache.org/jira/browse/JCRCMIS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriele Columbro updated JCRCMIS-5: Description: For the AtomPub component a programmatic Jetty server creation approach was used (still hanging ATM). Another way (generically used by maven projects) is to startup jetty embedded server in maven and run integration testing from there. We'll test this approach for the WS server component and then investigate if the approach can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml) This task comprises: - Find a mean to separate unit from integration tests (e.g. add integration tests in a specific package, e.g. org.apache.jackrabbit.*.integration*) - Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing) - Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase - have jackrabbit.war with the jcr-cmis-ws extension deployed in jetty - Have surefire run all integration tests in the 'integration-test' phase against the running server (using some cxf ws-client support) - Configure jetty to be stopped just after that in the 'post-integration-test' phase was: For the AtomPub component a programmatic Jetty server creation approach was used (still hanging ATM). Another way (generically used by maven projects) is to startup jetty embedded server in maven and run integration testing from there. We'll test this approach for the WS server component and then investigate if the approach can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml) This task comprises: - Find a mean to separate unit from integration tests (e.g. add integration tests in a specific package, e.g. org.apache.jackrabbit.*.integration*) - Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing) - Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase and deploy the jackrabbit.war with the jcr-cmis-ws extension - Have surefire run all integration tests in the 'integration-test' phase against the running server (using some cxf ws-client support) - Configure jetty to be stopped just after that in the 'post-integration-test' phase > [WS] Setup integration testing framework at build time > -- > > Key: JCRCMIS-5 > URL: https://issues.apache.org/jira/browse/JCRCMIS-5 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro > Original Estimate: 8h > Remaining Estimate: 8h > > For the AtomPub component a programmatic Jetty server creation approach was > used (still hanging ATM). > Another way (generically used by maven projects) is to startup jetty embedded > server in maven and run integration testing from there. > We'll test this approach for the WS server component and then investigate if > the approach can be reused/shared also with the AtomPub component ( by moving > to the server/pom.xml) > This task comprises: > - Find a mean to separate unit from integration tests (e.g. add integration > tests in a specific package, e.g. org.apache.jackrabbit.*.integration*) > - Configure surefire to skip integration tests in the 'test' phase (see here > http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing) > - Configure maven-jetty-plugin to be started up in the 'pre-integration-test' > phase > - have jackrabbit.war with the jcr-cmis-ws extension deployed in jetty > - Have surefire run all integration tests in the 'integration-test' phase > against the running server (using some cxf ws-client support) > - Configure jetty to be stopped just after that in the > 'post-integration-test' phase -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCRCMIS-6) [WS] Have proper License included in the WSDL generated java file
[ https://issues.apache.org/jira/browse/JCRCMIS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriele Columbro updated JCRCMIS-6: Description: Java classes/interfaces generated by CXF wsdl2java are now without license. Either add it manually (boring ;) ) or have wsdl2java generate files with proper license. was: Java classes/interfaces generated by CXF wsdl2java are now without license. Either add it manually (boring ;) or have wsdl2java generated files with proper license. > [WS] Have proper License included in the WSDL generated java file > - > > Key: JCRCMIS-6 > URL: https://issues.apache.org/jira/browse/JCRCMIS-6 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro >Priority: Minor > > Java classes/interfaces generated by CXF wsdl2java are now without license. > Either add it manually (boring ;) ) or have wsdl2java generate files with > proper license. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCRCMIS-6) [WS] Have proper License included in the WSDL generated java file
[WS] Have proper License included in the WSDL generated java file - Key: JCRCMIS-6 URL: https://issues.apache.org/jira/browse/JCRCMIS-6 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro Priority: Minor Java classes/interfaces generated by CXF wsdl2java are now without license. Either add it manually (boring ;) or have wsdl2java generated files with proper license. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRCMIS-6) [WS] Have proper License included in the WSDL generated java file
[ https://issues.apache.org/jira/browse/JCRCMIS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658859#action_12658859 ] Paolo Mottadelli commented on JCRCMIS-6: If we automatically generate classes from wsdl (using the wsdl2java tool), we also have to add the license comment automatically, or we will have to do it manually every time we need to regenerate the classes from a new version of wsdl. > [WS] Have proper License included in the WSDL generated java file > - > > Key: JCRCMIS-6 > URL: https://issues.apache.org/jira/browse/JCRCMIS-6 > Project: Jackrabbit CMIS Sandbox > Issue Type: Task >Reporter: Gabriele Columbro >Priority: Minor > > Java classes/interfaces generated by CXF wsdl2java are now without license. > Either add it manually (boring ;) ) or have wsdl2java generate files with > proper license. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
