You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by "Robert A. Decker" <de...@robdecker.com> on 2014/05/05 09:30:44 UTC
can't do a clean build
I’m trying to do a fresh build (sync’d around 8:30am this morning) and getting:
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom
Which doesn’t exist:
http://maven-repository.com/artifact/org.eclipse/org.eclipse.osgi
more output pasted below.
Robert A. Decker
decker@robdecker.com
http://robdecker.com/about
[ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to collect dependencies at org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 -> org.eclipse.jdt:core:jar:3.3.0-v_771 -> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 -> org.eclipse.core:filesystem:jar:1.1.0-v20070606 -> org.eclipse:osgi:jar:v20080605-1900: Failed to read artifact descriptor for org.eclipse:osgi:jar:v20080605-1900: Could not transfer artifact org.eclipse:osgi:pom:v20080605-1900 from/to astra.internal (http://archiva.astracorp.com/repository/internal/): Failed to transfer file: http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom. Return code is: 500 , ReasonPhrase:Unable to fetch artifact resource.. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to collect dependencies at org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 -> org.eclipse.jdt:core:jar:3.3.0-v_771 -> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 -> org.eclipse.core:filesystem:jar:1.1.0-v20070606 -> org.eclipse:osgi:jar:v20080605-1900
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
Re: can't do a clean build
Posted by Carsten Ziegeler <cz...@apache.org>.
I didn't try a clean build, but as this worked at some point of time, it
seems something has changed somewhere.
Actually, our launchpad should point to 2.1.1-SNAPSHOT of commons compiler,
but I didn't do that as that one is in the contrib section and we first
need to move it to the bundles section
Carsten
2014-05-05 16:02 GMT+02:00 Robert A. Decker <de...@robdecker.com>:
> I sync’d again this afternoon and saw some files come down but I still
> cannot build. Is it just me?
>
> When I do a google search for:
> filetype:pom "osgi-v20080605-1900.pom”
> I get zero results.
>
> Instead, this exists:
> osgi-3.4.0-v20080605-1900.pom
>
> (has version number 3.4.0 in the filename)
>
> Is there a place I can look at sling’s nightly build record?a
>
>
> Robert A. Decker
> decker@robdecker.com
> http://robdecker.com/about
>
>
> On 05 May 2014, at 09:30, Robert A. Decker <de...@robdecker.com> wrote:
>
> > I’m trying to do a fresh build (sync’d around 8:30am this morning) and
> getting:
> >
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT
> > [INFO]
> ------------------------------------------------------------------------
> > Downloading:
> http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom
> >
> > Which doesn’t exist:
> > http://maven-repository.com/artifact/org.eclipse/org.eclipse.osgi
> >
> > more output pasted below.
> >
> >
> > Robert A. Decker
> > decker@robdecker.com
> > http://robdecker.com/about
> >
> > [ERROR] Failed to execute goal on project org.apache.sling.launchpad:
> Could not resolve dependencies for project
> org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to
> collect dependencies at
> org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 ->
> org.eclipse.jdt:core:jar:3.3.0-v_771 ->
> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 ->
> org.eclipse.core:filesystem:jar:1.1.0-v20070606 ->
> org.eclipse:osgi:jar:v20080605-1900: Failed to read artifact descriptor for
> org.eclipse:osgi:jar:v20080605-1900: Could not transfer artifact
> org.eclipse:osgi:pom:v20080605-1900 from/to astra.internal (
> http://archiva.astracorp.com/repository/internal/): Failed to transfer
> file:
> http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom.
> Return code is: 500 , ReasonPhrase:Unable to fetch artifact resource.. ->
> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal on project org.apache.sling.launchpad: Could not resolve
> dependencies for project
> org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to
> collect dependencies at
> org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 ->
> org.eclipse.jdt:core:jar:3.3.0-v_771 ->
> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 ->
> org.eclipse.core:filesystem:jar:1.1.0-v20070606 ->
> org.eclipse:osgi:jar:v20080605-1900
> > at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
>
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: can't do a clean build
Posted by "Robert A. Decker" <de...@robdecker.com>.
I sync’d again this afternoon and saw some files come down but I still cannot build. Is it just me?
When I do a google search for:
filetype:pom "osgi-v20080605-1900.pom”
I get zero results.
Instead, this exists:
osgi-3.4.0-v20080605-1900.pom
(has version number 3.4.0 in the filename)
Is there a place I can look at sling’s nightly build record?a
Robert A. Decker
decker@robdecker.com
http://robdecker.com/about
On 05 May 2014, at 09:30, Robert A. Decker <de...@robdecker.com> wrote:
> I’m trying to do a fresh build (sync’d around 8:30am this morning) and getting:
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom
>
> Which doesn’t exist:
> http://maven-repository.com/artifact/org.eclipse/org.eclipse.osgi
>
> more output pasted below.
>
>
> Robert A. Decker
> decker@robdecker.com
> http://robdecker.com/about
>
> [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to collect dependencies at org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 -> org.eclipse.jdt:core:jar:3.3.0-v_771 -> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 -> org.eclipse.core:filesystem:jar:1.1.0-v20070606 -> org.eclipse:osgi:jar:v20080605-1900: Failed to read artifact descriptor for org.eclipse:osgi:jar:v20080605-1900: Could not transfer artifact org.eclipse:osgi:pom:v20080605-1900 from/to astra.internal (http://archiva.astracorp.com/repository/internal/): Failed to transfer file: http://archiva.astracorp.com/repository/internal/org/eclipse/osgi/v20080605-1900/osgi-v20080605-1900.pom. Return code is: 500 , ReasonPhrase:Unable to fetch artifact resource.. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: Failed to collect dependencies at org.apache.sling:org.apache.sling.commons.compiler:jar:2.1.0 -> org.eclipse.jdt:core:jar:3.3.0-v_771 -> org.eclipse.core:resources:jar:3.2.1-R32x_v20060914 -> org.eclipse.core:filesystem:jar:1.1.0-v20070606 -> org.eclipse:osgi:jar:v20080605-1900
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)