5:27 a.m.
FYI, while updating the docs, i noticed a serious mismatch. jbpm-jpdl had been
changed with jbpm-core. To prevent confusion, I'm changing the artifactId from
jbpm-core to jbpm-jpdl. I still leave the module in directory modules/core.
I have build the installer and run the core test suite. Now I'll be running full
test suite: first building, installing and starting jboss and then running the full
test suite including the enterprise tests. When that succeeds locally, I'll check in
and start a hudson build.
Also, the download I renamed to jbpm-jpdl-{version}-installer.jar to be in sync with
previous namings.
--
regards, tom.
2:02 a.m.
why is that necessary? especially at this stage of the release cycle?
it breaks all dependend modules. i tend to do a rollback on this one.
/Heiko
On Nov 9, 2008, at 12:27 PM, Tom Baeyens wrote:
FYI, while updating the docs, i noticed a serious mismatch. jbpm-
jpdl had been changed with jbpm-core. To prevent confusion, I'm
changing the artifactId from jbpm-core to jbpm-jpdl. I still leave
the module in directory modules/core.
I have build the installer and run the core test suite. Now I'll be
running full test suite: first building, installing and starting
jboss and then running the full test suite including the enterprise
tests. When that succeeds locally, I'll check in and start a hudson
build.
Also, the download I renamed to jbpm-jpdl-{version}-installer.jar to
be in sync with previous namings.
--
regards, tom.
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
8:31 a.m.
New subject: AW: jbpm-core --> jbpm-jpdl
I appreciate the change, it was a bit confusing that it is renamed to
jbpm-core, since it is still the jbpm-jpdl.jar. No change in content
shouldn't result in a change in name here... And migrating projects have
to update their build scripts (not hard, sure, but also not necessary?).
But just my 2 cents... Since it is not my work to resolve the maven
dependencies ;-)
-----Ursprüngliche Nachricht-----
Von: jbpm-dev-bounces(a)lists.jboss.org
[mailto:jbpm-dev-bounces@lists.jboss.org] Im Auftrag von Heiko Braun
Gesendet: Montag, 10. November 2008 09:03
An: Tom Baeyens
Cc: jbpm-dev(a)lists.jboss.org
Betreff: Re: [jbpm-dev] jbpm-core --> jbpm-jpdl
why is that necessary? especially at this stage of the release cycle?
it breaks all dependend modules. i tend to do a rollback on this one.
/Heiko
On Nov 9, 2008, at 12:27 PM, Tom Baeyens wrote:
FYI, while updating the docs, i noticed a serious mismatch. jbpm-
jpdl had been changed with jbpm-core. To prevent confusion, I'm
changing the artifactId from jbpm-core to jbpm-jpdl. I still leave
the module in directory modules/core.
I have build the installer and run the core test suite. Now I'll be
running full test suite: first building, installing and starting
jboss and then running the full test suite including the enterprise
tests. When that succeeds locally, I'll check in and start a hudson
build.
Also, the download I renamed to jbpm-jpdl-{version}-installer.jar to
be in sync with previous namings.
--
regards, tom.
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
5809
days inactive
5810
days old
2 comments
3 participants
participants (3)
-
Bernd Rücker -
Heiko Braun -
Tom Baeyens