You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by jbl <la...@tatrc.org> on 2001/07/24 19:27:47 UTC

build.sh w/o classic java compiler

I am running Solaris 8 on a Sun Ultra 2. 

I do not have the option to use the java classic compiler for the
jetspeed build. I tried the native option instead but with no luck.

Any suggestions?

THANX,
 JBL

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by Vincent Bonamy <vi...@geomath.fr>.
jbl wrote:

> >jbl wrote:
> >
> >> The target option I see are core or dist.
> >>
> >> I tried both and none.
> >>
> >> JBL
> >
> >So, you use the version 1.3a1 !
> >I spoke about the current CVS, i'm sorry.
> >A simple solution would be to download the war, isn't it?
>
> What would the war be worth w/o installing of Jetspeed?
>
> JBL
>

The war contains all jetspeed: it's like a jar file, you can deploy it
with the jar tool of java.
Instead the war contains the binary file of jetspeed.
war is auto-deploys when you put it in the directory webapps of tomcat
(for example).

vincent.



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by jbl <la...@tatrc.org>.
>jbl wrote:
>
>> The target option I see are core or dist.
>>
>> I tried both and none.
>>
>> JBL
>
>So, you use the version 1.3a1 !
>I spoke about the current CVS, i'm sorry.
>A simple solution would be to download the war, isn't it?


What would the war be worth w/o installing of Jetspeed?

JBL

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by Vincent Bonamy <vi...@geomath.fr>.
jbl wrote:

> The target option I see are core or dist.
>
> I tried both and none.
>
> JBL

So, you use the version 1.3a1 !
I spoke about the current CVS, i'm sorry.
A simple solution would be to download the war, isn't it?


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by jbl <la...@tatrc.org>.
The target option I see are core or dist.

I tried both and none.

JBL

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by Vincent Bonamy <vi...@geomath.fr>.
jbl wrote:

> I did set JAVA_HOME and everything else manually then ran java.
> The error is not generated from the shell script; it is from the
> build.xml
>
> JBL
>

Do you try to call the script build.sh with targets : war, jar or init ?
...


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by jbl <la...@tatrc.org>.
I did set JAVA_HOME and everything else manually then ran java.
The error is not generated from the shell script; it is from the
build.xml

JBL

>jbl wrote:
>
>> I did not have a tick on the line in the call to the shell script.
>> I get the error now even after trying to build it manually.
>>
>> JBL ?
>>
>
>The only line where there is a tick is when the script buid.sh specifies
>the JAVA_HOME.
>I advise you so to specifie manually JAVA_HOME  ( ie ~  "   setenv
>JAVA_HOME    $HOME/jdk   ")
>and run the script.
>
>vincent.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by Vincent Bonamy <vi...@geomath.fr>.
jbl wrote:

> I did not have a tick on the line in the call to the shell script.
> I get the error now even after trying to build it manually.
>
> JBL ?
>

The only line where there is a tick is when the script buid.sh specifies
the JAVA_HOME.
I advise you so to specifie manually JAVA_HOME  ( ie ~  "   setenv
JAVA_HOME    $HOME/jdk   ")
and run the script.

vincent.



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by jbl <la...@tatrc.org>.
I did not have a tick on the line in the call to the shell script.
I get the error now even after trying to build it manually.

JBL ?


> I found out that the JRE does not include classic option, but the full
> JDK does. So, I am past that hurdle, but the build.sh script bombs now
> with message:
>
> BUILD FAILED
>
> ' does not exist in this project
>
> What in the world does the single tick signify?
>
> THANX,
>  JBL
>

I think you wrote in your shell:
sh ./build.sh '
(the single tick is next to the Enter !)

you write
sh ./build.sh
and you obtain the jar file. (in directory bin)

you write
sh ./build.sh war
and you obtain the war (and the jar) file. (in directory bin)

and if problems keep, you can read the file build.sh.

vincent.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by Vincent Bonamy <vi...@geomath.fr>.

> I found out that the JRE does not include classic option, but the full
> JDK does. So, I am past that hurdle, but the build.sh script bombs now
> with message:
>
> BUILD FAILED
>
> ' does not exist in this project
>
> What in the world does the single tick signify?
>
> THANX,
>  JBL
>

I think you wrote in your shell:
sh ./build.sh '
(the single tick is next to the Enter !)

you write
sh ./build.sh
and you obtain the jar file. (in directory bin)

you write
sh ./build.sh war
and you obtain the war (and the jar) file. (in directory bin)

and if problems keep, you can read the file build.sh.

vincent.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: build.sh w/o classic java compiler

Posted by jbl <la...@tatrc.org>.
I found out that the JRE does not include classic option, but the full
JDK does. So, I am past that hurdle, but the build.sh script bombs now
with message:

BUILD FAILED

' does not exist in this project

What in the world does the single tick signify?

THANX,
 JBL

=================================================

I am running Solaris 8 on a Sun Ultra 2. 

I do not have the option to use the java classic compiler for the
jetspeed build. I tried the native option instead but with no luck.

Any suggestions?

THANX,
 JBL

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org