AndroMDA

Eclipse runner
--------------

         Key: AAAA-23
         URL: http://jira.andromda.org/browse/AAAA-23
     Project: AndroMDA 4
        Type: New Feature

  Components: Eclipse integration  
    Reporter: Matthias Bohlen
 Assigned to: Matthias Bohlen 
     Fix For: 4.0-M2


This web page
http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.

Steps:
0. Think about where to get that workflow description URL from.
1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.

Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12831 ] 

Peter Friese commented on AAAA-23:
----------------------------------

Considering the fact that the Eclipse runner has some dependencies to Eclipse itself, I am not sure if this approach is feasible. I'd rather go this way:
- Have Martin write the AndroMDAEngine
- package the AndroMDAEngine in a JAR file (with all other engine / core stuff)

- write an Eclipse plug-in which enables the user to start AndroMDA by clicking on a button or a context menu entry or whatever
- import the JAR file mentioned above into the Eclipse plug-in
- let the Eclipse plug-in call the AndroMDAEngine whcih resides in the JAR file

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Peter Friese
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12855 ] 

Matthias Bohlen commented on AAAA-23:
-------------------------------------

The jar file you suggested exists now. I have implemented integration/runners/common, the jar is called andromda-runners-common.jar.

Question: How do you "import" it into the Eclipse plugin? I hope, it is not necessary to add it to your plugin project in binary form? I always hate to commit binaries to a version control system.

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Peter Friese
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12856 ] 

Peter Friese commented on AAAA-23:
----------------------------------

In the latest snapshot of Android, I implemented a dynamic discovery mechanism for AndroMDA artifacts and other libraries. It works like this:
1) The user configures his Maven repo / AndroMDA install location
2) Android uses the DirectoryScanner from ANT to recursively scan for the libraries it needs. The trick is to use the ANT DirectoryScanner, since it supports pattern searching like in "**/andromda-j2ee-maven-cartridge-3.2-SNAPSHOT.jar"
3) Set up an URLClassloader with all discovered artifacts.
4) Use reflection (or MethodUtils) to invoke org.andromda.andromdapp.AndroMDApp.addConfiguration() and org.andromda.andromdapp.AndroMDApp.run().
5) Off you go :-)

I envisage using the same approach to embed the new common runner.

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Peter Friese
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12857 ] 

Matthias Bohlen commented on AAAA-23:
-------------------------------------

Phew, all kinds of magic things going on...

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Peter Friese
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12858 ] 

Peter Friese commented on AAAA-23:
----------------------------------

Well, when integrating something in Eclipse you basically have two options:
a) create a plug-in containing your binary code
b) dynamically discover your code

Option a) might be feasible if we can make sure that we can build our Eclipse plug-ins as a part of our Maven build loop. Thus, we wouldn't need to check-in our binaries.

However, I much more like option b) since it results in a stronger decoupling of the core and the GUI.

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Peter Friese
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=all ]

Thorsten Pohl reassigned AAAA-23:
---------------------------------

    Assign To: Thorsten Pohl  (was: Peter Friese)

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=all ]
     
Work on AAAA-23 started by Thorsten Pohl

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13910 ] 

Thorsten Pohl commented on AAAA-23:
-----------------------------------

I have started implementing a Launcher so that AndroMDA will be availible to run using the "run" and "run as..." actions inside eclipse. 
I think it would be intuitive, if you could right-click your workflow and run it as AndroMDA run.

I think, when the runner discovers the AndroMDA Core and the PlugIns, it will need to get all of their dependencies as well.

Question: How can we determine which jars to scan for? 
Is there a way to automatically create a List of the dependencies of the AndroMDA Core (maybe during it's build) and also for each Plug-In that is registered inside the Plug-In Registry?

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13911 ] 

Matthias Bohlen commented on AAAA-23:
-------------------------------------

Yes, this should be possible. Look at the contents of the maven/2/andromdapp/**/ClasspathWriter.java file in the source tree of AndroMDA 3. This is a class which generates an Eclipse .classpath file from a Maven build project with nested pom.xml files. It collects all the dependencies and writes them into the .classpath file. The ClasspathWriter class is part of the andromdapp plugin and is run when you type "mvn andromdapp:eclipse" on the command line. This short form of invocation works only if you have the following three lines in your $HOME/.m2/settings.xml file:
  <pluginGroups>
    <pluginGroup>org.andromda.maven.plugins</pluginGroup>
  </pluginGroups>

You could copy the code from ClasspathWriter.java and create a new Maven2 plugin (Mojo) which writes an XML dependency file that you can use when booting the Launcher. 

The only thing is that the user will also have to invoke this Mojo from his own build to make sure that his own cartridges and will be part of the list of dependencies, too. The advantage is that even transitive dependencies from other frameworks will be detected.

She must finally tell the Eclipse launcher plugin somehow where to find the dependency file. Should the Eclipse runner have a preference page for this or is there a better, more 'automatic' way (example: keep the dependency file always at the same place in the user's Eclipse project)?

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13920 ] 

Peter Friese commented on AAAA-23:
----------------------------------

I'd like to point out two things:

1) The user experience must be Eclipse-like. I like Thorsten idea of having a launcher that finally apperas in the "run..." dropdown menu. Tools like the WTP chose the same approach (.WAR files have a "run on server" context menu entry), so we are in good company.

2) Dependencies should be discovered dynamically / on the fly. I really do not like the idea of having an extra description file containing a list of dependencies. Things are likely to break this way.

Android will contain a bootstrapping module that makes sure Android will download all AndroMDA libraries to your favourite directory (can be either your local maven repo, your ANT lib dir or some other directory of your choice). See AND-11 for more info. 

Most people are using Maven in conjunction with AndroMDA, so we can be pretty sure that the local maven repo has all dependencies. Thus, the only thing we need to make sure is that we can discover all dependencies the way maven does.

If we do not want to end up re-implementing major parts of maven functionality for AndroMDA / Android, the only option will be to run maven in the background. Android already contains a maven runner.

(Maven is a great tool, but it imposes some very inconvenient restrictions on tool integrator. *Sigh*)

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13941 ] 

Matthias Bohlen commented on AAAA-23:
-------------------------------------

Peter, you said: "Thus, the only thing we need to make sure is that we can discover all dependencies the way maven does." That's exactly what I suggested above: Let's write a small Maven plugin that collects the dependency information which Maven already has in memory and spills this info out to an XML file, automatically. Then, let's read this file from within Eclipse, and we're done: the Eclipse runner plugin knows exactly which jars should be pulled onto the classpath.

If the small Maven plugin is part of each Maven build, I cannot see how the dependency information should ever become inconsistent because Maven always is the master.

The same XML file could be auto-generated from an Ant build, so regardless of the tool environment that people use, we always have exact dependency information.

Or did I miss anything?
Cheers,
Matthias


> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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

[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13950 ] 

Thorsten Pohl commented on AAAA-23:
-----------------------------------

I think that a combination of automatic dependency discovery and generated dependency description would serve us best on this issue.

If we can discover the needed jar's for a dependency in a directory of the user's choice, we would be able to run both in a maven repository environment and in a custom "repository" env.

I think, the dependency-list Matthias suggested should contain the following information: The dependency's name and version.

Then the runner can try to auto-discover the jars from a given base-directory. The ResourceResolver from Android should be able to do this job. But I think (as mentioned below) the dependency configuration should be customizable by the user so that additional libs can be incorporated and the paths of "undetectable" jars can be added.


About the handling of a runner:

I think it would be Eclipse-like, if the launch-configuration has the final control over which libraries are in the classpath for each individual run. This way the user can use different plugins with each configuration. I am thinking about something like the "classpath"-tab in the ant-launch-configuration of eclipse.

On the other hand an initial configuration should be provided, and maybe even customized using eclipse's preferences.

Do you have any additional ideas?

> Eclipse runner
> --------------
>
>          Key: AAAA-23
>          URL: http://jira.andromda.org/browse/AAAA-23
>      Project: AndroMDA 4
>         Type: New Feature

>   Components: Eclipse integration
>     Reporter: Matthias Bohlen
>     Assignee: Thorsten Pohl
>      Fix For: 4.0-M2

>
> This web page
> http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9
> shows a sequence diagram that describes how to start AndroMDA 4. The test case in technology/workflow-test also shows how to start a sample workflow. An Eclipse plugin should be developed that gets a URL property for the workflow definition file and runs AndroMDAEngine as shown on the sequence diagram.
> Steps:
> 0. Think about where to get that workflow description URL from.
> 1. Create the Eclipse plugin in the folder integration/runners/eclipse and put the classes into the package org.andromda.integration.eclipse.
> 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by Martin in AAAA-22.
> Pair with Martin because his Maven runner is very similar in nature.

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