Hi Anders,
Anders Hammar wrote:
> You will be trying to deploy the pom twice (once for each build run) which
> the release repository policy of your Nexus instance will not let you do.
> Thus, the build will fail (as it should).
> But you might be using some tooling will less checking...
No, it
You will be trying to deploy the pom twice (once for each build run) which
the release repository policy of your Nexus instance will not let you do.
Thus, the build will fail (as it should).
But you might be using some tooling will less checking...
/Anders
On Thu, Apr 14, 2011 at 16:15, Jörg Scha
Hi Anders,
Anders Hammar wrote:
> How are you executing one build run that produces both artifacts? Are you
> really deploying to a repository? I can't see how that would work, but I
> could be missing something.
Why do you have to? Even for a release you don't have to release the
component in
Interesting solution. thanks! I will consult
2011/4/13 Jörg Schaible
> Hi,
>
> Fernando Wermus wrote:
>
> > Hi all,
> > We have a proyect which we need to compile under java 1.4 for some
> > companies and 1.6 for other companies. The problem is that in java 1.6 we
> > have a class that imple
How are you executing one build run that produces both artifacts? Are you
really deploying to a repository? I can't see how that would work, but I
could be missing something.
/Anders
On Thu, Apr 14, 2011 at 12:00, Jörg Schaible wrote:
> Hi Anders,
>
> Anders Hammar wrote:
>
> > I strongly recomm
Hi Anders,
Anders Hammar wrote:
> I strongly recommend staying away from profiles (and having multiple
> artifacts being produced by one Maven project). Sooner or later it will
> bit you. Also, in a true Maven build, you only do one build (including
> deploying to the repository) and therefore ha
I strongly recommend staying away from profiles (and having multiple
artifacts being produced by one Maven project). Sooner or later it will bit
you. Also, in a true Maven build, you only do one build (including deploying
to the repository) and therefore having different profiles being activated
ba
Hi,
Fernando Wermus wrote:
> Hi all,
> We have a proyect which we need to compile under java 1.4 for some
> companies and 1.6 for other companies. The problem is that in java 1.6 we
> have a class that implements an interface named ResulSet. Result changes
> its methods from 1.4 to 1.6 becaus
On 13/04/2011 10:52 AM, Fernando Wermus wrote:
Alex,
My boss rejects this option. Any idea?
Did he give any reason why?
Does he have a solution that he would suggest?
If you have modules that have different functionality, they are
different modules regardless of why the functionality is
Alex,
My boss rejects this option. Any idea?
2011/4/13 Alex Lopez
> Yes, the thing is create 2 projects (in fact 3).
>
> So you can include same classes/packages in different jars (different
> projects). And have the 3rd project depend on each of the others depending
> on the active profile.
Yes, the thing is create 2 projects (in fact 3).
So you can include same classes/packages in different jars (different
projects). And have the 3rd project depend on each of the others
depending on the active profile.
I don't know how to do it with only one project... Of course there might
be
Alex,
I understand your proposal. Do I need to create two proyects for this
situation or could I avoid this?
2011/4/13 Alex Lopez
> Make the classes into different jars (java 1.4 and 1.6) and add one ore the
> other as dependencies under different profiles.
>
> Em 13-04-2011 15:01, Fernando
Make the classes into different jars (java 1.4 and 1.6) and add one ore
the other as dependencies under different profiles.
Em 13-04-2011 15:01, Fernando Wermus escreveu:
Hi all,
We have a proyect which we need to compile under java 1.4 for some
companies and 1.6 for other companies. The p
13 matches
Mail list logo
