[Building Sakai] Can you build trunk now ?

Aaron Zeckoski azeckoski at unicon.net
Mon Nov 19 07:21:40 PST 2012


I can take care of this if someone wants to create the JIRA and assign it to me.
-AZ


On Mon, Nov 19, 2012 at 10:09 AM, Jean-Francois Leveque
<jean-francois.leveque at upmc.fr> wrote:
> After checking
> kernel/component-manager/src/test/java/org/sakaiproject/util/Compiler.java's
> code it seems to me the best solution is to remove it.
>
> I'm afraid I cannot do it myself because I'm not a Kernel Team member.
> Removing this file is easy and providing a patch for this would be
> ridiculous.
>
> Could someone in the Kernel Team take this low hanging fruit and deal
> with it from JIRA creation to closing the issue after removing the file
> and doing merges for 2.8 and 2.9?
>
> J-F
>
> On 28/09/2012 16:51, Matthew Jones wrote:
>> I don't think it's been decided that it's mandatory, but it goes EOL in
>> November, 2012. It the vendor is still being reported as Sun, and
>> they're no longer packaging the tools.jar (it was a local jar) then that
>> component manager would need to be cleaned up. It would not be testable
>> or a problem with newer versions of Java though.
>>
>> It's only used by a test case, so you could.
>> 1) Use Java 7
>> 2) Skip tests when building kernel
>> 3) Someone can fix whatever the Compiler.java test in component-manager
>> was doing, or just remove it since it doesn't work anymore anyway.
>>
>> On Fri, Sep 28, 2012 at 10:46 AM, Jean-Francois Leveque
>> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque at upmc.fr>>
>> wrote:
>>
>>     https://confluence. sakaiproject.org/display/BOOT/
>>     Development+Environment+Setup+ Walkthrough
>>     <https://confluence.sakaiproject.org/display/BOOT/Development+Environment+Setup+Walkthrough>
>>
>>     Has mixed Java 1.6 and 1.7.
>>
>>     Is Java 1.7 mandatory for trunk?
>>
>>     J-F
>>
>>
>>     On 28/09/2012 16:19, Matthew Jones wrote:
>>
>>         I'm not sure what this is used for .  . . But this looks like
>>         something
>>         activated if the java vendor is "Sun Microsystems Inc". Which
>>         shouldn't
>>         come up anyone,
>>
>>         <profile>
>>         <id>sakai-sun</id>
>>         <activation>
>>         <property>
>>         <name>java.vendor</name>
>>         <value>Sun Microsystems Inc.</value>
>>         </property>
>>         </activation>
>>
>>         On mine it says
>>         java.vendor=Oracle Corporation
>>
>>         Compile this program to see, maybe you're using the wrong java?
>>
>>         Save as file PropertiesTest.java, javac PropertiesTest.java, java
>>         PropertiesTest
>>         =-=-=-=-=-=-=
>>         import java.io.FileInputStream; import java.util.Properties; public
>>         class PropertiesTest {public static void main(String[] args) throws
>>         Exception {System.getProperties().list( System.out);}}
>>
>>         On Fri, Sep 28, 2012 at 7:09 AM, Jean-Francois Leveque
>>         <jean-francois.leveque at upmc.fr
>>         <mailto:jean-francois.leveque at upmc.fr>
>>         <mailto:jean-francois.leveque@ upmc.fr
>>         <mailto:jean-francois.leveque at upmc.fr>>>
>>
>>         wrote:
>>
>>              I haven't built trunk for a long time.
>>
>>              I'm still having a failure with "Sakai Component Manager".
>>
>>              Any hint how to solve the following?
>>
>>              J-F
>>
>>              Missing:
>>              ----------
>>              1) com.sun:tools:jar:1.5.0
>>
>>                  Try downloading the file manually from the project website.
>>
>>                  Then, install it using the command:
>>                      mvn install:install-file -DgroupId=com.sun
>>         -DartifactId=tools
>>              -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
>>
>>                  Alternatively, if you host your own repository you can
>>         deploy the
>>              file there:
>>                      mvn deploy:deploy-file -DgroupId=com.sun
>>         -DartifactId=tools
>>              -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
>>         -Durl=[url]
>>              -DrepositoryId=[id]
>>
>>                  Path to dependency:
>>                        1)
>>              org.sakaiproject.kernel:sakai- component-manager:jar:1.4.0-
>>         SNAPSHOT
>>                        2) com.sun:tools:jar:1.5.0
>>
>>              ----------
>>              1 required artifact is missing.
>>
>>              for artifact:
>>                  org.sakaiproject.kernel:sakai-
>>         component-manager:jar:1.4.0- SNAPSHOT
>>
>>              from the specified remote repositories:
>>                  default (http://repo1.maven.org/maven2 ),
>>                  central (http://repo1.maven.org/maven2 ),
>>                  sakai-maven (http://source.sakaiproject. org/maven2
>>         <http://source.sakaiproject.org/maven2>),
>>                  sonatype-nexus-snapshots
>>              (https://oss.sonatype.org/ content/repositories/snapshots
>>         <https://oss.sonatype.org/content/repositories/snapshots> )
>>
>>
>>              On 27/09/2012 15:02, David Horwitz wrote:
>>          > Could there be a problem  with the Sakai maven repo?
>>          >
>>          >
>>              Downloading:http://source. sakaiproject.org/maven2/org/
>>         simpleframework/simple-xml/2. 3.5/simple-xml-2.3.5.jar
>>         <http://source.sakaiproject.org/maven2/org/simpleframework/simple-xml/2.3.5/simple-xml-2.3.5.jar>
>>          > [WARNING] Unable to get
>>              resource'org.azeckoski: reflectutils:jar:0.9.14'  from
>>         repository
>>              sakai-maven (http://source.sakaiproject. org/maven2
>>         <http://source.sakaiproject.org/maven2>): GET request of:
>>              org/azeckoski/reflectutils/0. 9.14/reflectutils-0.9.14.jar from
>>              sakai-maven failed
>>          >
>>          > D
>>          >
>>          >
>>          > On 09/27/2012 02:58 PM, Jean-Francois Leveque wrote:
>>          >> Hi all,
>>          >>
>>          >> A build did not work on my local trunk test server.
>>          >>
>>          >> Nightly's trunk build seems to have failed too.
>>          >>
>>          >> I cannot find builds onhttp://builds.sakaiproject. org:8080/
>>         <http://builds.sakaiproject.org:8080/>
>>         <http://builds.sakaiproject. org:8080/
>>         <http://builds.sakaiproject.org:8080/>>.
>>
>>          >>
>>          >> Am I missing something?
>>          >>
>>          >> Cheers,
>>          >>
>>          >> J-F
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile


More information about the sakai-dev mailing list