[
https://issues.apache.org/jira/browse/DIRMINA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655164#action_12655164
]
Emmanuel Lecharny commented on DIRMINA-616:
-------------------------------------------
It does not work... The 2.2-beta63-SNAPSHOT does not exist anywhere ...
(skipped some rude sentences about maven ...)
[INFO] A required plugin was not found: Plugin could not be found - check that
the goal name is correct: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.plugins
-DartifactId=maven-assembly-plugin -Dversion=2.2-beta-3-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins
-DartifactId=maven-assembly-plugin -Dversion=2.2-beta-3-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
org.apache.maven.plugins:maven-assembly-plugin:maven-plugin:2.2-beta-3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.apache.maven.plugins:maven-assembly-plugin:maven-plugin:2.2-beta-3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
> New release.xml file
> --------------------
>
> Key: DIRMINA-616
> URL: https://issues.apache.org/jira/browse/DIRMINA-616
> Project: MINA
> Issue Type: Improvement
> Reporter: Barend Garvelink
> Assignee: Julien Vermillard
> Attachments: release.xml
>
>
> In response to http://markmail.org/message/fhjl74dnlyaojrzr , here's an
> updated release.xml file.
> It generally works as it should, but it's affected by
> http://jira.codehaus.org/browse/MASSEMBLY-285, which causes duplicate entries
> in the lib/ directory inside the archive. When extracting the archive using
> 7zip for win32, I get prompted to overwrite/skip/cancel for each duplicate
> entry. Other archivers may file entirely (?). The only work-around I can come
> up with as a fix right now is to add a maven-antrun-plugin to the package
> phase of the root pom which post-processes the release file to fix this. I
> haven't done that, but if MASSEMBLY-285 isn't fixed before the next release,
> we may have to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
