Alex Karasulu wrote:
Steve,
Unfortunately, I'm still having the same merlin plugin issues after blowing away all Avalon and merlin directories in the maven repository. My plugin seems crippled now. In terms of the merlin CLI bat file the problem where it cannot find the maven repository's paths still persists. Note once again the CLI run of the bat file does not show the same problem that the plugin was showing with the double repository/repository path components. It just does not see the ldapd-server artifact group directory.
OK - seems like we two seperate issues.
1. merlin cli repository handling 2. plugin status
If you would like fell free to contact me via MSN IM to troubleshoot the problem. Once again my user id is [EMAIL PROTECTED]
Sorry - don't have MSN IM.
Lets try and sort things here for now.
First off lets focus just on merlin cli and relative to the hello demo. I know you have already done some of this already, but can I get you do the following:
1. delete %MAVEN_HOME%/plugins/merlin* I.e. make sure you delete both the merlin-plugin-1.0 directory and the merlin-plugin-1.0.jar file. Unfortunately multi-version plugins in Maven are not supported so we have to patch things manually. 2. delete %MAVEN_HOME%/repository/avalon-* directories 3. delete %MAVEN_HOME%/repository/merlin directory 4. bring you merlin installation to a virgin RC3 5. go to the hello demo and do the following:
$ maven clean jar:install $ merlin target/classes -execute -info
6. post the results
After that we can start to look at repository stitching once we know that the basics are functioning correctly.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
