good point there. id opt for the simple solution too.
On Thu, Dec 9, 2010 at 10:18 AM, Ron Wheeler <rwhee...@artifact-software.com > wrote: > On 09/12/2010 1:08 PM, Jon Paynter wrote: > >> why 2 projects? >> it seems 1 maven project with profiles and a batch script will work >> >> something like so: >> mvn deploy -P SunProfileName >> mvn deploy -P IBMProfileName >> > If it works, I would have no objection but 2 projects will work for sure > and everyone knows how to set up a simple project. > The same can not be said about profiles and they seem to encourage complex > solutions that generate lots of traffic and frustrated Maven users here. > > Sometimes it is a lot easier to do 2 simple things that are 90% identical > than 1 complex thing that has no redundant code. > > Ron > > > On Thu, Dec 9, 2010 at 5:15 AM, Ron Wheeler >> <rwhee...@artifact-software.com>wrote: >> >> On 09/12/2010 7:52 AM, Asmann, Roland wrote: >>> >>> On 09.12.2010 11:29, Stephen Connolly wrote: >>>> >>>> you need to add an exclusion on the dependency that is being brought in >>>>> by >>>>> profile activation. >>>>> >>>>> It was a mistake that profiles include the<dependency> section as >>>>> there >>>>> is >>>>> all manor of issues. >>>>> >>>>> The profile gets activated based on the environment where maven is >>>>> running, >>>>> not the environment where the artifact is deployed. >>>>> >>>>> If you have 3rd party deps that use profile activation to pull in >>>>> dependencies, you will need to define exclusions on those >>>>> dependencies... >>>>> that will stabilise your build. >>>>> >>>>> If your build uses profile activation to pull in dependencies, that is >>>>> your >>>>> bad, take it out >>>>> >>>>> -Stephen >>>>> >>>>> No, this is NOT the solution, since I will need the artifact on both >>>>> SUN >>>>> >>>> and JDK machines. The problem is that when I build with only one of >>>> those, I can also only deploy it to one of those! Therefor, I need to >>>> build one artifact with IBM JDK, which will then be deployed to the IBM >>>> JDK server, and one with SUN, which will likewise be deployed to the SUN >>>> server. >>>> >>>> I understand that I can build both versions on either JDK by either >>>> adding or excluding dependencies, the fact is that I don't want to do >>>> this manually, but let Maven handle it (as it can!) depending on which >>>> JDK I build. >>>> >>>> >>>> Like I said before, the real problem is that I want to have my release >>> >>>> build BOTH artifacts at once, and I am not sure how I could achieve this >>>> goal... >>>> >>>> 2 maven projects and a batch script. >>>> >>> Ron >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
