Re: Build Challenges Continued...

"Pete Carapetyan" <pete-FuitFV/z38NHGIDo6mWpe1aTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.java.keel.devel
Message-ID <[email protected]>
> 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.

I did not find it, so was going to check it in, but the one that I have
that I changed to make things work appears to be a generated file or
something because when I synched first to commit there was no such
existing file to commit.

Doing a find in eclipse for plugin.jelly it was only one of two that I
found, and the other was different anyway...

So whatever is supposed to happen with this still is not done, FYI

>But, remember to do a
> "maven plugin:install" (or something like that), from the Keel maven
> plugin directory.

Yes, specifically that is from keel-build\maven-plugins\keel in case
anyone got confused like me and tried to go to tool-maven a few times.
Doesn't work.

>
>>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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.