Re: Build Challenges Continued...

Guys:

I found I had to key in MAVEN_REPO manually on Windows, but on *nix the
maven eclipse:generate-classpath defined it for me just fine. Also on
Windows it seems to ignore MAVEN_REPO at the environment level (which
might be why it doesn't go into Eclipse properly).

Also, if theres an error in the plugin.jelly, you need to do a
plugin:uninstall, then a plugin:install. If that still fails, you need
to actually delete the *keel*.jar in MAVEN_HOME/plugins, then do the
plugin:install again.

Makes debugging plugins a bit of a PITA. There's probably an easier way,
but the above works for now.

Mike


On Mon, 2005-02-07 at 13:34, Sasvata (Shash) Chatterjee wrote:
> Pete,
> 
> >Following the archives of the thread titled "Maven build help " I was able
> >to make all of the changes by hand that the Shash and Michael referenced.
> >(Apparently these have not yet been checked in). Also ran the extra maven
> >targets plugin install etc.
> >
> >Must not have done it right though, because am getting same jelly error
> >that Shash got before the changes discussed were made, I want that same
> >"woohoo" that Shash declared !
> >
> >Any chance you guys could check in the changes so I could try them out ?
> >
> >  
> >
> All of that stuff is at home, so I can't check.  But, the only change 
> was in plugin.jelly, and Mike checked that in.  But, remember to do a 
> "maven plugin:install" (or something like that), from the Keel maven 
> plugin directory.
> 
> >I have also started to go through and add the
> >maven.repo.remote=http://www.ibiblio.org/maven,http://www.keelframework.org/maven
> >line to the build.properties files. Should these be done to EVERY
> >build.properties?  Should I check them in once so done ?
> >
> >  
> >
> yes, I'd think so.
> 
> >Also this is more than bizarre, but is anyone else having problems with
> >eclipse actually seeing the MAVEN_REPO stuff ? I have done it and checked
> >it until my eyes turn red and can't find any booboos, and if I look in the
> >java perspective it can absolutely see all of the files in question. But
> >it still blows up on all of the variations of project clean that I can
> >think of trying, and in the Problems view it says "missing required
> >library MAVEN_REPO" etc - and then points to the EXACT path that is
> >perfectly correct and has the real dude in there... %^$#^%!
> >  
> >
> I ran into this too.  I think you can delete the MAVEN_REPO variable in 
> Eclipse's build path dialog, and re add it for it to see the changes.
> 
> Shash
> 
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com