Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed the attach goal to always copy the artifacts to the build direct... #3

Merged
merged 2 commits into from
May 9, 2012

Conversation

nawroth
Copy link
Contributor

@nawroth nawroth commented May 8, 2012

...ory. Added an attachsignatures goal which will attach existing signatures with the project.

Signatures can now be attached and are included in the deploy.

Note: I haven't verified that they are correct as well.

Also, the project configured for deploy will upload signatures for all classifiers existing somewhere in the attached artifacts, but for itself instead. Looks weird.

This one is for @simpsonjulian

…ectory. Added an attachsignatures goal which will attach existing signatures with the project.
@nawroth
Copy link
Contributor Author

nawroth commented May 9, 2012

@simpsonjulian I fixed the issues I found. Also verified that the signatures are ok. The only artifact from the deploy project itself that gets deployed is the pom (and its signature), which is kind of unavoidable. Other than that, only the attached artifacts are deployed.

simpsonjulian added a commit that referenced this pull request May 9, 2012
Changed the attach goal to always copy the artifacts to the build direct...
@simpsonjulian simpsonjulian merged commit 6a8ccd5 into neo4j:master May 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants