ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Vogel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-335) Migrate from Bndtools1 to Bndtools2
Date Wed, 06 Feb 2013 12:47:12 GMT

    [ https://issues.apache.org/jira/browse/ACE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572372#comment-13572372
] 

Christian Vogel commented on ACE-335:
-------------------------------------

I've already done 1,2,3,4,5,6,7! The changes before step 7 were affecting a lot of projects.
I had to add a specific version for the bundle osgi.core (v4.1.0) to resolve some osgi framework
issues (some classes couldnt be found without providing a version number) in following projects:

* org.apache.ace.authentication
* org.apache.ace.webui.vaadin
* org.apache.ace.configurator.serveruseradmin
* org.apache.ace.deployment.verifier

More changes I've done so far:

* replaced bndlib with biz.aQute.bnd in org.apache.ace.client.rest.itest (bndlib no more provided)
* easymock isnt provided anymore. i added it to my local repository.
* Apache Ace repository is now included as remote repository (fixedindexedrepo) ----> wasnt
sure if we still need all to be located on the local drive
                
> Migrate from Bndtools1 to Bndtools2
> -----------------------------------
>
>                 Key: ACE-335
>                 URL: https://issues.apache.org/jira/browse/ACE-335
>             Project: ACE
>          Issue Type: Task
>            Reporter: Christian Vogel
>              Labels: patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The current trunk version is not compatible to the new Bndtools version. Therefore, steps
should be executed to migrate the current 1.0.0.REL to 2.0.0.REL.
> Steps.:
> 1. make a backup copy of the current 'cnf' project folder
> 2. delete the old one and let the new Bndtools version create a new 'cnf' project for
you
> 3. add the Apache Ace additional repositories to 'cnf/ext/repositories.bnd'
> 4. copy the 'lib' folder of your backup 'cnf' to the new 'cnf' project
> 5. copy 'update-lib.sh' from your backup to the new 'cnf' project
> 6. copy 'cnf/src' from your backup to the new 'cnf' project
> 7. resolve all left project issues during different versionings of bundles in new 'cnf'
> 8. add additional targets from old ant build file to 'cnf/build.xml'
> 9. update  run configurations

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message