www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2352) Build artifacts not getting deployed for Camel
Date Mon, 15 Mar 2010 20:29:27 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845507#action_12845507

Brian Fox commented on INFRA-2352:

Nexus doesn't control what Hudson deploys, so this sounds like a hudson problem. If _any_
of these camel artifacts are able to be deployed, they all should be allowed by Nexus.

> Build artifacts not getting deployed for Camel
> ----------------------------------------------
>                 Key: INFRA-2352
>                 URL: https://issues.apache.org/jira/browse/INFRA-2352
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Hudson, Nexus
>            Reporter: Jonathan Anstey
>            Assignee: Brian Fox
> I recently added source jars to the Camel build in Hudson. To do this, I added a profile
and then added -Psource-jar to the Maven options in the Camel build config http://hudson.zones.apache.org/hudson/job/Camel
> So now Hudson reports the new build artifacts are generated. Looking at the camel-core
module for instance, Hudson reports these artifacts:
>     * pom.xml [fingerprint]
>     * camel-core-2.1-SNAPSHOT-tests.jar [fingerprint]
>     * camel-core-2.1-SNAPSHOT-sources.jar [fingerprint]
>     * camel-core-2.1-SNAPSHOT.jar [fingerprint]
> So I thought that the camel-core-2.1-SNAPSHOT-sources.jar file would be deployed like
the rest. Not so. Looking at https://repository.apache.org/content/repositories/snapshots/org/apache/camel/camel-core/2.1-SNAPSHOT/
only the other build artifacts are deployed... does anyone know what could be happening here?
Or should I try and contact the Hudson team about this?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message