Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (asf.osuosl.org: domain of karan.malhi@gmail.com designates
 64.233.162.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
        b=lJv3+oTpkXARIAqJHgJSF7z1rmFj0UdAM1a6zKvRXsfDyMK3ahCtNsPAo6uDHTh5tcv8IbVIMtkQy2+vju0KKGFI3HHYMkjYgN44kl3FlQ4pc9edSf/r+UYVGYXk+1vNo+Kn4rTiCJwtc+Z+Ni4hTZlC0yl2xTeCjaH3xylS/Wo=
Message-ID: <ac85de2505091713113739c098@mail.gmail.com>
Date: Sat, 17 Sep 2005 16:11:21 -0400
From: Karan Malhi <karan.malhi@gmail.com>
Reply-To: karan.malhi@gmail.com
To: jdo-dev@db.apache.org
Subject: maven console issue
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_19997_28288894.1126987881392"

------=_Part_19997_28288894.1126987881392
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

I have been able to fix the maven console issue to some extent. looks like=
=20
maven console is not very mature as it does not provide enough hooks to=20
write preGoals.

The only thing i have not been able to fix (and i would have to hack the=20
plugin.jelly file for the console plugin to fix it) is, when i have the=20
maven console running and now want to change the property to some other=20
value.=20

So if i start the console giving the following command:

maven -bo -Djdo.tck.cfglist=3Dinheritance1.conf -
Djdo.tck.identitytypes=3Dapplicationidentity console


and now i want to change a property when the console is running, so i give=
=20
the following command:

jdo.tck.cfglist=3Dinheritance2.conf

then maven console does not set this property in a separate goal , but it=
=20
does it in the "console" goal itself. Which means that if i wanted to trap=
=20
this event using a pre/post Goal, then i cant.

The only way i can think of doing it is to hack the plugin.jelly for maven=
=20
console plugin and extract the code setting the property into a separate=20
goal, but i dont know how open you are to doing something like this (dirty=
=20
solution in my opinion).

Second way to copy the plugin.jelly goals into our project.xml file (the on=
e=20
in the trunk folder) . Then it becomes very easy to change and modify it.=
=20
Again i am not sure if you guys are open to that .

Maven Gurus: can i get to a variable declared in the plugin.jelly file for =
a=20
plugin from the maven.xml file? if so, how? I am not sure if=20
context.getVariable('variableName') works in this case.


--=20
Karan Malhi

------=_Part_19997_28288894.1126987881392--