You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2009/11/26 14:49:39 UTC
[jira] Created: (INFRA-2352) Build artifacts not getting deployed
for Camel
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
Reporter: Jonathan Anstey
I recently added source jars to the Camel build in Hudson. To do this, I added a profile http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845561#action_12845561 ]
Jukka Zitting commented on INFRA-2352:
--------------------------------------
You may want to try configuring the Hudson build to use "mvn clean deploy" instead of "mvn clean install" and the "Deploy artifacts to Maven repository" option. I believe the Maven integration in Hudson is not able to capture all attached artifacts correctly in all cases, especially when the build uses profiles or other more complex Maven settings.
> 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796189#action_12796189 ]
Jonathan Anstey commented on INFRA-2352:
----------------------------------------
Seems I can't deploy to the Apache Nexus instance. Last time I tried to deploy anything manually we were still using people.apache.org :) Any pointers on how to get Nexus deploy karma?
> 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
> Reporter: Jonathan Anstey
>
> I recently added source jars to the Camel build in Hudson. To do this, I added a profile http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Updated: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated INFRA-2352:
-------------------------
Component/s: Nexus
Add Nexus component, Brian Fox should be contacted about the Nexus question.
> 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
>
> I recently added source jars to the Camel build in Hudson. To do this, I added a profile http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836610#action_12836610 ]
Jonathan Anstey commented on INFRA-2352:
----------------------------------------
Hmmm... still not working for me. I kicked off a redeploy via Hudson and it still only deployed the original 2 artifacts, not the new -sources artifact.
3 jar artifacts from the build:
http://hudson.zones.apache.org/hudson/job/Camel/org.apache.camel$camel-core/661/artifact/org.apache.camel/camel-core/2.3-SNAPSHOT/
Hudson redeploy log only shows 2 artifacts:
http://hudson.zones.apache.org/hudson/job/Camel/org.apache.camel$camel-core/661/redeploy/1/
Wondering now if this is a Hudson issue? If this was an Nexus access issue I would think that it would show it the redeploy log that it tried to deploy the -sources artifact but failed?
> 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853144#action_12853144 ]
Jonathan Anstey commented on INFRA-2352:
----------------------------------------
Totally missed this last comment. Thanks, will try that out and see if it fixes our problem.
> 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836477#action_12836477 ]
Brian Fox commented on INFRA-2352:
----------------------------------
Likely this was caused because of a disconnect between the project as imported and as authorized in Nexus. Now that r.a.o is using Ldap, it should be fully synced. Can you let me know if this is still an issue?
> 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
>
> I recently added source jars to the Camel build in Hudson. To do this, I added a profile http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Commented: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795758#action_12795758 ]
Jason van Zyl commented on INFRA-2352:
--------------------------------------
Have you tried this yourself from the command line to try and isolate whether it's a Maven, Hudson or Nexus thing? If you can do this from the command line then that rules out Maven and 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
> Reporter: Jonathan Anstey
>
> I recently added source jars to the Camel build in Hudson. To do this, I added a profile http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
[jira] Closed: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-2352.
----------------------------
Resolution: Fixed
> 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (INFRA-2352) Build artifacts not getting deployed
for Camel
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reassigned INFRA-2352:
--------------------------------
Assignee: Brian Fox
> 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 http://svn.apache.org/viewvc/camel/trunk/pom.xml?r1=882039&r2=884081&pathrev=884081 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.