But shouldn't my classified artifacts end up in repository the same way, classified 3rd-party artifacts do? Why should it be easy to deploy classified 3rd-parties but hard to deploy own classifieds from a user's point of view?
Since lots of artifacts are developed like this (I'd reckon), how will they end up in the repository then? the current configuration just goes to the repo? I was looking for a classifier-element in maven model, to state an artifacts classifier just as one states its version, groupId, etc. May it be a top-level-element of the pom structure or an element of deploy-plugin's configuration. There's none. But should there be one? No need for it? -Stefan 2006/6/28, dan tran <[EMAIL PROTECTED]>:
yes, deploy:deploy-file is used to deploy thirdary artifacts. In your case, you want to deploy your artifact dynamically depending on env ( profile) during build -D On 6/28/06, Stefan Hübner <[EMAIL PROTECTED]> wrote: > > Is this use case that different from deploying "classified" > 3rd-party-libraries? > > -Stefan > > 2006/6/28, dan tran <[EMAIL PROTECTED]>: > > in that case, the closest i can think of is build-helper-maven-plugin, > not > > sure > > that will solve your issue > > > > -D > > > > > > On 6/28/06, Stefan Hübner <[EMAIL PROTECTED]> wrote: > > > > > > Hi Dan, > > > > > > I've got some artifacts, whose resources get filtered regarding to the > > > environment they'll be running in. So applying classifiers would be > > > the way to distinguish between those differently modified artifacts, I > > > guess. I don't know of a way to apply classifiers to the final > > > artifacts to be deployed. > > > > > > But don't they need to be distinguished in the repository too, once > > > they get deployed? Just as 3rd-party-components. Otherwise one would > > > end up with deployed artifacts, where he can't be sure about their > > > configuration. > > > > > > Or did I miss something here? > > > > > > --Stefan > > > > > > 2006/6/28, dan tran <[EMAIL PROTECTED]>: > > > > what is your use case? > > > > > > > > -D > > > > > > > > > > > > On 6/28/06, Stefan Hübner <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi all, > > > > > > > > > > I'm not sure, if you keep track of closed jira issues. So I > forward my > > > > > question on MDEPLOY-19 to this list: > > > > > > > > > > "Was there any particular reason, to issue this only for the > > > > > deploy-file goal? Doesn't this also make sense for the > deploy-goal?" > > > > > > > > > > If closed issues don't get off your radar, I'm sorry for > > > > > double-posting the comment here. > > > > > > > > > > > > > > > Cheers, > > > > > Stefan > > > > > > > > > > ---------- Forwarded message ---------- > > > > > From: Stefan H?bner (JIRA) <[EMAIL PROTECTED]> > > > > > Date: 28.06.2006 13:21 > > > > > Subject: [jira] Commented: (MDEPLOY-19) Ability to deploy-file as > > > > > classifier > > > > > To: [EMAIL PROTECTED] > > > > > > > > > > > > > > > [ > > > http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_68444] > > > > > > > > > > Stefan Hübner commented on MDEPLOY-19: > > > > > -------------------------------------- > > > > > > > > > > Was there any particular reason, to issue this only for the > > > > > deploy-file goal? Doesn't this also make sense for the > deploy-goal? > > > > > > > > > > > Ability to deploy-file as classifier > > > > > > ------------------------------------ > > > > > > > > > > > > Key: MDEPLOY-19 > > > > > > URL: http://jira.codehaus.org/browse/MDEPLOY-19 > > > > > > Project: Maven 2.x Deploy Plugin > > > > > > Type: New Feature > > > > > > > > > > > Versions: 2.1 > > > > > > Environment: xp > > > > > > Reporter: Dan Tran > > > > > > Assignee: Allan Ramirez > > > > > > Fix For: 2.2 > > > > > > Attachments: MDEPLOY19.diff > > > > > > > > > > > > Time Spent: 2 hours > > > > > > Remaining: 0 minutes > > > > > > > > > > > > deploy-file currently does not support this option > > > > > > > > > > -- > > > > > 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 > > > > > > > > > > > > > > > > > > > > >
