[
http://jira.codehaus.org/browse/MOJO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135578#action_135578
]
Jon Osborn commented on MOJO-599:
---------------------------------
But if you make a project dependency on the target in question, it will deploy
the war/ear if it finds one.
> Deploy from artifact instead of artifactPath
> --------------------------------------------
>
> Key: MOJO-599
> URL: http://jira.codehaus.org/browse/MOJO-599
> Project: Mojo
> Issue Type: Improvement
> Components: weblogic
> Reporter: Willie Vu
>
> The deploy mojo currently deploys either the artifact built by the current
> project, or the artifact explicitly specified by artifactPath.
> A common use case is to deploy an artifact from repositories. I propose to
> add a configuration called artifact as the following:
> -------------------
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>weblogic-maven-plugin</artifactId>
> <version>2.9.0-SNAPSHOT</version>
> <configuration>
> <artifact>
> <groupId>...</groupId>
> <artifactId>...</artifactId>
> <version>...</version>
> <type>...</type>
> <classifier>...</classifier>
> </artifact>
> </configuration>
> </plugin>
> -------------------
> Then, the artifact is resolved using the following code:
> Artifact artifact = artifactFactory.createArtifactWithClassifier(groupId,
> artifactId, version, type, classifier);
> resolver.resolve(artifact, remoteRepositories, localRepository);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
