db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "karan singh malhi (JIRA)" <j...@apache.org>
Subject [jira] Created: (JDO-149) maven console doesnt set properties properly
Date Fri, 23 Sep 2005 18:09:28 GMT
maven console doesnt set properties properly
--------------------------------------------

         Key: JDO-149
         URL: http://issues.apache.org/jira/browse/JDO-149
     Project: JDO
        Type: Improvement
  Components: tck20  
    Reporter: karan singh malhi
    Priority: Trivial


the setProps goal tokenizes properties into some sort of Collection. Maven console does not
work very well if we set properties after the console has started. 

I start maven console using the following command:

karan@j2ee:~/Projects/jdo/trunk/tck20$ maven -bo -Djdo.tck.cfglist=inheritance1.conf -Djdo.tck.identitytypes=applicationidentity
console
-----------------------------------------------------------------------------------------------------------------------
This starts the maven console. Then i run the runtck.jdori goal. Below is the partial output:

jdo2-tck 2.0-SNAPSHOT > [default]
runtck.jdori
build:start:

console:
console:help:

setProps:
    [echo] setProps:
    [echo] Configurations for this run are "inheritance1.conf". To override this, use -Djdo.tck.cfglist=xxx
on the maven command line.
    [echo] Databases for this run are "derby". To override this, use -Djdo.tck.dblist=xxx
on the maven command line.
    [echo] Identity types for this run are "applicationidentity". To override this, use -Djdo.tck.identitytypes=xxx
on the maven command line.
-------------------------------------------------------------------------------------------------------------------------------
Then i run it again "notice the [ ] brackets arond the inheritance1.conf, derby and applicationidentity.conf
in the [echo] of the setProps goal

jdo2-tck 2.0-SNAPSHOT > [runtck.jdori]
runtck.jdori


setProps:
    [echo] setProps:
    [echo] Configurations for this run are "[inheritance1.conf]". To override this, use -Djdo.tck.cfglist=xxx
on the maven command line.
    [echo] Databases for this run are "[derby]". To override this, use -Djdo.tck.dblist=xxx
on the maven command line.
    [echo] Identity types for this run are "[applicationidentity]". To override this, use
-Djdo.tck.identitytypes=xxx on the maven command line.
-----------------------------------------------------------------------------------------------------------------------------------
If i run it again, this time notice [[  ]] around inheritance1.conf, derby and applicationidentity.conf
in the [echo] of the setProps goal.

jdo2-tck 2.0-SNAPSHOT > [runtck.jdori]
runtck.jdori


setProps:
    [echo] setProps:
    [echo] Configurations for this run are "[[inheritance1.conf]]". To override this, use
-Djdo.tck.cfglist=xxx on the maven command line.
    [echo] Databases for this run are "[[derby]]". To override this, use -Djdo.tck.dblist=xxx
on the maven command line.
    [echo] Identity types for this run are "[[applicationidentity]]". To override this, use
-Djdo.tck.identitytypes=xxx on the maven command line.


THE RESULT OF THE ABOVE IS THAT THE enhance.prepare goal fails with the following message:

enhance.prepare:
    [mkdir] Created dir: /home/karan/Projects/jdo/trunk/tck20/target/enhanced/jdori/[[applicationidentity]]
org.apache.commons.jelly.JellyTagException: /home/karan/Projects/jdo/trunk/tck20/maven.xml:414:71:
<copy> /home/karan/Projects/jdo/trunk/tck20/test/jdo/[[applicationidentity]] not found.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message