Hi Grant,

do you think you could just run the ant target
"generate-maven-artifacts", which will deploy to the local dist dir, and
then have the build script copy it using scp?

We could use the maven-ant-tasks for that, but the "wagon-ssh" provider,
which is needed for scp, seems to be in beta state, which makes me
nervous. Also, using scp in the build script seems easier to implement.

Would that work?

-Michael

Grant Ingersoll wrote:
> Funny, I was just thinking of looking into setting up snapshot
> publishing.  Let me know what needs to be done to hook it up into the
> build process and I can take care of that.
> 
> Right now, Zones uses scp to copy the website to p.a.o, but we should be
> able to setup scp for M2 using the distribution management tag, right? 
> Nightly builds are currently hosted on zones.
> 
> -Grant
> 
> On Oct 31, 2007, at 9:21 PM, Michael Busch (JIRA) wrote:
> 
>>
>>     [
>> https://issues.apache.org/jira/browse/LUCENE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>  ]
>>
>>
>> Michael Busch updated LUCENE-935:
>> ---------------------------------
>>
>>    Attachment: lucene-935-new.patch
>>
>> This small patch adds the property "m2.repository.url", that defaults to
>> "file://${maven.dist.dir}". You easily can set a different value:
>>  ant -Dm2.repository.url="file://C:\temp\maven"
>>
>> I'm going to commit this now. In case our build machine cannot deploy to
>> the snapshot repository using the local path
>> "file:///www/people.apache.org/maven-snapshot-repository" let me know
>> please, then we'll have to register a provider for an appropriate
>> transfer
>> protocol.
>>
>>> Improve maven artifacts
>>> -----------------------
>>>
>>>                Key: LUCENE-935
>>>                URL: https://issues.apache.org/jira/browse/LUCENE-935
>>>            Project: Lucene - Java
>>>         Issue Type: Improvement
>>>         Components: Build
>>>           Reporter: Michael Busch
>>>           Assignee: Michael Busch
>>>           Priority: Minor
>>>            Fix For: 2.3
>>>
>>>        Attachments: lucene-935-new.patch,
>>> lucene-935-rename-poms.patch, lucene-935.patch
>>>
>>>
>>> There are a couple of things we can improve for the next release:
>>> - "*pom.xml" files should be renamed to "*pom.xml.template"
>>> - artifacts "lucene-parent" should extend "apache-parent"
>>> - add source jars as artifacts
>>> - update <generate-maven-artifacts> task to work with latest version
>>> of maven-ant-tasks.jar
>>> - metadata filenames should not contain "local"
>>
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> --------------------------
> Grant Ingersoll
> http://lucene.grantingersoll.com
> 
> Lucene Boot Camp Training:
> ApacheCon Atlanta, Nov. 12, 2007.  Sign up now!  http://www.apachecon.com
> 
> Lucene Helpful Hints:
> http://wiki.apache.org/lucene-java/BasicsOfPerformance
> http://wiki.apache.org/lucene-java/LuceneFAQ
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to