They moved it. I must have the artifacts locally. I'll update the URL. If you search in Google, you'll find it otherwise I can send it in about a half hour. On Jan 7, 2014 4:25 AM, "Jérôme LELEU" <lel...@gmail.com> wrote:
> Hi, > > I tried to take a look at these libraries to see the licensing, but I > haven't been able to make the build complete. > > I have the following error: *Could not transfer artifact > com.atlassian.seraph:atlassian-seraph:pom:2.5.1 from/to atlassian > (http://repository.atlassian.com/maven2/ > <http://repository.atlassian.com/maven2/>): repository.atlassian.com > <http://repository.atlassian.com>: Nom ou service inconnu: Unknown host > repository.atlassian.com <http://repository.atlassian.com>*. > > It seems that this url does not respond anymore. I've seen the following > url: https://maven.atlassian.com/repository/public on the Atlassian's > wiki. > > Am I missing something ? > > Thanks. > Best regards, > Jérôme > > > > 2014/1/7 Scott Battaglia <scott.battag...@gmail.com> > >> So I actually had to go through all 165 things the NOTICE plugin could >> not figure out and exclude them or add them to the license list. I was >> able to successfully do that for 163 of them :-) >> >> Two remaining: >> <artifact> >> <groupId>com.atlassian.confluence</groupId> >> <artifactId>confluence</artifactId> >> <version>3.5</version> >> </artifact> >> <artifact> >> <groupId>com.atlassian.jira</groupId> >> <artifactId>jira-core</artifactId> >> <version>4.4</version> >> </artifact> >> >> These are provided scope but I'm required to relate them back to a >> license. Does anyone know what I should flag it as? Just a link to the >> JIRA/Confluence license page? >> >> For reference, here are the other licenses: >> https://source.jasig.org/licenses/license-mappings.xml >> >> >> >> On Tue, Dec 31, 2013 at 10:05 AM, Scott Battaglia < >> scott.battag...@gmail.com> wrote: >> >>> Just a note that I know people have been waiting on the release. We've >>> been playing some upgrade games with a combination of the Maven Notice >>> Plugin and the Jasig Parent POM file, discovering some incompatibilities. >>> I believe Misagh and I have worked them all out so I will upgrade the >>> parent POM to the latest Notice plugin tomorrow morning (probably won't get >>> to it today) and then push the CAS Client release tomorrow night. >>> >>> In theory, assuming everything goes according to plan, which as we can >>> see, hasn't happened so far :-) >>> >>> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> >> > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
