Well, maybe I missed an email. But such changes need more
advertisement, or maybe an udpated README in the bootstrap directory
if the committer KNOWS there is going to be an issue.
But why should I use "-d"? That's for updating subdirectories. And
it apparently didn't update anything over what I have already done (3
times):
MB:/gf-trunk/build/glassfish/bootstrap lloyd$ cvs update -dP
cvs server: Updating .
cvs server: Updating legal
cvs server: Updating make
cvs server: Updating maven-glassfish-plugin
cvs server: Updating maven-glassfish-plugin/src
cvs server: Updating maven-glassfish-plugin/src/main
cvs server: Updating maven-glassfish-plugin/src/main/java
cvs server: Updating maven-glassfish-plugin/src/main/java/com
cvs server: Updating maven-glassfish-plugin/src/main/java/com/sun
cvs server: Updating maven-glassfish-plugin/src/main/java/com/sun/
enterprise
cvs server: Updating maven-glassfish-plugin/src/main/java/com/sun/
enterprise/build
cvs server: Updating maven-glassfish-plugin/src/main/java/org
cvs server: Updating maven-glassfish-plugin/src/main/java/org/apache
cvs server: Updating maven-glassfish-plugin/src/main/java/org/apache/
maven
cvs server: Updating maven-glassfish-plugin/src/main/java/org/apache/
maven/scm
cvs server: Updating maven-glassfish-plugin/src/main/java/org/apache/
maven/scm/plugin
cvs server: Updating maven-glassfish-plugin/src/test
cvs server: Updating maven-glassfish-plugin/src/test/java
cvs server: Updating maven-glassfish-plugin/src/test/java/com
cvs server: Updating maven-glassfish-plugin/src/test/java/com/sun
cvs server: Updating maven-glassfish-plugin/src/test/java/com/sun/
enterprise
cvs server: Updating maven-glassfish-plugin/src/test/java/com/sun/
enterprise/build
cvs server: Updating package
Lloyd
On Nov 9, 2006, at 9:07 AM, Anissa Lam wrote:
> Dinesh Patil wrote:
>> Build is not broken.. you will have to update bootstrap module and
>> try from clean state..
> 'cd glassfish/bootstrap; maven checkout bootstrap-all build' is
> NOT giving a REAL up-to-date copy of ALL the jars/files should
> really be addressed. There are so many times when one forget to
> do 'cvs update -d' in the bootstrap directory itself and ends up
> with out-of-sync situation.
> Is it really impossible for the bootstrap-all command to update the
> bootstrap directory itself ?
>>
>> Hudson builds are failing in 4 Admin GUI tests though, after some
>> changes in admin-gui yesterday..
> We haven't changed anything relating to the current version of
> Admin GUI for quite some times. Senthil will take a look though.
>
> thanks
> Anissa.
>
>> See the console log here.
>> http://glassfishbuildtools.sun.com:8000/hudson/job/glassfish/build/
>> 2006-11-08_12-08-19/changes#detail12
>>
>> thanks
>> Dinesh
>>
>> Lloyd L Chambers wrote:
>>
>>> Anyone know what might be wrong? I did a 'cvs update' on
>>> 'bootstrap' first.
>>>
>>> MB:/gf-trunk/build/glassfish/bootstrap lloyd$ maven clean; maven
>>> clobber; maven bootstrap all; maven checkout; maven build
>>>
>>>
>>> [java] compile-web:
>>> [java] [echo] Compiling com/sun/enterprise/web/**
>>> [java]
>>> [java] compile-loader:
>>> [java] [echo] Compiling com/sun/enterprise/loader
>>> [java]
>>> [java] compile-server:
>>> [java] [echo] Compiling com/sun/ejb, com/sun/ejb
>>> [java] [javac] Compiling 1 source file to /gf-trunk/
>>> build/ glassfish/appserv-core/build
>>> [java] [echo] Compiling com/sun/web, com/sun/jndi, com/
>>> sun/ enterprise
>>> [java] [javac] Compiling 20 source files to /gf-trunk/
>>> build/ glassfish/appserv-core/build
>>> [java] [javac] /gf-trunk/build/glassfish/appserv-core/
>>> src/ java/com/sun/enterprise/naming/NamingManagerImpl.java:62:
>>> cannot find symbol
>>> [java] [javac] symbol : class ContainerResolver
>>> [java] [javac] location: package com.sun.xml.ws.api.server
>>> [java] [javac] import
>>> com.sun.xml.ws.api.server.ContainerResolver;
>>> [java] [javac] ^
>>> [java] [javac] /gf-trunk/build/glassfish/appserv-core/
>>> src/ java/com/sun/enterprise/webservice/WSContainerResolver.java:
>>> 27: cannot find symbol
>>> [java] [javac] symbol : class ContainerResolver
>>> [java] [javac] location: package com.sun.xml.ws.api.server
>>> [java] [javac] import
>>> com.sun.xml.ws.api.server.ContainerResolver;
>>> [java] [javac] ^
>>> [java] [javac] /gf-trunk/build/glassfish/appserv-core/
>>> src/ java/com/sun/enterprise/webservice/WSContainerResolver.java:
>>> 35: cannot find symbol
>>> [java] [javac] symbol: class ContainerResolver
>>> [java] [javac] public class WSContainerResolver extends
>>> ContainerResolver {
>>> [java] [javac] ^
>>> [java] [javac] /gf-trunk/build/glassfish/appserv-core/
>>> src/ java/com/sun/enterprise/naming/NamingManagerImpl.java:1054:
>>> cannot find symbol
>>> [java] [javac] symbol : variable ContainerResolver
>>> [java] [javac] location: class
>>> com.sun.enterprise.naming.NamingManagerImpl
>>> [java] [javac]
>>> ContainerResolver.setInstance(new WSContainerResolver(desc));
>>> [java] [javac] ^
>>> [java] [javac] Note: Some input files use or override a
>>> deprecated API.
>>> [java] [javac] Note: Recompile with -Xlint:deprecation
>>> for details.
>>> [java]
>>> [java] BUILD FAILED
>>> [java] [javac] Note: Some input files use unchecked or
>>> unsafe operations.
>>> [java] [javac] Note: Recompile with -Xlint:unchecked for
>>> details.
>>> [java] [javac] 4 errors
>>> [java] /gf-trunk/build/glassfish/appserv-core/compile.xml:
>>> 207: Compile failed; see the compiler error output for details.
>>> [java]
>>> [java] Total time: 5 seconds
>>> [java] [ERROR] Java Result: 1
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>