stumbled on the same issue as Antom, and I have provided a pull
request to activate custom profile.
Check it out here : https://github.com/heroku/heroku-buildpack-java/pull/5

On 4 avr, 20:11, James Ward <[email protected]> wrote:
> Right now there isn't a good way to handle that.  To change the command
> that is used to run the Maven build, you can fork the 
> buildpack:https://github.com/heroku/heroku-buildpack-java
>
> Hope that helps.
>
> -James
>
> On 03/27/2012 11:52 PM, Anton Naumov wrote:
>
>
>
>
>
>
>
> > Hi everyone,
>
> > I'm trying to deploy Java application to Heroku and everything looks
> > good except one important detail. I have a profiles configured inside
> > my pom.xml and activated by environment variable. On my local machine
> > activation works exactly like expected, but on Heroku side I've always
> > got default profile activated.
> > Is it any chance to configure environment or pom.xml to activate
> > correct Maven profile?
>
> > Thank you in advance.
>
> > Regards,
> > Anton

-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

Reply via email to