This project is read-only.

Project Importer Form

May 18, 2009 at 5:09 PM

I was thinking about the project importer form and ways to keep it clean as things are possibly added to it.

I think that having the form tabbed with one tab for required info to get the basic pom and an Advanced tab when optional items such as the scm, and version feilds could be kept.  I think this will keep it looking clean and the users that don't want to deal with the scm tag, version and so on won't have to see it.

What do you think?

May 19, 2009 at 3:49 AM

What IF...

We removed the Generate Pom Window.

Once the solution is loaded AND the NPanday AddIn is Activated we check if there is an existing pom.xml file. if not we ask the user if he wants to convert his project to a maven project. "Do you want your project to be a Maven Project?" then the textbox for the GroupId will popout if he clicks yes then the windo where they select the Test Project. but if its already has a pom, we ask him if he wants to sync his project (this question is not really neccessary just added it for discussion).

Any changes with project will be sync to the pom.xml. Except for the Property page of the Project (which we can't sync yet).

We Add a new Form. actually something like the Object Viewer in Visual Studio. where there is treeview in the right panel. But in the right is actually a Pom Viewer.This will be the page where the user can edit the pom of each of the project. he can update the pom.  Adding Parent tags, SCM tags, Build Tags, where he can see the plugins if we wants to. this is some what a window for advance NPanday user.