Hi, just in case this note falls through the cracks (I know *I* don't always
read the JIRA mail that gets piped to dspace-devel), I wanted to make clear
that Mark and I would like for us all to discuss the possibility of utilizing
the Maven Enforcer Plugin [1] to define some rules so we don't end up with a
similar situation to DS-1971 down the road. Ideally we can articulate a policy
of disallowing transitive dependencies on SNAPSHOTs, which we can still chose
to disable when building DSpace on our own, but will run by default and also
run explicitly during the Bamboo/Travis CI builds.
This is not something the absolutely *has* to be run be default, if there is
strong opposition to it in the community, I'll probably look into setting up
the enforcer plugin locally for myself.
--Hardy
[1] http://maven.apache.org/enforcer/maven-enforcer-plugin/
________________________________
From: Mark H. Wood (DuraSpace JIRA) [no-re...@duraspace.org]
Sent: Tuesday, April 15, 2014 2:33 PM
To: dspace-devel@lists.sourceforge.net
Subject: [Dspace-devel] [DuraSpace JIRA] (DS-1971) 'bte-io' (v 0.9.2.3)
dependency from EKT has an invalid SNAPSHOT dependency in its POM
[https://jira.duraspace.org/secure/useravatar?ownerId=mwood&avatarId=10570]
Mark H. Wood<https://jira.duraspace.org/secure/ViewProfile.jspa?name=mwood>
commented on an issue
Re: 'bte-io' (v 0.9.2.3) dependency from EKT has an invalid SNAPSHOT dependency
in its POM<https://jira.duraspace.org/browse/DS-1971>
>From #dspace, 15-Apr-2014
(14:25:24) hpottinger: Kevin Clarke points out to me (in another channel) that
the Maven Enforcer plugin can be set up to prevent you from ever making
dependencies on snapshots
(14:33:34) mhwood: "This rule checks that the current project is not a
snapshot." Not quite what we want?
(14:36:01) mhwood: Or was that bannedDependencies, excluding *:*:*-SNAPSHOT?
But we'd have to turn the rule off during development....
(14:36:35) mhwood: I guess we could include org.dspace:dspace*:*-SNAPSHOT.
(15:21:49) hpottinger: mhwood: thoughts about putting enforcer to use? perhaps
a disabled by default config, which Bamboo and Travis CI can make use of?
(15:23:39) mhwood: What exactly do we want to enforce? We could forbid any
-SNAPSHOT artifacts *other* than our own, for example, with an exclude/include
setup.
(15:23:50) mhwood: We might not need to disable that one.
(15:24:59) mhwood: I'm not sure I want the CIs to surprise us with rule
failures that I don't see locally.
(15:25:28) hpottinger: that's pretty much what happened today :-)
(15:26:34) mhwood: Exactly. If we'd had the inclusion/exclusion patterns I
suggested above, we'd have seen this coming.
[Add Comment] <https://jira.duraspace.org/browse/DS-1971#add-comment> Add
Comment<https://jira.duraspace.org/browse/DS-1971#add-comment>
DSpace<https://jira.duraspace.org/browse/DS> / [Bug]
<https://jira.duraspace.org/browse/DS-1971>
DS-1971<https://jira.duraspace.org/browse/DS-1971>
'bte-io' (v 0.9.2.3) dependency from EKT has an invalid SNAPSHOT dependency in
its POM<https://jira.duraspace.org/browse/DS-1971>
For the Biblio Transformation Engine (BTE), DSpace includes dependencies on
'bte-io' and 'bte-core' versions 0.9.2.3 in it's main POM:
https://github.com/DSpace/DSpace/blob/master/dspace-api/pom.xml#L439
Unfortunately, it seems that 'bte-core' version 0.9.2.3 itself has a dependency
on 'bte-core' version 0.9.2.3-SNAPSHOT in its POM in Maven Central:...
This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d)
[Atlassian logo]
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
