Jenkins build became unstable: Aries » Apache Aries Blog sample iTests #963

See

Jenkins build became unstable: Aries #963

See

Jenkins build is back to normal : Aries #962

See

Jenkins build is back to normal : Aries » Apache Aries Application OBR Resolver #962

See

Build failed in Jenkins: Aries #961

See Changes: [ejiang] ARIES-618: Create a command line repository generator tool [ejiang] ARIES-618: Create a command line repository generator tool [ejiang] ARIES-618: Create a command line repository generator tool [ejiang] ARIES-618:

Build failed in Jenkins: Aries » Apache Aries Application OBR Resolver #961

See Changes: [ejiang] ARIES-618: Create a command line repository generator tool -- [INFO]

Re: Getting Started

Simon, Sreelatha, just to let you know the link is now fixed. Thanks for spotting it. On 6 April 2011 13:32, Simon Maple wrote: > OK, I'll submit a patch to fix the broken link now. > > Thanks, > > Simon Maple > WAS Developer & OSGi Technical Evangelist > IBM Hursley Park, Winchester SO21 2JN > >

[jira] [Resolved] (ARIES-630) Broken link on the apache aries home page

[ https://issues.apache.org/jira/browse/ARIES-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hughes resolved ARIES-630. - Resolution: Fixed Fix is now live > Broken link on the apache aries home page > -

[jira] [Assigned] (ARIES-630) Broken link on the apache aries home page

[ https://issues.apache.org/jira/browse/ARIES-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hughes reassigned ARIES-630: --- Assignee: Jeremy Hughes > Broken link on the apache aries home page >

Re: semantic version packages and bundles

Hi Emily, Am Donnerstag, den 07.04.2011, 10:09 +0100 schrieb Emily Jiang: > Thanks Felix fo your reply. > > The plus side for changing packaging version is not to forget it when we do > a release. Just one concern: we may end up increase the package version too > many times as each commit might

Re: semantic version packages and bundles

Thanks you Zoe pointing me to the policy. It makes more sense and solves my concern. Thanks On Thu, Apr 7, 2011 at 10:09 AM, Emily Jiang wrote: > Thanks Felix fo your reply. > > The plus side for changing packaging version is not to forget it when we do > a release. Just one concern: we may end

Re: semantic version packages and bundles

Thanks Felix fo your reply. The plus side for changing packaging version is not to forget it when we do a release. Just one concern: we may end up increase the package version too many times as each commit might end up bumping up package version when changing APIs in the same package. This could m

Re: semantic version packages and bundles

Hi Emily - you do need to change the package version but not the bundle version. The policy is documented here http://aries.apache.org/development/versionpolicy.html. You need to make changes to teh package version that reflect whatever changes you have made to the code. At release time the re