[mojo-dev] [jira] (MRPM-185) Predictable final RPM location

[Sergei Ivanov (JIRA)]

Title: Message Title

Sergei Ivanov commented on an issue   Re: Predictable final RPM location If the RPM was earlier attached to the build as an artifact, you can use something like this to locate it (type will be "rpm", classifier can either be null or be optionally configured via plugin parameters): private Artifact getAttachedArtifact(final String type, final String classifier) throws MojoFailureException { Artifact result = null; final List<Artifact> attachedArtifacts = project.getAttachedArtifacts(); for (final Artifact artifact : attachedArtifacts) { if (type.equals(artifact.getType())) { if (StringUtils.equals(classifier, artifact.getClassifier())) { result = artifact; } } } if (result == null) { throw new MojoFailureException("Unable to locate the attached artifact"); } return result; } ...then you can use artifact.getFile().getAbsolutePath() to retrieve the file location. Add Comment   Mojo's RPM Maven Plugin / MRPM-185 Predictable final RPM location I have a requirement to deploy RPM into another box during build. I plan to write a custom plugin to push the rpm out, however, it is not possible to programmatically determine the RPM location after it is created in my polo since the rpm path is dynamically named This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email