I think you are structuring this all upside down
have a root aggregator pom
have child projects
release all as one in one go
On 2 November 2010 13:16, Leon Rosenberg wrote:
> Ok, first of all thank you for your time and let me understand what
> the "maven way" means for me in this case:
> I ta
Ok, first of all thank you for your time and let me understand what
the "maven way" means for me in this case:
I take the project and make 2 out of it, like
xyz-generators module and
xyz-generators-test module, as well as
xyz-runtime module.
Whenever I'm releasing xyz-generators they are actually
On 2 November 2010 11:54, Justin Lee wrote:
> I do something simliar but I use two modules. My very first module builds
> various build related tools such as apt plugins. Then subsequent modules
> depend on that first module.
>
And that is the "Maven way"
> On Tue, Nov 2, 2010 at 7:25 AM, Step
I do something simliar but I use two modules. My very first module builds
various build related tools such as apt plugins. Then subsequent modules
depend on that first module.
On Tue, Nov 2, 2010 at 7:25 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> You are fighting the "Mave
You are fighting the "Maven way"
Drink the coolaid, split your "two phases" into two projects and you
will actually end up with a cleaner project in the first place... and
a simpler build process... and it will be doing what you want
Maven is opinionated... you have hit a core opinion, either use
Sorry, I was not able to answer to this message in the previous three days...
If I understand your replies correctly, I cannot split the compile
phase into two with maven. This sounds pretty ... shitty ;-(
regards
Leon
On Fri, Oct 29, 2010 at 11:07 PM, Manfred Moser wrote:
> You could move the
Well, my code generator is attached and it works, the problem is that
the code generator itself has to be compiled first.
regards
Leon
On Fri, Oct 29, 2010 at 11:10 PM, Paul Benedict wrote:
> On Fri, Oct 29, 2010 at 4:03 PM, Leon Rosenberg
> wrote:
>> Hi,
>>
>> I have following requirement. I h
On Fri, Oct 29, 2010 at 4:03 PM, Leon Rosenberg
wrote:
> Hi,
>
> I have following requirement. I have a project, in which I have one
> source folder which contains a code generator (run with apt), another
> source folder
> which contains code, which is processed by the generator from folder
> 1, a
You could move the code generator and the generated code out to a separate
project. That will save you build time and solve your problem.
manfred
> Hi,
>
> I have following requirement. I have a project, in which I have one
> source folder which contains a code generator (run with apt), another
>
The code generator should be broken into a separate project.
Justin
On Oct 29, 2010, at 5:03 PM, Leon Rosenberg wrote:
> Hi,
>
> I have following requirement. I have a project, in which I have one
> source folder which contains a code generator (run with apt), another
> source folder
> which c
Hi,
I have following requirement. I have a project, in which I have one
source folder which contains a code generator (run with apt), another
source folder
which contains code, which is processed by the generator from folder
1, and a third folder that relies on the code generated by the second
fol
11 matches
Mail list logo