Hi Ahmed,
Twist is a standalone product that is an IDE that provides refactoring and editing capabilities for scenarios. We do not have plans to use junit infrastructure to bootstrap and run scenarios within other IDEs.
We may look at providing support for junit executions, and other IDEs in the future if more customers ask for this feature.
The test execution from with ant does provide junit compatible XML output for CI tools to figure out test failures.
-- Ketan
Tim,
Is there some way to associate and persist a card/task query with a Mingle Repo so that I can open a list of Mingle tasks without having to copy the query into that query dialog each time?
Just run an update from the update manager to pull a new version :)
-- Ketan
Tim,
The link comes from the twist documentation, which happens to be a product based on eclipse, so the steps would be similar.
Update: I've modified the post to reflect the instructions for installing and using the plugin.
Cheers!
-- Ketan
Tim,
The Open Repo Task screen will not help in this case. You need to create a query that allows you to pull cards/tasks from mingle. The instructions for doing so are available here.
Regarding "full" integration between mingle and twist -- the task page in minglyn provides a full browser view of the mingle card which should suffice for most purposes.
Let us know what specific feature you're looking for and we'll be happy to look into it.
-- Ketan
Hi Tim,
Can you provide screenshots of the repository configuration dialog, and information on the version of mingle you are using ?
-- Ketan
Hi Tim,
Creating a new card(or modifying an existing one) is not currently supported. The mingle integration is one-way and minglyn only knows to pull cards from mingle.
We'll be glad to provide more features as an when there's a few people asking for something.
-- Ketan
It might be worth including this information in your docs.
Aye, Aye :)
-- Ketan
Hi James,
The .metadata folder contains a lot of information that is specific to a particular machine -- folder names, caches, preferences, local history, et.al.
You should not check in the WORKSPACE/.metadata files, you can preferably add that to your version controls' ignore files. You can check in all your projects into source control. You should ignore WORKSPACE/PROJECT_NAME/bin which contains the generated class files -- most eclipse CVS/SVN plugins do this by default.
A nice way for your team to share a project is team-project-sets. You can export the information needed for the team to checkout the projects using File>Export>Team Project Set. The rest of the team imports this using File>Import>Team Project Set, and eclipse will checkout whatever projects were exported in the project set. More about it on the eclipse help site.
-- Ketan
Hi Ramin,
Thanks for reporting this issue.
The update site works only with eclipse 3.4 nothing higher, we’re working on to resolve this issue. You’ll need to move to eclipse 3.4 until we resolve this issue.
—Ketan
Stuart,
Please uncheck the feature ‘Mylyn PDE Bridge’ in the update manager. Twist does not bundle PDE and therefore you may not need this particular dependency.
—Ketan
Great. Hope you enjoy using Twist!
—Ketan
Hi Ross,
Setting JAVA_HOME does not necessarily force eclipse (and therefore twist) to use the java installed there. Running “java -version” would probably reveal that you’re on a 1.4 jre/jdk.
I’d recommend adding the path to JAVA_HOME/bin to the front of your PATH environment variable (you should also expand JAVA_HOME since the windows may not know what JAVA_HOME is when it’s trying to evaluate PATH)
If everything else fails (there’s no reason to) as a workaround you may force twist to use a jdk of your choice. Edit the twist.ini in your twist installation folder to add the following two lines (be sure to back it up first):
-vm C:\path_to_JAVA_HOME\bin\javaw.exe -vmargs ... ...
Note that you’ll need to add the lines before the ‘-vmargs’ line
More on this here: http://wiki.eclipse.org/Eclipse.ini
—Ketan
Hi Rag,
Here’s what you can do to fix the error:
The documentation went a bit out of date, and it did not cover a new property ‘confDir’ for the ant task. Not setting this property caused the NullPointerException. Thanks for bringing this up and we’ll be fixing the documentation shortly.
—Ketan
Hi Stuart,
Thanks for pointing that out.
The generics in the java code confused the forums to think it is HTML code. I’ve updated my post above with the new java code.
—Ketan