ace-commits mailing list archives

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

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

Marcel Offermans commented on ACE-335:
--------------------------------------

To start with your last question, you can attach a patch by pressing "More Actions" and then
choosing "Attach Files".

What kind of classes could not be found before you used a specific version of osgi.core, because
I assumed that all OSGi releases so far have been backward compatible. Or was something even
older than 4.1.0 being used?

The changes so far make sense, Having the repository on the local drive is just a speed optimization
and ideally we should still support both. However, we can do this one step at a time. Let's
first make sure we migrate and can run the server and targets, plus all our tests, and then
worry about the continuous build and how to setup everything for releases. Timing wise, it
makes sense to do this migration now, since everybody will upgrade to Bndtools 2 now anyway.
                
> 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