Skip to Content.
Sympa Menu

shibboleth-dev - Re: [Shib-Dev] Trying to setup subversion - 2.1.2 or 2.1.3

Subject: Shibboleth Developers

List archive

Re: [Shib-Dev] Trying to setup subversion - 2.1.2 or 2.1.3


Chronological Thread 
  • From: Joseph Valerio <>
  • To: "" <>
  • Subject: Re: [Shib-Dev] Trying to setup subversion - 2.1.2 or 2.1.3
  • Date: Tue, 07 Jul 2009 14:55:00 -0400

Chad,

1. vendor drop - http://svnbook.red-bean.com/en/1.1/ch07s05.html

I drop your code in a vendor section of my svn repo, copy it to my dev branch, make mods/hacks, build my release.  You cut a new release, I drop your new release locally, I merge our changes and cut a new release.  Standard open-source subversion.

2. Sorry, it was a branch.  The REL_2 branch's externals reference the idp version 2.1.3 , and common version 1.1.3.

From your instructions, "It is recommended that you use the java-idp-main repository, REL_2 branch, when building the Java IdP."

If you are going to suggest to people that the java-idp-main is what we should be using for building the idp, then you should provide a TAG with externals that references tagged version of the two components that went into creating each release.  You should also include  OpenSAML 2.2.4 in the externals if it is only available in subversion, so we can actually build the project.  I don't have the energy to argue the use of a final release version number in the POM while the code is still in a branch.  IMHO a very bad practice. 

Yeah, I could drop the 2.1.2 code, but the tests are all borked up.  I guess they reference test code in the commons tests that are not in the maven artifact.  Now I have to go and get the 1.1.2 commons source after having to look up the version number in the idp 2.1.2 pom.  You could deploy a test artifact with the test objects to maven and make it a test dependence in the idp allowing you to build and test the idp without having to build/test commons at the same time.

- Joe


Chad La Joie wrote:
First, I have no idea what you mean by "my vendor drop".

Second, pretty much everything you said about java-idp-main was wrong. 
There are no tags to it and its externals do not point to 2.1.3.  That 
project is simply a helper for checking out and building the latest code 
in the repository.  It's meant for those people who help us test and do 
frequent rebuilds of the code.

If you want a build of 2.1.2 then go out and download it.  If you want 
the binaries download them.  If you want the source then download that.

Joseph Valerio wrote:
  
Hi All,

I am trying to setup my vendor drop for Shib idp.  The java-idp-main 
REL_2 tag references java-idp 2.1.3 in the externals, while the 
currently supported release is 2.1.2.  Can you create an 2.1.2 tag in 
the idp-main that references the tagged versions that were used to build 
the 2.1.2 idp release, so that I can build from there.

Side note:  Even if I wanted to use the 2.1.3 release I can't build it 
because I can't get my hands on OpenSAML 2.2.4.  The maven repo only has 
2.2.3, and the subversion repo does not have a tagged version for 2.2.4 
either.

Thanks,

- Joe

    

  


--
Joseph Valerio

Senior Systems Programmer

Yale University
Technology & Planning
Information Technology Services

phone: 203-432-1196
email:
smail: 25 Science Park, New Haven, CT 06511



Archive powered by MHonArc 2.6.16.

Top of Page