Error while building maven console
by Bernd Rücker
Hi!
I checked out the gwt console and tried to build is as decribed here:
https://www.jboss.org/community/docs/DOC-12879
And my antipathy against Maven rose again, after downloading the internet
the build failed. Seems to be something wrong with the maven dependencies?
Maybe anybody has a spontaneous idea whats wrong here?
Thanks a lot and cheers
Bernd
15 years, 9 months
Re: [jbpm-dev] Re: gpd 3.1.7 release
by Thomas Diesler
Hi Koen,
the current POM says
<jbpm.designer.version>3.1.6</jbpm.designer.version>
<jbpm.jsf-console.version>3.3.1.GA</jbpm.jsf-console.version>
which would indicate that there is no change WRT 3.2.5
Could you please work with Heiko to get this resolved?
cheers
-thomas
Koen Aers wrote:
> It was Heiko who did the last commit on December 17th. Would it be
> possible to revert this for the next release? I suppose this also means
> that the upload page in the jsf console has to change slightly in order
> to accomodate this rollback as I think it uses the upload servlet...
>
> Cheers,
> Koen
>
> Op 20-feb-09, om 10:52 heeft Thomas Diesler het volgende geschreven:
>
>> That the upload servlet is protected is new to me. Could you please
>> find out who did this so we know who to talk to?
>>
>> cheers
>> -thomas
>>
>> Koen Aers wrote:
>>> Hi Thomas,
>>> While testing the deployment of processes from the gpd I came across
>>> the fact that the deployment servlet in the previous jBPM releases
>>> (3.3.1 and 3.2.5) is now secured. Also, the connection url for the
>>> deployment has changed. While the latter is not that much of an issue
>>> (as it can be changed in the preferences pages of the designer), the
>>> former is very much so. To be able to make this work again I need to
>>> be able to provide the credentials in a programmatic way. Maybe you
>>> can help me, but I couldn't find an easy way to do so as the logon
>>> mechanism used is a jsf specific one. Additionally, there should be a
>>> way to change the user and password strings (or store them as
>>> preferences). I am not sure if I will be able to incorporate these
>>> changes before the release.
>>> In addition, as argued in https://jira.jboss.org/jira/browse/GPD-278
>>> and the other related issues, we need to keep the out-of-the-box
>>> experience as smooth as possible for our community users, so IMO the
>>> upload servlet does not need to be protected as the SOA platform
>>> removes the servlet for production use.
>>> I am not sure if creating a new GPD makes sense if users will not be
>>> able to deploy their processes.
>>> Regards,
>>> Koen
>>
>> --
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thomas Diesler
>> BPM Product Lead
>> JBoss, a division of Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> _______________________________________________
>> jbpm-dev mailing list
>> jbpm-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
BPM Product Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years, 9 months
