[ANN] Apache Archiva 2.2.3 Released
The Apache Archiva team is pleased to announce the release of Archiva 2.2.3. Archiva is available for download from the web site. Archiva is an application for managing one or more remote repositories, including administration, artifact handling, browsing and searching. If you have any questions, please consult: the web site: http://archiva.apache.org/ the archiva-user mailing list: http://archiva.apache.org/mail-lists.html Apache Archiva 2.2.3 is a bugs fix release. Compatibility Changes: This release contains new security features for the REST API. Depending on your hosting environment there may be additional configuration steps necessary. See the release notes for more information: http://archiva.apache.org/docs/2.2.3/release-notes.html Improvement [MRM-1925] - Make User-Agent header configurable for HTTP requests [MRM-1861], [MRM-1924] - Increasing timeouts for repository check [MRM-1937] - Prevent creating initial admin user with wrong name. Adding origin header validation checks for REST requests Bugs fixed [MRM-1859] - Error upon viewing 'Artifacts' tab when browsing an artifact [MRM-1874] - Login Dialog triggers multiple events (+messages) [MRM-1908] - Logged on users can write any repository [MRM-1909] - Remote repository check fails for https://repo.maven.apache.org/maven2 [MRM-1923] - Fixing bind issue with certain ldap servers, when user not found [MRM-1926] - Invalid checksum files in Archiva repository after download from remote repository [MRM-1928] - Bad redirect URL when using Archiva through HTTP reverse proxy [MRM-1933] - No message body writer has been found for class org.apache.archiva.rest.services.ArchivaRestError [MRM-1940] - Slashes appended to remote repo url Have fun! -- The Apache Archiva Team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency:analyze controversial result
activemq-all, as its name suggests, bundles third-party dependencies in its JAR (rather than declaring them as dependencies), and it happens to include slf4j: http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1 So I suppose, the first run finds slf4j classes in activemq-all so it marks the slf4j dependency as "unused declared". Do not ever use "uberjars" as dependencies, and report it upstream if it comes as a transitive dependency of a third party (and in the meantime, exclude the transitive dependency and add the proper non-uberjar dependencies instead). On Wed, May 17, 2017 at 10:14 AM Kristof Meixner < kristof.meix...@fatlenny.net> wrote: > Hi! > > Maybe I was too unclear about the specific problem. > > I've got a project that has org.slf4j:slf4j-api:1.7.12 as dependency as it > uses the Logger in the Java code. The > dependency is declared in POM but comes also as a transitive dependency. > > When running 'dependency:analyze' it is marked as 'unused declared'. When > I remove the dependency from the POM, and run > 'dependency:analyze' again it is marked as 'used undeclared'. Furthermore, > in the first case suddenly another dependency > [1] is marked as 'used undeclared' although it is never used directly. > > Best regards > Kristof > > [1] org.apache.activemq:activemq-all:5.11.1 > > On 05/16/2017 08:13 PM, Alexander Kriegisch wrote: > > Maybe because > > > > a) your project uses dependencies which were never declared explicitly > > in any of your POMs and > > b) at least some of your modules have dependencies declared which are > > not actually used in your code? > > > > What do you think? > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: dependency:analyze controversial result
Hi! Maybe I was too unclear about the specific problem. I've got a project that has org.slf4j:slf4j-api:1.7.12 as dependency as it uses the Logger in the Java code. The dependency is declared in POM but comes also as a transitive dependency. When running 'dependency:analyze' it is marked as 'unused declared'. When I remove the dependency from the POM, and run 'dependency:analyze' again it is marked as 'used undeclared'. Furthermore, in the first case suddenly another dependency [1] is marked as 'used undeclared' although it is never used directly. Best regards Kristof [1] org.apache.activemq:activemq-all:5.11.1 On 05/16/2017 08:13 PM, Alexander Kriegisch wrote: > Maybe because > > a) your project uses dependencies which were never declared explicitly > in any of your POMs and > b) at least some of your modules have dependencies declared which are > not actually used in your code? > > What do you think? > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
