Ah woops. I was confused - I thought that's how we did it in Forge, but we
don't - had a crazy moment there. A more likely solution would be to import
the BOM into the Windup-parent POM. Not the other way around.
On Wed, Jan 28, 2015 at 1:04 PM, Jess Sightler <jsightle(a)redhat.com> wrote:
That sounds worse than maintaining it in two places.
On 01/28/2015 12:32 PM, Lincoln Baxter, III wrote:
No, but what we can do is remove the <version.forge> property in the BOM
itself, and in the windup-parent POM, and instead specify the version on
the command line using -Dversion.forge=2.13.X.Y
On Tue, Jan 27, 2015 at 4:26 PM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
> Hi,
>
> to keep the Forge versions aligned, and generally let those two share
> some properties, plugin configs, versions etc.,
>
> we could let them have a common parent. To prevent issues like we were
> solving now - with <version.forge> differing in those two, causing
>
https://issues.jboss.org/browse/FORGE-2206 .
>
> Note that it would not mean moving everything under a new directory
> level - parent can be in a sibling directory.
>
> WDYT?
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing
listwindup-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
--
Calendar Free/Busy:
https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=A...
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev