from:"Jason Dillon"


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GERONIMO-3771.
--

Resolution: Fixed

> Move maven-plugins/* to buildsupport/* and update groupId to 
> org.apache.geronimo.buildsupport
> -
>
> Key: GERONIMO-3771
> URL: https://issues.apache.org/jira/browse/GERONIMO-3771
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
> Fix For: 2.1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-2996) Car modules should have explicit dependencies


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GERONIMO-2996:
--

Assignee: David Jencks  (was: Jason Dillon)

I think you've implemented this right?  If so can you please close this puppy?

> Car modules should have explicit dependencies
> -
>
> Key: GERONIMO-2996
> URL: https://issues.apache.org/jira/browse/GERONIMO-2996
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: car-maven-plugin
>Reporter: Jason Dillon
>Assignee: David Jencks
>
> When building car files currently, the enclosing maven pom is inspected for 
> dependencies, which can sometimes lead to unwanted dependencies being 
> included.  Also as a side effect we have to overload the meaning of _scope_ 
> to alter the behavior when setting up the configuration modules plan.
> By making the list of dependencies to be included in the plan explicit, the 
> plugin becomes simpler, faster and with predictable behavior wrt what 
> dependencies will be included.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-3677) Add support for cli options for host/port and user/pass for commands


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GERONIMO-3677.
--

Resolution: Fixed

> Add support for cli options for host/port and user/pass for commands
> 
>
> Key: GERONIMO-3677
> URL: https://issues.apache.org/jira/browse/GERONIMO-3677
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 2.1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Trunk might break for a little while

2008-01-23 Thread Jason Dillon


On Jan 23, 2008, at 9:17 AM, Jarek Gawor wrote:

Jason,

Some modules there were moved from applications/ directory use
org.apache.geronimo.applications as groupId and some use
org.apache.geronimo.plugins. Should we use org.apache.geronimo.plugins
for all these apps to be consistent?


Yes, I tried to look for them and change, but I think my regex for s/r  
was bad.  The org.apache.geronimo.applications groupId should be  
changed to org.apache.geronimo.plugins.


--jason

Re: Trunk might break for a little while

2008-01-23 Thread Jason Dillon

I've fixed a few things in the testsuite and it seems to be running  
fine.  Most of the tests seemed to pass, though I do recall seeing one  
failure, but I'm sleepy and can't remember where.


I checked the javaee5 and minimal assemblies to make sure they boot  
up... which they do.  Might have missed something, but it looks like  
things are back to normal after the module parentage change.


--jason


On Jan 22, 2008, at 11:04 PM, Jarek Gawor wrote:


I updated bunch of things so trunk should work better now but I think
testsuites poms still need some updates.

Jarek

On Jan 22, 2008 5:56 PM, David Jencks <[EMAIL PROTECTED]> wrote:

I'm trying to help jdillon check the pom cleanup he's been working on
but I'm having trouble applying the patches, so I've asked him to
commit his work so far.  We're not 100% sure if it builds correctly
or not so you might not want to svn up until we are more sure
hopefully very soon.

Hope this does not cause too much disruption and thanks
david jencks

[jira] Closed: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GERONIMO-3747.
--

Resolution: Fixed

Module parentage has been updated so that the module's parent is ../pom.xml.  
All bits under {{framework/\*}} are now in the 
{{org.apache.geronimo.framework}} groupId.  Other bits under {{plugins/\*}} are 
still using {{org.apache.geronimo.modules}} and 
{{org.apache.geronimo.configs}}, which should be changed, but can wait until 
2.2.

In addition the {{components/\*}} and {{applications/\*}} modules have been 
relocated under {{plugins}}.

> subprojects should use file system parent poms as parent poms in general
> 
>
> Key: GERONIMO-3747
> URL: https://issues.apache.org/jira/browse/GERONIMO-3747
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: David Jencks
>Assignee: Jason Dillon
> Fix For: 2.1
>
> Attachments: GERONIMO-3747-step-1.diff.zip, 
> GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still 
> o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad 
> idea.  I think the main thing that needs to be changed is to move the car 
> plugin setup code into the root pom.  However I'm not sure if this is 
> possible bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Trunk might break for a little while

2008-01-22 Thread Jason Dillon

Kay, thanks for your help.  I'm sync'ing now to run a clean build and  
will see if I can get it happier.


--jason


On Jan 22, 2008, at 11:04 PM, Jarek Gawor wrote:


I updated bunch of things so trunk should work better now but I think
testsuites poms still need some updates.

Jarek

On Jan 22, 2008 5:56 PM, David Jencks <[EMAIL PROTECTED]> wrote:

I'm trying to help jdillon check the pom cleanup he's been working on
but I'm having trouble applying the patches, so I've asked him to
commit his work so far.  We're not 100% sure if it builds correctly
or not so you might not want to svn up until we are more sure
hopefully very soon.

Hope this does not cause too much disruption and thanks
david jencks

Re: svn commit: r614433 - in /geronimo/server/trunk/plugins/welcome: welcome-jetty/pom.xml welcome-tomcat/pom.xml

2008-01-22 Thread Jason Dillon


Thanks :-)

--jason


On Jan 22, 2008, at 10:23 PM, [EMAIL PROTECTED] wrote:


Author: gawor
Date: Tue Jan 22 22:23:21 2008
New Revision: 614433

URL: http://svn.apache.org/viewvc?rev=614433&view=rev
Log:
update groupid

Modified:
   geronimo/server/trunk/plugins/welcome/welcome-jetty/pom.xml
   geronimo/server/trunk/plugins/welcome/welcome-tomcat/pom.xml

Modified: geronimo/server/trunk/plugins/welcome/welcome-jetty/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/welcome/welcome-jetty/pom.xml?rev=614433&r1=614432&r2=614433&view=diff
=
=
=
=
=
=
=
=
==
--- geronimo/server/trunk/plugins/welcome/welcome-jetty/pom.xml  
(original)
+++ geronimo/server/trunk/plugins/welcome/welcome-jetty/pom.xml Tue  
Jan 22 22:23:21 2008

@@ -100,7 +100,7 @@
${jasperDeployer}deploymentConfig>



-org.apache.geronimo.applicationsgroupId>
+org.apache.geronimo.pluginsgroupId>

geronimo-welcome
${version}
war

Modified: geronimo/server/trunk/plugins/welcome/welcome-tomcat/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/welcome/welcome-tomcat/pom.xml?rev=614433&r1=614432&r2=614433&view=diff
= 
= 
= 
= 
= 
= 
= 
= 
==
--- geronimo/server/trunk/plugins/welcome/welcome-tomcat/pom.xml  
(original)
+++ geronimo/server/trunk/plugins/welcome/welcome-tomcat/pom.xml Tue  
Jan 22 22:23:21 2008

@@ -100,7 +100,7 @@
${jasperDeployer}deploymentConfig>



-org.apache.geronimo.applicationsgroupId>
+org.apache.geronimo.pluginsgroupId>

geronimo-welcome
${version}
war

Re: Trunk might break for a little while

2008-01-22 Thread Jason Dillon

Aye, thnks for the note David.  I hope you and I can get everything  
happy and giggling sometime tonight :-)


--jason


On Jan 22, 2008, at 2:56 PM, David Jencks wrote:

I'm trying to help jdillon check the pom cleanup he's been working  
on but I'm having trouble applying the patches, so I've asked him to  
commit his work so far.  We're not 100% sure if it builds correctly  
or not so you might not want to svn up until we are more  
sure hopefully very soon.


Hope this does not cause too much disruption and thanks
david jencks

[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

2008-01-22 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GERONIMO-3747:
---

Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> 
>
> Key: GERONIMO-3747
> URL: https://issues.apache.org/jira/browse/GERONIMO-3747
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: David Jencks
>Assignee: Jason Dillon
> Fix For: 2.1
>
> Attachments: GERONIMO-3747-step-1.diff.zip, 
> GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still 
> o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad 
> idea.  I think the main thing that needs to be changed is to move the car 
> plugin setup code into the root pom.  However I'm not sure if this is 
> possible bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

2008-01-22 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GERONIMO-3747:
---

Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> 
>
> Key: GERONIMO-3747
> URL: https://issues.apache.org/jira/browse/GERONIMO-3747
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: David Jencks
>Assignee: Jason Dillon
> Fix For: 2.1
>
> Attachments: GERONIMO-3747-step-1.diff.zip, 
> GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still 
> o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad 
> idea.  I think the main thing that needs to be changed is to move the car 
> plugin setup code into the root pom.  However I'm not sure if this is 
> possible bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

2008-01-21 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GERONIMO-3747:
---

Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> 
>
> Key: GERONIMO-3747
> URL: https://issues.apache.org/jira/browse/GERONIMO-3747
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: David Jencks
>Assignee: Jason Dillon
> Fix For: 2.1
>
> Attachments: GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still 
> o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad 
> idea.  I think the main thing that needs to be changed is to move the car 
> plugin setup code into the root pom.  However I'm not sure if this is 
> possible bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

2008-01-21 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GERONIMO-3747:
--

Assignee: Jason Dillon

> subprojects should use file system parent poms as parent poms in general
> 
>
> Key: GERONIMO-3747
> URL: https://issues.apache.org/jira/browse/GERONIMO-3747
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: David Jencks
>Assignee: Jason Dillon
> Fix For: 2.1
>
>
> After the move of most stuff into plugins, the parent pom is usually still 
> o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad 
> idea.  I think the main thing that needs to be changed is to move the car 
> plugin setup code into the root pom.  However I'm not sure if this is 
> possible bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Evil windows path limit...

2008-01-20 Thread Jason Dillon

anyone know how close we are to the limit for the repository?  I'd  
like to be able to use longer groupIds to organize plugins, like:


org.apache.geronimo.plugins.activemq

which would have all of the activemq plugin modules  
(.jar, .war, .car, .whatever).  But I'm fairly sure that following  
this pattern would cause windows to crap its pants.


one solution I was thinking of was to update the G repo code to have  
some well known prefix resolution alias fluff... like:


oag/plugins/activemq -> org/apache/geronimo/plugins/activemq

so in _our_ repo we can shorten the names of some of these groupIds  
and prevent windows from messing itself.  though, there will still be  
full names in the local m2 repo cache.


and actually, I really want to put 'server' into the base groupId, so  
the above would really be more like:


org.apache.geronimo.server.plugins.activemq

and the short version:

oags/plugins/activemq

Anyone have any comments?

--jason

[jira] Commented: (GERONIMO-3771) Move maven-plugins/* to buildsupport/* and update groupId to org.apache.geronimo.buildsupport

2008-01-20 Thread Jason Dillon (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560875#action_12560875
 ] 

Jason Dillon commented on GERONIMO-3771:


Still pending fix up of the testsuite bits, will do shortly after the mvn 
deploy of the new bits are done.

> Move maven-plugins/* to buildsupport/* and update groupId to 
> org.apache.geronimo.buildsupport
> -
>
> Key: GERONIMO-3771
> URL: https://issues.apache.org/jira/browse/GERONIMO-3771
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1
>Reporter: Jason Dillon
>Assignee: Jason Dillon
> Fix For: 2.1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3771) Move maven-plugins/* to buildsupport/* and update groupId to org.apache.geronimo.buildsupport

2008-01-20 Thread Jason Dillon (JIRA)

Move maven-plugins/* to buildsupport/* and update groupId to 
org.apache.geronimo.buildsupport
-

 Key: GERONIMO-3771
 URL: https://issues.apache.org/jira/browse/GERONIMO-3771
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
Affects Versions: 2.1
Reporter: Jason Dillon
Assignee: Jason Dillon
 Fix For: 2.1




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: 2.1 Release -- Banging the drum

2008-01-20 Thread Jason Dillon

I'm going to start working on this... looks like there are more  
problems that I thought, though not hard to fix... just a PITA.


--jason


On Jan 20, 2008, at 8:13 AM, Kevan Miller wrote:



On Jan 19, 2008, at 1:18 PM, Jacek Laskowski wrote:


On Jan 18, 2008 3:15 AM, Kevan Miller <[EMAIL PROTECTED]> wrote:

I agree with Jason. We shouldn't be carrying forward the current  
structure.
And, I think we have enough time to fix this problem while we are  
fixing

other issues with the release.


Even though I tend to agree I understand the pain of our end users  
who

suffer from working with 2.0.2 when we keep telling them use the
unofficial 2.1 release and I wish we could release G 2.1 as soon as
possible. No issues should be counted any more. Just go ahead,  
release

and keep working on 2.2 release.


Jacek,
Let's level-set for a second. From my original note on this subject:

On Jan 16, 2008, at 10:27 AM, Kevan Miller wrote:



I'd like to set a target of 2 weeks for reviewing and fixing  
problems. After that would start the branching, final tck, and  
packaging work. If we feel this might negatively impact post-2.1  
development activities. We can consider creating a 2.1 branch  
sooner...


Are you ok with the 2 week target for reviewing the current trunk  
codebase and resolving issues?


The structure of our pom's are one of the issues that I think have  
been identified in our current codebase. Seems like we can resolve  
the problem within our 2 week timeframe. So, I'm all for fixing the  
poms...


--kevan

Re: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

2008-01-19 Thread Jason Dillon

I don't mind seeing this from time to time... just not happy to get in  
every hour... every day :-)


Thanks,

--jason


On Jan 19, 2008, at 1:16 PM, Jarek Gawor wrote:


Btw, from time to time you still might see these messages since the
testsuite build scripts fix the permissions after the files are
uploaded. So there is a little bit of time where the files exist
without the right permissions and in which your cron job might run.
Also, if somebody knows how to configure things so that scp respects
the umask value please let me know. I tried a bunch of things like
putting the umask setting in the different shell rc files but I still
couldn't get it to work it right.

Jarek

On Jan 19, 2008 1:20 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:

Still getting these hourly...

Shall I update the cron job to spam dev@ ?

--jason


Begin forwarded message:


From: [EMAIL PROTECTED] (Cron Daemon)
Date: January 19, 2008 10:17:13 AM PST

To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync



chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
build-2000.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2

Fwd: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

2008-01-19 Thread Jason Dillon


Still getting these hourly...

Shall I update the cron job to spam dev@ ?

--jason


Begin forwarded message:


From: [EMAIL PROTECTED] (Cron Daemon)
Date: January 19, 2008 10:17:13 AM PST
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
build-2000.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binar

Fwd: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

2008-01-18 Thread Jason Dillon


And now I'm getting these...

:-(

--jason


Begin forwarded message:


From: [EMAIL PROTECTED] (Cron Daemon)
Date: January 18, 2008 6:22:11 PM PST
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
build-2000.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/enterprise-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/console-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/web-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite/target: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/webservices-testsuite: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var: Operation not permitted
chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-2000-tomcat/corba

Re: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

2008-01-18 Thread Jason Dillon


Kay, thx :-)

--jason


On Jan 18, 2008, at 1:42 PM, Jarek Gawor wrote:


My fault, this should be fixed now.

I changed the location where the the test reports and the binaries are
published and forgot about the permission settings.

Jarek

On Jan 18, 2008 4:29 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:

Um, anyone know what happened to the site perms?

--jason


Begin forwarded message:

From: [EMAIL PROTECTED] (Cron Daemon)
Date: January 18, 2008 1:18:41 PM PST
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync

chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
build-0200.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
geronimo-tomcat6-jee5-2.0.3-SNAPSHOT-bin.zip:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
geronimo-jetty6-jee5-2.0.3-SNAPSHOT-bin.zip:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/enterprise-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/console-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- 
SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/web-testsuite:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log/geronimo.log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var/log:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT/var:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- 
jee5-2.0.3-SNAPSHOT:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite/target:

Operation not permitted
chmod:
/www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ 
logs-0200-tomcat/webservices-testsuite:

Operation not permitted

Re: 2.1 Release -- Banging the drum

2008-01-17 Thread Jason Dillon

It should take a day or two to fix, nothing significant.  It should  
have been done when the modules were reorganized... and I have no idea  
why it was not.  The reorg task should be completed before we  
release.  I don't understand why folks tend to discount build related  
issues.  Maybe we should consult the resident m2 expert?  :-P


--jason


On Jan 17, 2008, at 2:22 PM, Jacek Laskowski wrote:


On Jan 17, 2008 6:39 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
I think we need to fix the pom parentage post reorganization before  
we

can branch for a 2.1 release.  IMO the reorg is only half done... and
really needs to be finished.


I disagree. We've been living with it for a while and am sure we can
live with it a bit longer. I'm against any issues/tasks that would
make the 2.1 release delayed. I don't want to tell our users that 2.1
is the solution to their problems as it doesn't exist yet. I've seen a
lot of answers with 2.1 as the solution so if we've suggested using
2.1 it's ready. There's no need to wait any longer and it should be
released now provided it passes TCK. Any other issues can be fixed in
2.2.

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Updated: (GSHELL-76) Full and minimal assemblies require different layout.xml


 [ 
https://issues.apache.org/jira/browse/GSHELL-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GSHELL-76:
---

Fix Version/s: (was: 1.0-alpha-1)
   1.0-alpha-2

> Full and minimal assemblies require different layout.xml
> 
>
> Key: GSHELL-76
> URL: https://issues.apache.org/jira/browse/GSHELL-76
> Project: GShell
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GSHELL-73) {redirec} does not work with exported content


 [ 
https://issues.apache.org/jira/browse/GSHELL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GSHELL-73:
---

Fix Version/s: (was: 1.0-alpha-1)
   1.0-alpha-2

> {redirec} does not work with exported content
> -
>
> Key: GSHELL-73
> URL: https://issues.apache.org/jira/browse/GSHELL-73
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Website
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
>
> Pages like this have redirects:
>   * http://cwiki.apache.org/GSHELL/issue-tracking.html
> But they don't work on the exported pages,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-48) Add file/URL support to the script command


 [ 
https://issues.apache.org/jira/browse/GSHELL-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-48.
--

Resolution: Fixed

Applied thx

> Add file/URL support to the script command
> --
>
> Key: GSHELL-48
> URL: https://issues.apache.org/jira/browse/GSHELL-48
> Project: GShell
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Commands - BSF
>Affects Versions: 1.0-alpha-1
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Minor
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-48.patch
>
>
> Should be able to give the BSF {{script}} command a file or URL to execute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GSHELL-49) When --language is not given and we have a file/URL try and figure out the lang to use


 [ 
https://issues.apache.org/jira/browse/GSHELL-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-49:
--

Assignee: Jason Dillon  (was: Jason Warner)

> When --language is not given and we have a file/URL try and figure out the 
> lang to use
> --
>
> Key: GSHELL-49
> URL: https://issues.apache.org/jira/browse/GSHELL-49
> Project: GShell
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: Commands - BSF
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Trivial
> Fix For: 1.0-alpha-2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-49) When --language is not given and we have a file/URL try and figure out the lang to use


 [ 
https://issues.apache.org/jira/browse/GSHELL-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-49.
--

Resolution: Fixed

Applied thx

> When --language is not given and we have a file/URL try and figure out the 
> lang to use
> --
>
> Key: GSHELL-49
> URL: https://issues.apache.org/jira/browse/GSHELL-49
> Project: GShell
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: Commands - BSF
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Trivial
> Fix For: 1.0-alpha-2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-70) Boolean options should be able to take an optional argument to negate, ie. --foo=false


 [ 
https://issues.apache.org/jira/browse/GSHELL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-70.
--

Resolution: Fixed

Applied, thx.  In the future can we get tests for new features to make sure 
things keep working.

> Boolean options should be able to take an optional argument to negate, ie. 
> --foo=false
> --
>
> Key: GSHELL-70
> URL: https://issues.apache.org/jira/browse/GSHELL-70
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Support - CLP
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-70.patch
>
>
> Boolean options, like:
> {code:java}
> @Option(name="-f", aliases={"--foo"})
> private boolean foo;
> {code}
> Should support negation with:
> {noformat}
> --foo=false
> {noformat}
> or:
> {noformat}
> -f=false
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GSHELL-48) Add file/URL support to the script command


 [ 
https://issues.apache.org/jira/browse/GSHELL-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-48:
--

Assignee: Jason Dillon  (was: Jason Warner)

> Add file/URL support to the script command
> --
>
> Key: GSHELL-48
> URL: https://issues.apache.org/jira/browse/GSHELL-48
> Project: GShell
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Commands - BSF
>Affects Versions: 1.0-alpha-1
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Minor
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-48.patch
>
>
> Should be able to give the BSF {{script}} command a file or URL to execute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GSHELL-70) Boolean options should be able to take an optional argument to negate, ie. --foo=false


 [ 
https://issues.apache.org/jira/browse/GSHELL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-70:
--

Assignee: Jason Dillon  (was: Jason Warner)

> Boolean options should be able to take an optional argument to negate, ie. 
> --foo=false
> --
>
> Key: GSHELL-70
> URL: https://issues.apache.org/jira/browse/GSHELL-70
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Support - CLP
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-70.patch
>
>
> Boolean options, like:
> {code:java}
> @Option(name="-f", aliases={"--foo"})
> private boolean foo;
> {code}
> Should support negation with:
> {noformat}
> --foo=false
> {noformat}
> or:
> {noformat}
> -f=false
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GSHELL-98) NotFoundException when trying to use non-builtin commands in full assembly


[ 
https://issues.apache.org/jira/browse/GSHELL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560011#action_12560011
 ] 

Jason Dillon commented on GSHELL-98:


I'm about to apply this, though I don't really understand how it was broken 
before... not that I think it was not broken before.

Can you give me an example of a command execution which fails w/o the patch and 
runs as expected with the patch?

> NotFoundException when trying to use non-builtin commands in full assembly
> --
>
> Key: GSHELL-98
> URL: https://issues.apache.org/jira/browse/GSHELL-98
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Core
>Affects Versions: 1.0-alpha-2
>    Reporter: Jason Warner
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-98.patch
>
>
> The full assembly of gshell includes all the available commands by default.  
> When trying to use one of the commands included outside of builtins, a 
> NotFoundException is received.  This seems to be caused by the groupings in 
> the layout.xml file.  When the groupings were removed, all the commands could 
> be used successfully.  Ideally, we'd like to be able to keep the groupings, 
> though.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: 2.1 Release -- Banging the drum

2008-01-17 Thread Jason Dillon

I think we need to fix the pom parentage post reorganization before we  
can branch for a 2.1 release.  IMO the reorg is only half done... and  
really needs to be finished.


--jason


On Jan 16, 2008, at 7:27 AM, Kevan Miller wrote:


All,
This note is a bit overdue (it's been a distracting start to the New  
Year for me). Time, IMO, for us to get focused on our 2.1 release.


As David Jencks has pointed out. We need to start cleaning out the  
2.1 Jiras. It looks like I've got several open that have been fixed,  
either by additional development activities or redundant jira's.  
First step is to take a look at Jira's that you've created and make  
sure they are still valid and if you think it's important that they  
be fixed for 2.1.


We also need to be taking a close look at our current functionality.  
Make sure things are working the way we want them to... Especially  
need to cast a critical eye on our the usability aspects of the new  
2.1. Along the way, will be great if we can start pulling docs  
together.


I started running tests last night. Right away, I'm noticing little  
things like warning messages being sent to STDOUT, etc. I'll start  
registering problem areas that I'm seeing.


I'd like to set a target of 2 weeks for reviewing and fixing  
problems. After that would start the branching, final tck, and  
packaging work. If we feel this might negatively impact post-2.1  
development activities. We can consider creating a 2.1 branch  
sooner...


Thoughts?

--kevan

Re: [YOKO] Yoko web site

2008-01-17 Thread Jason Dillon

Did you get this sorted... or on your way to sorted?  Ping me if you  
need any help... especially if its the kinda help where I don't really  
have to do anything :-P


--jason


On Jan 16, 2008, at 4:41 PM, Alan D. Cabrera wrote:

I want to start creating the new Yoko website and wiki.  How do I do  
this?



Regards,
Alan

Re: [YOKO] Yoko web site

2008-01-16 Thread Jason Dillon

They use confluence and auto-export. 

--jason


-Original Message-
From: "Alan D. Cabrera" <[EMAIL PROTECTED]>

Date: Wed, 16 Jan 2008 21:39:43 
To:dev@geronimo.apache.org
Subject: Re: [YOKO] Yoko web site


:)


What does XBean and GShell do?


Regards,
Alan

On Jan 16, 2008, at 5:18 PM, Jason Dillon wrote:

> Well there is this thing called HTML and you use it to make things  
> called "pages" and then put them on a "web server"...
>
> :-P
>
> What do you want... Something backed up by confluence?  Or static  
> via svn?
>
> --jason
>
>
> -Original Message-
> From: "Alan D. Cabrera" <[EMAIL PROTECTED]>
>
> Date: Wed, 16 Jan 2008 16:41:30
> To:Developers Geronimo 
> Subject: [YOKO] Yoko web site
>
>
> I want to start creating the new Yoko website and wiki.  How do I do
> this?
>
>
> Regards,
> Alan
>
>
>
>

Re: [YOKO] Yoko web site

2008-01-16 Thread Jason Dillon

Well there is this thing called HTML and you use it to make things called 
"pages" and then put them on a "web server"...

:-P

What do you want... Something backed up by confluence?  Or static via svn?

--jason


-Original Message-
From: "Alan D. Cabrera" <[EMAIL PROTECTED]>

Date: Wed, 16 Jan 2008 16:41:30 
To:Developers Geronimo 
Subject: [YOKO] Yoko web site


I want to start creating the new Yoko website and wiki.  How do I do  
this?


Regards,
Alan

[jira] Assigned: (GSHELL-98) NotFoundException when trying to use non-builtin commands in full assembly

2008-01-15 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GSHELL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-98:
--

Assignee: Jason Dillon  (was: Jason Warner)

> NotFoundException when trying to use non-builtin commands in full assembly
> --
>
> Key: GSHELL-98
> URL: https://issues.apache.org/jira/browse/GSHELL-98
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Core
>Affects Versions: 1.0-alpha-2
>Reporter: Jason Warner
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-98.patch
>
>
> The full assembly of gshell includes all the available commands by default.  
> When trying to use one of the commands included outside of builtins, a 
> NotFoundException is received.  This seems to be caused by the groupings in 
> the layout.xml file.  When the groupings were removed, all the commands could 
> be used successfully.  Ideally, we'd like to be able to keep the groupings, 
> though.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GSHELL-98) NotFoundException when trying to use non-builtin commands in full assembly

2008-01-15 Thread Jason Dillon (JIRA)


[ 
https://issues.apache.org/jira/browse/GSHELL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559214#action_12559214
 ] 

Jason Dillon commented on GSHELL-98:


Cool!  I will look at this later today.  Still a little jet lagged though...

> NotFoundException when trying to use non-builtin commands in full assembly
> --
>
> Key: GSHELL-98
> URL: https://issues.apache.org/jira/browse/GSHELL-98
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Core
>Affects Versions: 1.0-alpha-2
>Reporter: Jason Warner
>Assignee: Jason Warner
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-98.patch
>
>
> The full assembly of gshell includes all the available commands by default.  
> When trying to use one of the commands included outside of builtins, a 
> NotFoundException is received.  This seems to be caused by the groupings in 
> the layout.xml file.  When the groupings were removed, all the commands could 
> be used successfully.  Ideally, we'd like to be able to keep the groupings, 
> though.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Wishing you Happy New Year 2008 (leaving for a couple of days)

2007-12-28 Thread Jason Dillon

Um... Aria na krap?

--jason


-Original Message-
From: Matt Hogstrom <[EMAIL PROTECTED]>

Date: Sat, 29 Dec 2007 00:10:29 
To:dev@geronimo.apache.org
Subject: Re: Wishing you Happy New Year 2008 (leaving for a couple of days)


Wszystkiego najlepszego w nowym roku

back at ya bubba :)


On Dec 28, 2007, at 3:37 PM, Jacek Laskowski wrote:

> Hi Geronimos,
>
> I'm leaving for a couple of days skiing in the Polish mountains and
> I'll be offline till 01/03. Just though I'd wish you Happy New Year
> 2008 and better Geronimo-OpenEJB integration as well as less bugs and
> more features coming into the upcoming Geronimo releases. I wished it
> to OpenEJBists, but thought it'd be nice to say it again - if we
> happen to fix all the bugs reported before Java EE 6, it'd be superb!
> Having OSGi layer in Geronimo could definitely make the year 2008
> better.
>
> Have fun!
>
> Jacek
>
> -- 
> Jacek Laskowski
> http://www.JacekLaskowski.pl
>

Re: [VOTE RESULT] Release GShell 1.0-alpha-1

2007-12-22 Thread Jason Dillon

Its out... sorry about the delay.  Now I'm off to Thailand for a few  
weeks :-)


--jason


On Dec 20, 2007, at 11:22 PM, Guillaume Nodet wrote:


Any news about that ?

On Dec 19, 2007 9:39 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
This vote has passed with 8 +1, no other votes.

I will release this later today.

--jason


On Dec 14, 2007, at 6:02 PM, Jason Dillon wrote:

> Oh ya... the time is now, all you party people get out on the floor
> and shake what your mother gave ya...
>
> This is the *first* _official_ release of GShell... and I invite all
> of you to go an have a quick look over the only docs we got at the
> moment:
>
>http://cwiki.apache.org/GSHELL
>
> More docs are on there way I can assure you... as well as more
> features, functionality and fun with your command-line... aight!
>
> * * *
>
> GShell has been a dream of mine for... er um what seems like years
> now... oh wait it has been years.  And well, the universe has
> finally aligned and things are falling into place quite nicely I'd
> say.  Some external groups are already consuming these goodies,
> others have asked me about it, and there might even been some
> commercial apps wanting a simple/easy/kick-ass command-line (remote
> scriptable) interface to their application on the horizon too.
>
> If any of you remember the JBucks days, when I whittled Twiddle out
> of thin air as a pluggable command-line  framework (only realized to
> invoke lame JMX muck)... well, GShell is here to carve out its own
> notch... or well, I hope it can get sharp enough to cut something.
> I think it will... just believe, imagine and well we make dreams
> reality her in the land of source which is open... na... aighty.
>
> Keep in mind this is an *alpha-1* release, and is a little rough (or
> in some cases more than a little) around the corners.  I hope, with
> the help, guidance and suggestions of the community, that we can
> sort though all of the significant issues and polish GShell off
> enough to make it generally mass-consumable by applications (like
> ServiceMix, ActiveMQ, and other sister server-orient projects which
> need a sophisticated command-line interface for administration,
> configuration, whatever).
>
> This version of GShell was inspired a little (okay... a lot) by the
> work I've done on the Groovy projects 'groovysh' command-line tool  
( http://groovy.codehaus.org/Groovy+Shell

>  ).  Actually working on 'groovysh' really helped me to figure out
> many things w/GShell... and maybe one day Groovy's 'groovysh' will
> actually use GShell as a framework, though there is a bit of work
> left in the core to make that a reality.  For folks that haven't use
> my new 'groovysh', you can easily have a look by using the 'groovy-
> maven-plugin', as in:
>
>mvn groovy:shell
>
> You'll notice a lot of similarities between 'groovysh' and 'gsh' I'm
> sure.
>
> * * *
>
> While working on this release I've come to realize that GShell and
> Maven2 are very similar creatures... which I'll elaborate on more in
> the future... but because of that significant functionality which is
> already implemented in Maven2 is 90% (or sometimes more) compatible
> with the direction GShell is headed towards.  For example, one
> feature alpha-2 will have is to allow command plugins to define
> 'dependencies' just as a Maven project does now.  And GShell can be
> configured (a bit more flexibly than Maven ATM) for how to find
> those dependencies (in a local repo, in a remote repo, in some uber-
> jar, etc).  This will all leverage the maturing Maven2 codebase.  So
> in some ways GShell will grow with Maven2 as they both become more
> and more functional, stable, reliable... and well ass-kicking no
> doubt.
>
> Um... crap, I'm e-babbling again; sorry.   So, lets vote and push
> this puppy out already... ?!
>
> +1Oh ya, come on baby... you know you want it
> +0Um... I don't know what is wrong with batch personally,  
can't we

> just use that?
> -1I like cheese, cheese makes me happy... but damn it cheese  
won't

> let me remotely administer my application... wtf, no way... WAIT
>
> So, its Friday evening, 6ish PST... so lets say _sometime_ on
> Tuesday the 25th I'll call the vote.  That is a little more than 72
> hours... so get your #2 pencils out and shake what your mother gave
> ya...
>
> --jason
>
>




--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

[VOTE RESULT] Release GShell 1.0-alpha-1

2007-12-19 Thread Jason Dillon

This vote has passed with 8 +1, no other votes.

I will release this later today.

--jason

On Dec 14, 2007, at 6:02 PM, Jason Dillon wrote:

Oh ya... the time is now, all you party people get out on the floor
and shake what your mother gave ya...

This is the *first* _official_ release of GShell... and I invite all
of you to go an have a quick look over the only docs we got at the
moment:

http://cwiki.apache.org/GSHELL

More docs are on there way I can assure you... as well as more
features, functionality and fun with your command-line... aight!

* * *

GShell has been a dream of mine for... er um what seems like years
now... oh wait it has been years. And well, the universe has
finally aligned and things are falling into place quite nicely I'd
say. Some external groups are already consuming these goodies,
others have asked me about it, and there might even been some
commercial apps wanting a simple/easy/kick-ass command-line (remote
scriptable) interface to their application on the horizon too.

If any of you remember the JBucks days, when I whittled Twiddle out
of thin air as a pluggable command-line framework (only realized to
invoke lame JMX muck)... well, GShell is here to carve out its own
notch... or well, I hope it can get sharp enough to cut something.
I think it will... just believe, imagine and well we make dreams
reality her in the land of source which is open... na... aighty.

Keep in mind this is an *alpha-1* release, and is a little rough (or
in some cases more than a little) around the corners. I hope, with
the help, guidance and suggestions of the community, that we can
sort though all of the significant issues and polish GShell off
enough to make it generally mass-consumable by applications (like
ServiceMix, ActiveMQ, and other sister server-orient projects which
need a sophisticated command-line interface for administration,
configuration, whatever).

This version of GShell was inspired a little (okay... a lot) by the
work I've done on the Groovy projects 'groovysh' command-line tool ( http://groovy.codehaus.org/Groovy+Shell
). Actually working on 'groovysh' really helped me to figure out
many things w/GShell... and maybe one day Groovy's 'groovysh' will
actually use GShell as a framework, though there is a bit of work
left in the core to make that a reality. For folks that haven't use
my new 'groovysh', you can easily have a look by using the 'groovy-
maven-plugin', as in:

mvn groovy:shell

You'll notice a lot of similarities between 'groovysh' and 'gsh' I'm
sure.

* * *

While working on this release I've come to realize that GShell and
Maven2 are very similar creatures... which I'll elaborate on more in
the future... but because of that significant functionality which is
already implemented in Maven2 is 90% (or sometimes more) compatible
with the direction GShell is headed towards. For example, one
feature alpha-2 will have is to allow command plugins to define
'dependencies' just as a Maven project does now. And GShell can be
configured (a bit more flexibly than Maven ATM) for how to find
those dependencies (in a local repo, in a remote repo, in some uber-
jar, etc). This will all leverage the maturing Maven2 codebase. So
in some ways GShell will grow with Maven2 as they both become more
and more functional, stable, reliable... and well ass-kicking no
doubt.

Um... crap, I'm e-babbling again; sorry. So, lets vote and push
this puppy out already... ?!

+1 Oh ya, come on baby... you know you want it
+0 Um... I don't know what is wrong with batch personally, can't we
just use that?
-1 I like cheese, cheese makes me happy... but damn it cheese won't
let me remotely administer my application... wtf, no way... WAIT

So, its Friday evening, 6ish PST... so lets say _sometime_ on
Tuesday the 25th I'll call the vote. That is a little more than 72
hours... so get your #2 pencils out and shake what your mother gave
ya...

--jason

Re: [VOTE] Release GShell 1.0-alpha-1

2007-12-19 Thread Jason Dillon


Yes, you need to build trunk.

--jason


On Dec 17, 2007, at 11:13 PM, Alan D. Cabrera wrote:


I want to test building it.  This must be trunk?


Regards,
Alan

On Dec 14, 2007, at 6:02 PM, Jason Dillon wrote:

Oh ya... the time is now, all you party people get out on the floor  
and shake what your mother gave ya...


This is the *first* _official_ release of GShell... and I invite  
all of you to go an have a quick look over the only docs we got at  
the moment:


  http://cwiki.apache.org/GSHELL

More docs are on there way I can assure you... as well as more  
features, functionality and fun with your command-line... aight!


* * *

GShell has been a dream of mine for... er um what seems like years  
now... oh wait it has been years.  And well, the universe has  
finally aligned and things are falling into place quite nicely I'd  
say.  Some external groups are already consuming these goodies,  
others have asked me about it, and there might even been some  
commercial apps wanting a simple/easy/kick-ass command-line (remote  
scriptable) interface to their application on the horizon too.


If any of you remember the JBucks days, when I whittled Twiddle out  
of thin air as a pluggable command-line  framework (only realized  
to invoke lame JMX muck)... well, GShell is here to carve out its  
own notch... or well, I hope it can get sharp enough to cut  
something.  I think it will... just believe, imagine and well we  
make dreams reality her in the land of source which is open...  
na... aighty.


Keep in mind this is an *alpha-1* release, and is a little rough  
(or in some cases more than a little) around the corners.  I hope,  
with the help, guidance and suggestions of the community, that we  
can sort though all of the significant issues and polish GShell off  
enough to make it generally mass-consumable by applications (like  
ServiceMix, ActiveMQ, and other sister server-orient projects which  
need a sophisticated command-line interface for administration,  
configuration, whatever).


This version of GShell was inspired a little (okay... a lot) by the  
work I've done on the Groovy projects 'groovysh' command-line tool  
( http://groovy.codehaus.org/Groovy+Shell ).  Actually working on  
'groovysh' really helped me to figure out many things w/GShell...  
and maybe one day Groovy's 'groovysh' will actually use GShell as a  
framework, though there is a bit of work left in the core to make  
that a reality.  For folks that haven't use my new 'groovysh', you  
can easily have a look by using the 'groovy-maven-plugin', as in:


  mvn groovy:shell

You'll notice a lot of similarities between 'groovysh' and 'gsh'  
I'm sure.


* * *

While working on this release I've come to realize that GShell and  
Maven2 are very similar creatures... which I'll elaborate on more  
in the future... but because of that significant functionality  
which is already implemented in Maven2 is 90% (or sometimes more)  
compatible with the direction GShell is headed towards.  For  
example, one feature alpha-2 will have is to allow command plugins  
to define 'dependencies' just as a Maven project does now.  And  
GShell can be configured (a bit more flexibly than Maven ATM) for  
how to find those dependencies (in a local repo, in a remote repo,  
in some uber-jar, etc).  This will all leverage the maturing Maven2  
codebase.  So in some ways GShell will grow with Maven2 as they  
both become more and more functional, stable, reliable... and well  
ass-kicking no doubt.


Um... crap, I'm e-babbling again; sorry.   So, lets vote and push  
this puppy out already... ?!


+1  Oh ya, come on baby... you know you want it
+0	Um... I don't know what is wrong with batch personally, can't we  
just use that?
-1	I like cheese, cheese makes me happy... but damn it cheese won't  
let me remotely administer my application... wtf, no way... WAIT


So, its Friday evening, 6ish PST... so lets say _sometime_ on  
Tuesday the 25th I'll call the vote.  That is a little more than 72  
hours... so get your #2 pencils out and shake what your mother gave  
ya...


--jason

Re: GShell 1.0-alpha-1 release update

2007-12-14 Thread Jason Dillon

No worries take a whack at it. Though IMO its too bad the "apache way" slows 
down releasing binaries so much. Like I want to push out alpha-1 um like a week 
ago. I know there are holes, which well filla nd then roll out another alpha. 

Its certainly not going to be perfect that's for sure. Which is why I tend to 
follow the release often strategy. Push out something that is functional, fix 
it up and then push it out again. 

Seems to me like we have a 2-3 week minumum for each release, almost 
regaurdless of what it is... Though the javaee server and its tck muck 
certainly adds on more weeks. 

It seems like if nothing at all changed ina subproject it will still take the 
better part of a month to make a release :-(

Well take a look... Let's try to get this finished in the next week na... I'm 
goinig to be out of the country for 3 weeks startin on the 22nd And I'd 
reallly, really like to have the release done by then

But more so I think we need to rethink our stratagy.  on releases It should 
be easy and quick. IMO the 3 day vote period is long enough :-P

Well ping me if you need something changed. I'm at your disposal next week if 
it helps move things along...aight?

:-)

--jason

-Original Message-
From: Kevan Miller <[EMAIL PROTECTED]>

Date: Fri, 14 Dec 2007 20:07:07 
To:dev@geronimo.apache.org
Subject: Re: GShell 1.0-alpha-1 release update

On Dec 14, 2007, at 3:12 PM, Jason Dillon wrote:

> I *completely* agree!!
>
> I'm going to give it the rest of the day for feedback on my email  
> and if there is no decent, then I will start the vote.

At the moment, some Geronimo commands are/will be(?) available *only*  
through gshell (e.g. assemble). So, I'm interested in insuring that  
gshell does have "meets-min" capabilities. You could argue that we  
should have console/java cli support for these functions (or I'm just  
wrong... ;-), but that's the way things are ATM...

I'm not advocating for a more robust 'help' command. However, I would  
like to be sure it's readable and instructive.

Personally, I'd like to take a little time to kick the tires and make  
sure we don't have any glaring problems...

--kevan

Re: [VOTE] Release GShell 1.0-alpha-1

2007-12-14 Thread Jason Dillon

+1

 * * *

Oh, and I forgot to mention... that I'd really like to thank David
Jencks for taking the time to fiddle with things, provide feedback and
really I'd even go as far as advocating using GShell.

Jeff Genender too, who has been pimping GShell to the Terracotta folks
(who I've heard really dig GShell).

Guillaume Nodet too for his help in gentrification of GShell to allow
the codebase to work with Plexus and OSGI environments.

And those of you who have committed patches (ie. Jason #2... their can
be only one... hehe).  Ha, its like I'm accepting an Oscar or
something...

/me hears the music start to play

Anyways... thanks to everyone.  And I really do look forward to any
and all input/comments/suggestions/whatever you have to say (not that
I'll like it mind you), but I value all input... aighty?

Cheers,

--jason



On Dec 14, 2007 6:02 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Oh ya... the time is now, all you party people get out on the floor
> and shake what your mother gave ya...
>
> This is the *first* _official_ release of GShell... and I invite all
> of you to go an have a quick look over the only docs we got at the
> moment:
>
> http://cwiki.apache.org/GSHELL
>
> More docs are on there way I can assure you... as well as more
> features, functionality and fun with your command-line... aight!
>
>  * * *
>
> GShell has been a dream of mine for... er um what seems like years
> now... oh wait it has been years.  And well, the universe has finally
> aligned and things are falling into place quite nicely I'd say.  Some
> external groups are already consuming these goodies, others have asked
> me about it, and there might even been some commercial apps wanting a
> simple/easy/kick-ass command-line (remote scriptable) interface to
> their application on the horizon too.
>
> If any of you remember the JBucks days, when I whittled Twiddle out of
> thin air as a pluggable command-line  framework (only realized to
> invoke lame JMX muck)... well, GShell is here to carve out its own
> notch... or well, I hope it can get sharp enough to cut something.  I
> think it will... just believe, imagine and well we make dreams reality
> her in the land of source which is open... na... aighty.
>
> Keep in mind this is an *alpha-1* release, and is a little rough (or
> in some cases more than a little) around the corners.  I hope, with
> the help, guidance and suggestions of the community, that we can sort
> though all of the significant issues and polish GShell off enough to
> make it generally mass-consumable by applications (like ServiceMix,
> ActiveMQ, and other sister server-orient projects which need a
> sophisticated command-line interface for administration,
> configuration, whatever).
>
> This version of GShell was inspired a little (okay... a lot) by the
> work I've done on the Groovy projects 'groovysh' command-line tool ( 
> http://groovy.codehaus.org/Groovy+Shell
>  ).  Actually working on 'groovysh' really helped me to figure out
> many things w/GShell... and maybe one day Groovy's 'groovysh' will
> actually use GShell as a framework, though there is a bit of work left
> in the core to make that a reality.  For folks that haven't use my new
> 'groovysh', you can easily have a look by using the 'groovy-maven-
> plugin', as in:
>
> mvn groovy:shell
>
> You'll notice a lot of similarities between 'groovysh' and 'gsh' I'm
> sure.
>
>  * * *
>
> While working on this release I've come to realize that GShell and
> Maven2 are very similar creatures... which I'll elaborate on more in
> the future... but because of that significant functionality which is
> already implemented in Maven2 is 90% (or sometimes more) compatible
> with the direction GShell is headed towards.  For example, one feature
> alpha-2 will have is to allow command plugins to define 'dependencies'
> just as a Maven project does now.  And GShell can be configured (a bit
> more flexibly than Maven ATM) for how to find those dependencies (in a
> local repo, in a remote repo, in some uber-jar, etc).  This will all
> leverage the maturing Maven2 codebase.  So in some ways GShell will
> grow with Maven2 as they both become more and more functional, stable,
> reliable... and well ass-kicking no doubt.
>
> Um... crap, I'm e-babbling again; sorry.   So, lets vote and push this
> puppy out already... ?!
>
> +1  Oh ya, come on baby... you know you want it
> +0  Um... I don't know what is wrong with batch personally, can't we
> just use that?
> -1  I like cheese, cheese makes me happy... but damn it cheese won't
> let me remotely administer my application... wtf, no way... WAIT
>
> So, its Friday evening, 6ish PST... so lets say _sometime_ on Tuesday
> the 25th I'll call the vote.  That is a little more than 72 hours...
> so get your #2 pencils out and shake what your mother gave ya...
>
> --jason
>
>
>

[VOTE] Release GShell 1.0-alpha-1

2007-12-14 Thread Jason Dillon

Oh ya... the time is now, all you party people get out on the floor
and shake what your mother gave ya...

This is the *first* _official_ release of GShell... and I invite all
of you to go an have a quick look over the only docs we got at the
moment:

http://cwiki.apache.org/GSHELL

More docs are on there way I can assure you... as well as more
features, functionality and fun with your command-line... aight!

* * *

GShell has been a dream of mine for... er um what seems like years
now... oh wait it has been years. And well, the universe has finally
aligned and things are falling into place quite nicely I'd say. Some
external groups are already consuming these goodies, others have asked
me about it, and there might even been some commercial apps wanting a
simple/easy/kick-ass command-line (remote scriptable) interface to
their application on the horizon too.

If any of you remember the JBucks days, when I whittled Twiddle out of
thin air as a pluggable command-line framework (only realized to
invoke lame JMX muck)... well, GShell is here to carve out its own
notch... or well, I hope it can get sharp enough to cut something. I
think it will... just believe, imagine and well we make dreams reality
her in the land of source which is open... na... aighty.

Keep in mind this is an *alpha-1* release, and is a little rough (or
in some cases more than a little) around the corners. I hope, with
the help, guidance and suggestions of the community, that we can sort
though all of the significant issues and polish GShell off enough to
make it generally mass-consumable by applications (like ServiceMix,
ActiveMQ, and other sister server-orient projects which need a
sophisticated command-line interface for administration,
configuration, whatever).

This version of GShell was inspired a little (okay... a lot) by the
work I've done on the Groovy projects 'groovysh' command-line tool ( http://groovy.codehaus.org/Groovy+Shell
). Actually working on 'groovysh' really helped me to figure out
many things w/GShell... and maybe one day Groovy's 'groovysh' will
actually use GShell as a framework, though there is a bit of work left
in the core to make that a reality. For folks that haven't use my new
'groovysh', you can easily have a look by using the 'groovy-maven-
plugin', as in:

mvn groovy:shell

You'll notice a lot of similarities between 'groovysh' and 'gsh' I'm
sure.

* * *

While working on this release I've come to realize that GShell and
Maven2 are very similar creatures... which I'll elaborate on more in
the future... but because of that significant functionality which is
already implemented in Maven2 is 90% (or sometimes more) compatible
with the direction GShell is headed towards. For example, one feature
alpha-2 will have is to allow command plugins to define 'dependencies'
just as a Maven project does now. And GShell can be configured (a bit
more flexibly than Maven ATM) for how to find those dependencies (in a
local repo, in a remote repo, in some uber-jar, etc). This will all
leverage the maturing Maven2 codebase. So in some ways GShell will
grow with Maven2 as they both become more and more functional, stable,
reliable... and well ass-kicking no doubt.

Um... crap, I'm e-babbling again; sorry. So, lets vote and push this
puppy out already... ?!

So, its Friday evening, 6ish PST... so lets say _sometime_ on Tuesday
the 25th I'll call the vote. That is a little more than 72 hours...
so get your #2 pencils out and shake what your mother gave ya...

--jason

Re: [VOTE RESULT] Release Genesis 1.3

2007-12-14 Thread Jason Dillon

Release is done, pending sync to Central... hopefully in an hour or  
so... and then things should be sorted.


--jason


On Dec 14, 2007, at 12:17 PM, Jason Dillon wrote:


Looks like this vote passed:

   +1   12
   +0   2
   -1   0

(Sorry, I'm too lazy to list all the names, peep at the nabble  
archive if you wanna know aighty?)


* * *

And with no naysayers... I herby decree that Genesis 1.3 shall be  
released... which I'll do later tonight or tomorrow pending on the  
mood of the universe.


--jason


On Dec 11, 2007, at 1:58 AM, Jason Dillon wrote:

Folks, a small change to Genesis was made to support a custom legal  
resource bundle for the GShell release.  I'd like to get this out  
so we can get GShell out too.


+1 -Release it
+0 -Eh, whatever
-1 -Um, no no no no no...

--jason

Re: Building with c:\Documents and Setting as .m2 repo

2007-12-14 Thread Jason Dillon

I hearby decree that the operating system know as "windows" is officially the 
crappiest of the most possible crap that anyone in the entire universe has ever 
crapped before. Ya and that does include crazy alien crap too. 

--jason


--Original Message--
From: Anita Kulshreshtha
To: dev@geronimo.apache.org
ReplyTo: dev@geronimo.apache.org
Sent: Dec 14, 2007 4:08 PM
Subject: Re: Building with c:\Documents and Setting as .m2 repo

It worked before Nov 28th. The default user home on windows is
c:\Documents and Settings\uesr and maven uses it for default .m2 repo.
Thanks for looking into this..

Anita

--- David Jencks <[EMAIL PROTECTED]> wrote:

> This is probably my fault.  Do you know when the last time it worked 
> 
> was?  Is this the normal m2 repo location on xp?  I have a lot of  
> local changes around this area that I'm hoping to get working and  
> committed today: hopefully this will get fixed as part of those
> changes.
> 
> thanks
> david jencks
> 
> On Dec 14, 2007, at 8:35 AM, Anita Kulshreshtha wrote:
> 
> >I get following stack trace while building using "c:\Documents
> and
> > Setting" as .m2 repo. This used to work..
> >
> > Thanks
> > Anita
> >
> > Caused by:
> > org.apache.geronimo.kernel.repository.MissingDependencyException:
> > Missing
> > artifact in repositories:
> > [file:/C:/Documents%20and%20Settings//.m2/repository/]
> >
> > Missing dependency:
> > org.apache.geronimo.configs/server-security-config/2.1-SNAPSHOT/c
> > ar
> > at
> > org.apache.geronimo.system.plugin.PluginInstallerGBean.findArtifact
> 
> > (Plugin
> > InstallerGBean.java:1624)
> > at
> > org.apache.geronimo.system.plugin.PluginInstallerGBean.openStream 
> > (PluginIn
> > stallerGBean.java:1424)
> > at
> >
>
org.apache.geronimo.system.plugin.PluginInstallerGBean.downloadArtifac
> 
> > t(Pl
> > uginInstallerGBean.java:10

Re: Building with c:\Documents and Setting as .m2 repo

2007-12-14 Thread Jason Dillon

I hearby decree that the operating system know as "windows" is officially the 
crappiest of the most possible crap that anyone in the entire universe has ever 
crapped before. Ya and that does include crazy alien crap too. 

--jason


-Original Message-
From: Anita Kulshreshtha <[EMAIL PROTECTED]>

Date: Fri, 14 Dec 2007 16:08:00 
To:dev@geronimo.apache.org
Subject: Re: Building with c:\Documents and Setting as .m2 repo


It worked before Nov 28th. The default user home on windows is
c:\Documents and Settings\uesr and maven uses it for default .m2 repo.
Thanks for looking into this..

Anita

--- David Jencks <[EMAIL PROTECTED]> wrote:

> This is probably my fault.  Do you know when the last time it worked 
> 
> was?  Is this the normal m2 repo location on xp?  I have a lot of  
> local changes around this area that I'm hoping to get working and  
> committed today: hopefully this will get fixed as part of those
> changes.
> 
> thanks
> david jencks
> 
> On Dec 14, 2007, at 8:35 AM, Anita Kulshreshtha wrote:
> 
> >I get following stack trace while building using "c:\Documents
> and
> > Setting" as .m2 repo. This used to work..
> >
> > Thanks
> > Anita
> >
> > Caused by:
> > org.apache.geronimo.kernel.repository.MissingDependencyException:
> > Missing
> > artifact in repositories:
> > [file:/C:/Documents%20and%20Settings//.m2/repository/]
> >
> > Missing dependency:
> > org.apache.geronimo.configs/server-security-config/2.1-SNAPSHOT/c
> > ar
> > at
> > org.apache.geronimo.system.plugin.PluginInstallerGBean.findArtifact
> 
> > (Plugin
> > InstallerGBean.java:1624)
> > at
> > org.apache.geronimo.system.plugin.PluginInstallerGBean.openStream 
> > (PluginIn
> > stallerGBean.java:1424)
> > at
> >
>
org.apache.geronimo.system.plugin.PluginInstallerGBean.downloadArtifac
> 
> > t(Pl
> > uginInstallerGBean.java:1021)
> > at
> > org.apache.geronimo.system.plugin.PluginInstallerGBean.install 
> > (PluginInsta
> > llerGBean.java:675)
> > at
> > org.apache.geronimo.mavenplugins.car.InstallModulesMojo.doExecute 
> > (InstallM
> > odulesMojo.java:163)
> > at
> > org.codehaus.mojo.pluginsupport.MojoSupport.execute 
> > (MojoSupport.java:122)
> > ... 18 more
> > [INFO]
> >
>
--
> 
> > --
> > [INFO] Total time: 29 seconds
> > [INFO] Finished at: Fri Dec 14 10:45:06 EST 2007
> > [INFO] Final Memory: 50M/254M
> > [INFO]  
> >
>
--
> 
> > --
> >
> >
> >
> >
>
__
> 
> > __
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile.  Try it now.  http:// 
> > mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> 
> 



  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[VOTE RESULT] Release Genesis 1.3

2007-12-14 Thread Jason Dillon


Looks like this vote passed:

+1  12
+0  2
-1  0

(Sorry, I'm too lazy to list all the names, peep at the nabble archive  
if you wanna know aighty?)


 * * *

And with no naysayers... I herby decree that Genesis 1.3 shall be  
released... which I'll do later tonight or tomorrow pending on the  
mood of the universe.


--jason


On Dec 11, 2007, at 1:58 AM, Jason Dillon wrote:

Folks, a small change to Genesis was made to support a custom legal  
resource bundle for the GShell release.  I'd like to get this out so  
we can get GShell out too.


+1 -Release it
+0 -Eh, whatever
-1 -Um, no no no no no...

--jason

Re: [VOTE] Release Genesis 1.3

2007-12-14 Thread Jason Dillon

Ooops, I always forget to vote...
+1

--jason


On Dec 11, 2007 1:58 AM, Jason Dillon <[EMAIL PROTECTED]> wrote:

> Folks, a small change to Genesis was made to support a custom legal
> resource bundle for the GShell release.  I'd like to get this out so
> we can get GShell out too.
>
> +1 -Release it
> +0 -Eh, whatever
> -1 -Um, no no no no no...
>
> --jason
>

Re: GShell 1.0-alpha-1 release update

2007-12-14 Thread Jason Dillon


I *completely* agree!!

I'm going to give it the rest of the day for feedback on my email and  
if there is no decent, then I will start the vote.


--jason


On Dec 14, 2007, at 11:51 AM, Guillaume Nodet wrote:

I'd like to release GShell asap.  Having more frequent release is  
imho a good idea (though it's usually easier to say than to do...).

GShell is already useful, even if there is still lots of things to do.

On Dec 14, 2007 8:35 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
Folks, the majority of the issues (mostly legal muck) and a few small
bugs/improvements have been cleaned up for the 1.0-alpha-1 release of
GShell.

There is one issue which has been pointed out regarding the 'help'
command, which ATM is less than ideal, but does show the information.
The idea of the 'help' command is to be sort of a combination of 'ls'
and 'man', so that running it with no argument shows the commands
available in the current context, and running with an argument, the
argument is assumed to be a command path, which is resolved and the
help docs for the command are displayed.

To make this work is a little bit more than a minor change, and I've
planned to get it fixed up for the next version (hopefully in a few
months)... and really, this is a moderately complex command which is
well suited for someone wanting to learn more about how GShell works
to tackle (which another reason why I didn't make it all super-uber-
sexy).

BUT... I think we really need to get 1.0-alpha-1 released, so it can
be consumed by G 2.1 (as well as other projects which are starting to
use GShell).  And IMO, the 'help' commands ugliness is not a big
enough priority to delay the release.

IMO, GShell is still a work in progress, while quite functional for
many purposes, its still a little rough around the edges and will take
some more love to sift through the issues, flesh out the features and
iron those pesky buggers out.  My recommendation is that for G 2.1
that we don't advertise GShell as a _feature_, but just let it be
ASIS, handling the CLI bits for G and average users won't really know
the difference.  Advanced folks might want to play with it, which is
fine (good even to get more feedback), but I don't think that G 2.1 is
the release where we want to unleash this on to the world.

I would rather let GShell cook... and then simmer for a while longer,
pull in more feedback (as now more folks are starting to be aware of
the framework and are implementing tools with it *yay*), fix up the
architecture, fill in some major holes, write some *real*
documentation, and then hand it to the masses... perhaps in G 2.2.

Though keep in mind, GShell isn't really Geronimo-specific... its
intended to be a light(ish) framework for building rich command-line
applications.  It just so happens that Geronimo needs such a system to
handle its growing cli needs.  And GShell's remote login feature makes
it ideal for administrators to use that cli to perform installs,
maintenance, scripts ala BSF or whatever.

Geronimo is definitely, well... IMO, an ideal candidate for GShell
integration and I really believe that there is a *huge* value add
here.  But... before we go telling the world how dope the GShell
integration in Geronimo is... I'd really like to fix some of its warts
and create some documentation.

 * * *

Anyways, the point of this email is really to ask you folks... can we
live with how GShell works right now for the 1.0-alpha-1 release?  Or
are their any blocking issues which *must* be resolved?

I'd really like to spin up a vote today or tomorrow... so if anyone
has any input... now is the time.

--jason

PS.  Thanks for those of you who have taken time to play with GShell
and provided feedback.  Your input is invaluable and IMO critical to
the growth and success of GShell.  So thanks again!



--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

GShell 1.0-alpha-1 release update

2007-12-14 Thread Jason Dillon

Folks, the majority of the issues (mostly legal muck) and a few small  
bugs/improvements have been cleaned up for the 1.0-alpha-1 release of  
GShell.


There is one issue which has been pointed out regarding the 'help'  
command, which ATM is less than ideal, but does show the information.   
The idea of the 'help' command is to be sort of a combination of 'ls'  
and 'man', so that running it with no argument shows the commands  
available in the current context, and running with an argument, the  
argument is assumed to be a command path, which is resolved and the  
help docs for the command are displayed.


To make this work is a little bit more than a minor change, and I've  
planned to get it fixed up for the next version (hopefully in a few  
months)... and really, this is a moderately complex command which is  
well suited for someone wanting to learn more about how GShell works  
to tackle (which another reason why I didn't make it all super-uber- 
sexy).


BUT... I think we really need to get 1.0-alpha-1 released, so it can  
be consumed by G 2.1 (as well as other projects which are starting to  
use GShell).  And IMO, the 'help' commands ugliness is not a big  
enough priority to delay the release.


IMO, GShell is still a work in progress, while quite functional for  
many purposes, its still a little rough around the edges and will take  
some more love to sift through the issues, flesh out the features and  
iron those pesky buggers out.  My recommendation is that for G 2.1  
that we don't advertise GShell as a _feature_, but just let it be  
ASIS, handling the CLI bits for G and average users won't really know  
the difference.  Advanced folks might want to play with it, which is  
fine (good even to get more feedback), but I don't think that G 2.1 is  
the release where we want to unleash this on to the world.


I would rather let GShell cook... and then simmer for a while longer,  
pull in more feedback (as now more folks are starting to be aware of  
the framework and are implementing tools with it *yay*), fix up the  
architecture, fill in some major holes, write some *real*  
documentation, and then hand it to the masses... perhaps in G 2.2.


Though keep in mind, GShell isn't really Geronimo-specific... its  
intended to be a light(ish) framework for building rich command-line  
applications.  It just so happens that Geronimo needs such a system to  
handle its growing cli needs.  And GShell's remote login feature makes  
it ideal for administrators to use that cli to perform installs,  
maintenance, scripts ala BSF or whatever.


Geronimo is definitely, well... IMO, an ideal candidate for GShell  
integration and I really believe that there is a *huge* value add  
here.  But... before we go telling the world how dope the GShell  
integration in Geronimo is... I'd really like to fix some of its warts  
and create some documentation.


 * * *

Anyways, the point of this email is really to ask you folks... can we  
live with how GShell works right now for the 1.0-alpha-1 release?  Or  
are their any blocking issues which *must* be resolved?


I'd really like to spin up a vote today or tomorrow... so if anyone  
has any input... now is the time.


--jason

PS.  Thanks for those of you who have taken time to play with GShell  
and provided feedback.  Your input is invaluable and IMO critical to  
the growth and success of GShell.  So thanks again!

[jira] Commented: (GSHELL-86) command groups in help screen


[ 
https://issues.apache.org/jira/browse/GSHELL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551839
 ] 

Jason Dillon commented on GSHELL-86:


Understood... and thank you :-)

So for alpha-1 we are basically sorted only the smallest changes are going in.  
Hopefully will release in a day or so... er I mean start a vote in a day or so.

 * * *

I will start to write up some roadmap documentation, kinda like a brain-dump 
for what I'm thinking, maybe some crude UML or sketches too... so that we can 
have some discussion around whats going to change for alpha-2... and how it 
will keep working for your needs, Geronimos needs... and still make me feel 
happy that GShell will dominate the universe in due time :-)

> command groups in help screen
> -
>
> Key: GSHELL-86
> URL: https://issues.apache.org/jira/browse/GSHELL-86
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Reporter: Jarek Gawor
> Fix For: 1.0-alpha-1
>
>
> The help screen shows the following:
>   ...
>   /deploy
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..
> which I would interpret that I need to type "/deploy/connect" to execute the 
> command. But that does not work but "deploy/connect" works. So I would 
> propose updating the help screen to show the slash at the end of the group 
> name instead of the front. e.g.:
>   ...
>   deploy/
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

GShell legal muck

2007-12-14 Thread Jason Dillon

Hey Kevan, I *think*... nay, *hope* the GShell legal files are now all  
in order.  I've added the NOTICE and LICENSE for gshell-embeddable,  
gshell-diet-log4j has some custom bits and the rest are all using the  
legal-bundle from Genesis via the m-r-r-p.


I'm going to deploy a new set of artifacts.  Can you please review?

I've committed a few other minor changes, might add a few more, but I  
think we are 95% (or more) ready for release.


So if you can review the legal files and give me the nod, then I will  
spin up a vote.


:-)

--jason


PS. I've been up all night hacking on stuff, so I'll probs not be  
around until later tonight.

[jira] Closed: (GSHELL-86) command groups in help screen


 [ 
https://issues.apache.org/jira/browse/GSHELL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-86.
--

Resolution: Fixed

Okay, I've stripped of the leading "/"... but really this command needs a 
healthy looking  at and a swift kick in the rear.  I think with the next 
release the path stuff (or sub-shell) whatever it be, should be better sorted 
out and we can fix this command then.

> command groups in help screen
> -
>
> Key: GSHELL-86
> URL: https://issues.apache.org/jira/browse/GSHELL-86
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Reporter: Jarek Gawor
> Fix For: 1.0-alpha-1
>
>
> The help screen shows the following:
>   ...
>   /deploy
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..
> which I would interpret that I need to type "/deploy/connect" to execute the 
> command. But that does not work but "deploy/connect" works. So I would 
> propose updating the help screen to show the slash at the end of the group 
> name instead of the front. e.g.:
>   ...
>   deploy/
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: structure of GShell commands

2007-12-14 Thread Jason Dillon

The structure is just for namespace, you can arrange commands however  
you like... one of the benefits of GShell.


I just setup the structure, cause I'm anal and I organize  
everything... er except my bedroom, which is a huge cluster*uck.


 * * *

My _recommendation_ is to have some sort of organization... though it  
doesn't need to be "geronimo/*"...


Assuming that the configuration of GShell is specific to Geronimo,  
then lets consider what someone using the interface might want/expect/ 
need?  But also keep in mind that they are free to drop in other  
commands, like the BSF scripting bits (the 'script' command) or the  
VFS commands (currently only 'copy') or remote support ('remote- 
shell', 'rsh', 'remote-shell-server', 'rshd').


I'm not sure what the right organization is really... cause we are  
just getting things rolling in this direction.


So I say we take a stab at what we *think* folks want, then do it...  
and make changes later as needed.  IMO there is no reason not to  
change something if we are making it easier/better.


--jason


On Dec 13, 2007, at 5:22 AM, Matt Hogstrom wrote:

If GShell would be targeted at more servers than G then I think  
these commands should be under geronimo.  If not, then I think a  
flat structure makes sense.


On Dec 11, 2007, at 10:04 AM, Kevan Miller wrote:

We currently have the following structure for Geronimo GShell  
commands:


geronimo/
start-server
stop-server
start-client

deploy/
install-library
disconnect
deploy
...

This doesn't make much sense to me. Let's either assume GShell is  
used for Geronimo server or assume that GShell can be used for  
multiple target environments, but not both...


I think the current deploy/ commands should be under the geronimo  
tree. What do others think? I think applying a bit more structure,  
now, will minimize entropy over time...


Anybody want to have a shot at proposing a command structure?

--kevan

[jira] Commented: (GSHELL-86) command groups in help screen


[ 
https://issues.apache.org/jira/browse/GSHELL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551830
 ] 

Jason Dillon commented on GSHELL-86:


Sooo... the only significant difference, is that instead of:

{noformat}
obr info
{noformat}

You would:

{noformat}
obr/info
{noformat}

Or if you like:

{noformat}
obr
info
{noformat}

But... please *do* keep the thoughts and ideas coming in!!!  GShell ASIS is 
basically what I had been dreaming about since the JBucks 3.x days w/Twiddle 
(and what I really wanted to have in G 1.0, but eh...).

My point is though that I've been working insolation with-out input for a while 
on this stuff, so some of the ways GShell works are just based on my own 
preferences and whatever.  I do want to make GShell as *easy* to use a possible 
and make it be able to do *just about anything* that someone wants in a cli app.

So... lets see if we can make it work for everyone :-)


> command groups in help screen
> -
>
> Key: GSHELL-86
> URL: https://issues.apache.org/jira/browse/GSHELL-86
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Reporter: Jarek Gawor
> Fix For: 1.0-alpha-1
>
>
> The help screen shows the following:
>   ...
>   /deploy
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..
> which I would interpret that I need to type "/deploy/connect" to execute the 
> command. But that does not work but "deploy/connect" works. So I would 
> propose updating the help screen to show the slash at the end of the group 
> name instead of the front. e.g.:
>   ...
>   deploy/
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GSHELL-86) command groups in help screen


[ 
https://issues.apache.org/jira/browse/GSHELL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551828
 ] 

Jason Dillon commented on GSHELL-86:


So the point of the path and tree muck in GShell is to facilitate this 
_sub-shell_ idea, so that a _sub-shell_ is simply a namespace for commands.  
And when you enter the name of a path (which exists) then the current path is 
set to that path, changing the name-space and effectively entering that 
sub-shell.

BTW, you are free to re-implement the {{help}} command and bind in your own 
version that behaves better for your application in the layout :-)

> command groups in help screen
> -
>
> Key: GSHELL-86
> URL: https://issues.apache.org/jira/browse/GSHELL-86
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Reporter: Jarek Gawor
> Fix For: 1.0-alpha-1
>
>
> The help screen shows the following:
>   ...
>   /deploy
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..
> which I would interpret that I need to type "/deploy/connect" to execute the 
> command. But that does not work but "deploy/connect" works. So I would 
> propose updating the help screen to show the slash at the end of the group 
> name instead of the front. e.g.:
>   ...
>   deploy/
>   list-plugins  Install plugins into a geronimo server
>   connect   Connect to a Geronimo server
>   disconnectDisconnect from a Geronimo server
>   ..

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-97) License and Notice info for gshell-embeddable


 [ 
https://issues.apache.org/jira/browse/GSHELL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-97.
--

Resolution: Fixed

Using some groovy muck and static LICENSE and NOTICE files for this... maybe 
one day we can make the templates do our bidding, but for now... a wee bit of 
build magic and the problem is solved.

> License and Notice info for gshell-embeddable
> -
>
> Key: GSHELL-97
> URL: https://issues.apache.org/jira/browse/GSHELL-97
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Build
>Affects Versions: 1.0-alpha-1
>Reporter: Kevan Miller
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-1
>
> Attachments: embeddableLicense.txt, embeddableNotice.txt
>
>
> gshell-embeddable needs to License and Notice files to be included in the jar 
> file.
> I'm not sure how to add these when using the shade plugin. Hoping Jason D can 
> lend a hand.
> Will attach the license and notice files to this jira.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-74) Update/include license/notice and other legal muck


 [ 
https://issues.apache.org/jira/browse/GSHELL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-74.
--

Resolution: Fixed

> Update/include license/notice and other legal muck
> --
>
> Key: GSHELL-74
> URL: https://issues.apache.org/jira/browse/GSHELL-74
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r604053 - /geronimo/server/trunk/pom.xml

2007-12-13 Thread Jason Dillon

I've changed the rule to allow 2.0.5, 2.0.6 and 2.0.7, which AFAIK  
should build the tree correctly.


I've also created an issue to fix the 2.0.8 problems:

https://issues.apache.org/jira/browse/GERONIMO-3705

--jason


On Dec 13, 2007, at 5:49 PM, Jarek Gawor wrote:


Ok, sure but doesn't that cut off 2.0.5 and 2.0.6 users?

Jarek

On Dec 13, 2007 8:28 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:

Aye.

--jason



On Dec 13, 2007, at 5:13 PM, Jay D. McHugh wrote:


I believe that the build will crash if you use Maven 2.0.8

That is probably why Jason forced the maven version.

Jay

Jarek Gawor wrote:

Jason,

Can you give a reason for this change? I might have to update a few
machines.

Thanks,
Jarek

On Dec 13, 2007 5:41 PM,  <[EMAIL PROTECTED]> wrote:

Author: jdillon
Date: Thu Dec 13 14:41:50 2007
New Revision: 604053

URL: http://svn.apache.org/viewvc?rev=604053&view=rev
Log:
Require Maven 2.0.7 for now

Modified:
  geronimo/server/trunk/pom.xml

Modified: geronimo/server/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=604053&r1=604052&r2=604053&view=diff
=
=
=
=
=
=
=
=
=
=
= 
= 
==

--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu Dec 13 14:41:50 2007
@@ -2095,9 +2095,9 @@
   [1.5,1.6)
   

-
+
   
-[2.0.5,)
+[2.0.7]

[jira] Created: (GERONIMO-3705) Maven 2.0.8 causes build problems

Maven 2.0.8 causes build problems
-

 Key: GERONIMO-3705
 URL: https://issues.apache.org/jira/browse/GERONIMO-3705
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: buildsystem
Affects Versions: 2.1
Reporter: Jason Dillon
Assignee: Jason Dillon
Priority: Critical




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r604053 - /geronimo/server/trunk/pom.xml

2007-12-13 Thread Jason Dillon

I suppose 2.0.6 should work. We can include that. 

--jason


-Original Message-
From: "Jarek Gawor" <[EMAIL PROTECTED]>

Date: Thu, 13 Dec 2007 20:49:10 
To:dev@geronimo.apache.org
Subject: Re: svn commit: r604053 - /geronimo/server/trunk/pom.xml


Ok, sure but doesn't that cut off 2.0.5 and 2.0.6 users?

Jarek

On Dec 13, 2007 8:28 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Aye.
>
> --jason
>
>
>
> On Dec 13, 2007, at 5:13 PM, Jay D. McHugh wrote:
>
> > I believe that the build will crash if you use Maven 2.0.8
> >
> > That is probably why Jason forced the maven version.
> >
> > Jay
> >
> > Jarek Gawor wrote:
> >> Jason,
> >>
> >> Can you give a reason for this change? I might have to update a few
> >> machines.
> >>
> >> Thanks,
> >> Jarek
> >>
> >> On Dec 13, 2007 5:41 PM,  <[EMAIL PROTECTED]> wrote:
> >>> Author: jdillon
> >>> Date: Thu Dec 13 14:41:50 2007
> >>> New Revision: 604053
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=604053&view=rev
> >>> Log:
> >>> Require Maven 2.0.7 for now
> >>>
> >>> Modified:
> >>>geronimo/server/trunk/pom.xml
> >>>
> >>> Modified: geronimo/server/trunk/pom.xml
> >>> URL: 
> >>> http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=604053&r1=604052&r2=604053&view=diff
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> =
> >>> 
> >>> --- geronimo/server/trunk/pom.xml (original)
> >>> +++ geronimo/server/trunk/pom.xml Thu Dec 13 14:41:50 2007
> >>> @@ -2095,9 +2095,9 @@
> >>> [1.5,1.6)
> >>> 
> >>>
> >>> -
> >>> +
> >>> 
> >>> -[2.0.5,)
> >>> +[2.0.7]
> >>> 
> >>> 
> >>> 
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>

[jira] Commented: (GSHELL-97) License and Notice info for gshell-embeddable


[ 
https://issues.apache.org/jira/browse/GSHELL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551671
 ] 

Jason Dillon commented on GSHELL-97:


Usage of the shade plugin is making this more of a pain to use a static or even 
m-r-r-p generated license/notice... will fix, but probs have to do some custom 
ant or groovy muck to get the right bits in there.

> License and Notice info for gshell-embeddable
> -
>
> Key: GSHELL-97
> URL: https://issues.apache.org/jira/browse/GSHELL-97
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Build
>Affects Versions: 1.0-alpha-1
>Reporter: Kevan Miller
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-1
>
> Attachments: embeddableLicense.txt, embeddableNotice.txt
>
>
> gshell-embeddable needs to License and Notice files to be included in the jar 
> file.
> I'm not sure how to add these when using the shade plugin. Hoping Jason D can 
> lend a hand.
> Will attach the license and notice files to this jira.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r604053 - /geronimo/server/trunk/pom.xml

2007-12-13 Thread Jason Dillon


Aye.

--jason


On Dec 13, 2007, at 5:13 PM, Jay D. McHugh wrote:


I believe that the build will crash if you use Maven 2.0.8

That is probably why Jason forced the maven version.

Jay

Jarek Gawor wrote:

Jason,

Can you give a reason for this change? I might have to update a few  
machines.


Thanks,
Jarek

On Dec 13, 2007 5:41 PM,  <[EMAIL PROTECTED]> wrote:

Author: jdillon
Date: Thu Dec 13 14:41:50 2007
New Revision: 604053

URL: http://svn.apache.org/viewvc?rev=604053&view=rev
Log:
Require Maven 2.0.7 for now

Modified:
   geronimo/server/trunk/pom.xml

Modified: geronimo/server/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=604053&r1=604052&r2=604053&view=diff
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 


--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu Dec 13 14:41:50 2007
@@ -2095,9 +2095,9 @@
[1.5,1.6)


-
+

-[2.0.5,)
+[2.0.7]

Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2

2007-12-13 Thread Jason Dillon

We can remove some of the gshell bloat by not using the gshell- 
embedable jar which contains xstream, jexl, log4j-diet, jline and some  
other bits which are already in the repository.  Might drop things  
down by 1 or 2m.


Also we can make a diet version of groovy and ant, containing on the  
bits which are needed.  Might drop another meg or 2.


The mina stuff... um, that might be because of the remote shell  
stuff?  That probably shouldn't be included...


--jason


On Dec 13, 2007, at 1:03 PM, Joe Bohn wrote:




Joe Bohn wrote:
It looks like the size of our images is increasing dramatically  
(nearly 2x).
For example, the geronimo-jetty6-minimal snapshots have been  
growing like this (these image sizes are from the snapshot repo):
16604006 Jul 26 18:54 geronimo-jetty6-minimal-2.1-20070726.182538-1- 
bin.tar.gz
17086729 Jul 26 18:53 geronimo-jetty6-minimal-2.1-20070726.182538-1- 
bin.zip
22310769 Nov  1 03:19 geronimo-jetty6-minimal-2.1-20071101.014839-2- 
bin.tar.gz
22744083 Nov  1 03:18 geronimo-jetty6-minimal-2.1-20071101.014839-2- 
bin.zip
30812531 Nov 30 22:45 geronimo-jetty6-minimal-2.1-20071130.211933-3- 
bin.tar.gz
31248864 Nov 30 22:43 geronimo-jetty6-minimal-2.1-20071130.211933-3- 
bin.zip

The javaee5 images have also grown significantly.
57099671 Jul 26 18:39 geronimo-jetty6-jee5-2.1-20070726.182538-1- 
bin.tar.gz
58685668 Jul 26 18:36 geronimo-jetty6-jee5-2.1-20070726.182538-1- 
bin.zip
55113050 Nov  1 03:28 geronimo-jetty6-javaee5-2.1-20071101.014839-1- 
bin.tar.gz
56827820 Nov  1 03:25 geronimo-jetty6-javaee5-2.1-20071101.014839-1- 
bin.zip
71313050 Nov 30 22:54 geronimo-jetty6-javaee5-2.1-20071130.211933-2- 
bin.tar.gz
73094816 Nov 30 22:50 geronimo-jetty6-javaee5-2.1-20071130.211933-2- 
bin.zip





Here are the latest image sizes from a build this morning (12/13/07  
svn rev. 603936).   While it appears that things have slightly  
improved, there isn't a substantial difference from earlier (esp. in  
the minimal assemblies).



23492694 Dec 13 15:15 geronimo-framework-2.1-SNAPSHOT-bin.zip
23187538 Dec 13 15:15 geronimo-framework-2.1-SNAPSHOT-bin.tar.gz

29732445 Dec 13 15:15 geronimo-jetty6-minimal-2.1-SNAPSHOT-bin.tar.gz
30216770 Dec 13 15:15 geronimo-jetty6-minimal-2.1-SNAPSHOT-bin.zip

31206202 Dec 13 15:16 geronimo-tomcat6-minimal-2.1-SNAPSHOT-bin.tar.gz
31695270 Dec 13 15:16 geronimo-tomcat6-minimal-2.1-SNAPSHOT-bin.zip

68474964 Dec 13 15:15 geronimo-jetty6-javaee5-2.1-SNAPSHOT-bin.tar.gz
70303613 Dec 13 15:16 geronimo-jetty6-javaee5-2.1-SNAPSHOT-bin.zip

69713173 Dec 13 15:17 geronimo-tomcat6-javaee5-2.1-SNAPSHOT-bin.tar.gz
71559684 Dec 13 15:17 geronimo-tomcat6-javaee5-2.1-SNAPSHOT-bin.zip

As you can see, the framework itself is now larger than the minimal  
assemblies used to be.  Some of the growth in the framework assembly  
(I'm not intending to imply that these should or should not included  
in framework ... just pointing out the new additions to framework):


- boilerplate minimal assembly (3.6M)
- ant (1.2M)
- G-Shell (1.5M)
- yoko (1.8M)
- groovy (2.4M)
- plexus (.5M)
- woodstox (.5M)
- cglib (.33M)
- xstream (.36M)
- mina (.33M)

That accounts for nearly all of the growth since 2.0.2.


Joe

[jira] Closed: (GSHELL-20) `set foo="bar"` does not work as expected


 [ 
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-20.
--

Resolution: Fixed

Thanks :-)

> `set foo="bar"` does not work as expected
> -
>
> Key: GSHELL-20
> URL: https://issues.apache.org/jira/browse/GSHELL-20
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Commands, Core
>Affects Versions: 1.0-alpha-1
>Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Critical
> Fix For: 1.0-alpha-1
>
> Attachments: GShell-20.patch, GShell-20SingleQuote.patch
>
>
> Due to the way parsing happens, this line:
> {noformat}
> set foo="bar"
> {noformat}
> Ends up calling the command with 2 arguments: "foo=" and "bar", which is not 
> what the command expects, which is one argument of: "foo=bar"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GSHELL-20) `set foo="bar"` does not work as expected


 [ 
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GSHELL-20:
---

Affects Version/s: (was: 0.0.1)
   1.0-alpha-1
Fix Version/s: (was: 1.0-alpha-2)
   1.0-alpha-1

I will put this bandaid on for this release :-)

> `set foo="bar"` does not work as expected
> -
>
> Key: GSHELL-20
> URL: https://issues.apache.org/jira/browse/GSHELL-20
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Commands, Core
>Affects Versions: 1.0-alpha-1
>Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Critical
> Fix For: 1.0-alpha-1
>
> Attachments: GShell-20.patch, GShell-20SingleQuote.patch
>
>
> Due to the way parsing happens, this line:
> {noformat}
> set foo="bar"
> {noformat}
> Ends up calling the command with 2 arguments: "foo=" and "bar", which is not 
> what the command expects, which is one argument of: "foo=bar"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GSHELL-20) `set foo="bar"` does not work as expected


 [ 
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-20:
--

Assignee: Jason Dillon  (was: Jason Warner)

> `set foo="bar"` does not work as expected
> -
>
> Key: GSHELL-20
> URL: https://issues.apache.org/jira/browse/GSHELL-20
> Project: GShell
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Commands, Core
>Affects Versions: 1.0-alpha-1
>Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Critical
> Fix For: 1.0-alpha-1
>
> Attachments: GShell-20.patch, GShell-20SingleQuote.patch
>
>
> Due to the way parsing happens, this line:
> {noformat}
> set foo="bar"
> {noformat}
> Ends up calling the command with 2 arguments: "foo=" and "bar", which is not 
> what the command expects, which is one argument of: "foo=bar"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: GShell ANSI colors support on Window.

2007-12-12 Thread Jason Dillon


Did you hear back from Marc about this?

--jason


On Dec 11, 2007, at 9:19 PM, Hiram Chirino wrote:


It was a bit of bummer when I noticed that GShell has no colorized
output on Windows.  :(
But I noticed that the Perl guys were able to do it.  See the
"Win32::Console::ANSI' project [1].

So I updated the jline dll that is used on Windows with the c code
that the Perl project is using and BAM!, we have color.  I sent a note
out to the jline project about this.  Hopefully they incorporate this
feature into future releases.

--
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Re: GShell ANSI colors support on Window.

2007-12-11 Thread Jason Dillon

Swt!

--jason

-Original Message-
From: "Hiram Chirino" <[EMAIL PROTECTED]>

Date: Wed, 12 Dec 2007 00:19:47 
To:dev@geronimo.apache.org, [EMAIL PROTECTED]
Subject: GShell ANSI colors support on Window.

It was a bit of bummer when I noticed that GShell has no colorized
output on Windows.  :(
But I noticed that the Perl guys were able to do it.  See the
"Win32::Console::ANSI' project [1].

So I updated the jline dll that is used on Windows with the c code
that the Perl project is using and BAM!, we have color.  I sent a note
out to the jline project about this.  Hopefully they incorporate this
feature into future releases.

-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

[jira] Updated: (GERONIMO-3700) alias command fails

2007-12-11 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GERONIMO-3700:
---

Component/s: (was: gbuild)
 general

> alias command fails
> ---
>
> Key: GERONIMO-3700
> URL: https://issues.apache.org/jira/browse/GERONIMO-3700
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Reporter: Kevan Miller
>    Assignee: Jason Dillon
> Fix For: 2.1
>
>
> Running the alias command fails with an IllegalStateException:
> [EMAIL PROTECTED]:/> alias
> ERROR IllegalStateException: Alias file 
> /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml
>  does not exist
> Could be that Geronimo should be including this file in assemblies, or gshell 
> should create (if not present), or something else is wrong...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3700) alias command fails

2007-12-11 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GERONIMO-3700:
---

  Component/s: gbuild
Fix Version/s: 2.1

> alias command fails
> ---
>
> Key: GERONIMO-3700
> URL: https://issues.apache.org/jira/browse/GERONIMO-3700
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: gbuild
>Reporter: Kevan Miller
>    Assignee: Jason Dillon
> Fix For: 2.1
>
>
> Running the alias command fails with an IllegalStateException:
> [EMAIL PROTECTED]:/> alias
> ERROR IllegalStateException: Alias file 
> /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml
>  does not exist
> Could be that Geronimo should be including this file in assemblies, or gshell 
> should create (if not present), or something else is wrong...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3700) alias command fails

2007-12-11 Thread Jason Dillon (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550721
 ] 

Jason Dillon commented on GERONIMO-3700:


The alias command has been introduced in {{geronimo-commands}} and is not 
really part of the core GShell bits, so I'm moving this issue.

I've yet to really look at what the alias command is doing, though I did 
suggest that we wanted to use the command alias mechanism in GShell for this... 
but perhaps that mechanism needs more work to be more useful.

> alias command fails
> ---
>
> Key: GERONIMO-3700
> URL: https://issues.apache.org/jira/browse/GERONIMO-3700
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Kevan Miller
>Assignee: Jason Dillon
>
> Running the alias command fails with an IllegalStateException:
> [EMAIL PROTECTED]:/> alias
> ERROR IllegalStateException: Alias file 
> /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml
>  does not exist
> Could be that Geronimo should be including this file in assemblies, or gshell 
> should create (if not present), or something else is wrong...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: jira 404's

2007-12-11 Thread Jason Dillon

I get that too :-(

--jason

--Original Message--
From: Kevan Miller
To: Geronimo Dev
ReplyTo: dev@geronimo.apache.org
Sent: Dec 11, 2007 6:49 AM
Subject: jira 404's

Is anybody else having problems with Jira?

When I create a Geronimo Jira, I get the following 404:

HTTP Status 404 - No view for result [error] exists for action [ViewIssue]

type Status report
message No view for result [error] exists for action [ViewIssue]
description The requested resource (No view for result [error] exists for 
action [ViewIssue]) is not available.

Apache Tomcat/5.5.20

Re: jira 404's

2007-12-11 Thread Jason Dillon

I get that too :-(

--jason

-Original Message-
From: Kevan Miller <[EMAIL PROTECTED]>

Date: Tue, 11 Dec 2007 09:49:58 
To:Geronimo Dev 
Subject: jira 404's

Is anybody else having problems with Jira?

When I create a Geronimo Jira, I get the following 404:

HTTP Status 404 - No view for result [error] exists for action [ViewIssue]

type Status report
message No view for result [error] exists for action [ViewIssue]
description The requested resource (No view for result [error] exists for 
action [ViewIssue]) is not available.

Apache Tomcat/5.5.20

[VOTE] Release Genesis 1.3

2007-12-11 Thread Jason Dillon

Folks, a small change to Genesis was made to support a custom legal  
resource bundle for the GShell release.  I'd like to get this out so  
we can get GShell out too.


+1 -Release it
+0 -Eh, whatever
-1 -Um, no no no no no...

--jason

[jira] Assigned: (GERONIMO-3694) gsh script in javaee5 server assemblies is not marked executable

2007-12-10 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GERONIMO-3694:
--

Assignee: Jason Dillon

> gsh script in javaee5 server assemblies is not marked executable 
> -
>
> Key: GERONIMO-3694
> URL: https://issues.apache.org/jira/browse/GERONIMO-3694
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1
>Reporter: Kevan Miller
>Assignee: Jason Dillon
> Fix For: 2.1
>
>
> 'gsh' is not marked as executable. there seem to be different mechanisms for 
> the different assemblies.
> looks like gsh is executable in framework/minimal assemblies (in fact all 
> files are executable in the bin directory of these assemblies). Better if 
> only shell scripts were marked executable...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GSHELL-46) Add flag to show exception stacktraces

2007-12-10 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GSHELL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GSHELL-46:
--

Assignee: Jason Dillon  (was: Jason Warner)

> Add flag to show exception stacktraces
> --
>
> Key: GSHELL-46
> URL: https://issues.apache.org/jira/browse/GSHELL-46
> Project: GShell
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: CLI
>Affects Versions: 1.0-alpha-1
>    Reporter: Jason Dillon
>Assignee: Jason Dillon
>Priority: Trivial
> Fix For: 1.0-alpha-2
>
> Attachments: GShell-46.patch
>
>
> Add a flag to the main CLI to show exception stacktraces (like mvn -e)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: GShell 1.0-alpha-1 update

2007-12-06 Thread Jason Dillon

Aside from the legal bits and few itty-bitty things GShell is ready  
for a release.  Will try to wrap this up tonight.


--jason


On Nov 30, 2007, at 8:42 AM, Kevan Miller wrote:



On Nov 29, 2007, at 3:18 AM, Jason Dillon wrote:

Folks, I've halted any significant changes to GShell so we can push  
out a stable release for Geronimo to consume in the next week or  
so.  Right now it is pending some dependency releases:


* plexus-cdc-anno
* plexus-component-annotations
* maven-remote-resources-plugin
* groovy-maven-plugin
* cobertura-maven-plugin

I've got the ball rolling on each of those and with a wee bit of  
luck and probably a healthy dose of pestering folks, we should get  
all of these resolved to facilitate the first *official* GShell  
release... yay!


I'm hoping to get GShell 1.0-alpha-1 out in the next week or so,  
really as soon as the deps are published I will start the ball  
moving.  I could use a little help in the mean time for things like  
legal oversight and anything else I might have missed to help make  
the vote+release as smooth as possible,  So if you have a few  
minutes spare it would be nice if you could build the tree and poke  
around a bit er something.


Hi Jason,
I took a look at the GShell source. Things look good. Two files had  
old-style src license headers. I'm updating those.


Remaining work, legal-wise, is getting license/notice files in your  
jars (and updating notice/license file in the root directory). Let's  
sync up later today. Can discuss the maven-remote-resources plugin  
and see if we can get it working for GShell...


--kevan

[jira] Updated: (GSHELL-77) Upgrade Groovy+Maven integration to 1.0-beta-3


 [ 
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon updated GSHELL-77:
---

Summary: Upgrade Groovy+Maven integration to 1.0-beta-3  (was: Upgrade 
Groovy+Maven integreation to 1.0-beta-3)

> Upgrade Groovy+Maven integration to 1.0-beta-3
> --
>
> Key: GSHELL-77
> URL: https://issues.apache.org/jira/browse/GSHELL-77
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-77) Upgrade Groovy+Maven integration to 1.0-beta-3


 [ 
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-77.
--

Resolution: Fixed

> Upgrade Groovy+Maven integration to 1.0-beta-3
> --
>
> Key: GSHELL-77
> URL: https://issues.apache.org/jira/browse/GSHELL-77
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GSHELL-77) Upgrade Groovy+Maven integreation to 1.0-beta-3


[ 
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549206
 ] 

Jason Dillon commented on GSHELL-77:


This is needed for the javacc-m-p

> Upgrade Groovy+Maven integreation to 1.0-beta-3
> ---
>
> Key: GSHELL-77
> URL: https://issues.apache.org/jira/browse/GSHELL-77
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-91) Upgrade to plexus-component-annotations 1.0-alpha-1


 [ 
https://issues.apache.org/jira/browse/GSHELL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-91.
--

Resolution: Fixed

> Upgrade to plexus-component-annotations 1.0-alpha-1
> ---
>
> Key: GSHELL-91
> URL: https://issues.apache.org/jira/browse/GSHELL-91
> Project: GShell
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GSHELL-83) Upgrade to plexus-cdc-anno 1.0-alpha-9


 [ 
https://issues.apache.org/jira/browse/GSHELL-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GSHELL-83.
--

Resolution: Fixed

> Upgrade to plexus-cdc-anno 1.0-alpha-9
> --
>
> Key: GSHELL-83
> URL: https://issues.apache.org/jira/browse/GSHELL-83
> Project: GShell
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: Build
>Reporter: Jason Dillon
>    Assignee: Jason Dillon
> Fix For: 1.0-alpha-1
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GSHELL-83) Upgrade to plexus-cdc-anno 1.0-alpha-9