1:30 a.m.
Hi guys,
Something I see a lot in mailing lists is an issue of permissions
for developers;
When a developer will install JBoss from RPM, it'll probably get
root permissions and the jboss:jboss as an owner.
A developer who wishes to deploy his/her work, will need to hack
the deployments folder so his maven or any other framework could
actually deploy it.
I'd like to know what's your view on it, and will you consider
providing some script or install option for developers (jboss-set-dev ?)
in order to handle this and maybe other issues?
Doron
3:47 a.m.
In essence it is a matter of creation a copy of the configuration
starting AS from that copy.
1. cp -a $JBOSS_HOME/standalone $WORK/standalone
2. $JBOSS_HOME/bin/standalone.sh -Djboss.server.base.dir=$WORK/standalone
Carlo
On 03/20/2012 07:30 AM, Doron Fediuck wrote:
Hi guys,
Something I see a lot in mailing lists is an issue of permissions
for developers;
When a developer will install JBoss from RPM, it'll probably get
root permissions and the jboss:jboss as an owner.
A developer who wishes to deploy his/her work, will need to hack
the deployments folder so his maven or any other framework could
actually deploy it.
I'd like to know what's your view on it, and will you consider
providing some script or install option for developers (jboss-set-dev ?)
in order to handle this and maybe other issues?
Doron
_______________________________________________
jboss-rpm mailing list
jboss-rpm(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-rpm
9:08 p.m.
Thanks Carlo.
So developers should be working on $WORK/standalone.
Got it.
Thanks.
On 20/03/12 10:47, Carlo de Wolf wrote:
In essence it is a matter of creation a copy of the configuration
starting AS from that copy.
1. cp -a $JBOSS_HOME/standalone $WORK/standalone
2. $JBOSS_HOME/bin/standalone.sh -Djboss.server.base.dir=$WORK/standalone
Carlo
On 03/20/2012 07:30 AM, Doron Fediuck wrote:
> Hi guys,
> Something I see a lot in mailing lists is an issue of permissions
> for developers;
> When a developer will install JBoss from RPM, it'll probably get
> root permissions and the jboss:jboss as an owner.
> A developer who wishes to deploy his/her work, will need to hack
> the deployments folder so his maven or any other framework could
> actually deploy it.
>
> I'd like to know what's your view on it, and will you consider
> providing some script or install option for developers (jboss-set-dev ?)
> in order to handle this and maybe other issues?
>
> Doron
> _______________________________________________
> jboss-rpm mailing list
> jboss-rpm(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-rpm
4:27 a.m.
New subject: How to use this thing ? :)
In essence it is a matter of creation a copy of the configuration
starting AS from that copy.
1. cp -a $JBOSS_HOME/standalone $WORK/standalone
2. $JBOSS_HOME/bin/standalone.sh -Djboss.server.base.dir=$WORK/standalone
i'm trying to install and use the jboss-as rpm that was released friday(?)
I've installed it as root and when running it I get permission errors on the logging
files/directories.
Then I tried to do the cp from above but that fails too since cp -a remain the symbolic
link in place.
cp -Lr fails too because of root permissions on the files installed.
I tried even adding my user to jboss-as group but that didn't help.
I had to do this instead:
0. su root # since noone else have access to copy
1. cp -Lr $JBOSS_HOME/standalone $WORK/standalone # traverse symbolic links so user can be
someone else than root
2. chown -hR <user> $WORK/standalone # set owner and group to be able to write
3. chgrp -hR <user> $WORK/standalone
4. $JBOSS_HOME/bin/standalone.sh -Djboss.server.base.dir=$WORK/standalone
Now it starts.
...and now the window manager in F17 crashed again on me....
...and now f17 is very dead :(
I guess it will have to wait to verify if the welcome page work and if it gets recognized
by tools :(
/max
4660
days inactive
4680
days old
3 comments
3 participants
participants (3)
-
Carlo de Wolf -
Doron Fediuck -
Max Rydahl Andersen