You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by Kurt T Stam <ku...@gmail.com> on 2009/07/29 05:30:08 UTC
[VOTE] Release scout-1.1
Hi guys,
I have staged the scout-1.1 artifacts in
http://people.apache.org/~kstam/staging-site/scout-1.1/
This is the first time I am using the maven release plugin (thanks to a
lot of help from David Jencks, thank you David), so hopefully all is ok.
I simply ran
mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
It also created a tag:
http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
my vote +1
Cheers,
--Kurt
This release includes he following:
Bug
* [SCOUT-76] - orgKey can be null in ServiceImpl
* [SCOUT-80] - copying lists into arrays invites code errors such as
NPEs
* [SCOUT-81] - jaxr-api cannot contain generics
* [SCOUT-83] - Create the derby db in the target dir
* [SCOUT-84] - Users not assigned to Organization properly
* [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
not needed
Improvement
* [SCOUT-82] - use maven best practices in build
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by Kurt T Stam <ku...@gmail.com>.
The staged artifacts can be found here:
https://repository.apache.org/content/repositories/scout-004/
I forgot to mention that this vote depends on a successful vote for the
geronimo-jaxb_2.1_spec release, and it will be open for 72 since the
start of this thread.
Cheers,
--Kurt
David Jencks wrote:
>
> On Jul 29, 2009, at 10:33 AM, Kurt T Stam wrote:
>
>> Right.. still new at this. I can run it now. Will it find the
>> geronimo-jaxb_2.1_spec.jar?
>
> I assume you succeeded in getting that into your local maven repo,
> since the regular build succeeded. So it should be available to the
> build the maven release plugin tries to do.
>
> thanks
> david jencks
>
>>
>> --Kurt
>>
>> David Jencks wrote:
>>> I checked that the tar.gz source archive is sufficient to build the
>>> project and has appropriate legal files, so this is in line with
>>> apache policy.
>>>
>>> However, I think Kurt produced the release candidates from the
>>> checkout on which he was running mvn release:prepare and as a result
>>> the source archives have a number of files that shouldn't be included:
>>> release.properties
>>> pom.xml.releaseBackup
>>> ..settings
>>> ..classpath
>>> ..project
>>>
>>> Also, the release candidate is not in apache nexus and I don't know
>>> how you'd deploy it there.
>>>
>>> I would strongly advise that Kurt run
>>>
>>> mvn release:perform -Papache-release
>>>
>>> in the same directory he ran mvn release:prepare
>>>
>>> This will svn export the tag, build it, and upload the artifacts to
>>> apache nexus, ready for promotion.
>>>
>>> thanks
>>> david jencks
>>>
>>> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I have staged the scout-1.1 artifacts in
>>>>
>>>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>>>
>>>> This is the first time I am using the maven release plugin (thanks
>>>> to a lot of help from David Jencks, thank you David), so hopefully
>>>> all is ok.
>>>>
>>>> I simply ran
>>>>
>>>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
>>>>
>>>> It also created a tag:
>>>> http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>>>
>>>> my vote +1
>>>>
>>>> Cheers,
>>>>
>>>> --Kurt
>>>>
>>>> This release includes he following:
>>>>
>>>> Bug
>>>>
>>>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>>>> * [SCOUT-80] - copying lists into arrays invites code errors such
>>>> as NPEs
>>>> * [SCOUT-81] - jaxr-api cannot contain generics
>>>> * [SCOUT-83] - Create the derby db in the target dir
>>>> * [SCOUT-84] - Users not assigned to Organization properly
>>>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
>>>> not needed
>>>>
>>>> Improvement
>>>>
>>>> * [SCOUT-82] - use maven best practices in build
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by Kurt T Stam <ku...@gmail.com>.
Cool I think that worked :)
https://repository.apache.org/content/repositories/scout-004/
--Kurt
David Jencks wrote:
> Only someone with scout permissions can see this...
>
> go to https://repository.apache.org/
> log in (upper right corner) with your apache id and subversion password
>
> click "Staging" in the left hand menu
>
> If you see the scout staging repo, it got staged OK. Now you need to
> select the staging repo, it will open a panel in the middle of the page.
> If you like what is there, right click and select "close".
>
> This will prevent adding more stuff to the repo and make if publically
> visible.
>
> Find the link to it and post it to the vote thread :-)
>
> thanks
> david jencks
>
> On Jul 29, 2009, at 11:14 AM, Kurt T Stam wrote:
>
>> OK just ran it, and it looks ok, I think. How do I check that things
>> are in nexus?
>>
>> [INFO] 194b uploaded (scout-1.1-source-release.tar.gz.asc)
>> [INFO] Uploading:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ws/scout/scout/1.1/scout-1.1-source-release.zip.asc
>>
>> [INFO] 194/194b
>> [INFO] 194b uploaded (scout-1.1-source-release.zip.asc
>> [INFO] [INFO] [bundle:deploy]
>> [INFO] [INFO] Remote OBR update disabled (enable with -DremoteOBR)
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD SUCCESSFUL
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 1 minute 2 seconds
>> [INFO] [INFO] Finished at: Wed Jul 29 14:11:35 EDT 2009
>> [INFO] [INFO] Final Memory: 33M/60M
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Cleaning up after release...
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESSFUL
>>
>>
>>
>> David Jencks wrote:
>>>
>>> On Jul 29, 2009, at 10:33 AM, Kurt T Stam wrote:
>>>
>>>> Right.. still new at this. I can run it now. Will it find the
>>>> geronimo-jaxb_2.1_spec.jar?
>>>
>>> I assume you succeeded in getting that into your local maven repo,
>>> since the regular build succeeded. So it should be available to the
>>> build the maven release plugin tries to do.
>>>
>>> thanks
>>> david jencks
>>>
>>>>
>>>> --Kurt
>>>>
>>>> David Jencks wrote:
>>>>> I checked that the tar.gz source archive is sufficient to build
>>>>> the project and has appropriate legal files, so this is in line
>>>>> with apache policy.
>>>>>
>>>>> However, I think Kurt produced the release candidates from the
>>>>> checkout on which he was running mvn release:prepare and as a
>>>>> result the source archives have a number of files that shouldn't
>>>>> be included:
>>>>> release.properties
>>>>> pom.xml.releaseBackup
>>>>> ..settings
>>>>> ..classpath
>>>>> ..project
>>>>>
>>>>> Also, the release candidate is not in apache nexus and I don't
>>>>> know how you'd deploy it there.
>>>>>
>>>>> I would strongly advise that Kurt run
>>>>>
>>>>> mvn release:perform -Papache-release
>>>>>
>>>>> in the same directory he ran mvn release:prepare
>>>>>
>>>>> This will svn export the tag, build it, and upload the artifacts
>>>>> to apache nexus, ready for promotion.
>>>>>
>>>>> thanks
>>>>> david jencks
>>>>>
>>>>> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> I have staged the scout-1.1 artifacts in
>>>>>>
>>>>>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>>>>>
>>>>>> This is the first time I am using the maven release plugin
>>>>>> (thanks to a lot of help from David Jencks, thank you David), so
>>>>>> hopefully all is ok.
>>>>>>
>>>>>> I simply ran
>>>>>>
>>>>>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw>
>>>>>> -Prelease
>>>>>>
>>>>>> It also created a tag:
>>>>>> http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>>>>>
>>>>>> my vote +1
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> --Kurt
>>>>>>
>>>>>> This release includes he following:
>>>>>>
>>>>>> Bug
>>>>>>
>>>>>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>>>>>> * [SCOUT-80] - copying lists into arrays invites code errors such
>>>>>> as NPEs
>>>>>> * [SCOUT-81] - jaxr-api cannot contain generics
>>>>>> * [SCOUT-83] - Create the derby db in the target dir
>>>>>> * [SCOUT-84] - Users not assigned to Organization properly
>>>>>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace
>>>>>> when not needed
>>>>>>
>>>>>> Improvement
>>>>>>
>>>>>> * [SCOUT-82] - use maven best practices in build
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by David Jencks <da...@yahoo.com>.
Only someone with scout permissions can see this...
go to https://repository.apache.org/
log in (upper right corner) with your apache id and subversion password
click "Staging" in the left hand menu
If you see the scout staging repo, it got staged OK. Now you need to
select the staging repo, it will open a panel in the middle of the page.
If you like what is there, right click and select "close".
This will prevent adding more stuff to the repo and make if publically
visible.
Find the link to it and post it to the vote thread :-)
thanks
david jencks
On Jul 29, 2009, at 11:14 AM, Kurt T Stam wrote:
> OK just ran it, and it looks ok, I think. How do I check that things
> are in nexus?
>
> [INFO] 194b uploaded (scout-1.1-source-release.tar.gz.asc)
> [INFO] Uploading: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ws/scout/scout/1.1/scout-1.1-source-release.zip.asc
> [INFO] 194/194b
> [INFO] 194b uploaded (scout-1.1-source-release.zip.asc
> [INFO] [INFO] [bundle:deploy]
> [INFO] [INFO] Remote OBR update disabled (enable with -DremoteOBR)
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] BUILD SUCCESSFUL
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 1 minute 2 seconds
> [INFO] [INFO] Finished at: Wed Jul 29 14:11:35 EDT 2009
> [INFO] [INFO] Final Memory: 33M/60M
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] Cleaning up after release...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
>
>
>
> David Jencks wrote:
>>
>> On Jul 29, 2009, at 10:33 AM, Kurt T Stam wrote:
>>
>>> Right.. still new at this. I can run it now. Will it find the
>>> geronimo-jaxb_2.1_spec.jar?
>>
>> I assume you succeeded in getting that into your local maven repo,
>> since the regular build succeeded. So it should be available to
>> the build the maven release plugin tries to do.
>>
>> thanks
>> david jencks
>>
>>>
>>> --Kurt
>>>
>>> David Jencks wrote:
>>>> I checked that the tar.gz source archive is sufficient to build
>>>> the project and has appropriate legal files, so this is in line
>>>> with apache policy.
>>>>
>>>> However, I think Kurt produced the release candidates from the
>>>> checkout on which he was running mvn release:prepare and as a
>>>> result the source archives have a number of files that shouldn't
>>>> be included:
>>>> release.properties
>>>> pom.xml.releaseBackup
>>>> ..settings
>>>> ..classpath
>>>> ..project
>>>>
>>>> Also, the release candidate is not in apache nexus and I don't
>>>> know how you'd deploy it there.
>>>>
>>>> I would strongly advise that Kurt run
>>>>
>>>> mvn release:perform -Papache-release
>>>>
>>>> in the same directory he ran mvn release:prepare
>>>>
>>>> This will svn export the tag, build it, and upload the artifacts
>>>> to apache nexus, ready for promotion.
>>>>
>>>> thanks
>>>> david jencks
>>>>
>>>> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>>>>
>>>>> Hi guys,
>>>>>
>>>>> I have staged the scout-1.1 artifacts in
>>>>>
>>>>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>>>>
>>>>> This is the first time I am using the maven release plugin
>>>>> (thanks to a lot of help from David Jencks, thank you David), so
>>>>> hopefully all is ok.
>>>>>
>>>>> I simply ran
>>>>>
>>>>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -
>>>>> Prelease
>>>>>
>>>>> It also created a tag: http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>>>>
>>>>> my vote +1
>>>>>
>>>>> Cheers,
>>>>>
>>>>> --Kurt
>>>>>
>>>>> This release includes he following:
>>>>>
>>>>> Bug
>>>>>
>>>>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>>>>> * [SCOUT-80] - copying lists into arrays invites code errors
>>>>> such as NPEs
>>>>> * [SCOUT-81] - jaxr-api cannot contain generics
>>>>> * [SCOUT-83] - Create the derby db in the target dir
>>>>> * [SCOUT-84] - Users not assigned to Organization properly
>>>>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace
>>>>> when not needed
>>>>>
>>>>> Improvement
>>>>>
>>>>> * [SCOUT-82] - use maven best practices in build
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by Kurt T Stam <ku...@gmail.com>.
OK just ran it, and it looks ok, I think. How do I check that things are
in nexus?
[INFO] 194b uploaded (scout-1.1-source-release.tar.gz.asc)
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ws/scout/scout/1.1/scout-1.1-source-release.zip.asc
[INFO] 194/194b
[INFO] 194b uploaded (scout-1.1-source-release.zip.asc)
[INFO] [INFO] [bundle:deploy]
[INFO] [INFO] Remote OBR update disabled (enable with -DremoteOBR)
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] BUILD SUCCESSFUL
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Total time: 1 minute 2 seconds
[INFO] [INFO] Finished at: Wed Jul 29 14:11:35 EDT 2009
[INFO] [INFO] Final Memory: 33M/60M
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] Cleaning up after release...
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
David Jencks wrote:
>
> On Jul 29, 2009, at 10:33 AM, Kurt T Stam wrote:
>
>> Right.. still new at this. I can run it now. Will it find the
>> geronimo-jaxb_2.1_spec.jar?
>
> I assume you succeeded in getting that into your local maven repo,
> since the regular build succeeded. So it should be available to the
> build the maven release plugin tries to do.
>
> thanks
> david jencks
>
>>
>> --Kurt
>>
>> David Jencks wrote:
>>> I checked that the tar.gz source archive is sufficient to build the
>>> project and has appropriate legal files, so this is in line with
>>> apache policy.
>>>
>>> However, I think Kurt produced the release candidates from the
>>> checkout on which he was running mvn release:prepare and as a result
>>> the source archives have a number of files that shouldn't be included:
>>> release.properties
>>> pom.xml.releaseBackup
>>> ..settings
>>> ..classpath
>>> ..project
>>>
>>> Also, the release candidate is not in apache nexus and I don't know
>>> how you'd deploy it there.
>>>
>>> I would strongly advise that Kurt run
>>>
>>> mvn release:perform -Papache-release
>>>
>>> in the same directory he ran mvn release:prepare
>>>
>>> This will svn export the tag, build it, and upload the artifacts to
>>> apache nexus, ready for promotion.
>>>
>>> thanks
>>> david jencks
>>>
>>> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I have staged the scout-1.1 artifacts in
>>>>
>>>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>>>
>>>> This is the first time I am using the maven release plugin (thanks
>>>> to a lot of help from David Jencks, thank you David), so hopefully
>>>> all is ok.
>>>>
>>>> I simply ran
>>>>
>>>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
>>>>
>>>> It also created a tag:
>>>> http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>>>
>>>> my vote +1
>>>>
>>>> Cheers,
>>>>
>>>> --Kurt
>>>>
>>>> This release includes he following:
>>>>
>>>> Bug
>>>>
>>>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>>>> * [SCOUT-80] - copying lists into arrays invites code errors such
>>>> as NPEs
>>>> * [SCOUT-81] - jaxr-api cannot contain generics
>>>> * [SCOUT-83] - Create the derby db in the target dir
>>>> * [SCOUT-84] - Users not assigned to Organization properly
>>>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
>>>> not needed
>>>>
>>>> Improvement
>>>>
>>>> * [SCOUT-82] - use maven best practices in build
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by David Jencks <da...@yahoo.com>.
On Jul 29, 2009, at 10:33 AM, Kurt T Stam wrote:
> Right.. still new at this. I can run it now. Will it find the
> geronimo-jaxb_2.1_spec.jar?
I assume you succeeded in getting that into your local maven repo,
since the regular build succeeded. So it should be available to the
build the maven release plugin tries to do.
thanks
david jencks
>
> --Kurt
>
> David Jencks wrote:
>> I checked that the tar.gz source archive is sufficient to build the
>> project and has appropriate legal files, so this is in line with
>> apache policy.
>>
>> However, I think Kurt produced the release candidates from the
>> checkout on which he was running mvn release:prepare and as a
>> result the source archives have a number of files that shouldn't be
>> included:
>> release.properties
>> pom.xml.releaseBackup
>> ..settings
>> ..classpath
>> ..project
>>
>> Also, the release candidate is not in apache nexus and I don't know
>> how you'd deploy it there.
>>
>> I would strongly advise that Kurt run
>>
>> mvn release:perform -Papache-release
>>
>> in the same directory he ran mvn release:prepare
>>
>> This will svn export the tag, build it, and upload the artifacts to
>> apache nexus, ready for promotion.
>>
>> thanks
>> david jencks
>>
>> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>>
>>> Hi guys,
>>>
>>> I have staged the scout-1.1 artifacts in
>>>
>>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>>
>>> This is the first time I am using the maven release plugin (thanks
>>> to a lot of help from David Jencks, thank you David), so hopefully
>>> all is ok.
>>>
>>> I simply ran
>>>
>>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -
>>> Prelease
>>>
>>> It also created a tag: http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>>
>>> my vote +1
>>>
>>> Cheers,
>>>
>>> --Kurt
>>>
>>> This release includes he following:
>>>
>>> Bug
>>>
>>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>>> * [SCOUT-80] - copying lists into arrays invites code errors such
>>> as NPEs
>>> * [SCOUT-81] - jaxr-api cannot contain generics
>>> * [SCOUT-83] - Create the derby db in the target dir
>>> * [SCOUT-84] - Users not assigned to Organization properly
>>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace
>>> when not needed
>>>
>>> Improvement
>>>
>>> * [SCOUT-82] - use maven best practices in build
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by Kurt T Stam <ku...@gmail.com>.
Right.. still new at this. I can run it now. Will it find the
geronimo-jaxb_2.1_spec.jar?
--Kurt
David Jencks wrote:
> I checked that the tar.gz source archive is sufficient to build the
> project and has appropriate legal files, so this is in line with
> apache policy.
>
> However, I think Kurt produced the release candidates from the
> checkout on which he was running mvn release:prepare and as a result
> the source archives have a number of files that shouldn't be included:
> release.properties
> pom.xml.releaseBackup
> ..settings
> ..classpath
> ..project
>
> Also, the release candidate is not in apache nexus and I don't know
> how you'd deploy it there.
>
> I would strongly advise that Kurt run
>
> mvn release:perform -Papache-release
>
> in the same directory he ran mvn release:prepare
>
> This will svn export the tag, build it, and upload the artifacts to
> apache nexus, ready for promotion.
>
> thanks
> david jencks
>
> On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
>
>> Hi guys,
>>
>> I have staged the scout-1.1 artifacts in
>>
>> http://people.apache.org/~kstam/staging-site/scout-1.1/
>>
>> This is the first time I am using the maven release plugin (thanks to
>> a lot of help from David Jencks, thank you David), so hopefully all
>> is ok.
>>
>> I simply ran
>>
>> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
>>
>> It also created a tag:
>> http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>>
>> my vote +1
>>
>> Cheers,
>>
>> --Kurt
>>
>> This release includes he following:
>>
>> Bug
>>
>> * [SCOUT-76] - orgKey can be null in ServiceImpl
>> * [SCOUT-80] - copying lists into arrays invites code errors such
>> as NPEs
>> * [SCOUT-81] - jaxr-api cannot contain generics
>> * [SCOUT-83] - Create the derby db in the target dir
>> * [SCOUT-84] - Users not assigned to Organization properly
>> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
>> not needed
>>
>> Improvement
>>
>> * [SCOUT-82] - use maven best practices in build
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by David Jencks <da...@yahoo.com>.
I checked that the tar.gz source archive is sufficient to build the
project and has appropriate legal files, so this is in line with
apache policy.
However, I think Kurt produced the release candidates from the
checkout on which he was running mvn release:prepare and as a result
the source archives have a number of files that shouldn't be included:
release.properties
pom.xml.releaseBackup
..settings
..classpath
..project
Also, the release candidate is not in apache nexus and I don't know
how you'd deploy it there.
I would strongly advise that Kurt run
mvn release:perform -Papache-release
in the same directory he ran mvn release:prepare
This will svn export the tag, build it, and upload the artifacts to
apache nexus, ready for promotion.
thanks
david jencks
On Jul 28, 2009, at 8:30 PM, Kurt T Stam wrote:
> Hi guys,
>
> I have staged the scout-1.1 artifacts in
>
> http://people.apache.org/~kstam/staging-site/scout-1.1/
>
> This is the first time I am using the maven release plugin (thanks
> to a lot of help from David Jencks, thank you David), so hopefully
> all is ok.
>
> I simply ran
>
> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
>
> It also created a tag: http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>
> my vote +1
>
> Cheers,
>
> --Kurt
>
> This release includes he following:
>
> Bug
>
> * [SCOUT-76] - orgKey can be null in ServiceImpl
> * [SCOUT-80] - copying lists into arrays invites code errors such
> as NPEs
> * [SCOUT-81] - jaxr-api cannot contain generics
> * [SCOUT-83] - Create the derby db in the target dir
> * [SCOUT-84] - Users not assigned to Organization properly
> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
> not needed
>
> Improvement
>
> * [SCOUT-82] - use maven best practices in build
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: [VOTE] Release scout-1.1
Posted by Tom Cunningham <tc...@redhat.com>.
+1
Kurt T Stam wrote:
> Hi guys,
>
> I have staged the scout-1.1 artifacts in
>
> http://people.apache.org/~kstam/staging-site/scout-1.1/
>
> This is the first time I am using the maven release plugin (thanks to
> a lot of help from David Jencks, thank you David), so hopefully all is
> ok.
>
> I simply ran
>
> mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
>
> It also created a tag:
> http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
>
> my vote +1
>
> Cheers,
>
> --Kurt
>
> This release includes he following:
>
> Bug
>
> * [SCOUT-76] - orgKey can be null in ServiceImpl
> * [SCOUT-80] - copying lists into arrays invites code errors such
> as NPEs
> * [SCOUT-81] - jaxr-api cannot contain generics
> * [SCOUT-83] - Create the derby db in the target dir
> * [SCOUT-84] - Users not assigned to Organization properly
> * [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
> not needed
>
> Improvement
>
> * [SCOUT-82] - use maven best practices in build
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
RE: [VOTE] Release scout-1.1
Posted by Jeff Faath <jf...@apache.org>.
+1
-----Original Message-----
From: Kurt T Stam [mailto:kurt.stam@gmail.com]
Sent: Tuesday, July 28, 2009 10:30 PM
To: scout-dev@ws.apache.org
Subject: [VOTE] Release scout-1.1
Hi guys,
I have staged the scout-1.1 artifacts in
http://people.apache.org/~kstam/staging-site/scout-1.1/
This is the first time I am using the maven release plugin (thanks to a
lot of help from David Jencks, thank you David), so hopefully all is ok.
I simply ran
mvn -e release:prepare -Dusername=<username> -Dpassword=<pw> -Prelease
It also created a tag:
http://svn.apache.org/repos/asf/webservices/scout/tags/scout-1.1/
my vote +1
Cheers,
--Kurt
This release includes he following:
Bug
* [SCOUT-76] - orgKey can be null in ServiceImpl
* [SCOUT-80] - copying lists into arrays invites code errors such as
NPEs
* [SCOUT-81] - jaxr-api cannot contain generics
* [SCOUT-83] - Create the derby db in the target dir
* [SCOUT-84] - Users not assigned to Organization properly
* [SCOUT-85] - BusinessQueryManager2Test printing stack trace when
not needed
Improvement
* [SCOUT-82] - use maven best practices in build
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org