Skip to content

Consider a copy goal #11

Closed
Closed

Description

@hinerm

We should investigate whether a copy goal would be necessary. The question is if maven-resources-plugin:copy-resources is sufficient.

See SO post.

Activity

  1. ctrueden commented on Feb 13, 2015

    @ctrueden
    Member

    There is also dependency:copy. But actually, what I meant in my email was actually an improvement to the imagej-maven-plugin to specifically support copying "bare" resources (e.g., scripts and configuration files) into a desired place in an ImageJ directory structure. We could use the convention of src/main/imagej for this, which the plugin would pick up on and copy appropriately. Such a feature would be necessary to make the fiji.git build fully replicate a Fiji user installation from scratch.

  2. ctrueden commented on Mar 19, 2015

    @ctrueden
    Member

    OK, I should file a separate issue for the imagej-maven-plugin level resources thing.

  3. ctrueden commented on Mar 23, 2015

    @ctrueden
    Member

    Upon consideration, let's close this in favor of imagej/imagej-maven-plugin#11. I do not think we need a general-purpose scijava:copy goal; we can reopen later if we find a use case for it beyond the imagej-maven-plugin use case.

  4. added 3 commits that reference this issue on Nov 13, 2021
    10285bc
    4098bdf
    5550404
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions