You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2013/07/10 21:53:48 UTC

release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

I've bumped up against lots of circular dependencies.  My last attempt to break
these worked locally, but not for mvn release:prepare.

I'm going to try the following:

1) release each artifact separately, starting with the
uima-build-helper-maven-plugin

1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
the staging repo.

1b) I'll "close" that staging repo, making it available

1c) following

http://uima.apache.org/testing-builds.html

I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.

2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.

3) close the 2nd staging repo, and post a vote with both of these.

Hope this works... -Marshall


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
On 7/11/2013 10:45 AM, Richard Eckart de Castilho wrote:
> When the uima-build-helper-maven-plugin doesn't use the uima-wide parent pom
> anymore, then it doesn't need to run in the same release build as the uima-wide parent pom.
>
> I was suggesting that uima-build-helper-maven-plugin should be disconnected from the
> uima-wide parent pom - and that it should be released separately from the 
> uima-wide parent pom. After that, the uima-wide parent pom can pick it up from Maven Central.
Yes, that would work too.  I was trying to avoid doing 2 release votes, and
combining them into just 1 :-)

I've just done the release of both things, and will post the vote.

-Marshall

> -- Richard
>
> Am 11.07.2013 um 16:32 schrieb Marshall Schor <ms...@schor.com>:
>
>> good idea :-)  I tried that...  I had the uima-build-helper-maven-plugin use
>> (for its parent pom) an older version of the uima-wide parent pom.
>>
>> The uima-build-helper-maven-plugin builds fine.
>>
>> What breaks I think is the dependency in the being-released parent-pom, on v 6
>> (no snapshot) of the uima-build-helper-maven-plugin.  Even though maven's built
>> it, the release process doesn't seem to be able find it where it can make use of it.
>>
>> -Marshall
>>
>> On 7/11/2013 10:11 AM, Richard Eckart de Castilho wrote:
>>> Maybe build-critical stuff like the maven build helper should not use the
>>> global uima parent pom at all. 99% of the stuff in there doesn't apply to it.
>>> Couldn't it directly use the global Apache POM and do the small stuff 
>>> it needs locally?
>>>
>>> -- Richard
>>>
>>> Am 11.07.2013 um 15:23 schrieb Marshall Schor <ms...@schor.com>:
>>>
>>>> On 7/10/2013 6:04 PM, Marshall Schor wrote:
>>>>> I tried that.  It worked ok for normal builds, but release:prepare did something
>>>>> that made it fail.
>>>> I think that Maven release:prepare isn't set up to do same-level releases of
>>>> multiple components, when one of them is a maven plugin that is specified to be
>>>> used in the build...
>>>>
>>>> -Marshall
>>>>> I didn't spend time to investigate, though...
>>>>>
>>>>> -Marshall
>>>>>
>>>>> On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
>>>>>> Why not release them at the same time (making them modules again)?
>>>>>>
>>>>>> -- Richard
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Richard Eckart de Castilho <ri...@gmail.com>.
When the uima-build-helper-maven-plugin doesn't use the uima-wide parent pom
anymore, then it doesn't need to run in the same release build as the uima-wide parent pom.

I was suggesting that uima-build-helper-maven-plugin should be disconnected from the
uima-wide parent pom - and that it should be released separately from the 
uima-wide parent pom. After that, the uima-wide parent pom can pick it up from Maven Central.

-- Richard

Am 11.07.2013 um 16:32 schrieb Marshall Schor <ms...@schor.com>:

> good idea :-)  I tried that...  I had the uima-build-helper-maven-plugin use
> (for its parent pom) an older version of the uima-wide parent pom.
> 
> The uima-build-helper-maven-plugin builds fine.
> 
> What breaks I think is the dependency in the being-released parent-pom, on v 6
> (no snapshot) of the uima-build-helper-maven-plugin.  Even though maven's built
> it, the release process doesn't seem to be able find it where it can make use of it.
> 
> -Marshall
> 
> On 7/11/2013 10:11 AM, Richard Eckart de Castilho wrote:
>> Maybe build-critical stuff like the maven build helper should not use the
>> global uima parent pom at all. 99% of the stuff in there doesn't apply to it.
>> Couldn't it directly use the global Apache POM and do the small stuff 
>> it needs locally?
>> 
>> -- Richard
>> 
>> Am 11.07.2013 um 15:23 schrieb Marshall Schor <ms...@schor.com>:
>> 
>>> On 7/10/2013 6:04 PM, Marshall Schor wrote:
>>>> I tried that.  It worked ok for normal builds, but release:prepare did something
>>>> that made it fail.
>>> I think that Maven release:prepare isn't set up to do same-level releases of
>>> multiple components, when one of them is a maven plugin that is specified to be
>>> used in the build...
>>> 
>>> -Marshall
>>>> I didn't spend time to investigate, though...
>>>> 
>>>> -Marshall
>>>> 
>>>> On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
>>>>> Why not release them at the same time (making them modules again)?
>>>>> 
>>>>> -- Richard


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
good idea :-)  I tried that...  I had the uima-build-helper-maven-plugin use
(for its parent pom) an older version of the uima-wide parent pom.

The uima-build-helper-maven-plugin builds fine.

What breaks I think is the dependency in the being-released parent-pom, on v 6
(no snapshot) of the uima-build-helper-maven-plugin.  Even though maven's built
it, the release process doesn't seem to be able find it where it can make use of it.

-Marshall

On 7/11/2013 10:11 AM, Richard Eckart de Castilho wrote:
> Maybe build-critical stuff like the maven build helper should not use the
> global uima parent pom at all. 99% of the stuff in there doesn't apply to it.
> Couldn't it directly use the global Apache POM and do the small stuff 
> it needs locally?
>
> -- Richard
>
> Am 11.07.2013 um 15:23 schrieb Marshall Schor <ms...@schor.com>:
>
>> On 7/10/2013 6:04 PM, Marshall Schor wrote:
>>> I tried that.  It worked ok for normal builds, but release:prepare did something
>>> that made it fail.
>> I think that Maven release:prepare isn't set up to do same-level releases of
>> multiple components, when one of them is a maven plugin that is specified to be
>> used in the build...
>>
>> -Marshall
>>> I didn't spend time to investigate, though...
>>>
>>> -Marshall
>>>
>>> On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
>>>> Why not release them at the same time (making them modules again)?
>>>>
>>>> -- Richard
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Richard Eckart de Castilho <ri...@gmail.com>.
Maybe build-critical stuff like the maven build helper should not use the
global uima parent pom at all. 99% of the stuff in there doesn't apply to it.
Couldn't it directly use the global Apache POM and do the small stuff 
it needs locally?

-- Richard

Am 11.07.2013 um 15:23 schrieb Marshall Schor <ms...@schor.com>:

> 
> On 7/10/2013 6:04 PM, Marshall Schor wrote:
>> I tried that.  It worked ok for normal builds, but release:prepare did something
>> that made it fail.
> I think that Maven release:prepare isn't set up to do same-level releases of
> multiple components, when one of them is a maven plugin that is specified to be
> used in the build...
> 
> -Marshall
>> 
>> I didn't spend time to investigate, though...
>> 
>> -Marshall
>> 
>> On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
>>> Why not release them at the same time (making them modules again)?
>>> 
>>> -- Richard


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
On 7/10/2013 6:04 PM, Marshall Schor wrote:
> I tried that.  It worked ok for normal builds, but release:prepare did something
> that made it fail.
I think that Maven release:prepare isn't set up to do same-level releases of
multiple components, when one of them is a maven plugin that is specified to be
used in the build...

-Marshall
>
> I didn't spend time to investigate, though...
>
> -Marshall
>
> On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
>> Why not release them at the same time (making them modules again)?
>>
>> -- Richard
>>
>> Am 10.07.2013 um 21:53 schrieb Marshall Schor <ms...@schor.com>:
>>
>>> I've bumped up against lots of circular dependencies.  My last attempt to break
>>> these worked locally, but not for mvn release:prepare.
>>>
>>> I'm going to try the following:
>>>
>>> 1) release each artifact separately, starting with the
>>> uima-build-helper-maven-plugin
>>>
>>> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
>>> the staging repo.
>>>
>>> 1b) I'll "close" that staging repo, making it available
>>>
>>> 1c) following
>>>
>>> http://uima.apache.org/testing-builds.html
>>>
>>> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>>>
>>> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>>>
>>> 3) close the 2nd staging repo, and post a vote with both of these.
>>>
>>> Hope this works... -Marshall
>>>
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
I tried that.  It worked ok for normal builds, but release:prepare did something
that made it fail.

I didn't spend time to investigate, though...

-Marshall

On 7/10/2013 5:27 PM, Richard Eckart de Castilho wrote:
> Why not release them at the same time (making them modules again)?
>
> -- Richard
>
> Am 10.07.2013 um 21:53 schrieb Marshall Schor <ms...@schor.com>:
>
>> I've bumped up against lots of circular dependencies.  My last attempt to break
>> these worked locally, but not for mvn release:prepare.
>>
>> I'm going to try the following:
>>
>> 1) release each artifact separately, starting with the
>> uima-build-helper-maven-plugin
>>
>> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
>> the staging repo.
>>
>> 1b) I'll "close" that staging repo, making it available
>>
>> 1c) following
>>
>> http://uima.apache.org/testing-builds.html
>>
>> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>>
>> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>>
>> 3) close the 2nd staging repo, and post a vote with both of these.
>>
>> Hope this works... -Marshall
>>
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Richard Eckart de Castilho <ri...@gmail.com>.
Why not release them at the same time (making them modules again)?

-- Richard

Am 10.07.2013 um 21:53 schrieb Marshall Schor <ms...@schor.com>:

> I've bumped up against lots of circular dependencies.  My last attempt to break
> these worked locally, but not for mvn release:prepare.
> 
> I'm going to try the following:
> 
> 1) release each artifact separately, starting with the
> uima-build-helper-maven-plugin
> 
> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
> the staging repo.
> 
> 1b) I'll "close" that staging repo, making it available
> 
> 1c) following
> 
> http://uima.apache.org/testing-builds.html
> 
> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
> 
> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
> 
> 3) close the 2nd staging repo, and post a vote with both of these.
> 
> Hope this works... -Marshall
> 


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
Some more interesting things.

Other's had already found (was a comment in the jcasgen-maven-plugin) this issue:
http://jira.codehaus.org/browse/MNG-5346

which has a work-around, which doesn't work when building from clean... -- for
the goal "helpmojo".

The workaround I'm adopting is this one, but leaving out the help mojo config. 
That way, any builds from clean (including release:prepare) which involves
running this, will get an error - signalling to the release manager that the
helpmojo function won't work without doing a pre-compile, if you really want to
do this...

I'll stick this configuration in the plugin-management of the parent-pom, too. 
Jira coming up.

-Marshall

On 7/10/2013 6:21 PM, Marshall Schor wrote:
> After a bit more thought:
>
> I'm wondering if it would be best to just remove the helpmojo goal (which is the
> root cause of needing 2 compiles), and then just change the phase for the
> descriptor goal to make it run after the compile step.
>
> -Marshall
>
> On 7/10/2013 6:10 PM, Marshall Schor wrote:
>> Found some Jiras posted against the maven-plugin-plugin related to this.
>>
>> It seems that there are some issues with the current design:
>>
>>   - if you specify maven plugin mojo parameters, as Java 5 Annotations, they are
>> scanned for in the .class files.  This is fine if the class files are there. 
>> But for the helpmojo goal, that is run "before" compiling things (because it is
>> going to generate source code to be included in the compile).  So it is run in a
>> lifecycle phase *before* the compile step, and therefore finds no annotations.
>>
>> This is an open issue
>> http://jira.codehaus.org/browse/MPLUGIN-238
>>
>> I see also that other goals we use for this plugin, e.g. "descriptor", also need
>> the annotations.
>>
>> The suggestion in the above Jira to set the <skipErrorNoDescriptorsFound> flag
>> to true lets the build proceed, but the resulting build is missing all the info
>> that the plugin-plugin was supposed to extract.
>>
>> I'm implementing a work-around for this, which I've tested: to do an "extra"
>> compile step before the generate-sources phase, so that the annotations will be
>> available for the plugin-plugin.  This approach makes it work, with the right data.
>>
>> I'll put this extra compile step in the generate-resources phase, and move the
>> phase for running the 2 plugin-plugin goals that need this annotation metadata
>> (the helpmojo and descriptor goals) to the phase right after generate-resources
>> and before compile  -- process-resources.
>>
>> Hopefully, that will cover all the needed cases.
>>
>> ======
>> If you're wondering why you haven't seen this in "normal" mvn install style of
>> building maven plugins, it's because you didn't try mvn clean plugin.  Without
>> the "clean", the compiled classes are typically there (from Eclipse building),
>> and so the annotations would be found.  mvn release does a "clean" style build.
>> ======
>>
>> -Marshall
>>
>> On 7/10/2013 4:27 PM, Marshall Schor wrote:
>>> Next issue -
>>>
>>> The uima-build-helper-maven-plugin now builds fine by itself.  But within
>>> release:prepare, it fails at the generated-helpmojo step.  This runs the
>>> helpmojo goal of the maven-plugin-plugin.  I ran this in debug mode, and find it
>>> doesn't seem to scan the project java source that it does fine when doing this
>>> outside of release:prepare.
>>>
>>> investigating...
>>>
>>> -Marshall
>>>
>>> On 7/10/2013 3:53 PM, Marshall Schor wrote:
>>>> I've bumped up against lots of circular dependencies.  My last attempt to break
>>>> these worked locally, but not for mvn release:prepare.
>>>>
>>>> I'm going to try the following:
>>>>
>>>> 1) release each artifact separately, starting with the
>>>> uima-build-helper-maven-plugin
>>>>
>>>> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
>>>> the staging repo.
>>>>
>>>> 1b) I'll "close" that staging repo, making it available
>>>>
>>>> 1c) following
>>>>
>>>> http://uima.apache.org/testing-builds.html
>>>>
>>>> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>>>>
>>>> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>>>>
>>>> 3) close the 2nd staging repo, and post a vote with both of these.
>>>>
>>>> Hope this works... -Marshall
>>>>
>>>>
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
After a bit more thought:

I'm wondering if it would be best to just remove the helpmojo goal (which is the
root cause of needing 2 compiles), and then just change the phase for the
descriptor goal to make it run after the compile step.

-Marshall

On 7/10/2013 6:10 PM, Marshall Schor wrote:
> Found some Jiras posted against the maven-plugin-plugin related to this.
>
> It seems that there are some issues with the current design:
>
>   - if you specify maven plugin mojo parameters, as Java 5 Annotations, they are
> scanned for in the .class files.  This is fine if the class files are there. 
> But for the helpmojo goal, that is run "before" compiling things (because it is
> going to generate source code to be included in the compile).  So it is run in a
> lifecycle phase *before* the compile step, and therefore finds no annotations.
>
> This is an open issue
> http://jira.codehaus.org/browse/MPLUGIN-238
>
> I see also that other goals we use for this plugin, e.g. "descriptor", also need
> the annotations.
>
> The suggestion in the above Jira to set the <skipErrorNoDescriptorsFound> flag
> to true lets the build proceed, but the resulting build is missing all the info
> that the plugin-plugin was supposed to extract.
>
> I'm implementing a work-around for this, which I've tested: to do an "extra"
> compile step before the generate-sources phase, so that the annotations will be
> available for the plugin-plugin.  This approach makes it work, with the right data.
>
> I'll put this extra compile step in the generate-resources phase, and move the
> phase for running the 2 plugin-plugin goals that need this annotation metadata
> (the helpmojo and descriptor goals) to the phase right after generate-resources
> and before compile  -- process-resources.
>
> Hopefully, that will cover all the needed cases.
>
> ======
> If you're wondering why you haven't seen this in "normal" mvn install style of
> building maven plugins, it's because you didn't try mvn clean plugin.  Without
> the "clean", the compiled classes are typically there (from Eclipse building),
> and so the annotations would be found.  mvn release does a "clean" style build.
> ======
>
> -Marshall
>
> On 7/10/2013 4:27 PM, Marshall Schor wrote:
>> Next issue -
>>
>> The uima-build-helper-maven-plugin now builds fine by itself.  But within
>> release:prepare, it fails at the generated-helpmojo step.  This runs the
>> helpmojo goal of the maven-plugin-plugin.  I ran this in debug mode, and find it
>> doesn't seem to scan the project java source that it does fine when doing this
>> outside of release:prepare.
>>
>> investigating...
>>
>> -Marshall
>>
>> On 7/10/2013 3:53 PM, Marshall Schor wrote:
>>> I've bumped up against lots of circular dependencies.  My last attempt to break
>>> these worked locally, but not for mvn release:prepare.
>>>
>>> I'm going to try the following:
>>>
>>> 1) release each artifact separately, starting with the
>>> uima-build-helper-maven-plugin
>>>
>>> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
>>> the staging repo.
>>>
>>> 1b) I'll "close" that staging repo, making it available
>>>
>>> 1c) following
>>>
>>> http://uima.apache.org/testing-builds.html
>>>
>>> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>>>
>>> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>>>
>>> 3) close the 2nd staging repo, and post a vote with both of these.
>>>
>>> Hope this works... -Marshall
>>>
>>>
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
Found some Jiras posted against the maven-plugin-plugin related to this.

It seems that there are some issues with the current design:

  - if you specify maven plugin mojo parameters, as Java 5 Annotations, they are
scanned for in the .class files.  This is fine if the class files are there. 
But for the helpmojo goal, that is run "before" compiling things (because it is
going to generate source code to be included in the compile).  So it is run in a
lifecycle phase *before* the compile step, and therefore finds no annotations.

This is an open issue
http://jira.codehaus.org/browse/MPLUGIN-238

I see also that other goals we use for this plugin, e.g. "descriptor", also need
the annotations.

The suggestion in the above Jira to set the <skipErrorNoDescriptorsFound> flag
to true lets the build proceed, but the resulting build is missing all the info
that the plugin-plugin was supposed to extract.

I'm implementing a work-around for this, which I've tested: to do an "extra"
compile step before the generate-sources phase, so that the annotations will be
available for the plugin-plugin.  This approach makes it work, with the right data.

I'll put this extra compile step in the generate-resources phase, and move the
phase for running the 2 plugin-plugin goals that need this annotation metadata
(the helpmojo and descriptor goals) to the phase right after generate-resources
and before compile  -- process-resources.

Hopefully, that will cover all the needed cases.

======
If you're wondering why you haven't seen this in "normal" mvn install style of
building maven plugins, it's because you didn't try mvn clean plugin.  Without
the "clean", the compiled classes are typically there (from Eclipse building),
and so the annotations would be found.  mvn release does a "clean" style build.
======

-Marshall

On 7/10/2013 4:27 PM, Marshall Schor wrote:
> Next issue -
>
> The uima-build-helper-maven-plugin now builds fine by itself.  But within
> release:prepare, it fails at the generated-helpmojo step.  This runs the
> helpmojo goal of the maven-plugin-plugin.  I ran this in debug mode, and find it
> doesn't seem to scan the project java source that it does fine when doing this
> outside of release:prepare.
>
> investigating...
>
> -Marshall
>
> On 7/10/2013 3:53 PM, Marshall Schor wrote:
>> I've bumped up against lots of circular dependencies.  My last attempt to break
>> these worked locally, but not for mvn release:prepare.
>>
>> I'm going to try the following:
>>
>> 1) release each artifact separately, starting with the
>> uima-build-helper-maven-plugin
>>
>> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
>> the staging repo.
>>
>> 1b) I'll "close" that staging repo, making it available
>>
>> 1c) following
>>
>> http://uima.apache.org/testing-builds.html
>>
>> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>>
>> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>>
>> 3) close the 2nd staging repo, and post a vote with both of these.
>>
>> Hope this works... -Marshall
>>
>>
>


Re: release plan for v 6 of parent-pom and uima-build-helper-maven-plugin

Posted by Marshall Schor <ms...@schor.com>.
Next issue -

The uima-build-helper-maven-plugin now builds fine by itself.  But within
release:prepare, it fails at the generated-helpmojo step.  This runs the
helpmojo goal of the maven-plugin-plugin.  I ran this in debug mode, and find it
doesn't seem to scan the project java source that it does fine when doing this
outside of release:prepare.

investigating...

-Marshall

On 7/10/2013 3:53 PM, Marshall Schor wrote:
> I've bumped up against lots of circular dependencies.  My last attempt to break
> these worked locally, but not for mvn release:prepare.
>
> I'm going to try the following:
>
> 1) release each artifact separately, starting with the
> uima-build-helper-maven-plugin
>
> 1a) uima-build-helper-maven-plugin v 6-SNAPSHOT becomes an rc at Version 6, in
> the staging repo.
>
> 1b) I'll "close" that staging repo, making it available
>
> 1c) following
>
> http://uima.apache.org/testing-builds.html
>
> I'll set up my .settings to include the staging repo's "v 6" of the uima-build-helper-maven-plugin.
>
> 2) release parent-pom: this specifies v 6 of the uima-build-helper-maven-plugin, and will find it in the staging repo.
>
> 3) close the 2nd staging repo, and post a vote with both of these.
>
> Hope this works... -Marshall
>
>