[
https://issues.apache.org/jira/browse/LUCENE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547913
]
Grant Ingersoll commented on LUCENE-935:
----------------------------------------
OK, now we just need to figure out how best to incorporate it into nightly.sh.
Part of the problem is Hudson is the account running nightly.sh and it doesn't
have an account on p.a.o. Thus, the need for Hudson to access a private key of
one of us w/ a zones account. I don't really like this idea.
Does generate-maven-artifacts fail if the remote repo stuff is not specified?
That is, can it still just generate the artifacts, but not publish them?
Perhaps a better approach would be to separate out generation from publication.
This would allow us at release time to publish to the main repo, but still use
the cron job for nightly.
> 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
> Attachments: lucene-935-new.patch, lucene-935-remote-repos.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]
