> Jason van Zyl wrote > Just wondering if any users had any feedback? I'm interested > in seeing if we're moving toward something that people are > happy using. > > Any comments would be welcome. >
This release is fantastic and kudos to Eugene, Jason and everyone who worked on it. I've been working with a customer who is using maven 2 for the last year. It's been a long road, but we are cooking now. Corporate repository indexing has been a pain point and the nexus indexer is _huge_ for us. I thought the wiki mentioned class level indexing (is there a way to search at the class level? If not, if there was another option like a classname search from the Ctrl+H Search - it would very nice.) Something like jarclassfinder but searching repositories instead of file systems. http://www.alphaworks.ibm.com/tech/jarclassfinder Project from archetype is awesome as well, so too is the ability to generate or process resources. We are beginning to document our process with the new plugin and roll it out to the groups. This is a big step forward! Other thoughts, in case you're running out of feature ideas: We run RAD 7. This appears to use JST 1.1.1.x and WTP 1.1.1.x or 1.1.2.x fwiw. But the official WST is the com.ibm space at version 7.0.x. We still have pain with WTP. I've thought about trying to work something out with AJDT, but don't have the knowledge or time. That's probably the final big issue for us. (I really want my server launchers to work - at the moment I disable m2 depencies and copy things in and out of my ear or war lib) * A nice to have would be the ability to right click a group of jars (or other archive types) and be able to have a context menu to add and/or bulk add to local repo and better yet to the corporate repo. [install-file / deploy-file functionality for third party jars.] A number of use case variants here (sorry if these are fringe cases): 1) From an existing classpath container. Our server configurations have their own libraries/classpath containers. It would be nice to add the entire container to local (its important we can use our convention which is groupId=com.vendor.productline.subproduct artifactId=jarfileame [minus version if present], version=version of product release x.x.x.x . We ignore manifest versions etc. Even when it's a well known jar - like commons-* we still put it under the product coordinates in case it was modified and not renamed by the vendor. 2) From an existing (non-maven) project, it would be nice click a workspace artifact into the local or remote repository. Note; I don't want our users/devs to do this on maven projects. 3) From a file system search - I have a maven plugin that does something like this in 2 stages. The recon goal takes a path to grab every jar it finds in the subtree and pulls them into a directory - renames them and tries to make a pom for them. I review the poms. The deploy goal iterates the directory invokes deploy plugin (actually I think I cut and paste deploy plugin here since I don't think it was component`ized.) But, some ability to discover, review, and deploy/install large sets of third-party jars. * Looking forward to the dependency graph / tree view. * It would be nice to see a visual representation of the build. From validate to deploy as sort of a timeline showing what plugins are configured in the project. Perhaps even the ability to add plugins from this view. > We will try to publish a roadmap of features, and we'll > definitely be putting resources behind having schedule and > stable releases. > Thanks, > Jason Thank you again for this release and the great effort. Glad to see the Eclipse proposal as well. BR, -TR --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
