[MGNLUI-1908] org.vaadin.addons:icepush:jar:0.5.3 not provided by magnolia nexus Created: 12/Aug/13  Updated: 06/Apr/16  Resolved: 30/Sep/13

Status: Closed
Project: Magnolia UI
Component/s: app framework
Affects Version/s: 5.0.1
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Christian Ringele Assignee: Magnolia International
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to ARCH-22 Archetype should hint at using the va... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: 5.1 - Final

 Description   

Creating a new local maven repo (Enterprise) following these instructions:
http://documentation.magnolia-cms.com/display/DOCS/Maven+init

Building the ui project produces this error:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.vaadin.addons:icepush:jar:0.5.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.vaadin.addons -DartifactId=icepush -Dversion=0.5.3 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.vaadin.addons -DartifactId=icepush -Dversion=0.5.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) info.magnolia.ui:magnolia-ui-vaadin-integration:jar:5.0.1
2) org.vaadin.addons:icepush:jar:0.5.3

----------
1 required artifact is missing.

for artifact:
info.magnolia.ui:magnolia-ui-vaadin-integration:jar:5.0.1

from the specified remote repositories:
central (http://repo1.maven.org/maven2),
magnolia.nexus.enterprise (http://nexus.magnolia-cms.com/content/groups/enterprise/)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch



 Comments   
Comment by Christian Ringele [ 12/Aug/13 ]

After installing icepush manually, next jars missing:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.vaadin.addons:cssinject:jar:2.0.3
[...]
2) org.vaadin.addons:gwt-graphics:jar:1.0.0
[...]
3) org.vaadin.addons:ckeditor-wrapper-for-vaadin:jar:7.8.3

Comment by Christian Ringele [ 12/Aug/13 ]

Of course you can solve it by adding the repo to the settings.xml.
But I think over this a lot of Maven un-experianced developers will stumble over.
A big goal of new Magnolia is to lower the entry barriers.

Why don't we proxy this repo by our nexus?

Comment by Magnolia International [ 13/Aug/13 ]

We do proxy it, but only in our internal mirror, for staff.
We will not proxy it in our public repos, but that would pollute our repos, and because that would prevent from properly mirroring our repos in the future.
We could maybe add it to the groups (as opposed to the repo themselves), but I'm not in favor of doing that either. Would drive too much unnecessary traffic to our repos.
Instead, what we can do:

  • Add that repo to the archetype. This will help folks creating a new project. This we can do right away. See ARCH-22.
  • Add that repo to magnolia_ui's pom: this will help folks building magnolia_ui. Before doing this though, we need to validate the impact on dependencies, with both Maven 2.2.1 and 3.1. I've had the feeling in the past, that sometimes transitive dependencies were looked up in the repositories defined in the dependency's pom. This might be a good thing, but might also have unwanted side-effects.

Keep in mind that adding a <repository> to settings.xml means that the given repo will be checked for every single dependency for any project you build - and most developers outside our team don't work full time on Magnolia-based projects

The really ideal solution would be that Vaadin mirrors their add-ons repository on Maven Central like they do with the main artifacts ...

Comment by Michael Nandris [ 18/Sep/13 ]

Yeah I get the an error for all 6 vaadin jars listed below.

mvn clean install
...
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
...

I am using the recommended maven 2.2.1

org.vaadin.addons:icepush:jar:0.5.3
org.vaadin.addon:easyuploads:jar:7.0.0
org.vaadin.addons:cssinject:jar:2.0.3
org.vaadin.addons:gwt-graphics:jar:1.0.0
org.vaadin.addons:ckeditor-wrapper-for-vaadin:jar:7.8.3
org.vaadin.addons:refresher:jar:1.2.1.7

Comment by Magnolia International [ 30/Sep/13 ]

Won't fix. Projects should declare their own usage of the vaadin.addons repo. The latest versions of the archetypes actually do that too.
(Magnolia-internal projects are not affected, since vaadin.addons is mirrored by our Nexus)

Generated at Mon Feb 12 08:51:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.