Apache

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • 1.1.0 Release

    5 answers - 698 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    I've completed significant bug fixes today and am ready to cut the 1.1.0
    release. I plan to post the release within the next day or two using:
    $mvn release:prepare
    $mvn clean install -P assembly
    $mvn release:perform
    for the creation of the binary and source distributions.
    Before I do so, I will make sure the release plugin is configured to
    deploy to a *staging* area vs. the live repo.
    If someone has a chance, it'd be great to have a second set of eyes look
    over the binary distribtions (run the 2nd command above) before I make
    the cut. This may help save some iterations in case I missed something.
    Thanks,
    David
  • No.1 | | 909 bytes | |

    Before we can release we have to follow the new licence policy:

    so all headers in our source files have to be changed. (There is a
    script somewhere doing the work)

    Carsten

    David H. DeWolf wrote:
    I've completed significant bug fixes today and am ready to cut the 1.1.0
    release. I plan to post the release within the next day or two using:

    $mvn release:prepare
    $mvn clean install -P assembly
    $mvn release:perform

    for the creation of the binary and source distributions.

    Before I do so, I will make sure the release plugin is configured to
    deploy to a *staging* area vs. the live repo.

    If someone has a chance, it'd be great to have a second set of eyes look
    over the binary distribtions (run the 2nd command above) before I make
    the cut. This may help save some iterations in case I missed something.

    Thanks,

    David
  • No.2 | | 1499 bytes | |

    I've gone through all the src/main/java files and ensured they have
    them. You're obviously finding some that I missed. . .can you please
    point me in the right direction?

    Carsten Ziegeler wrote:
    Before we can release we have to follow the new licence policy:

    so all headers in our source files have to be changed. (There is a
    script somewhere doing the work)

    Carsten

    David H. DeWolf wrote:
    >I've completed significant bug fixes today and am ready to cut the 1.1.0
    >release. I plan to post the release within the next day or two using:
    >>

    >$mvn release:prepare
    >$mvn clean install -P assembly
    >$mvn release:perform
    >>

    >for the creation of the binary and source distributions.
    >>

    >Before I do so, I will make sure the release plugin is configured to
    >deploy to a *staging* area vs. the live repo.
    >>

    >If someone has a chance, it'd be great to have a second set of eyes look
    >over the binary distribtions (run the 2nd command above) before I make
    >the cut. This may help save some iterations in case I missed something.
    >>
    >>

    >Thanks,
    >>
    >>

    >David
    >>


  • No.3 | | 3003 bytes | |

    David H. DeWolf wrote:
    I've gone through all the src/main/java files and ensured they have
    them. You're obviously finding some that I missed. . .can you please
    point me in the right direction?
    I think all files are still wrong :) The policy is to not have a
    copyright statement there, so the header should be (according to
    ):

    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements. See the NTICE file
    distributed with this work for additional information
    regarding copyright ownership. The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License. You may obtain a copy of the License at

    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHUT WARRANTIES R CNDITINS F ANY
    KIND, either express or implied. See the License for the
    specific language governing permissions and limitations
    under the License.

    Currently we have somethink like:

    /*
    * Copyright 2004 The Apache Software Foundation.
    *
    * Licensed under the Apache License, Version 2.0 (the "License");
    * you may not use this file except in compliance with the License.
    * You may obtain a copy of the License at
    *
    *
    *
    * Unless required by applicable law or agreed to in writing, software
    * distributed under the License is distributed on an "AS IS" BASIS,
    * WITHUT WARRANTIES R CNDITINS F ANY KIND, either express or implied.
    * See the License for the specific language governing permissions and
    * limitations under the License.
    */

    Carsten

    Carsten Ziegeler wrote:
    >Before we can release we have to follow the new licence policy:
    >>

    >
    >>

    >so all headers in our source files have to be changed. (There is a
    >script somewhere doing the work)
    >>

    >Carsten
    >>

    >David H. DeWolf wrote:

    I've completed significant bug fixes today and am ready to cut the 1.1.0
    release. I plan to post the release within the next day or two using:

    $mvn release:prepare
    $mvn clean install -P assembly
    $mvn release:perform

    for the creation of the binary and source distributions.

    Before I do so, I will make sure the release plugin is configured to
    deploy to a *staging* area vs. the live repo.

    If someone has a chance, it'd be great to have a second set of eyes look
    over the binary distribtions (run the 2nd command above) before I make
    the cut. This may help save some iterations in case I missed something.

    Thanks,

    David

    >>
  • No.4 | | 3025 bytes | |

    Gotcha! I see now.

    If anyone knows where the tool is to transform them, that would be a
    huge help. I'll hopefully have a chance to take a look later
    on today.

    David

    Carsten Ziegeler wrote:
    David H. DeWolf wrote:
    >I've gone through all the src/main/java files and ensured they have
    >them. You're obviously finding some that I missed. . .can you please
    >point me in the right direction?

    I think all files are still wrong :) The policy is to not have a
    copyright statement there, so the header should be (according to
    ):

    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements. See the NTICE file
    distributed with this work for additional information
    regarding copyright ownership. The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License. You may obtain a copy of the License at

    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHUT WARRANTIES R CNDITINS F ANY
    KIND, either express or implied. See the License for the
    specific language governing permissions and limitations
    under the License.

    Currently we have somethink like:

    /*
    * Copyright 2004 The Apache Software Foundation.
    *
    * Licensed under the Apache License, Version 2.0 (the "License");
    * you may not use this file except in compliance with the License.
    * You may obtain a copy of the License at
    *
    *
    *
    * Unless required by applicable law or agreed to in writing, software
    * distributed under the License is distributed on an "AS IS" BASIS,
    * WITHUT WARRANTIES R CNDITINS F ANY KIND, either express or implied.
    * See the License for the specific language governing permissions and
    * limitations under the License.
    */

    Carsten

    >Carsten Ziegeler wrote:

    Before we can release we have to follow the new licence policy:

    so all headers in our source files have to be changed. (There is a
    script somewhere doing the work)

    Carsten

    David H. DeWolf wrote:
    I've completed significant bug fixes today and am ready to cut the 1.1.0
    release. I plan to post the release within the next day or two using:

    $mvn release:prepare
    $mvn clean install -P assembly
    $mvn release:perform

    for the creation of the binary and source distributions.

    Before I do so, I will make sure the release plugin is configured to
    deploy to a *staging* area vs. the live repo.

    If someone has a chance, it'd be great to have a second set of eyes look
    over the binary distribtions (run the 2nd command above) before I make
    the cut. This may help save some iterations in case I missed something.

    Thanks,

    David

  • No.5 | | 244 bytes | |

    David H. DeWolf wrote:
    Gotcha! I see now.
    If anyone knows where the tool is to transform them, that would be a
    huge help. I'll hopefully have a chance to take a look later
    on today.
    See the faq
    #faq
    Carsten

Re: 1.1.0 Release


max 4000 letters.
Your nickname that display:
In order to stop the spam: 1 + 0 =
QUESTION ON "Apache"

EMSDN.COM